svn commit: r788662 - /websites/staging/rave/trunk/content/rave/get-involved.html

[bu...@apache.org]

Author: buildbot
Date: Fri Apr 22 21:35:33 2011
New Revision: 788662

Log:
Staging update by buildbot

Modified:
    websites/staging/rave/trunk/content/rave/get-involved.html

Modified: websites/staging/rave/trunk/content/rave/get-involved.html
==============================================================================
--- websites/staging/rave/trunk/content/rave/get-involved.html (original)
+++ websites/staging/rave/trunk/content/rave/get-involved.html Fri Apr 22 21:35:33 2011
@@ -64,7 +64,7 @@
 
   <div id="content">
     <p>You don't need to be a software developer to contribute to 
-Apache Rave. To be succesful this project 
+Apache Rave. To be successful this project 
 requires a huge range of different skills, levels of involvement and degrees of 
 technical expertise. So, if you want to get involved in Apache Rave, there 
 is almost certainly a role for you. </p>
@@ -86,10 +86,36 @@ is almost certainly a role for you. </p>
 the community. The project team and the broader community will 
 therefore welcome and encourage participation, and attempt to make it 
 as easy as possible for people to get involved. </p>
+<h2 id="mailing_lists">Mailing lists</h2>
 <p>Your first engagement with the project should be to subscribe to our
 mailing list by sending a mail to 
 <a href="mailto://rave-dev-subscribe@incubator.apache.org">rave-dev-subscribe@incubator.apache.org</a>. Once you have subscribed
 you should say hello by posting to <a href="mailto://rave-dev@incubator.apache.org">rave-dev@incubator.apache.org</a>.</p>
+<h2 id="decision_making">Decision Making</h2>
+<p>The most important thing about engaging with any Apache project is that everyone
+is equal. All people with an opinion are entitled to express that opinion and, where 
+appropriate, have it considered by the community.</p>
+<p>To some the idea of having to establish consensus in a large and distributed team 
+sounds inefficient and frustrating. Don't despair though, The Apache Way has a
+set of simple processes to ensure things proceed at a good pace.</p>
+<p>In ASF projects we don't like to vote. We reserve that for the few things that need 
+official approval for legal or process reasons (e.g. a release or a new committer). 
+Most of the time we work with the consensus building techniques documented below.</p>
+<h3 id="lazy_consensus">Lazy Consensus</h3>
+<p><a href="docs/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building 
+tool we have. Essentially lazy consensus means that you don't need to get explicit
+approval to proceed, but you need to be prepared to listen if someone objects.</p>
+<h3 id="consensus_building">Consensus Building</h3>
+<p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to
+make a proposal to the mailing list and discuss options. There are mechanisms
+for quickly showing your support or otherwise for a proposal and 
+<a href="docs/governance/voting.html">building consensus</a> amongst the community.</p>
+<p>Once there is a consensus people can proceed with the work under the <a href="docs/governance/lazyConsensus.html">lazy 
+consensus</a> model.</p>
+<h3 id="voting">Voting</h3>
+<p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
+have a measurable consensus. For example, when [voting][5] in new committers or 
+to approve a release. </p>
   </div>
 
   <div id="footer">