Documented "how to become a committer".

Added new document "committer-candidate-checklist.md" and wrote
a paragraph about the path to committership in "committers.md".

Review: https://reviews.apache.org/r/36197

docs/committer-candidate-checklist.md

@@ -0,0 +1,82 @@
+---
+layout: documentation
+---
+
+# Apache Mesos Committer Candidate Checklist
+
+This document contains categories of contributions and behaviors relevant to becoming an Apache Mesos  committer. As a committer candidate you can use a copy of this list to collect and aggregate data on what you have achieved so far. Neither is this an exhaustive list nor do all categories need to be addressed, since there can be reasonably diverse committer profiles. But some categories are always crucial to have covered, e.g., writing high quality source code and performing meaningful code reviews. Eventually, your nominator can hand in your filled-out variant of this list to the PMC to facilitate their reviewing your case.
+
+* Candidate name: <input type="text"/>
+
+* JIRA user name: <input type="text"/>
+
+* Github user name: <input type="text"/>
+
+* Reviewboard user name: <input type="text"/>
+
+* Nominator: <input type="text"/>
+
+* Understanding of the Apache philosophy ([The Apache Way](http://theapacheway.com)).
+Demonstrated by: <input type="text"/>
+
+* Understanding of the Mesos project's goals.
+Demonstrated by: <input type="text"/>
+
+* Commitment to the Mesos project.
+Demonstrated by: <input type="text"/>
+
+* Knowledge and activity breadth and depth in the Mesos project as well as areas where the candidate could be a maintainer:
+<input type="text"/>
+
+* Can the candidate be trusted to act the right way outside of known areas where he/she has already demonstrated committer-level expertise and behavior:
+<input type="text"/>
+
+* High quality source code.
+A committer vouches that the candidate writes high-quality, "readable" code, adhering to Mesos style and best practices standards, both formal and informal.
+Name of the committer: <input type="text"/>
+
+* Community participation.
+    + IRC: <input type="text"/>
+    + dev mailing list: <input type="text"/>
+    + user mailing list: <input type="text"/>
+    + JIRA comments: <input type="text"/>
+    + Stack Overflow: <input type="text"/>
+    + Quora: <input type="text"/>
+    + Developer Community Sync Meetings: <input type="text"/>
+    + Release votes: <input type="text"/>
+    + Documentation added: <input type="text"/>
+    + Other: <input type="text"/>
+
+* General comments on community engagement: <input type="text"/>
+
+* Helping new contributors: <input type="text"/>
+
+* Presentations at meetups, conferences, etc.: <input type="text"/>
+
+* Reviews catching functionality issues.
+List reviews and a committer for each as witness: <input type="text"/>
+
+* Reviews catching style issues.
+List reviews and a committer for each as witness: <input type="text"/>
+
+* Major source code contribution.
+Description of the contribution: <input type="text"/>
+
+* JIRA tickets created.
+List initiated JIRA tickets (or an equivalent JIRA query and count/summary): <input type="text"/>
+
+* JIRA tickets completed.
+List resolved JIRA tickets and committed review requests (or an equivalent JIRA query and count/summary): <input type="text"/>
+
+* Evidence of testing as a priority:
+A simple metric could be <#tests written> / <#testable tickets>. Or you could detail a particularly complex set of unit tests you had to write. Or explain how you have improved the project's testing infrastructure or best practices.
+NOTE: These are just suggestions for documenting testing efforts. The ultimate goal here is convincingly corroborating that all contributed source code is adequately covered by tests.
+
+* Initiated design documents: <input type="text"/>
+
+* Reviewed design documents: <input type="text"/>
+
+* Contributions to Documentation: <input type="text"/>
+
+* Dependability.
+Issues quickly / immediately solved that arose out of own contributions: <input type="text"/>

docs/committers.md

@@ -4,9 +4,15 @@ layout: documentation
 
 # Committers
 
+An Apache Mesos committer is a contributor who has been given write access to the Apache Mesos code repository and related Apache infrastructure. In the Mesos project, each committer is also a voting member of the PMC.
+
+## Becoming a committer
+
+Every new committer has to be proposed by a current committer and then voted in by the members of the Mesos PMC. For details about this process and for candidate requirements see the general [Apache guidelines for assessing new candidates for committership](https://community.apache.org/newcommitter.html). Candidates prepare for their nomination as committer by contributing to the Mesos project and its community, by acting according to the [Apache Way](http://theapacheway.com), and by generally following the path [from contributor to committer](https://community.apache.org/contributors/) for Apache projects. Specifically for the Mesos project, you can make use of the [Apache Mesos Committer Candidate Checklist](https://community.apache.org/committer-candidate-checklist/) for suggestions of what kind of contributions and demonstrated behaviors can be instrumental, and to keep track of your progress.
+
 ## Current Committers
 
-We'd like to thank the following committers to the Apache Mesos project who have helped get the project to where it is today. Committers are voted on by members of the Mesos PMC. This list might be stale, the canonical list is located on [Apache's website](http://people.apache.org/committers-by-project.html#mesos).
+We'd like to thank the following committers to the Apache Mesos project who have helped get the project to where it is today. This list might be stale, the canonical list is located on [Apache's website](http://people.apache.org/committers-by-project.html#mesos).
 
 <table class="table table-hover table-condensed">
   <thead>