Skip to content
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

Adding collaborators #181

Closed
mikeal opened this issue Sep 21, 2015 · 33 comments
Closed

Adding collaborators #181

mikeal opened this issue Sep 21, 2015 · 33 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Sep 21, 2015

We should create a list of proposed people to add as collaborators and potentially even a few to add as Working Group members. I'd like to see this project move to more of an "OPEN Open Source" contribution model and we've had a ton of people show up recently and do great work.

We may also want to schedule a WG meeting soon.

@fhemberger
Copy link
Contributor

Looking at git shortlog -s -n with contributions > 1:

   175  Frederic Hemberger
    43  Mikeal Rogers
    20  Phillip Johnsen
    19  Rod Vagg
    13  Sean Ouimet
     8  Jeremiah Senkpiel
     7  Divjot Singh
     5  Austin Winstanley
     5  Ben Noordhuis
     5  Evan Lucas
     4  &! (bitandbang)
     4  Thomas Jensen
     4  MassimilianoMura
     3  Rich Trott
     3  Yosuke Furukawa
     3  Max Ogden
     2  paulgrock
     2  andygout
     2  Chayoung You
     2  Francisco Baio Dias
     2  Elin
     2  Trent Oswald
     2  Steven Sinatra
     2  Steve Mao
     2  rnsloan

@mikeal
Copy link
Contributor Author

mikeal commented Sep 21, 2015

In core we consider people with only a single commit as well. If it's more than a trivial change we onboard them as a committer.

@mikeal
Copy link
Contributor Author

mikeal commented Sep 21, 2015

Also, this might be a little more useful since it's got people's GitHub usernames https://github.com/nodejs/new.nodejs.org/graphs/contributors

@mikeal
Copy link
Contributor Author

mikeal commented Oct 7, 2015

@silverwind
Copy link
Contributor

Happy to join 👍

@stevemao
Copy link
Contributor

stevemao commented Oct 8, 2015

I'm quite happy if I can help 👍

@Delapouite
Copy link
Contributor

Would be my pleasure to contribute again.

@thefourtheye
Copy link
Contributor

I would love that :)

@JungMinu
Copy link
Member

JungMinu commented Oct 8, 2015

Happy to join 😄 Thanks

@s3ththompson
Copy link
Contributor

👍

4 similar comments
@fabiosantoscode
Copy link
Contributor

+1

@csabapalfi
Copy link
Contributor

👍

@fbaiodias
Copy link
Contributor

👍

@mrkiffie
Copy link
Contributor

mrkiffie commented Oct 8, 2015

👍

@PatrickHeneise
Copy link
Contributor

Thanks

@elinnet
Copy link
Contributor

elinnet commented Oct 8, 2015

[image: 👍]

On 8 October 2015 at 09:28, Patrick Heneise notifications@github.com
wrote:

Thanks


Reply to this email directly or view it on GitHub
#181 (comment)
.

@lpinca
Copy link
Member

lpinca commented Oct 8, 2015

I'm happy to help.

@diagramatics
Copy link
Contributor

👍

@paulgrock
Copy link
Contributor

I'd love to help.

@evanlucas
Copy link
Contributor

Thanks! I'm open to joining :]

@mikeal
Copy link
Contributor Author

mikeal commented Oct 8, 2015

@fhemberger waiting to get a nod from you before I add everyone :)

@srl295
Copy link
Member

srl295 commented Oct 8, 2015

Thanks for readding me! +1

@fhemberger
Copy link
Contributor

@mikeal I still feel a bit uncertain giving so many people commit rights to master (not because of any of the contributors, I simply don't have any experience with this kind of setup). Is it possible to set up some kind of GitHub workflow? (e.g. changes need to be introduced as PR and need another person to merge them.)

With the next step of adding all translators to the website repo as well, we would have more than 50 people. What do you think?

@mikeal
Copy link
Contributor Author

mikeal commented Oct 8, 2015

@fhemberger ah, I had assumed that we brought over the contribution policy from core but it looks like we are missing it :)

The policy for core is that nobody can merge their own commit, everything is a PR :) I'll send a PR to our README for that.

@thefourtheye
Copy link
Contributor

@fhemberger Ah, I agree. Too many cooks spoil the broth :D I contribute (though I check most of the PRs) only time to time. So, I would like to opt-out.

@fhemberger
Copy link
Contributor

@mikeal Great, thanks.

@bogas04
Copy link
Contributor

bogas04 commented Oct 8, 2015

Awesome news!
Glad to be part of the project.
Thanks a lot.

Divjot Singh http://bogas04.github.io/
Computer Engineering Undergraduate
Netaji Subhas Institute of Technology,
University of New Delhi

On 08-Oct-2015, at 5:03 AM, Mikeal Rogers notifications@github.com wrote:

Ok, I'm not sure if we need any "onboarding" here, the website is pretty easy to contribute to and the guidelines are written up.

Any objection to adding:

@bogas04 https://github.com/bogas04
@AustinWinstanley https://github.com/AustinWinstanley
@evanlucas https://github.com/evanlucas
@JungMinu https://github.com/JungMinu
@Trott https://github.com/Trott
@tjconcept https://github.com/tjconcept
@thefourtheye https://github.com/thefourtheye
@yosuke-furukawa https://github.com/yosuke-furukawa
@MassimilianoMura https://github.com/MassimilianoMura
@maxogden https://github.com/maxogden
@yous https://github.com/yous
@xicombd https://github.com/xicombd
@andygout https://github.com/andygout
@mrkiffie https://github.com/mrkiffie
@rnsloan https://github.com/rnsloan
@diagramatics https://github.com/diagramatics
@stevemao https://github.com/stevemao
@PatrickHeneise https://github.com/PatrickHeneise
@paulgrock https://github.com/paulgrock
@srl295 https://github.com/srl295
@lpinca https://github.com/lpinca
@bentinata https://github.com/bentinata
@hoxoa https://github.com/hoxoa
@Delapouite https://github.com/Delapouite
@s3ththompson https://github.com/s3ththompson
@narqo https://github.com/narqo
@csabapalfi https://github.com/csabapalfi
@marocchino https://github.com/marocchino
@targos https://github.com/targos
@silverwind https://github.com/silverwind
@simonmcmanus https://github.com/simonmcmanus
@brycebaril https://github.com/brycebaril
@elinnet https://github.com/elinnet
@wonderdogone https://github.com/wonderdogone
@fabiosantoscode https://github.com/fabiosantoscode

Reply to this email directly or view it on GitHub #181 (comment).

@mikeal
Copy link
Contributor Author

mikeal commented Oct 8, 2015

Ok, #224 this is based on the governance proposal I put up yesterday. Rather than a "TC" model we have an "admin group" which is elected by the full WG. The obvious candidates at this time would be the top 4 or 5 contributors, but we'll need to do that election shortly after we add all these members :)

@AustinWinstanley
Copy link

Thanks! I'm definitely open to helping more.

@phillipj
Copy link
Member

phillipj commented Oct 8, 2015

Great @mikeal! Very happy to get more people on board :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests