You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by vi...@apache.org on 2015/07/30 19:14:13 UTC
svn commit: r1693460 - in /mesos/site:
publish/documentation/committer-candidate-checklist/
publish/documentation/latest/committer-candidate-checklist/
source/documentation/latest/
Author: vinodkone
Date: Thu Jul 30 17:14:12 2015
New Revision: 1693460
URL: http://svn.apache.org/r1693460
Log:
Added committer checklist.
Added:
mesos/site/publish/documentation/committer-candidate-checklist/
mesos/site/publish/documentation/committer-candidate-checklist/index.html
mesos/site/publish/documentation/latest/committer-candidate-checklist/
mesos/site/publish/documentation/latest/committer-candidate-checklist/index.html
mesos/site/source/documentation/latest/committer-candidate-checklist.md
Added: mesos/site/publish/documentation/committer-candidate-checklist/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/committer-candidate-checklist/index.html?rev=1693460&view=auto
==============================================================================
--- mesos/site/publish/documentation/committer-candidate-checklist/index.html (added)
+++ mesos/site/publish/documentation/committer-candidate-checklist/index.html Thu Jul 30 17:14:12 2015
@@ -0,0 +1,164 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta charset="utf-8">
+ <title></title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" rel="stylesheet">
+ <link rel="alternate" type="application/atom+xml" title="Apache Mesos Blog" href="/blog/feed.xml">
+
+ <link href="../../assets/css/main.css" media="screen" rel="stylesheet" type="text/css" />
+
+
+
+ <!-- Google Analytics Magic -->
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-20226872-1']);
+ _gaq.push(['_setDomainName', 'apache.org']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </head>
+ <body>
+ <!-- magical breadcrumbs -->
+ <div class="topnav">
+ <ul class="breadcrumb">
+ <li>
+ <div class="dropdown">
+ <a data-toggle="dropdown" href="#">Apache Software Foundation <span class="caret"></span></a>
+ <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel">
+ <li><a href="http://www.apache.org">Apache Homepage</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ </ul>
+ </div>
+ </li>
+ <li><a href="http://mesos.apache.org">Apache Mesos</a></li>
+
+
+ <li><a href="/documentation
+/">Documentation
+</a></li>
+
+
+ </ul><!-- /breadcrumb -->
+ </div>
+
+ <!-- navbar excitement -->
+ <div class="navbar navbar-static-top" role="navigation">
+ <div class="navbar-inner">
+ <div class="container">
+ <a href="/" class="logo"><img src="/assets/img/mesos_logo.png" alt="Apache Mesos logo" /></a>
+ <div class="nav-collapse">
+ <ul class="nav nav-pills navbar-right">
+ <li><a href="/gettingstarted/">Getting Started</a></li>
+ <li><a href="/documentation/latest/">Documentation</a></li>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/community/">Community</a></li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div><!-- /.navbar -->
+
+ <div class="container">
+
+ <div class="row-fluid">
+ <div class="col-md-4">
+ <h4>If you're new to Mesos</h4>
+ <p>See the <a href="/gettingstarted/">getting started</a> page for more information about downloading, building, and deploying Mesos.</p>
+
+ <h4>If you'd like to get involved or you're looking for support</h4>
+ <p>See our <a href="/community/">community</a> page for more details.</p>
+ </div>
+ <div class="col-md-8">
+ <h1>Apache Mesos Committer Candidate Checklist</h1>
+
+<p>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.</p>
+
+<ul>
+<li><p>Candidate name: <input type="text"/></p></li>
+<li><p>JIRA user name: <input type="text"/></p></li>
+<li><p>Github user name: <input type="text"/></p></li>
+<li><p>Reviewboard user name: <input type="text"/></p></li>
+<li><p>Nominator: <input type="text"/></p></li>
+<li><p>Understanding of the Apache philosophy (<a href="http://theapacheway.com">The Apache Way</a>).
+Demonstrated by: <input type="text"/></p></li>
+<li><p>Understanding of the Mesos project’s goals.
+Demonstrated by: <input type="text"/></p></li>
+<li><p>Commitment to the Mesos project.
+Demonstrated by: <input type="text"/></p></li>
+<li><p>Knowledge and activity breadth and depth in the Mesos project as well as areas where the candidate could be a maintainer:
+<input type="text"/></p></li>
+<li><p>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"/></p></li>
+<li><p>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"/></p></li>
+<li><p>Community participation.</p>
+
+<ul>
+<li>IRC: <input type="text"/></li>
+<li>dev mailing list: <input type="text"/></li>
+<li>user mailing list: <input type="text"/></li>
+<li>JIRA comments: <input type="text"/></li>
+<li>Stack Overflow: <input type="text"/></li>
+<li>Quora: <input type="text"/></li>
+<li>Developer Community Sync Meetings: <input type="text"/></li>
+<li>Release votes: <input type="text"/></li>
+<li>Documentation added: <input type="text"/></li>
+<li>Other: <input type="text"/></li>
+</ul>
+</li>
+<li><p>General comments on community engagement: <input type="text"/></p></li>
+<li><p>Helping new contributors: <input type="text"/></p></li>
+<li><p>Presentations at meetups, conferences, etc.: <input type="text"/></p></li>
+<li><p>Reviews catching functionality issues.
+List reviews and a committer for each as witness: <input type="text"/></p></li>
+<li><p>Reviews catching style issues.
+List reviews and a committer for each as witness: <input type="text"/></p></li>
+<li><p>Major source code contribution.
+Description of the contribution: <input type="text"/></p></li>
+<li><p>JIRA tickets created.
+List initiated JIRA tickets (or an equivalent JIRA query and count/summary): <input type="text"/></p></li>
+<li><p>JIRA tickets completed.
+List resolved JIRA tickets and committed review requests (or an equivalent JIRA query and count/summary): <input type="text"/></p></li>
+<li><p>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.</p></li>
+<li><p>Initiated design documents: <input type="text"/></p></li>
+<li><p>Reviewed design documents: <input type="text"/></p></li>
+<li><p>Contributions to Documentation: <input type="text"/></p></li>
+<li><p>Dependability.
+Issues quickly / immediately solved that arose out of own contributions: <input type="text"/></p></li>
+</ul>
+
+
+ </div>
+</div>
+
+
+ <hr>
+
+ <!-- footer -->
+ <div class="footer">
+ <p>© 2012-2015 <a href="http://apache.org">The Apache Software Foundation</a>.
+ Apache Mesos, the Apache feather logo, and the Apache Mesos project logo are trademarks of The Apache Software Foundation.<p>
+ </div><!-- /footer -->
+
+ </div> <!-- /container -->
+
+ <!-- JS -->
+ <script src="//code.jquery.com/jquery-1.11.0.min.js" type="text/javascript"></script>
+ <script src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js" type="text/javascript"></script>
+ </body>
+</html>
Added: mesos/site/publish/documentation/latest/committer-candidate-checklist/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/committer-candidate-checklist/index.html?rev=1693460&view=auto
==============================================================================
--- mesos/site/publish/documentation/latest/committer-candidate-checklist/index.html (added)
+++ mesos/site/publish/documentation/latest/committer-candidate-checklist/index.html Thu Jul 30 17:14:12 2015
@@ -0,0 +1,164 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta charset="utf-8">
+ <title></title>
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link href="//netdna.bootstrapcdn.com/bootstrap/3.1.1/css/bootstrap.min.css" rel="stylesheet">
+ <link rel="alternate" type="application/atom+xml" title="Apache Mesos Blog" href="/blog/feed.xml">
+
+ <link href="../../../assets/css/main.css" media="screen" rel="stylesheet" type="text/css" />
+
+
+
+ <!-- Google Analytics Magic -->
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-20226872-1']);
+ _gaq.push(['_setDomainName', 'apache.org']);
+ _gaq.push(['_trackPageview']);
+
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </head>
+ <body>
+ <!-- magical breadcrumbs -->
+ <div class="topnav">
+ <ul class="breadcrumb">
+ <li>
+ <div class="dropdown">
+ <a data-toggle="dropdown" href="#">Apache Software Foundation <span class="caret"></span></a>
+ <ul class="dropdown-menu" role="menu" aria-labelledby="dLabel">
+ <li><a href="http://www.apache.org">Apache Homepage</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ </ul>
+ </div>
+ </li>
+ <li><a href="http://mesos.apache.org">Apache Mesos</a></li>
+
+
+ <li><a href="/documentation
+/">Documentation
+</a></li>
+
+
+ </ul><!-- /breadcrumb -->
+ </div>
+
+ <!-- navbar excitement -->
+ <div class="navbar navbar-static-top" role="navigation">
+ <div class="navbar-inner">
+ <div class="container">
+ <a href="/" class="logo"><img src="/assets/img/mesos_logo.png" alt="Apache Mesos logo" /></a>
+ <div class="nav-collapse">
+ <ul class="nav nav-pills navbar-right">
+ <li><a href="/gettingstarted/">Getting Started</a></li>
+ <li><a href="/documentation/latest/">Documentation</a></li>
+ <li><a href="/downloads/">Downloads</a></li>
+ <li><a href="/community/">Community</a></li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div><!-- /.navbar -->
+
+ <div class="container">
+
+ <div class="row-fluid">
+ <div class="col-md-4">
+ <h4>If you're new to Mesos</h4>
+ <p>See the <a href="/gettingstarted/">getting started</a> page for more information about downloading, building, and deploying Mesos.</p>
+
+ <h4>If you'd like to get involved or you're looking for support</h4>
+ <p>See our <a href="/community/">community</a> page for more details.</p>
+ </div>
+ <div class="col-md-8">
+ <h1>Apache Mesos Committer Candidate Checklist</h1>
+
+<p>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.</p>
+
+<ul>
+<li><p>Candidate name: <input type="text"/></p></li>
+<li><p>JIRA user name: <input type="text"/></p></li>
+<li><p>Github user name: <input type="text"/></p></li>
+<li><p>Reviewboard user name: <input type="text"/></p></li>
+<li><p>Nominator: <input type="text"/></p></li>
+<li><p>Understanding of the Apache philosophy (<a href="http://theapacheway.com">The Apache Way</a>).
+Demonstrated by: <input type="text"/></p></li>
+<li><p>Understanding of the Mesos project’s goals.
+Demonstrated by: <input type="text"/></p></li>
+<li><p>Commitment to the Mesos project.
+Demonstrated by: <input type="text"/></p></li>
+<li><p>Knowledge and activity breadth and depth in the Mesos project as well as areas where the candidate could be a maintainer:
+<input type="text"/></p></li>
+<li><p>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"/></p></li>
+<li><p>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"/></p></li>
+<li><p>Community participation.</p>
+
+<ul>
+<li>IRC: <input type="text"/></li>
+<li>dev mailing list: <input type="text"/></li>
+<li>user mailing list: <input type="text"/></li>
+<li>JIRA comments: <input type="text"/></li>
+<li>Stack Overflow: <input type="text"/></li>
+<li>Quora: <input type="text"/></li>
+<li>Developer Community Sync Meetings: <input type="text"/></li>
+<li>Release votes: <input type="text"/></li>
+<li>Documentation added: <input type="text"/></li>
+<li>Other: <input type="text"/></li>
+</ul>
+</li>
+<li><p>General comments on community engagement: <input type="text"/></p></li>
+<li><p>Helping new contributors: <input type="text"/></p></li>
+<li><p>Presentations at meetups, conferences, etc.: <input type="text"/></p></li>
+<li><p>Reviews catching functionality issues.
+List reviews and a committer for each as witness: <input type="text"/></p></li>
+<li><p>Reviews catching style issues.
+List reviews and a committer for each as witness: <input type="text"/></p></li>
+<li><p>Major source code contribution.
+Description of the contribution: <input type="text"/></p></li>
+<li><p>JIRA tickets created.
+List initiated JIRA tickets (or an equivalent JIRA query and count/summary): <input type="text"/></p></li>
+<li><p>JIRA tickets completed.
+List resolved JIRA tickets and committed review requests (or an equivalent JIRA query and count/summary): <input type="text"/></p></li>
+<li><p>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.</p></li>
+<li><p>Initiated design documents: <input type="text"/></p></li>
+<li><p>Reviewed design documents: <input type="text"/></p></li>
+<li><p>Contributions to Documentation: <input type="text"/></p></li>
+<li><p>Dependability.
+Issues quickly / immediately solved that arose out of own contributions: <input type="text"/></p></li>
+</ul>
+
+
+ </div>
+</div>
+
+
+ <hr>
+
+ <!-- footer -->
+ <div class="footer">
+ <p>© 2012-2015 <a href="http://apache.org">The Apache Software Foundation</a>.
+ Apache Mesos, the Apache feather logo, and the Apache Mesos project logo are trademarks of The Apache Software Foundation.<p>
+ </div><!-- /footer -->
+
+ </div> <!-- /container -->
+
+ <!-- JS -->
+ <script src="//code.jquery.com/jquery-1.11.0.min.js" type="text/javascript"></script>
+ <script src="//netdna.bootstrapcdn.com/bootstrap/3.1.1/js/bootstrap.min.js" type="text/javascript"></script>
+ </body>
+</html>
Added: mesos/site/source/documentation/latest/committer-candidate-checklist.md
URL: http://svn.apache.org/viewvc/mesos/site/source/documentation/latest/committer-candidate-checklist.md?rev=1693460&view=auto
==============================================================================
--- mesos/site/source/documentation/latest/committer-candidate-checklist.md (added)
+++ mesos/site/source/documentation/latest/committer-candidate-checklist.md Thu Jul 30 17:14:12 2015
@@ -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"/>