You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@labs.apache.org by bu...@apache.org on 2014/06/15 18:56:00 UTC

svn commit: r912646 - in /websites/staging/labs/trunk/content: ./ bylaws.html

Author: buildbot
Date: Sun Jun 15 16:56:00 2014
New Revision: 912646

Log:
Staging update by buildbot for labs

Modified:
    websites/staging/labs/trunk/content/   (props changed)
    websites/staging/labs/trunk/content/bylaws.html

Propchange: websites/staging/labs/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jun 15 16:56:00 2014
@@ -1 +1 @@
-1597996
+1602733

Modified: websites/staging/labs/trunk/content/bylaws.html
==============================================================================
--- websites/staging/labs/trunk/content/bylaws.html (original)
+++ websites/staging/labs/trunk/content/bylaws.html Sun Jun 15 16:56:00 2014
@@ -247,14 +247,7 @@
 
         <h2>Guidelines Rationale</h2>
         <p>
-            The voting guidelines are not established to induce rigid process, 
-            but rather to avoid that a single negative vote can act as a veto. We 
-            expect that most votes will resolve themselves with lazy consensus 
-            (three +1 and no -1). In case a -1 appears, it is good practice to 
-            try to reach a compromise that results in the removal of such -1. In 
-            case such a  compromise cannot be reached, the majority vote takes 
-            place. Established social practices throughout the foundation suggest 
-            that such cases are very rare.
+            Lazy consensus (72 hour) is used to make it easy to create a lab.
         </p>
 
         <p>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@labs.apache.org
For additional commands, e-mail: commits-help@labs.apache.org