-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Idea
Since we have many people that are working on the project but are not maintainers and/or component owner, since they do not fit in any of these categories because, they contribute in somehow in all of the sub-projects and/or in more than one component or part of our main project.
Role Name
The new project role will be named as "Contributor" and will be stored in a CONTRIBUTORS.md file in this repository (https://github.com/cloudnative-pg/governance/)
Definition of a contributor
By definition a contributor will be any person that contributes directly to the project and adds value to it. The contributions don't necessarily need to be code, but also be documentation and community work.
- Responsibilities include:
- Follow the CloudNativePG CoC (https://github.com/cloudnative-pg/governance/blob/main/CODE_OF_CONDUCT.md)
- Follow the project contributing guide
- Requirements (one or several of the below):
- Report and sometimes resolve issues
- Occasionally submit PRs
- Contribute to the documentation
- Show up at meetings, takes notes
- Answer questions from other community members
- Submit feedback on issues and PRs
- Test releases and patches and submit reviews
- Promote the project in public
Nomination of a contributor
Contributors can be proposed by project maintainers by opening an issue in the governance repository. Maintainers need to vote on the issue. Once the contributor is approved, their name needs to be added to the CONTRIBUTORS.md file.
Effects on being elected
The contributor level will not, in any case, imply that the contributor will be added to the organization and/or any specific project as collaborator, outside collaborator or any team.
Voting
I'm proposing this to a vote by all the maintainers
If being accepted
This will require to create an empty CONTRIBUTORS.md file so any PR can be created against this file.