Add a GradleUp Governance Charter #6
Conversation
oleg-nenashev
added
documentation
docs/community/governance.md
Outdated
| ## Roles | ||
|
|
||
| * **Contributor** - any individual who participates in the community and | ||
| adds value to in one form or another, | ||
| including but not limited to code, documentation ,automation, advocacy or | ||
| community support. | ||
| * **Team Member** - | ||
| A GradleUp contributor listed on the [GradleUp Team page](./team.md). | ||
| They participate in the project steering as whole. | ||
| New team members are added by the decision of the current team members. | ||
| * **Org Admin** - A team member with administrative access to the GitHub | ||
| organization and/or other community resources. | ||
| Permissions and access are granted based on the decision of the current team members. | ||
| * **Maintainer** - A GradleUp contributor who maintains a component hosted on GradleUp. | ||
| It includes roles _Triage_ or above. | ||
| Components may explicitly or implicitly introduce more Maintainer sub-roles. |
There was a problem hiding this comment.
Suggestion to simplify and have only 3 roles:
- Member
- access to a specific GitHub repository
- Maintainer
- admin access to a specific GitHub repository
- Admin
- admin access to GitHub org, Sonatype, Gradle plugin portal and DNS
Contributors can be anyone, right, we do accept pull requests, etc... Just like any other OSS orgs. I don't expect them to be part of the GradleUp team (unless they want to of course)
There was a problem hiding this comment.
It excludes the "GradleUp Team member" which is the current steering entity. I would prefer to keep it as is for now, given we may want to have less org admins with permissions.
There was a problem hiding this comment.
It excludes the "GradleUp Team member" which is the current steering entity
I'd say everyone in the GradleUp organization would effectively be a team member (https://github.com/orgs/GradleUp/people)?
- You're a repo maintainer => you're part of the GradleUp org
- You're a repo maintainer and you invite a new collaborator => they're part of the GradleUp org
There might be other ways but it's handy to have https://github.com/orgs/GradleUp/people as the source of truth for the "GradleUp" team.
Co-authored-by: Leonard Brünings <[email protected]> Co-authored-by: Louis CAD <[email protected]>
This change introduces the initial Governance Charter, including the positioning of the organization, legal notice, decision making process and licenses. I built it based on the Jenkins and WireMock governance models. I tried to keep it as lightweight as possible