Collaborator nomination

[joyeecheung]

I would like to nominate @starkwang and @mmarchini to join the team of collaborators

@starkwang:
Comments: https://github.com/nodejs/node/search?utf8=%E2%9C%93&q=commenter%3Astarkwang&type=Issues
Commits: https://github.com/nodejs/node/commits?author=starkwang

@mmarchini:
Comments: https://github.com/nodejs/node/search?utf8=%E2%9C%93&q=commenter%3Ammarchini&type=Issues
Commits: https://github.com/nodejs/node/commits?author=mmarchini
(Also there is the ongoing #14901 which is pretty significant and @mmarchini has been very patient and determined to push this forward)

cc @nodejs/tsc

[starkwang]

@joyeecheung Thank you! It's my great honor to be a collaborator!

[mcollina]

+1 to both of them.

[targos]

+1

[fhinkel]

+1

[benjamingr]

@starkwang looks very solid +1

@mmarchini looks a little new (been contributing to Node for 2 weeks) but very welcome - maybe wait until #14901 lands?

---

@mithunsasidharan has also been doing a lot of work recently (although I have the same 'still pretty new' reservation) - and we should consider them too.

Also worth discussing:

• @davidben https://github.com/nodejs/node/commits?author=davidben
• @Leko (but also pretty new) https://github.com/nodejs/node/commits?author=Leko

[BridgeAR]

I asked @joyeecheung if she thinks it makes sense to nominate @starkwang so I am definitely +1 there (I wanted to prevent issues like the last time when I nominated someone).

Even though @mmarchini is still quite new I guess he has already shown that he is a determined to help out where he can, so also +1 from me.

[cjihrig]

+1 to both.

I'd also like to nominate @vdeturckheim for their work on migrating domains to async hooks, and ongoing efforts in the Node security working group.

Comments: https://github.com/nodejs/node/search?utf8=%E2%9C%93&q=commenter%3Avdeturckheim&type=Issues
Commits: https://github.com/nodejs/node/commits?author=vdeturckheim

[mcollina]

+1 as well.

[addaleax]

Yes, I’m +1 to all 5 (@starkwang, @mmarchini, @davidben, @Leko & @vdeturckheim).

Also happy to take up a few of the onboarding sessions, haven’t done that in a while. :)

[mmarchini]

It would be an honor to join the team of collaborators! Thank you @joyeecheung for the nomination!

[apapirovski]

+1 to @starkwang, @mmarchini, @davidben & @vdeturckheim.

Also, just a thought but collaborator nominations are something that could belong in the new discussion area until they're agreed upon.

[devsnek]

@apapirovski if you're referring to github team discussions, is there any reason for those discussions to be non-public?

[apapirovski]

@devsnek because if someone ends up getting publicly rejected or not considered then it'll really suck. It's just a more sensitive way to go about it and also allows an actual discussion to happen.

[Trott]

@apapirovski @devsnek FWIW, Collaborator nominations need to be approved by the TSC anyway, and I'm usually the one who handles that (although there's no reason others on the TSC can't--it just usually ends up being me, which is fine by me). I usually consult with the TSC privately to see if anyone has concerns/objections. Not saying this is the ideal process or anything. Just publicly documenting what typically happens in the process.