incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r795630 - /websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
Date Mon, 12 Sep 2011 12:26:30 GMT
Author: buildbot
Date: Mon Sep 12 12:26:30 2011
New Revision: 795630

Log:
Staging update by buildbot

Modified:
    websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html

Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
(original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/governance/lazyConsensus.html
Mon Sep 12 12:26:30 2011
@@ -107,7 +107,10 @@ lazy consensus model. In these circumsta
 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>
+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.</p>
 <p>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 
 supports their actions. However, this differs from assuming lazy consensus 



Mime
View raw message