rave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r788663 - /websites/staging/rave/trunk/content/rave/get-involved.html
Date Fri, 22 Apr 2011 21:38:18 GMT
Author: buildbot
Date: Fri Apr 22 21:38:17 2011
New Revision: 788663

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:38:17 2011
@@ -102,19 +102,19 @@ set of simple processes to ensure things
 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 
+<p><a href="/rave/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

+<a href="/rave/docs/governance/consensusBuilding.html">building consensus</a>
amongst the community.</p>
+<p>Once there is a consensus people can proceed with the work under the <a href="/rave/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 
+have a measurable consensus. For example, when <a href="/rave/docs/governance/voting.html">voting</a>
in new committers or 
 to approve a release. </p>
   </div>
 



Mime
View raw message