svn commit: r791015 - in /websites/production/community: ./ content/committers/lazyConsensus.html

[rg...@apache.org]

Author: rgardler
Date: Wed Jun 15 19:21:26 2011
New Revision: 791015

Log:
Publishing merge to community site by rgardler

Modified:
    websites/production/community/   (props changed)
    websites/production/community/content/committers/lazyConsensus.html

Propchange: websites/production/community/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Jun 15 19:21:26 2011
@@ -1,2 +1,2 @@
 /websites/staging/comdev/trunk:779592-779702
-/websites/staging/community/trunk:779703-791012
+/websites/staging/community/trunk:779703-791014

Modified: websites/production/community/content/committers/lazyConsensus.html
==============================================================================
--- websites/production/community/content/committers/lazyConsensus.html (original)
+++ websites/production/community/content/committers/lazyConsensus.html Wed Jun 15 19:21:26 2011
@@ -126,9 +126,10 @@ of intent) early is likely to be greeted
 and cares.</p>
 <h2 id="stating_lazy_consensus">Stating Lazy Consensus</h2>
 <p>Sometimes a member of the community will believe a specific action is the correct 
-one for the community but are not sure enough to proceed with the work under the 
-lazy consensus model. In these circumstances they can state Lazy Consensus is in 
-operation.</p>
+one for the project but are not sure that there will be consensus. In these 
+circumstances they may not wish to proceed with the work without giving the 
+community an opportunity to feedback. In these circumstances they can make the 
+proposal and state Lazy Consensus is in operation.</p>
 <p>What this means is that they make a proposal and state that they will start 
 implementing it in 72 hours unless someone objects. 72 hours is chosen because
 it accounts for different timezones and non-apache commitments.</p>