-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
Good point. I think merged PR is important. I would say at least X number of PRs in 6 months or something like that. |
At note to all in team @gdg-x/core, please join a project team. The core team will be removed. |
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?
|
1st part should be a necessity 👍 |
@tasomaniac So you want something like the following:
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? |
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 |
What is the process here?
Is a merged PR required?
The text was updated successfully, but these errors were encountered: