rave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r788657 - in /websites/staging/rave/trunk/content/rave/docs: ./ governance/ governance/lazyConsensus.html
Date Fri, 22 Apr 2011 20:38:25 GMT
Author: buildbot
Date: Fri Apr 22 20:38:25 2011
New Revision: 788657

Staging update by buildbot


Added: websites/staging/rave/trunk/content/rave/docs/governance/lazyConsensus.html
--- websites/staging/rave/trunk/content/rave/docs/governance/lazyConsensus.html (added)
+++ websites/staging/rave/trunk/content/rave/docs/governance/lazyConsensus.html Fri Apr 22
20:38:25 2011
@@ -0,0 +1,108 @@
+<!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.
+  <link href="/rave/css/rave.css" rel="stylesheet" type="text/css">
+  <title>Lazy Consensus</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <div id="banner">
+    <img alt="Apache Rave (Incubating)" src="/rave/images/logo.png"/>
+    <h1 class="title">Lazy Consensus</h1>
+  </div>
+  <div id="navigation">
+  <h1 id="general">General</h1>
+<li><a href="index.html">About</a></li>
+<li><a href="/projects/rave.html">Incubator page</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
+<h1 id="documentation">Documentation</h1>
+<li><a href="http://cwiki.apache.org/">Wiki</a></li>
+<h1 id="community">Community</h1>
+<li><a href="get-involved.html">Get Involved</a></li>
+<li><a href="mailing-lists.html">Mailing Lists</a></li>
+<li><a href="people.html">People</a></li>
+<h1 id="development">Development</h1>
+<li><a href="source.html">Source Code</a></li>
+<li><a href="https://issues.apache.org/jira/browse/rave">Issue Tracker</a></li>
+<li><a href="https://builds.apache.org/hudson/view/M-R/view/Rave/">Continuous
+<h1 id="asf">ASF</h1>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+  </div>
+  <div id="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="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 id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version
+        <br />
+        Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>

View raw message