svn commit: r849526 - in /websites/staging/openoffice/trunk/content: ./ community-faqs.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb  5 23:25:33 2013
New Revision: 849526

Log:
Staging update by buildbot for openoffice

Modified:
    websites/staging/openoffice/trunk/content/   (props changed)
    websites/staging/openoffice/trunk/content/community-faqs.html

Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb  5 23:25:33 2013
@@ -1 +1 @@
-1441662
+1442795

Modified: websites/staging/openoffice/trunk/content/community-faqs.html
==============================================================================
--- websites/staging/openoffice/trunk/content/community-faqs.html (original)
+++ websites/staging/openoffice/trunk/content/community-faqs.html Tue Feb  5 23:25:33 2013
@@ -109,19 +109,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>
 <h2 id="what-is-lazy-consensus">What is "Lazy Consensus"?</h2>
-<p><a href="/openofficeorg/docs/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building 
+<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>
 <h2 id="consensus-building">Consensus Building</h2>
 <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="/openofficeorg/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="/openofficeorg/docs/governance/lazyConsensus.html">lazy 
+<a href="/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="/docs/governance/lazyConsensus.html">lazy 
 consensus</a> model.</p>
 <h2 id="what-about-voting">What about voting?</h2>
 <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to 
-have a measurable consensus. For example, when <a href="/openofficeorg/docs/governance/voting.html">voting</a> in new committers or 
+have a measurable consensus. For example, when <a href="/docs/governance/voting.html">voting</a> in new committers or 
 to approve a release. </p>
   </div>