I wrote some code to help us identify contributors and find new committers to onboard.
17 contributors had never contributors prior. ~44%
@mikeal did 30 commits (Is a collaborator)
@isaacs did 1 commits (New contributor. Is not a collaborator.)
@phillipj did 7 merges
Neat! What does this mean for us who made commits but aren't collaborators?
@mikeal Nice one. Is the code to generate this available anywhere?
Is it git-extras?
Neat! What does this mean for us who made commits but aren't collaborators?
That you'll likely be added as a collaborator soon :)
That you'll likely be added as a collaborator soon :)
I'd happily accept it :P
@mikeal There are again a few people to be added as contributors. Can you please put your script into the repo so we can create the list again? (Also unfortunately, you have to be org owner to add new members to GitHub teams)
I woul like to see @abouthiroppy added as collaborator. He made some nice contributions lately.
@lpinca absolutely!!!
@lpinca @59 Thank you! I want to participate and cooperate:)
@mikeal Can I participate as collaborator?
@fhemberger I'd like to be added if that is possible
Can someone from the @nodejs/website group (other than myself) sum up who should be added? I'll go through it and invite the people.
I haven't had the bandwidth to work on this since I starting working with Code for San Francisco, though I am still seeing my name on the repo's readme as part of the WG... Not sure if you guys want to leave me on or bump me off, I'm ok either way. Once I have more bandwidth to work on this, I'll for sure be jumping in. (That may have been discussed before, not entirely sure)
@Fishrock123 Unfortunately not. Since GitHub changed its organization roles, as "Team Maintainer" I can only remove people, not invite them to a team (which is IMHO pretty silly).
@everyone: Sorry for the inconvenience and thanks for your patience so far. We'll try to figure out how to optimize the onboarding process in the future. I plan to work on a script that generates the output of the first post, that should make things easier.
Sorry it's not clear to me who needs to be added and to which team. :(
I have org owner access permissions fwiw.
@Fishrock123 so far:
+1 to @TheAlphaNerd and @abouthiroppy from me. Should I add them?
+1 from me for them as well, i'd say go ahead
do we technically need someone from the admin group to approve them? most of the governance here changed a bit since I was last active on the website
No doubt @abouthiroppy and @TheAlphaNerd should be added 馃憤
Added/invited both to the website team.
Awesome, welcome to both of you 馃巻
woot 馃帀
thx 馃帀
Thank you so much :tada:
I just worked on a script to produce a similar output as above, so I checked the commits since January for people not already being a collaborator:
(No idea why @rvagg as WG admin is listed as well)
I'd also recommend @williamkapke, @detailyang and @Starefossen (who also wrote the Docker guide) as collaborators, if they're willing to join.
@fhemberger cool- I just checked out your script, I was going to do that for the bot to produce the report automatically (on whatever schedule) and post it. Maybe you can look into writing the bot script! :D
@phillipj @Fishrock123 and myself can help you out- just let us know.
@fhemberger i'm up for all of those people to be added! before that, we should wait for their individual consent tho
ping @fhemberger be willing to as a collaborator :grin:
Do you still need someone who's an org owner to add people?
@mikeal Yes. I'm just allowed to remove people.
Ok, added all the people in the contrib report :)
awesome!!! :grin:
Closing this now, we'll create a new issue for the next onboarding.
Most helpful comment
I just worked on a script to produce a similar output as above, so I checked the commits since January for people not already being a collaborator:
(No idea why @rvagg as WG admin is listed as well)
I'd also recommend @williamkapke, @detailyang and @Starefossen (who also wrote the Docker guide) as collaborators, if they're willing to join.