-
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: Combined TSC #2085
doc: Combined TSC #2085
Conversation
535aad3
to
7308eac
Compare
+1 |
Commit log could be a little better though. Combined TSC what? |
I'd like to see @mhdawson back in there, he's in the "official" list https://nodejs.org/about/organization/ and attends all the meetings |
Agreed, that was probably an oversight from that day or so we were worried that we might be over the limit for IBM or something. |
01783f4
to
2dfb7a5
Compare
Updated PTAL. It's changed quite a bit so I re-committed it under myself instead. Ordered roughly in order of addition (since the collaborators still are). And added @mhdawson back, even though we've never actually gotten consent from him on that. @bnoordhuis does this commit message look good? |
These members were collaborators on the old joyent/node repo prior to convergence of the Node.js and io.js projects under the Node Foundation. This updates our list to represent that they are now also part of the TSC (Technical Steering Committee), which was previously known as the io.js TC. PR-URL: nodejs#2085 Reviewed-By: Mikeal Rogers <[email protected]> Reviewed-By: Rod Vagg <[email protected]> Membership changes also previously reviewed by many more TSC & former TC members in nodejs#1710
2dfb7a5
to
4e92dbc
Compare
Enough waiting on this, landed in 4e92dbc |
Updated, the old version can be found at #1710.
Everyone gave their consent in that thread, except for @mhdawson, who I've removed until I get a "+1" from.
R= @mikeal / @nodejs/tsc
Note: the list is currently in no particular order at all.