community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r790944 - /websites/staging/community/trunk/content/committers/lazyConsensus.html
Date Tue, 14 Jun 2011 20:44:51 GMT
Author: buildbot
Date: Tue Jun 14 20:44:51 2011
New Revision: 790944

Log:
Staging update by buildbot

Added:
    websites/staging/community/trunk/content/committers/lazyConsensus.html

Added: websites/staging/community/trunk/content/committers/lazyConsensus.html
==============================================================================
--- websites/staging/community/trunk/content/committers/lazyConsensus.html (added)
+++ websites/staging/community/trunk/content/committers/lazyConsensus.html Tue Jun 14 20:44:51
2011
@@ -0,0 +1,157 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+<html>
+    <head>
+       <META name="description" content="Apache Community Development"/>
+       <META name="keywords" content="apache, apache community, community development,
opensource"/>
+
+    
+     <META http-equiv="Content-Type" content="text/html; charset=utf-8">
+      <LINK rel="stylesheet" href="/style/compressed.css" type="text/css" media="screen,
projection">
+      <LINK rel="stylesheet" href="/style/style.css" type="text/css" media="screen, projection">
+     <style type="text/css">
+.code {
+  border: 1px dashed #3c78b5;
+  font-size: 11px;
+  font-family: Courier;
+  margin: 10px;
+  margin-left: 0px;
+  line-height: 13px;
+}
+.codeHeader {
+  background-color: #f0f0f0;
+  border-bottom: 1px dashed #3c78b5;
+  padding: 3px;
+  text-align: center;
+}
+.codeContent {
+  text-align: left;
+  background-color: #f0f0f0;
+  padding: 3px;
+}
+
+.preformatted {
+  border: 1px dashed #3c78b5;
+  font-size: 11px;
+  font-family: Courier;
+  margin: 10px;
+  line-height: 13px;
+}
+.preformattedHeader {
+  background-color: #f0f0f0;
+  border-bottom: 1px dashed #3c78b5;
+  padding: 3px;
+  text-align: center;
+}
+.preformattedContent {
+  background-color: #f0f0f0;
+  padding: 3px;
+}
+        </style>
+
+        <LINK rel="SHORTCUT ICON" href="/images/favicon.ico">   
+        <TITLE>Apache Community Development - Lazy Consensus</TITLE>
+    </head>
+
+    <body onload="init()">
+      <div class="container">
+      <HR class="space col">
+      <DIV class="block">
+        <DIV class="column span-24">
+            <DIV id="header">
+                <h1>The Apache Software Foundation<BR />
+                <SPAN class="alt"><small>Meritocracy in Action.</small></SPAN></h1>
+             </DIV>
+          </DIV>
+      </DIV>
+      <HR/>
+
+
+        <TABLE border="0" cellpadding="2" cellspacing="0" width="100%">
+            <TR class="topBar">
+                <td align="left" valign="middle" class="topBarDiv" nowrap="true" width="100%">
+                    &nbsp;<a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/committers">Committers</a>&nbsp;&raquo&nbsp;<a href="/committers/lazyConsensus.html">Lazy
Consensus</a>
+                </td>
+                <td align="right" valign="middle" class="topBarDiv" align="left" nowrap="true">
+                    <A href="http://community.apache.org">Apache Community Development</A>
| <A href="http://mail-archives.apache.org/mod_mbox/community-dev/">Mailling List</A>
+                </td>
+            </TR>
+        </TABLE>
+
+        <TABLE border="0" cellpadding="0" width="100%">
+            <TR>
+                <td align="left" valign="top">
+                  <DIV id="PageContent">        
+                     <DIV class="pagecontent">
+                         <DIV class="wiki-content">
+                          <p>The concept of "Lazy Consensus" is very important in our
project. Lazy
+Consensus means that when you are convinced that you know what the community
+would like to see happen you can simply assume that you already have consensus
+and get on with the work. You don't have to insist people discuss and/or
+approve your plan, and you certainly don't need to call a vote to get approval.
+You just assume you have the communities support unless someone says otherwise.</p>
+<p>We have a time machine (Subversion), this means that as long as you commit 
+(or submit patches) early and often the community has plenty of opportunity 
+to indicate disapproval. If you believe the community will support your action
+you can operate on lazy consensus as long as you are prepared to roll back 
+any work should a valid objection is raised.</p>
+<h2 id="avoiding_unnecessary_discussion">Avoiding Unnecessary Discussion</h2>
+<p>The key thing about lazy consensus is that it's easier for people to agree,
+by doing nothing, than it is to object, which requires an
+alternative to be proposed. This has two effects, firstly people are less 
+likely to object for the sake of it and secondly it cuts down on the amount 
+of unnecessary mail traffic and discussion.</p>
+<p>Lazy consensus means we can avoid waiting for a community based decision 
+before proceeding. However, it does require everyone who cares for the health
+of the project to watch what is happening, as it is happening. Objecting too 
+far down the road will cause upset, but objecting (or asking for clarification 
+of intent) early is likely to be greeted with relief that someone is watching
+and cares.</p>
+<h2 id="stating_lazy_consensus">Stating Lazy Consensus</h2>
+<p>Sometimes a member of the community will believe a specific action is the correct

+one for the community but are not sure enough to proceed with the work under the 
+lazy consensus model. In these circumstances they can state Lazy Consensus is in 
+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>
+<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 
+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 
+mail - quick and easy to read and reassuring for the implementer. However, 
+remember, in a lazy consensus world silence is the equivalent to support. This
+can take some time to get used to.</p>
+                         </DIV>
+                     </DIV>
+                  </DIV>
+                </td>
+            </TR>
+        </TABLE>
+
+        <DIV class="footer">
+            Copyright © 2003-2011, The Apache Software Foundation&nbsp;&nbsp;
+        </DIV>
+
+    </BODY>
+</HTML>



Mime
View raw message