-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: add NAN WG #1226
doc: add NAN WG #1226
Conversation
+1 But I like more general Working Group name. NAN stands for |
Good call @yosuke-furukawa, I've changed it to the "Addon API Working Group" but am open to alternative suggestions. |
Should this be tc-agenda? I think the TC would ratify this, right? |
I think this can be closed now? The WG was unanimously accepted in Wednesday's TC meeting. |
I think it needs to be rebased, but it should be merged. |
PR-URL: nodejs#1226 Reviewed-By: Yosuke Furukawa <[email protected]> Reviewed-By: TC
landed @ 12e51d5 |
please welcome the new @iojs/addon-api team |
\o/ |
Proposing a NAN Working Group and the move of the nan and node-addon-examples (to be renamed "addon-examples") repos to the iojs org.
Corresponding proposal to the NAN owners is here, note that it's already run as an open project in a similar model to io.js so this needs to be agreed upon there too. Initial WG members would be those listed on the NAN README although that's not quite final because there's a couple of people who may be removed due to inactivity (it'll be their choice).