Author: buildbot Date: Tue May 6 19:37:19 2014 New Revision: 908238 Log: Staging update by buildbot for labs
Modified: websites/staging/labs/trunk/content/ (props changed) websites/staging/labs/trunk/content/faq.html Propchange: websites/staging/labs/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Tue May 6 19:37:19 2014 @@ -1 +1 @@ -1592336 +1592846 Modified: websites/staging/labs/trunk/content/faq.html ============================================================================== --- websites/staging/labs/trunk/content/faq.html (original) +++ websites/staging/labs/trunk/content/faq.html Tue May 6 19:37:19 2014 @@ -102,7 +102,7 @@ The Apache Labs SVN repository is write-accessible to all apache committers, so, in theory, anyone of them can just go ahead and create a lab for themselves. The Apache Labs <a href="bylaws.html">bylaws</a> state that a lab needs to be approved by lazy - consensus (three +1 and no -1 in a 72 hour period) of + consensus in a 72 hour period of the <a href="team.html">Apache Labs PMC</a> before it can be established. This is done to avoid that committers use labs as their personal 'dumping' grounds and that labs remain topic-specific. Also allows the PMC to force the committers to express their intention --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@labs.apache.org For additional commands, e-mail: commits-h...@labs.apache.org