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

Website WG Membership / Collaborator Establishment #13

Closed
bnb opened this issue Jun 19, 2015 · 16 comments
Closed

Website WG Membership / Collaborator Establishment #13

bnb opened this issue Jun 19, 2015 · 16 comments

Comments

@bnb
Copy link
Contributor

bnb commented Jun 19, 2015

This is an issue a la #4 (comment). If you want to be a member or collaborator in the Website WG...

  • via grandfathering from the old iojs/website WG repo
  • via official Joyent/Node Foundation role
  • via Node Foundation membership

... make it known here, and you will be appropriately added to the WG. (or directly add yourself in #14)

If you want to join, but are not a member of one of these groups, you should see the (in-progress) GOVERNANCE.md - namely:

Individuals making significant and valuable contributions are made Collaborators and given commit-access to the project. These individuals are identified by the WG and their addition as Collaborators is discussed during the weekly WG meeting.

Note: If you make a significant contribution and are not considered for commit-access log an issue or contact a WG member directly and it will be brought up in the next WG meeting.

@therebelrobot
Copy link
Contributor

It is known. ;)

@snostorm
Copy link
Contributor

As names are added here are you going to keep adding to a parallel PR? I expected there just just to be an "ongoing" PR-issue we could all just pull/add our names to. (I can set this up? I just wasn't able to when I suggested it.)

@bnb
Copy link
Contributor Author

bnb commented Jun 20, 2015

@snostorm That sounds excellent. If you can't set it up, I'll be able to figure out a way to do it.

@snostorm
Copy link
Contributor

See #14. To contribute just pull the README-adds-wg-collaborator branch and then push back up.

@fhemberger
Copy link
Contributor

I'd like to become a WG member as well (also for io.js) … is there an official "process"? (There were no WG meetings in the last few weeks, also nodejs/iojs.org#203 shows no recent activity)

@mikeal
Copy link
Contributor

mikeal commented Jul 13, 2015

We should adopt and improve the liberal contributor agreement core has so that anyone contributing becomes a member of the WG.

@robertkowalski
Copy link
Contributor

@fhemberger I think you are a member if you add yourself to the README.md - you are also owner of this repo, you just need to push your commit

@mikeal +1 sounds great!

@fhemberger
Copy link
Contributor

@robertkowalski I know that I'm able to just go ahead and do it, but it would feel like giving myself a promotion. That's why I asked before.

@robertkowalski
Copy link
Contributor

oh, i thought we were all wg members? are there differences? which?

@fhemberger
Copy link
Contributor

On the io.js website repo we had two different "roles" so far: contributors and WG members. The first one you get (obviously) after some contribution to the project to encourage shared code responsibility. The latter is more about long term commitment and getting actively involved in decision making regarding the project's course. But the lines between those two are blurred. (I hope I summed this up correctly).

@mikeal
Copy link
Contributor

mikeal commented Jul 13, 2015

Maybe we could come up with a way for the WG to essentially contain "current active contributors" to make it easy to shuffle people out of the meetings who get caught up in other work and easily bring in the people who are more actively contributing.

@fhemberger
Copy link
Contributor

@mikeal Can you please add @phillipj to the contributors?

@mikeal
Copy link
Contributor

mikeal commented Sep 7, 2015

@fhemberger added, and I made you a team maintainer.

@fhemberger
Copy link
Contributor

@mikeal Cool, thanks.

@phillipj
Copy link
Member

phillipj commented Sep 7, 2015

Oooh appreciate it, thanks! 👯

@mikeal
Copy link
Contributor

mikeal commented Oct 7, 2015

Everyone is merged in now AFAIK.

@mikeal mikeal closed this as completed Oct 7, 2015
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

7 participants