openbmc/docs/community-membership.md

8 …------------------- | ------------------------------------------------------ | -------------------…
11 …                                            | [OWNERS] entry within the meta-\* subfolder for the …
27 Role-specific expectations, responsibilities, and requirements are enumerated
34 Gerrit, and pre-submit tests are automatically run for their reviews. Members
41 - Have made multiple contributions to the project or community. Contribution may
43   - Authoring or reviewing code reviews on Gerrit
44   - Filing or commenting on issues on GitHub
45   - Contributing to design review, subproject, or community discussions (e.g.
47 - Subscribed to the [mailing list]
48 - Have read the [contributor guide]
49 - Actively contributing to 1 or more subprojects.
50 - **[Submit a CLA]**
54 Designated Reviewers are capable of reviewing code for quality and correctness
71 - Member for at least 3 months
72 - Primary reviewer for at least 5 changes to the codebase
73 - Reviewed or merged at least 5 substantial changes to the codebase
74 - Knowledgeable about the codebase
75 - Sponsored by a subproject approver
76   - With no objections from other approvers
77   - Done through PR to update the OWNERS file
78 - May either self-nominate or be nominated by an approver in this subproject.
85 - Code reviewer status may be a precondition to accepting large code
87 - Responsible for project quality control via [code reviews]
88   - Focus on code quality and correctness, including testing and factoring
89   - May also review for more holistic issues, but not a requirement
90 - Expected to be responsive to review requests as per [community expectations]
91 - Assigned changes to review related to subproject of expertise
92 - Assigned test bugs related to subproject of expertise
96 Platform maintainers are able to review configuration changes for quality and
109 - Member for at least 3 months
110 - Primary reviewer for at least 5 reviews to the codebase
111 - Knowledgeable about the specific platforms constraints
112 - Access to a platform to test and run code
113 - Demonstrated knowledge of bitbake metadata
114 - Sponsored by a root approver from openbmc/openbmc OWNERS file
115   - With no objections from other approvers
116   - Done through PR to update the OWNERS file
117 - May either self-nominate or be nominated by an approver in this subproject.
124 - Having an owner with platform maintainer status may be a precondition to
126 - Responsible for platform stability
127   - Testing on a regular cadence (base expectation is every quarter)
128   - Providing results and insight to the community on platform-specific issues.
129 - Expected to be responsive to review requests as per [community expectations]
130 - Assigned changes to review and test related to the platform
131 - Communicating with the technical-oversight-forum any long-term (> 1 month)
138 code review is focused on code quality and correctness, approval is focused on
153 - Reviewer of the codebase for at least 9 months
154 - Primary reviewer for at least 10 substantial changes to the codebase
155 - Reviewed or merged at least 30 changes to the codebase
156 - Access to a suitable platform environment
157 - Nominated by two subproject or TOF root owner sponsors
158   - With no objections from other subproject owners
159   - Done through PR to update the subprojects top-level OWNERS file
160   - **Note the following expectations for sponsors**:
161     - Sponsors must have close interactions with the prospective member - e.g.
163     - Sponsors must be approver in at least one subproject.
164     - Sponsors must be from multiple member companies to demonstrate integration
172 - Approver status may be a precondition to accepting large code contributions
173 - Demonstrate sound technical judgement
174 - Responsible for project quality control via [code reviews]
175   - Focus on holistic acceptance of contribution such as dependencies with other
177   - Maintain a codebase that is free from unnecessary or unused code, and remove
179 - Expected to be responsive to review requests as per [community expectations]
180 - Mentor contributors and reviewers
181 - May approve code contributions for acceptance
185 **Note:** This is a generalized high-level description of the role, and the
193 direction and make or approve design decisions for their subproject - either
200 The per-repository requirements for becoming an subproject Owner should be
207 - Deep understanding of the technical goals and direction of the subproject
208 - Deep understanding of the technical domain of the subproject
209 - Sustained contributions to design and direction by doing all of:
210   - Authoring and reviewing proposals
211   - Initiating, contributing and resolving discussions (emails, GitHub issues,
213   - Identifying subtle or complex issues in designs and implementation reviews
214   - Ensure through testing that the subproject is functional on one or more
216 - Directly contributed to the subproject through implementation and/or review
217 - Meet all subproject specific requirements outlined in the OWNERS file
223 - Make and approve technical design decisions for the subproject.
224 - Set technical direction and priorities for the subproject.
225 - Mentor and guide approvers, reviewers, and contributors to the subproject.
226 - Ensure continued health of subproject
227   - Adequate test coverage to confidently release
228   - Tests are present and passing reliably (i.e. not flaky) and are fixed when
230 - Ensure a healthy process for discussion and decision making is in place.
231 - Work with other subproject owners to maintain the project's overall health and
233 - Keep abreast of technical changes to the overall project and maintain and/or
250 - Deep understanding of the technical goals and direction of the project
251 - Knowledge of community members, technical experts within and outside the
253 - Deep understanding of the technical domain of OpenBMC and BMCs in general.
254 - Sustained contributions to design and direction by doing all of:
255   - Authoring, reviewing, and voting on proposals to the
256     technical-oversight-forum repository
257   - Initiating, contributing and resolving discussions that involve project-wide
259   - Identifying subtle or complex issues in designs and implementation that
260     occur cross-project.
261   - Ensure through testing that the project is functional (to the extent
263   - Ensure that coding standards, project norms, and community guidelines are
265 - Directly contributed to the project through implementation and/or review
269 - Make and approve technical design decisions for OpenBMC.
270 - Define milestones and releases.
271 - Mentor and guide approvers, reviewers, and contributors to the project.
272 - Create new subprojects, and ensure their addition continues the growth and
274 - Define and maintain a healthy process for discussion and decision making.
275 - Work with subproject owners and platform maintainers to maintain the project's
278 [new contributors]: /CONTRIBUTING.md#starting-out
282 [community expectations]: /code-of-conduct.md
283 [submit a cla]: /CONTRIBUTING.md#starting-out
285 [tof election cycle]: /tof/membership-and-voting.md