Community Members
Responsibilities of most roles are focused on special interest groups (SIGs). The distinction between maintainers and committers does not relate to Gitee permissions but rather to the extent of governance within SIGs. For details, see the following description.
Contributor
Responsibilities: Act as the major contributor to a SIG and projects, main fixer of issues in code repositories, and code develpoer.
Committer
Responsibilities: Act as the primary owner of some repositories in a SIG and review the contributions of other members.
Requirements: Frequently contribute to the SIG, have extensive experience, and be willing to participate in review.
Maintainer
Responsibilities: Act as a SIG leader, driver, and planner, ensure the development and evolution of the SIG, and may also act as a project owner.
Requirements: Have extensive experience, a strong sense of responsibility, excellent technical skills, and management abilities.
Contributor
Contributors are continuously active developers in the community. They can claim issues and PRs, participate in SIG activities, and complete tests before committing PRs.
Joining Requirements
- Register with Gitee.
- Make contributions to a SIG or community in many ways, including but not limited to committing or reviewing PRs on Gitee, archiving or commenting on issues on Gitee, and participating in SIG or community discussions.
- Read Contribution Guide and be familiar with the contribution process.
- Join in one or more SIGs.
Responsibilities and Rights
- Respond to assigned issues and PRs.
- Ensure that the contributed code is at least well tested, passes all test cases, and fixes faults or issues.
- Assign issues or PRs.
Note: Contributors who actively participate in code review have the opportunity to become SIG committers.
Committer
Committers are core contributors who have the permission to merge code and are also owners of code repositories, ensuring the code quality and correctness, and are responsible for the project development.
Definition: See Committer entries in the sig-info.yaml file in repositories owned by MindSpore SIGs.
Joining Requirements
- Be a contributor for at least three months.
- Participate in at least 6 PR reviews as the primary reviewer.
- Review or merge at least 20 PRs into the code repository.
- Be familiar with the code repository.
- Be self-nominated or nominated by SIG committers or maintainers.
Responsibilities and Rights
- Review PRs committed by contributors: For details, see Programming Suggestions and Security Coding Specifications.
- Distribute and handle issues: For details, see Issue Submission and Handling Guide.
- Track dependency issues: In a development branch, project dependencies of a SIG may be damaged by updates of other SIGs. In this case, committers will receive an alert and try to perform rebuilding. Errors in dependencies may prevent end users from updating the system. The packaging team will also intervene and rebuild projects with dependency issues, but committers should not rely on these rebuilds.
- Notify SIGs that may be affected by interface changes. Committers should understand and review the impact on dependencies caused by changes, and announce and send alert emails about API or ABI changes. Such announcements should be made at least one week before the change occurs, and all SIGs that may be affected should be notified.
Maintainer
Maintainers are the managers, drivers, and planners of SIGs. They lead the review, update, and fixing of related code to ensure stability and compatibility. They are key roles in the project ecosystem. Maintainers have all the responsibilities and permissions of reviewers. In addition, maintainers are responsible for determining technical roadmaps and internal and external coordination of SIGs.
Definition: See Maintainer entries in the sig-info.yaml file in repositories owned by MindSpore SIGs.
Joining Requirements
- Be a committer for at least three months.
- Participate in at least 12 PR reviews as the primary reviewer.
- Review or merge at least 30 PRs into the code repository.
- Be familiar with the code repository.
- Be self-nominated or nominated by a subproject maintainer with no objection from other subproject maintainers.
Responsibilities and Rights
- Determine technical roadmaps for projects of a SIG, including planning and defining technical directions, roadmaps, and architecture evolution.
- Develop the release plan for projects of a SIG, including determine the key requirements and release plan of the SIG, participating in the PM activities of the community, and coordinating the SIG plan to match the milestones/schedule of the community release.
- Participate in community activities as a representative of a SIG, including activities and specific meetings organized by the MindSpore Technical Committee or Council.
- Regularly convene SIG meetings to make decisions on disputes escalated within a SIG.