governance: add new collaborators #V

[Fishrock123]

It's been a little too long.

Who wants to run this one? I'm willing to join in to help / prepare to possibly do future ones, but I can't quite answer the sort of questions some of the other TC members can quite yet. :) /cc @chrisdickinson

Thread is otherwise open for @iojs/tc to nominate folks for onboarding as per our governance. @iojs/collaborators, feel free to make suggestions.

Previous onboarding threads: [4], [3], [2], [1].

[chrisdickinson]

I'm totally happy to run this one, or to help someone else run it if they're feeling up to it!

[Fishrock123]

Nominating:

@ofrobots
@domenic (Similar to how I was added, he's been quite helpful.)

[chrisdickinson]

From previous onboarding issues:

@mathiasbynens
@bk2204
@teppeis

[Fishrock123]

Also: @monsanto

[amarkanala]

@amarkanala

[silverwind]

@amarkanala self-nomination is probably not possible.

[Fishrock123]

@amarkanala While it is possible to suggest yourself, it doesn't look like you have prior efforts on the project. Were you hoping to help with something specific? :)

[chrisdickinson]

@silverwind It's okay (encouraged, even!) to suggest yourself if you're interested in becoming a collaborator. It doesn't necessarily mean you'll be onboarded on this round, but it's a good place to start to get guidance.

[chrisdickinson]

For folks coming here from my tweets about this issue, here's how this process works:

Suggestions from community members (including self-suggestions) are welcome. It helps a lot if the person being suggested has a history of helping on IRC, the issue tracker, or within any of io.js' repos. Collaborators and TC members may nominate individuals from those suggestions for onboarding. They may also nominate individuals outside of those suggestions.

After this issue has been open for 48-72 hours, the person in charge of onboarding (usually me, but possibly @Fishrock123 this time) will put up a list of the candidates to be onboarded, and a doodle poll for them to fill out. For large groups, we'll usually split the pool into groups of 5-6, and pick two times from the poll. There's a 45-60 minute google hangout with each of the smaller groups where someone will cover basics of setting up the project, governance, M.O. of the issue tracker, and other topics. Then the new collaborators are added to the repo and given the task of adding themselves to the README.

In the past we've limited suggestions to the TC and existing collaborators. However I suspect there are quality potential candidates we're missing out on either because we don't know about them, or because they aren't aware of this process. So, this time around I put the question to the community at large (or at least, as "at large" as I can reach on Twitter and the issue tracker.)

If you don't make it in this round, don't despair! This is a recurring process. If you have questions about why you weren't included in the current batch, please direct them to my github email and I'd be happy to answer them.

Again, if you feel uncomfortable self-promoting, don't hesitate to contact me via my email.

[bk2204]

Again, while I do appreciate the offer, I'd like to submit more patches and get more familiar with the codebase before accepting a more formal role. My patch was more of a one-off submission, but that doesn't mean that I might not contribute more in the future if I have more time.

[chrisdickinson]

@bk2204 Ah, totally cool. Sorry to bug you again!

[jbergstroem]

I'd like to suggest @zcbenz which seems to be the main driver of io.js/node in atom. Their agenda as well as making sure they carry less patches on top of io.js seems like a great fit.

[silverwind]

Suggesting @rlidwka, a long time contributor.