community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgard...@apache.org
Subject svn commit: r791010 - in /websites/production/community: ./ content/committers/lazyConsensus.html
Date Wed, 15 Jun 2011 18:59:59 GMT
Author: rgardler
Date: Wed Jun 15 18:59:59 2011
New Revision: 791010

Log:
Publishing merge to community site by rgardler

Modified:
    websites/production/community/   (props changed)
    websites/production/community/content/committers/lazyConsensus.html

Propchange: websites/production/community/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Jun 15 18:59:59 2011
@@ -1,2 +1,2 @@
 /websites/staging/comdev/trunk:779592-779702
-/websites/staging/community/trunk:779703-791007
+/websites/staging/community/trunk:779703-791009

Modified: websites/production/community/content/committers/lazyConsensus.html
==============================================================================
--- websites/production/community/content/committers/lazyConsensus.html (original)
+++ websites/production/community/content/committers/lazyConsensus.html Wed Jun 15 18:59:59
2011
@@ -135,7 +135,7 @@ it accounts for different timezones and 
 <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 
-since it allows space and time to <a href="/rave/docs/governance/consensusBuilding.html">express
support or objections</a> and corrections to 
+since it allows space and time to <a href="/committers/consensusBuilding.html">express
support or objections</a> and corrections to 
 the proposal before work begins. </p>
 <h2 id="silence_is_consent">Silence is consent</h2>
 <p>People may choose to indicate their support for the actions taken with a +1 



Mime
View raw message