Contributor
Responsibilities: Drive community growth through code development, bug fixing, and documentation improvement.Requirements: Understand community technology, abide by the code of conduct, and actively contribute.
Committer
Responsibilities: Elevate code quality through meticulous code reviews and lead community progress through their own contributions.Requirements: Possess rich project experience, be familiar with code standards, provide constructive feedback, and share expertise.
Maintainer
Responsibilities: Grasp the technical direction, drive key decisions, and lead the long-term development of the community through critical contributions.Requirements: Understand the project architecture, with excellent collaboration skills and commitment to open source spirit. Guide long-term growth of the community.
New Contributors
New members are welcome! Refer to the openUBMC Contributor Guide to get started.
Existing Community Members
Align with the community's direction, adhere to the openUBMC Code of Conduct, and understand the community operation mechanism and technical capabilities.
For details on inactive member offboarding, see the Inactive Member Exit Criteria and Process.
For details on inactive member offboarding, see the Inactive Member Exit Criteria and Process.
Contributor
As the core of the community, contributors collectively drive project innovation and growth by participating in code development, documentation, bug fixes, community operations, and more.
Requirements
- Registered member on AtomGit.
- Demonstrate contributions to the SIG or community, including submitting or reviewing PRs on AtomGit, triaging or commenting on Issues on AtomGit, and participating in SIG or community discussions.
- Have read the Contributor Guide.
- Actively participate in one or more SIGs.
Responsibilities & Rights
- Address assigned Issues and PRs.
- Ensure the quality of contributed code, which must be well-tested, pass test cases consistently, and meet community DT coverage requirements, with resolutions for subsequent bugs or issues.
- Participate in design implementation.
- Eligible for Committer promotion.
One can become a Committer by actively participating in code review and design review activities alongside code contribution.
Committer
Committers are the core Maintainers of repositories with merge permissions. They ensure code quality through review, developer testing, and standards checks, driving the component's technical evolution and long-term health.
Requirements
- 3+ months as Contributor.
- Primary reviewer for 6+ PRs.
- Reviewed/merged 20+ basic PRs.
- Familiar with code repositories.
- Self-nominated, or nominated by a SIG Committer or Maintainer, and approved at the SIG meeting.
- Direct Committer status may be granted for a one-time contribution of a complete, fully featured component.
Responsibilities & Rights
- Review PRs and provide fair and objective feedback based on code design, implementation, security, extensibility, and compatibility.
- Mentor Contributors to complete code contributions, ensuring correct application of the process.
- Guide Contributors to participate in interface change review meetings, ensuring rationality, compatibility, necessity, readability, and usability of the interface design.
- Maintain the component's software engineering practices and establish a sound software engineering culture in the SIG.
- Oversee the component's code implementation design, ensuring rational feature designs.
- Update and maintain component versions, ensuring alignment with community project releases.
- Eligible for Maintainer promotion.
One can become a SIG Maintainer by becoming a committer for multiple repositories in the SIG and actively participating in SIG technical planning and architectural evolution.
Maintainer
As the core leaders of a SIG, Maintainers are responsible for technical direction, community collaboration, and long-term growth. They hold all Committer responsibilities while also driving component architectural evolution, quality assurance, and ecosystem compatibility, coordinating internal and external resources to achieve SIG goals.
Requirements
- 3+ months as Committer.
- Primary reviewer for 12+ PRs.
- Reviewed/merged 30+ basic PRs.
- Familiar with 50%+ of SIG code repositories.
- May be self-nominated, or nominated by an existing SIG Maintainer without objection from other Maintainers, and approved at a TC meeting.
Responsibilities & Rights
- Define the technical roadmap for the SIG's projects, including planning and deciding the SIG's technical direction, roadmap planning, and architectural evolution.
- Oversee the SIG's technical design proposals and foster a positive technical atmosphere within the group.
- Determine the SIG's key requirements and release plan; participate in community project management; and ensure SIG planning aligns with the community's version roadmap milestones.
- Participate in community coordination activities: Represent the SIG in openUBMC organized events and specific meetings.
- Regularly call SIG meetings to decide on escalated disputes within the SIG.
- Represent the SIG at the TC, reporting on SIG work and progress.
- Eligible for TC election.
One gains the opportunity to run for TC member by actively boosting SIG influence and collaborating with other SIGs.