Note : This document keeps changing based on the status and feedback of openGemini Community.
This document gives a brief overview of the openGemini community roles with the requirements and responsibilities associated with them.
| Role | Requirements | Responsibilities | Privileges |
|---|---|---|---|
| Member | Sponsor from 2 Committer, active in community, contributed to openGemini | Welcome and guide new contributors | openGemini GitHub organization Member |
| Committer | Sponsor from 2 Maintainers, has good experience and knowledge of domain, actively contributed to code and review | Review and approve contributions from community members or contributors | Write access in relevant repository. Name entry on the official website |
| Maintainer | Sponsor from 2 Maintainers, shown good technical judgement in feature design/development and PR review | Participate in release planning and feature development/maintenance | Top level write access to relevant repository. Name entry in Maintainers file of the repository |
Note : It is mandatory for all openGemini community members to follow openGemini Code of Conduct.
Members are active participants in the community who contribute by authoring PRs, reviewing issues/PRs or participate in community discussions on slack/mailing list.
- Sponsor from 2 committers
- Enabled [two-factor authentication] on their GitHub account
- Actively contributed to the community. Contributions may include, but are not limited to:
- Authoring PRs
- Reviewing issues/PRs authored by other community members
- Participating in community discussions on slack/mailing list
- Participate in openGemini community meetings
- Member of the openGemini GitHub organization
- Can be assigned to issues and PRs and community members can also request their review
- Participate in assigned issues and PRs
- Welcome new contributors
- Guide new contributors to relevant docs/files
- Help/Motivate new members in contributing to openGemini
committers are active members who have good experience and knowledge of the domain. They have actively participated in the issue/PR reviews and have identified relevant issues during review.
- Sponsor from 2 maintainers
- Review for at least 2 months
- Have reviewed good number of PRs
- Have good codebase knowledge
- Review code to maintain/improve code quality
- Acknowledge and work on review requests from community members
- May approve code contributions for acceptance related to relevant expertise
- Have 'write access' to specific packages inside a repo, enforced via bot
- Continue to contribute and guide other community members to contribute in openGemini project
Maintainers are committers who have shown good technical judgement in feature design/development in the past. Has overall knowledge of the project and features in the project.
- Sponsor from 2 Maintainer
- Committer for at least 2 months
- Nominated by a project owner
- Good technical judgement in feature design/development
- Participate in release planning
- Maintain project code quality
- Ensure API compatibility with forward/backward versions based on feature graduation criteria
- Analyze and propose new features/enhancements in openGemini project
- Demonstrate sound technical judgement
- Mentor contributors and committers
- Have top level write access to relevant repository (able click Merge PR button when manual check-in is necessary)
- Name entry in Maintainers file of the repository
- Participate & Drive design/development of multiple features