Growth Path
1. Role Definition
Contributors
Active contributors to SIGs, developers with certain code programming experience.
Responsibilities and Rights:
Participate in SIG or community contributions, discussions, organizing and planning activities, etc.; submit, assign, respond to, or review PRs (Pull Requests) on Gitee.
Committers
Responsible persons for some repositories of SIGs.
Responsibilities and Rights:
Have write permissions to some SIG code repositories. Responsible for distributing or reviewing PRs submitted by Contributors; responsible for reviewing and maintaining repository code; responsible for handling community issues and mailing list questions; responsible for mentoring Contributors to quickly understand SIG domain architecture design and improve code development skills; responsible for notifying all SIG members and other SIGs that may be affected of all code, interface, and software package changes.
Maintainers
SIG leaders who lead SIG governance.
Responsibilities and Rights:
Responsible for defining the work scope and business objectives of specific SIGs, responsible for the operation and maintenance of corresponding SIGs, planning and deciding SIG technical directions and structural planning; attract and develop Contributors and Committers to participate in project incubation, documentation improvement, and community promotion of corresponding SIGs; regularly hold SIG meetings to make decisions on issues within SIGs; regularly report SIG incubation projects and SIG operation progress to the Technical Oversight Committee, and complete related improvements based on the guidance and suggestions of the Technical Oversight Committee.
Technical Oversight Committee Members
Responsibilities and Rights:
Technical Oversight Committee members have voting rights on code repository write permissions, Open3DGMBE new version releases, new Technical Oversight Committee member nominations and access, and other community affairs; responsible for the management of the Open3DGMBE community, including open-source community version planning, competitiveness planning, feature development code maintenance, material development, patch planning, etc.; organize the election and exit of committee members; responsible for SIG application access, SIG incubation project guidance, SIG graduation project access, and other SIG lifecycle management affairs.
2. Promotion Mechanism
How to Become a Contributor
Requirements:
Become a registered member on Gitee
Have read the Contributor Guide
Make multi-faceted contributions to SIGs or the community, including but not limited to:
Submit or review PRs on Gitee
Participate in SIG or community discussions
Actively participate in one or more SIGs
How to Become a Committer
Excellent Open3DGMBE community contributors (Contributors) can become Open3DGMBE community Committers after being nominated and voted on by current Technical Oversight Committee members/Committers.
Requirements:
Be a contributor
Have experience in PR review and merging code repositories
Be familiar with code repositories
Can self-nominate or be nominated by reviewers or maintainers of that SIG
How to Become a SIG Maintainer
Existing SIG Maintainers: Excellent Open3DGMBE community committers (Committers), after self-nomination or nomination by Committers, Maintainers, or Technical Oversight Committee members of the corresponding SIG, and approval by the Technical Oversight Committee, and without opposition from other sub-project Maintainers, can become maintainers of the corresponding SIG.
New SIG Maintainers: Any developer can find 2-3 developers with common interests and goals in the community, determine SIG Maintainer candidates, send a PR application for a new SIG through the Technical Oversight Committee, and after approval by the Technical Oversight Committee, can become SIG Maintainers of this new SIG.
Requirements:
Be a committer
Be proficient in PR review and code repository merging processes
Be familiar with code repositories
How to Become a Technical Oversight Committee Member
Excellent Open3DGMBE community Committers can become Open3DGMBE community Technical Oversight Committee members after being proposed and voted on by current Technical Oversight Committee members.
3. Exit Mechanism
Member Exit Method
Members send an email to [EMAIL] to apply for exit.