| --- |
| title: Contribute | Become a committer |
| layout: default |
| --- |
| |
| <!-- Marketing messaging and featurettes |
| ================================================== --> |
| <!-- Wrap the rest of the page in another container to center all the content. --> |
| |
| <div class="container"> |
| <!-- CONTRIBUTE --> |
| <div class="row mb-5 mt-5 pt-3"> |
| <div class="col-2 sidenav-menu pt-3"> |
| <div class="pb-3 text-uppercase"><strong>Contribute</strong></div> |
| <ul class="list-unstyled mb-3"> |
| <li><a href="contribute.html">Get started contributing</a></li> |
| <li class="sidenav-menu-sub-title">Technical Docs</li> |
| <li> |
| <ul class="list-unstyled sidenav-menu-sub-list"> |
| <li><a href="contribute-testing.html">Testing guide</a></li> |
| <li><a href="contribute-dependencies-guide.html">Dependencies guide</a></li> |
| </ul> |
| </li> |
| <li class="sidenav-menu-sub-title">Policies</li> |
| <li> |
| <ul class="list-unstyled sidenav-menu-sub-list"> |
| <li><a href="contribute-pre-commit-test-policies.html">Pre-commit test policies</a></li> |
| <li><a href="contribute-post-commit-test-policies.html">Post-commit test policies</a></li> |
| </ul> |
| </li> |
| <li class="sidenav-menu-sub-title">Committers</li> |
| <li> |
| <ul class="list-unstyled sidenav-menu-sub-list"> |
| <li><a href="contribute-become-a-committer.html">Become a committer</a></li> |
| <li><a href="contribute-committer-guide.html">Committer guide</a></li> |
| <li><a href="contribute-release-guide.html">Release guide</a></li> |
| </ul> |
| </li> |
| </ul> |
| </div> |
| <div class="col-8 pt-3 offset-4"> |
| <h2>Become a Committer</h2> |
| |
| <p>An Apache Unomi <a target="_blank" href="https://www.apache.org/foundation/how-it-works.html#committers">committer</a> has write access to the repository for merging pull requests, but you don't have to be a code contributor to become a committer. Becoming a committer means that ou have the project's trust. Read the <a target="_blank" href="https://www.apache.org/dev/committers.html#committer-responsibilities">ASF documentation</a> for more about being a committer in the Apache Software Foundation.</p> |
| |
| <p>The <a target="_blank" href="https://www.apache.org/foundation/how-it-works.html#pmc-members">PMC</a> makes someone a committer via nomination, discussion, and then majority vote. We use data from as many sources as possible to inform our reasoning. Here are some examples:</p> |
| |
| <ul> |
| <li><a target="_blank" href="https://lists.apache.org/list.html?dev@unomi.apache.org">dev@ archives</a> and <a target="_blank" href="https://lists.apache.org/trends.html?dev@unomi.apache.org">statistics</a></li> |
| <li><a target="_blank" href="https://lists.apache.org/list.html?user@unomi.apache.org">user@ archives</a> and <a target="_blank" href="https://lists.apache.org/trends.html?user@unomi.apache.org">statistics</a></li> |
| <li>Git metrics for <a target="_blank" href="https://github.com/apache/unomi/graphs/contributors">Unomi</a> and the <a target="_blank" href="https://github.com/apache/unomi-site/graphs/contributors">Unomi site</a></li> |
| <li>Code reviews given and received on <a target="_blank" href="https://github.com/apache/unomi/pulls">Unomi</a> and the <a target="_blank" href="https://github.com/apache/unomi-site/pulls">Unomi site</a></li> |
| <li>Clear areas of ownership (runtime, API, persistence, documentation, etc.)</li> |
| <li>Public events</li> |
| <li>Firsthand PMC testimonials</li> |
| </ul> |
| |
| <p>The PMC has assembled the following set of guidelines for becoming a committer.</p> |
| |
| <h3>An Apache Unomi committer...</h3> |
| |
| <h4>Takes many forms</h4> |
| |
| <p>There are many actions other than coding that build the trust we place in a committer - code review, design discussion, user support, community outreach, improving infrastructure, documentation, project management, etc.</p> |
| |
| <h4>Knows, upholds, and reinforces the Apache Software Foundation code of conduct</h4> |
| |
| <p>See the <a target="_blank" href="https://www.apache.org/foundation/policies/conduct.html">ASF documentation</a>. In particular, they manifestly strive to:</p> |
| |
| <ul> |
| <li>Be open</li> |
| <li>Be empathetic</li> |
| <li>Be welcoming</li> |
| <li>Be friendly</li> |
| <li>Be patient</li> |
| <li>Be collaborative</li> |
| <li>Be inquisitive</li> |
| <li>Be careful in the words that they choose</li> |
| </ul> |
| |
| <h4>Knows, upholds, and reinforces the responsibilities of an Apache Software Foundation committer</h4> |
| |
| <p>See the <a target="_blank" href="https://www.apache.org/dev/committers.html#committer-responsibilities">ASF documentation</a>.</p> |
| |
| <ul> |
| <li>They help create a product that will outlive the interest of any particular volunteer (including themselves)</li> |
| <li>They grow and maintain the health of the Apache community</li> |
| <li>They help out with surrounding work, such as the website & documentation</li> |
| <li>They help users</li> |
| <li>They can be trusted to decide when code is ready for release, or when to ask someone else to make the judgment</li> |
| <li>They can be trusted to decide when to merge code (if a code contributor) or when to ask someone else to make the judgment</li> |
| </ul> |
| |
| <h4>Knows, upholds, and reinforces the Unomi community's practices</h4> |
| |
| <ul> |
| <li>They have a proven commitment to the project</li> |
| <li>They share their intentions with the community</li> |
| <li>They accept and integrate community feedback in their plans, designs, code, etc.</li> |
| <li>They earnestly try to make Unomi better with their contributions</li> |
| <li>In particular, if a code contributor: |
| <ul> |
| <li>They earnestly try to make Unomi better with their own code</li> |
| <li>They earnestly try to make Unomi better with code review</li> |
| <li>They accept and integrate feedback on their code</li> |
| <li>They know, follow, and enforce Unomi’s practices while reviewing/merging code - style, documentation, testing, backward compatibility, etc.</li> |
| </ul> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
