-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intent to start an open standards team #583
Comments
I'm interested |
Also nominating |
I’d love to be included. |
I'm interested |
I'm interested. |
I'd be interested, but have also raised my concerns in the past about independence as well as coordination. |
I am also very interested. |
I'd love to observe initially - in case that requires asking :) |
I'm in |
@bmeck as far as I'm concerned individuals who want to attend tc39 representing their company can and should continue to do so. This group should likely work on co-ordination and send 1 - 2 individuals per meeting to represent the interests of the project |
@MylesBorins that seems fine, but I'm more concerned with WHATWG where there isn't as clear a placement for a shared voice and my continued dealing with them. |
@bmeck seems like a great first agenda item 😄 |
@rubys is this something you'd be interested in participating in? |
Thanks, @MylesBorins. +1 for WhatWG I’d love to see W3C under this perview, so in addition to the specific agenda item of Node.js supporting Bradley’s effort in WhatWG, we could define scope around what bodies we want to engage with through this effort. |
I'm unsure. I don't really want to have to interact with the WhatWG (and I don't think we are or should be considered in "their domain" anyways), but may be willing to help with TC39 efforts. |
I'll spin up the repo soon and we can start talking about how we want to
structure the initiative.
My gut is that we can have an umbrella team to keep track of our overall
engagement and subteams to engage with specific bodies.
On Wed, Aug 15, 2018, 10:41 AM Jeremiah Senkpiel <notifications@github.com>
wrote:
I'm unsure. I don't really want to have to interact with the WhatWG (and I
don't think we are or should be considered in "their domain" anyways), but
may be willing to help with TC39 efforts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#583 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV8jJP4q3JligUt-4HfWacw1CwpVGks5uRDMsgaJpZM4V3eSr>
.
On Aug 15, 2018 10:41 AM, "Jeremiah Senkpiel" <notifications@github.com> wrote:
I'm unsure. I don't really want to have to interact with the WhatWG (and I
don't think we are or should be considered in "their domain" anyways), but
may be willing to help with TC39 efforts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#583 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV8jJP4q3JligUt-4HfWacw1CwpVGks5uRDMsgaJpZM4V3eSr>
.
|
I don't think that deciding what bodies we do, or do not, want to work with is the right starting place. If we want to work on JavaScript (for example on module support) then we need to work with ECMA. If we want to work on URLs (as that is a core node API), then we need to work with the WhatWG. Admittedly, HTML and DOM are gray areas, but that's mostly JSDOM's problem, and they seem to have made the right choice. I've worked with each group (and several others), and in many ways they are more different than they are alike. And in case it wasn't clear by my thumbs up to @mhdawson's question, I'm actively interested in helping. |
Agree that the focus should be more on the actual standards and APIs rather than the body that creates them. |
I'd be interested in helping out/observing out of personal interest ❤️ |
I'm happy to help out here wherever needed. cc @kenchris |
I am available to help too, so feel free to reach out if you need any help |
Thanks for the patience everyone... the group has been kicked off! |
Branching from #577
I think it is important for us to have consensus and co-ordination around our standards efforts.
I'd like to create a new repo that we can use to centralize the effort, I'd also like to nominate a few folks that I think would enjoy participating. Anyone else that we should include?
Nominating
@TimothyGu
@dshaw
@ladyleet
@jasnell
@bmeck
@devsnek
@addaleax
The text was updated successfully, but these errors were encountered: