-
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
Nominating @MylesBorins to the TSC #247
Comments
+1 from me. |
+1 from me, too. |
+1 from me too |
+1 from me, makes sense to bring people on who are willing to help out. |
+1. Somewhat relatedly I think, perhaps @MylesBorins can help us identify areas where the TSC can more deeply support Node's technical projects and perhaps reduce the burden on the CTC. |
+1 |
We have 8 yes's out of 14 TSC members at the moment. Until #142 lands we need a 2/3 vote to add someone (after that PR we'll just need a majority), which means we need at least 2 more yes votes. @rvagg @bnoordhuis @piscisaureus @mscdex @shigeki @trevnorris can you please vote? Thanks! |
Since #142 has landed and there are no objections I believe we can declare this as approved. |
can I put this on my linkedIn yet?? |
Sorry for my late vote. Of course +1. |
@MylesBorins I think we just need a PR to add you to the readme.md do you want to do that or would you like me to ? |
@nodejs/tsc ... I would like to nominate @MylesBorins to the TSC. The contributions to LTS, CITGM and just general overall ecosystem stability, not to mention the relatively new connections on the V8 side make it a fairly obvious choice, in my opinion. Following the normal procedure, the first step would be to invite @MylesBorins as an observer in the regular TSC calls.
The text was updated successfully, but these errors were encountered: