You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by rg...@apache.org on 2011/06/15 21:21:06 UTC
svn commit: r1136155 -
/comdev/site/trunk/content/committers/lazyConsensus.mdtext
Author: rgardler
Date: Wed Jun 15 19:21:06 2011
New Revision: 1136155
URL: http://svn.apache.org/viewvc?rev=1136155&view=rev
Log:
Clarify when and how to state lazy consensus
Modified:
comdev/site/trunk/content/committers/lazyConsensus.mdtext
Modified: comdev/site/trunk/content/committers/lazyConsensus.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/committers/lazyConsensus.mdtext?rev=1136155&r1=1136154&r2=1136155&view=diff
==============================================================================
--- comdev/site/trunk/content/committers/lazyConsensus.mdtext (original)
+++ comdev/site/trunk/content/committers/lazyConsensus.mdtext Wed Jun 15 19:21:06 2011
@@ -47,9 +47,10 @@ and cares.
## Stating Lazy Consensus
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.
+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.
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