svn commit: r1169709 - /incubator/ooo/site/trunk/content/openofficeorg/docs/governance/lazyConsensus.mdtext

[ma...@apache.org]

Author: marcus
Date: Mon Sep 12 12:26:05 2011
New Revision: 1169709

URL: http://svn.apache.org/viewvc?rev=1169709&view=rev
Log:
CMS commit to openofficeorg by marcus

Modified:
    incubator/ooo/site/trunk/content/openofficeorg/docs/governance/lazyConsensus.mdtext

Modified: incubator/ooo/site/trunk/content/openofficeorg/docs/governance/lazyConsensus.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/docs/governance/lazyConsensus.mdtext?rev=1169709&r1=1169708&r2=1169709&view=diff
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/docs/governance/lazyConsensus.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/docs/governance/lazyConsensus.mdtext Mon Sep 12 12:26:05 2011
@@ -53,7 +53,10 @@ 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
-it accounts for different timezones and non-apache commitments.
+it accounts for different timezones and non-apache commitments. If the 72 hours are
+touching a weekend it would be wise to extend the timeframe a bit. This will ensure
+that people can participate in the proposal even when they were offline over the
+weekend.
 
 In this approach the original proposal is not insisting that there is a discussion
 around their proposal, nor are they requesting that the community explicitly