Skip to content
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

nominating Michael Dawson to the TSC #206

Closed
jasnell opened this issue Feb 2, 2017 · 18 comments
Closed

nominating Michael Dawson to the TSC #206

jasnell opened this issue Feb 2, 2017 · 18 comments

Comments

@jasnell
Copy link
Member

jasnell commented Feb 2, 2017

It actually has not been clear whether or not @mhdawson is a voting member of the TSC or just an observer. If he is not currently a member, it would be good to make him a full member.

@cjihrig
Copy link
Contributor

cjihrig commented Feb 2, 2017

Does the TSC have the same rules about the number of representatives from a single company? If it's within the rules, +1 from me.

@mikeal
Copy link
Contributor

mikeal commented Feb 2, 2017

The TSC definitely has those rules, they are defined in the TSC Charter the board passed.

"No more than one-fourth of the TSC members may be affiliated with the same employer."

@addaleax
Copy link
Member

addaleax commented Feb 3, 2017

There are 12 current TSC members and, iirc, 3 of them (Ben, Bert & James) are already affiliated with IBM, so that might be a problem? :/

@jasnell
Copy link
Member Author

jasnell commented Feb 3, 2017 via email

@piscisaureus
Copy link

I think Michael Dawson absolutely deserves a TSC spot and he'll be much more useful than yours truly.
I would happily cede my TSC seat if that would make it possible.

cc @mhdawson @jasnell

@cjihrig
Copy link
Contributor

cjihrig commented Mar 9, 2017

With @jasnell leaving IBM, I'm +1 to getting @mhdawson on the TSC.

@jasnell
Copy link
Member Author

jasnell commented Mar 30, 2017

@nodejs/tsc ... revisiting this. I've put it on the tsc-agenda. Now that I am officially started with nearForm, IBM is no longer at it's limit.

@rvagg
Copy link
Member

rvagg commented Apr 3, 2017

@nodejs/tsc time for vote on this one. Best do it here because we're going to have trouble getting many people to a meeting this week so it'd be best if we can get the votes here then whoever is at the meeting this week can formalise it.

+1 from me!

@bnoordhuis
Copy link
Member

+1

4 similar comments
@shigeki
Copy link

shigeki commented Apr 3, 2017

+1

@mscdex
Copy link

mscdex commented Apr 3, 2017

+1

@indutny
Copy link
Member

indutny commented Apr 3, 2017

👍

@jasnell
Copy link
Member Author

jasnell commented Apr 3, 2017

+1

@cjihrig
Copy link
Contributor

cjihrig commented Apr 3, 2017

Still +1

@nebrius
Copy link
Contributor

nebrius commented Apr 3, 2017

+1

1 similar comment
@joshgav
Copy link
Contributor

joshgav commented Apr 4, 2017

+1

@Fishrock123
Copy link
Contributor

+1

@mhdawson
Copy link
Member

PR to add landed, closing.

@Trott Trott removed the tsc-agenda label Sep 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests