Nominating Sam Roberts (@sam-github) to the TSC #687
Comments
|
Thanks for the nomination, you all, I am looking forward to doing what I can to help the TSC. |
|
I'll open a PR tomorrow to add @sam-github to the observer list for the next TSC meetings. |
* doc: add Sam Roberts as observer for TSC PR-URL: #53 Refs: nodejs/TSC#687 Reviewed-By: Richard Lau <[email protected]>
|
I can't remember what the procedure with this is, is it 3 weeks observer then 4th week vote? @sam-github how many weeks has it been since you got to be an observer? |
It's been 3 the last few times. It used to be 4 but that seemed a bit longer than necessary to me. |
|
@rvagg There have been 3 TSC meetings since I was added as an observer, I was present at the last 2 (the first was too early in my TZ). |
|
Adding on agenda for whenever the next meeting happens, votes can be collected in here if you're not attending. A +1 from me obviously (next week's meeting is 2am for me and this week looks like it's being cancelled and is not a great time anyway). |
|
+1 |
5 similar comments
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
2 similar comments
|
+1 |
|
+1 |
|
12 of 18 have either provided a +1 or a 👍, no negatives (that I'm aware of). This week's meeting might be cancelled, #700, so I'm going call this successful and welcome @sam-github on board. I'll open a PR to the README in nodejs/node, when that's merged we can do the other permissiony things that need to be done. Before that lands, there is still time if there are any remaining concerns among TSC members. Please voice them now or contact me, or someone else on the TSC that you trust that can make it actionable. |
|
+1 |
Voted on async in the TSC repo. This adds him to the TSC list in the README. Fixes: nodejs/TSC#687
Ref: nodejs/node#27606 Ref: nodejs/TSC#687 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]>
PR-URL: #61 Refs: nodejs/node#27606 Refs: nodejs/TSC#687 Reviewed-By: Michael Dawson <[email protected]>
Voted on async in the TSC repo. This adds him to the TSC list in the README. Fixes: nodejs/TSC#687 PR-URL: #27606 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]>
Ref: nodejs/node#27606 Ref: nodejs/TSC#687 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]>
No objections from the TSC so far and Sam has given a 👍 so I'm nominating him for the TSC. The case for Sam on the TSC is that (a) he has a long history with Node core and that kind of perspective aids in continuity and stability and (b) he's essentially taking over leadership of crypto, or OpenSSL at least, an area where the TSC could do with more representation (I've been phasing out of that area and Sam has been picking up the reigns and I think he's a much better fit than me anyway!). I also expect that Sam is the most likely person to be handling many of the security releases in the near future and having an additional level of authority to get all of the awkward things done and being able to take responsibility for difficult decisions is helpful for that.
The text was updated successfully, but these errors were encountered: