accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r906152 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Date Mon, 14 Apr 2014 15:55:08 GMT
Author: buildbot
Date: Mon Apr 14 15:55:07 2014
New Revision: 906152

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 14 15:55:07 2014
@@ -1 +1 @@
-1586779
+1587229

Modified: websites/staging/accumulo/trunk/content/bylaws.html
==============================================================================
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Mon Apr 14 15:55:07 2014
@@ -166,7 +166,11 @@ See the <a href="http://www.apache.org/d
 </table>
 
 <p>All participants in the Accumulo project are encouraged to vote. For technical decisions,
only the votes of active committers are binding. Non-binding votes are still useful for those
with binding votes to understand the perception of an action across the wider Accumulo community.
For PMC decisions, only the votes of active PMC members are binding.</p>
-<p>Voting can also be applied to changes to the Accumulo codebase. Please refer to
the Accumulo commit and review standard for details.</p>
+<p>See the <a href="http://accumulo.apache.org/governance/voting.html">voting
page</a> for more details on the mechanics of voting.</p>
+<p><a name="CTR"></a></p>
+<h2 id="commit-then-review-ctr">Commit Then Review (CTR)</h2>
+<p>Voting can also be applied to changes to the Accumulo codebase. Under the Commit
Then Review policy, committers can make changes to the codebase without seeking approval beforehand,
and the changes are assumed to be approved unless an objection is raised. Only if an objection
is raised must a vote take place on the code change.</p>
+<p>For some code changes, committers may wish to get feedback from the community before
making the change. It is acceptable for a committer to seek approval before making a change
if they so desire.</p>
 <h2 id="approvals">Approvals</h2>
 <p>These are the types of approvals that can be sought. Different actions require different
types of approvals.</p>
 <table>
@@ -177,7 +181,7 @@ See the <a href="http://www.apache.org/d
 <tr><td>Majority Approval</td>
     <td>A majority approval vote passes with 3 binding +1 votes and more binding +1
votes than -1 votes.</td>
 <tr><td>Lazy Approval (or Lazy Consensus)</td>
-    <td>An action with lazy approval is implicitly allowed unless a -1 vote is received,
at which time, depending on the type of action, either majority approval or consensus approval
must be obtained.</td>
+    <td>An action with lazy approval is implicitly allowed unless a -1 vote is received,
at which time, depending on the type of action, either majority approval or consensus approval
must be obtained.  Lazy Approval can be either <em>stated</em> or <em>assumed</em>,
as detailed on the [lazy consensus page](http://accumulo.apache.org/governance/lazyConsensus.html).</td>
 </table>
 
 <h2 id="vetoes">Vetoes</h2>
@@ -185,6 +189,7 @@ See the <a href="http://www.apache.org/d
 <p>If you disagree with a valid veto, you must lobby the person casting the veto to
withdraw their veto. If a veto is not withdrawn, the action that has been vetoed must be reversed
in a timely manner.</p>
 <h2 id="actions">Actions</h2>
 <p>This section describes the various actions which are undertaken within the project,
the corresponding approval required for that action and those who have binding votes over
the action. It also specifies the minimum length of time that a vote must remain open, measured
in days. In general, votes should not be called at times when it is known that interested
members of the project will be unavailable.</p>
+<p>For Code Change actions, a committer may choose to employ assumed or stated Lazy
Approval under the <a href="#CTR">CTR</a> policy. Assumed Lazy Approval has no
minimum length of time before the change can be made.</p>
 <table>
 <tr><th>Action</th>
     <th>Description</th>



Mime
View raw message