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.

[apapirovski]

Collaborator nominations need to be approved by the TSC anyway

Oh, I know. But that's even more of a reason to have a private discussion first. Just because someone contributes doesn't mean they want to be a Collaborator and have their work publicly evaluated for "worthiness".

[Trott]

Assigning myself because I usually do the onboardings for new Collaborators but if anyone on the TSC is especially interested in onboarding any folks who the TSC approve, don't let me stop you. Add yourself as an assignee if you want.

[joyeecheung]

@Trott

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.

Do we have a document for this process? This is something that worth writing down.

[joyeecheung]

@Trott

Assigning myself because I usually do the onboardings for new Collaborators but if anyone on the TSC is especially interested in onboarding any folks who the TSC approve, don't let me stop you. Add yourself as an assignee if you want.

I can help out onboarding folks, I think it'd be helpful to indicate our usual timezones somewhere so it's easier to arrange things. I am in UTC+8 (China Standard Time) by the way.

[Trott]

Do we have a document for this process?

@joyeecheung The closest thing we have (that I'm aware of) to documentation for this is https://github.com/nodejs/node/blob/master/GOVERNANCE.md#collaborators. If we wanted to get more specific, that's probably the place to do it.

[mhdawson]

+1 from me as well.

[yosuke-furukawa]

I’m +1 to @Leko .
He asked me to how to be a collaborator on nodefest directly. He does not have so much experience but he has passion to contribute node core.

[mithunsasidharan]

@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.

Thanks for the appreciation and mention @benjamingr . Its a huge motivation and encouragement to keep contributing more to Node.js and evolve. A huge thanks to all the Node.js team members for all their support and special mention to @apapirovski and @thefourtheye who helped me a lot with all my queries and guiding me to get going 👍 Thank you !

[thefourtheye]

I also second @mithunsasidharan's nomination. If there are no explicit objections in this issue, I would like to proceed with his nomination by 17th Jan 2018.

[MylesBorins]

Hey All,

I'd like to nominate @devsnek to be a collaborator. They have been quite involved in modules, and I think they would be a great addition.

Commits in the nodejs/node repository.
Pull requests and issues opened in the nodejs/node repository.
Comments and reviews on issues and pull requests in the nodejs/node repository

[apapirovski]

@MylesBorins Strong +1 from me but could we start a new thread? I think the latest update to Contribution doc was that we would start a unique thread for each nomination so that it's easier to keep track of it.

(One side-effect benefit of that is that when the contributor's doc PR lands, it can close the associated issue.)

[devsnek]

@MylesBorins thank you ❤️

[joyeecheung]

@MylesBorins Yes, please start a new thread for the new nomination, thanks.

[jvelezpo]

+1 I am just starting and did my first 2 PR and @mmarchini made comments on them
so @mmarchini ha my +1