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

Add section about team membership #4

Open
Splaktar opened this issue Mar 13, 2016 · 6 comments
Open

Add section about team membership #4

Splaktar opened this issue Mar 13, 2016 · 6 comments

Comments

@Splaktar
Copy link
Contributor

What is the process here?

Is a merged PR required?

@tasomaniac
Copy link
Member

Good point. I think merged PR is important. I would say at least X number of PRs in 6 months or something like that.

@friedger
Copy link
Contributor

At note to all in team @gdg-x/core, please join a project team. The core team will be removed.

@Splaktar
Copy link
Contributor Author

Splaktar commented Apr 23, 2016

Just added a link directly to the team policies: https://github.com/gdg-x/code_of_conduct/blob/master/CONTRIBUTING.md#members

As for on boarding new members, how about something like this?

  1. PR submitted, reviewed, and merged.
  2. Official nomination made in Google+ Community by member of project team where PR was made.
  3. Monthly meeting will review nominations and approve/deny.
  4. Approved members will be invited to
    1. A GDG-X Project team (I.e. Frisbee) - this gives Write access to the project's repositories and also grants access to the gdg-x private Gitter channel
    2. G+ GDG-X Members community - this adds them to the monthly hangout invites

@tasomaniac
Copy link
Member

tasomaniac commented Apr 23, 2016

1st part should be a necessity 👍
4th part definitely makes sense.
I think 2 and 3 is too much to handle. Developer's willingness to contribute should be enough. If someone starts to contribute, I don't think there will be a reason to deny

@Splaktar
Copy link
Contributor Author

Splaktar commented Apr 23, 2016

@tasomaniac So you want something like the following:

  1. PR submitted, reviewed, and merged.
  2. Monthly meeting will review new contributors with merged PRs to make sure that
  3. They are invited to
    1. A GDG-X Project team (I.e. Frisbee) - this gives Write access to the project's repositories and also grants access to the gdg-x private Gitter channel
    2. G+ GDG-X Members community - this adds them to the monthly hangout invites

Is there never a case where after 1 merged PR, the existing members would not want to give a person access to our private forums/channels and write access to a set of repositories?

@tasomaniac
Copy link
Member

I think 1 merged PR is really small. For my understanding, continuity is very important. We always included people when they started submitting PRs regularly.

I think we should always discuss, but there shouldn't be strict rule and process. We already have a process for removing inactive people. I think that makes sense.

And also, we shouldn't have very much private forums. I think it is very good now and it is already very limited.

This is just my opinion. We should get others opinions as well.

/cc @ozasadnyy @stefanhoth @renfeng @rac2030 @PareshMayani @nitya @fnk0

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

3 participants