community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r791014 - /websites/staging/community/trunk/content/committers/lazyConsensus.html
Date Wed, 15 Jun 2011 19:21:16 GMT
Author: buildbot
Date: Wed Jun 15 19:21:15 2011
New Revision: 791014

Staging update by buildbot


Modified: websites/staging/community/trunk/content/committers/lazyConsensus.html
--- websites/staging/community/trunk/content/committers/lazyConsensus.html (original)
+++ websites/staging/community/trunk/content/committers/lazyConsensus.html Wed Jun 15 19:21:15
@@ -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 
+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>

View raw message