accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r902354 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html
Date Wed, 19 Mar 2014 16:59:35 GMT
Author: buildbot
Date: Wed Mar 19 16:59:34 2014
New Revision: 902354

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 Wed Mar 19 16:59:34 2014
@@ -1 +1 @@
-1579115
+1579297

Modified: websites/staging/accumulo/trunk/content/bylaws.html
==============================================================================
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Wed Mar 19 16:59:34 2014
@@ -110,14 +110,14 @@
 <p>All Apache committers are required to have a signed <a href="http://www.apache.org/licenses/icla.txt">Contributor
License Agreement</a> (CLA) on file with the Apache Software Foundation. Under the terms
of the CLA that all committers must sign, a committer's primary responsibility is to ensure
that all code committed to Apache Accumulo is licensed appropriately and meets those criteria
set forth in the CLA (including both original works and patches committed on behalf of other
contributors). There is a <a href="http://www.apache.org/dev/committers.html">Committer
FAQ</a> which provides more details on the requirements for committers. </p>
 <p>It is the custom of the Accumulo project to also invite each committer to become
a member of the Accumulo PMC.</p>
 <h2 id="project-management-committee">Project Management Committee</h2>
-<p>The role of the PMC from a Foundation perspective is <a href="http://apache.org/foundation/how-it-works.html#pmc">oversight</a>.
The main
-role of the PMC is not code and not coding - but to ensure that all legal
+<p>The role of the PMC, from a Foundation perspective, is <a href="http://apache.org/foundation/how-it-works.html#pmc">oversight</a>.
The main
+role of the PMC is not code and not coding, but to ensure that all legal
 issues are addressed, that procedure is followed, and that each and every
 release is the product of the community as a whole. That is key to our
 litigation protection mechanisms.</p>
-<p>Secondly the role of the PMC is to further the long term development and
+<p>Secondly, the role of the PMC is to further the long-term development and
 health of the community as a whole, and to ensure that balanced and wide
-scale peer review and collaboration does happen. Within the ASF we worry
+scale peer review and collaboration does happen. Within the ASF, we worry
 about any community which centers around a few individuals who are working
 virtually uncontested. We believe that this is detrimental to quality,
 stability, and robustness of both code and long term social structures.</p>
@@ -162,13 +162,13 @@ stability, and robustness of both code a
 <tr><td>Consensus Approval</td>
     <td>A consensus approval vote passes with 3 binding +1 votes and no binding vetoes.</td>
 <tr><td>Majority Approval</td>
-    <td>A majority approval vote passes with 3 binding +1 votes and more binding +1
votes that -1 votes.</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>
 </table>
 
 <h2 id="vetoes">Vetoes</h2>
-<p>A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied
by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed
by anyone who has a binding vote. This does not necessarily signify agreement with the veto
- merely that the veto is valid.</p>
+<p>A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied
by a valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed
by anyone who has a binding vote. This does not necessarily signify agreement with the veto,
but merely that the veto is valid.</p>
 <p>If you disagree with a valid veto, you must lobby the person casting the veto to
withdraw his or her 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>



Mime
View raw message