community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r985399 - in /websites/staging/community/trunk/content: ./ contributors/index.html
Date Mon, 11 Apr 2016 18:06:49 GMT
Author: buildbot
Date: Mon Apr 11 18:06:49 2016
New Revision: 985399

Log:
Staging update by buildbot for community

Modified:
    websites/staging/community/trunk/content/   (props changed)
    websites/staging/community/trunk/content/contributors/index.html

Propchange: websites/staging/community/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 11 18:06:49 2016
@@ -1 +1 @@
-1738616
+1738617

Modified: websites/staging/community/trunk/content/contributors/index.html
==============================================================================
--- websites/staging/community/trunk/content/contributors/index.html (original)
+++ websites/staging/community/trunk/content/contributors/index.html Mon Apr 11 18:06:49 2016
@@ -170,7 +170,7 @@ comfortable with open source development
 their way around The Apache Software Foundation and our way of developing software
 (commonly called "The Apache Way"). For those wishing to start from
 the very beginning we have a <a href="/newcomers/index.html">newcomers page</a>
too.</p>
-<h2 id="project-independence">Project Independence<a class="headerlink" href="#project-independence"
title="Permanent link">&para;</a></h2>
+<h1 id="project-independence-and-policies">Project Independence And Policies<a class="headerlink"
href="#project-independence-and-policies" title="Permanent link">&para;</a></h1>
 <p>While not all aspects of the Apache Way are practiced the same way by 
 all projects at the ASF, there are a number of rules that Apache 
 projects are required to follow – things like complying with PMC 
@@ -182,7 +182,7 @@ environemnt in which all participants ar
 opportunity to contribute to and benefit from our software, regardless
 of motivation or financial objectives. This is discussed in more detail
 in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
-<h2 id="from-contributor-to-committer">From contributor to committer<a class="headerlink"
href="#from-contributor-to-committer" title="Permanent link">&para;</a></h2>
+<h1 id="moving-from-contributor-to-committer">Moving From Contributor to Committer<a
class="headerlink" href="#moving-from-contributor-to-committer" title="Permanent link">&para;</a></h1>
 <p>Anyone can be a contributor to an Apache project. Being a contributor simply means
 that you take an interest in the project and contribute in some way, ranging from asking
 sensible questions (which documents the project and provides feedback to developers)
@@ -195,10 +195,14 @@ to be part of the core group within the
 (represented by the Project Management Committee, PMC). In a few projects a only a subset
of 
 committers, who have earned even more merit, are invited to be a part of the PMC.</p>
 <p>One thing that is sometimes hard to understand when you are new to the open 
-development1 process used at the ASF, is that we value the community more than 
+development process used at the ASF, is that we value the community more than 
 the code. A strong and healthy community will be respectful and be a fun and 
-rewarding place. Strong code will evolve. </p>
-<h3 id="contributing-to-the-project-copdoc">Contributing to the Project - CoPDoC<a
class="headerlink" href="#contributing-to-the-project-copdoc" title="Permanent link">&para;</a></h3>
+rewarding place. More importantly, a diverse and healthy community can 
+continue to support the code over the longer term, even as individual 
+companies come and go from the field.</p>
+<p>In particular, we have some <a href="http://community.apache.org/contributors/etiquette">etiquette
and behavior expectations</a> when 
+working with Apache communities.</p>
+<h2 id="contributing-a-project-copdoc">Contributing A Project - CoPDoC<a class="headerlink"
href="#contributing-a-project-copdoc" title="Permanent link">&para;</a></h2>
 <p>The foundations of an Apache project and how the community contributes to it is

 sometimes referred to by the acronym CoPDoC:</p>
 <ul>
@@ -207,13 +211,14 @@ sometimes referred to by the acronym CoP
 <li>(Do)cumentation - without it, the stuff remains only in the minds of the authors</li>
 <li>(C)ode - discussion goes nowhere without code</li>
 </ul>
-<h3 id="becoming-a-committer">Becoming a Committer<a class="headerlink" href="#becoming-a-committer"
title="Permanent link">&para;</a></h3>
+<h2 id="anyone-can-become-a-committer">Anyone Can Become A Committer<a class="headerlink"
href="#anyone-can-become-a-committer" title="Permanent link">&para;</a></h2>
 <p>There is nothing at The Apache Software Foundation that says you must write code

 in order to be a committer. Anyone who is supportive of the community and works 
 in any of the CoPDoC areas is a likely candidate for committership.</p>
 <p>Apache is a meritocracy. That is, once someone has contributed sufficiently to 
 any area of CoPDoC they can be voted in as a committer. Being a committer does 
-not mean you commit code, it means you are committed to the project.</p>
+not necessarily mean you commit code, it means you are committed to the project
+and are productively contributing to its success.</p>
 <p>One of the key contributions people can make to the community is through the 
 support of a wide user base by assisting users on the user list, writing user 
 oriented docs and ensuring the user viewpoint is understood by all developers. 
@@ -221,7 +226,8 @@ A main idea behind being a committer is
 cooperatively with your peers.</p>
 <p>Some of those users become committers in their own right. Some will test code, 
 some will write documentation, some will do bug triage and some will write code.</p>
-<p>For more details see our "<a href="http://www.apache.org/foundation/how-it-works.html">How
it works</a>" document.</p>
+<p>For more details see our "<a href="http://www.apache.org/foundation/how-it-works.html">How
it works</a>" document.  You can also make 
+<a href="http://community.apache.org/newbiefaq.html#websitecms">suggestions for how
to update this website</a> you're reading right now!</p>
 <h2 id="questions-and-feedback">Questions and Feedback<a class="headerlink" href="#questions-and-feedback"
title="Permanent link">&para;</a></h2>
 <p>Feedback can be provided and questions asked by subscribing to our mailing
 list by sending a mail to 



Mime
View raw message