Author: buildbot
Date: Thu Mar 20 19:40:11 2014
New Revision: 902579
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 Thu Mar 20 19:40:11 2014
@@ -1 +1 @@
-1579720
+1579722
Modified: websites/staging/accumulo/trunk/content/bylaws.html
==============================================================================
--- websites/staging/accumulo/trunk/content/bylaws.html (original)
+++ websites/staging/accumulo/trunk/content/bylaws.html Thu Mar 20 19:40:11 2014
@@ -104,8 +104,8 @@
<h2 id="contributors">Contributors</h2>
<p>All of the volunteers who are contributing time, code, documentation, or
resources to the Accumulo project are considered contributors. A contributor
that makes sustained, welcome contributions to the project may be invited to
become a committer, though the exact timing of such invitations depends on many
factors.</p>
<h2 id="committers">Committers</h2>
-<p>The project's committers are responsible for the project's technical
management. Committers have write access to the project's code repositories and
may cast binding votes on any technical discussion regarding Accumulo.
Committer access is by invitation only and must be approved by consensus
approval of the active PMC members. Upon acceptance of the invitation to become
a committer, it is the accepting memberâs responsibility to update his/her
status on the Accumulo web page accordingly.</p>
-<p>A committer is considered emeritus, meaning inactive, by his or her own
declaration or by not reviewing patches or committing patches to the project
for over six months. Emeritus members will be recognized by the PMC on the
Accumulo web page, in honor of their past contributions. Emeritus members
retain all voting and commit rights associated with their former designation
and can move themselves out of emeritus status by sending an announcement of
their return to the developer mailing list. It will be the returning member's
responsibility to update his/her status on the web page accordingly.</p>
+<p>The project's committers are responsible for the project's technical
management. Committers have write access to the project's code repositories and
may cast binding votes on any technical discussion regarding Accumulo.
Committer access is by invitation only and must be approved by consensus
approval of the active PMC members. Upon acceptance of the invitation to become
a committer, it is the accepting memberâs responsibility to update their
status on the Accumulo web page accordingly.</p>
+<p>A committer is considered emeritus, meaning inactive, by their own
declaration or by not reviewing patches or committing patches to the project
for over six months. Emeritus members will be recognized by the PMC on the
Accumulo web page, in honor of their past contributions. Emeritus members
retain all voting and commit rights associated with their former designation
and can move themselves out of emeritus status by sending an announcement of
their return to the developer mailing list. It will be the returning member's
responsibility to update their status on the web page accordingly.</p>
<p>An emeritus committerâs commit access may be disabled as part of routine
security. Access shall not be removed without notifying the committer, and
access shall be maintained if the committer wishes to leave it active. A
committerâs commit access shall be reactivated upon the committerâs request
to the PMC.</p>
<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>
@@ -131,8 +131,8 @@ stability, and robustness of both code a
<li>Maintaining these bylaws and other guidelines of the project.</li>
</ul>
<p>In particular, PMC members must understand both our project's criteria and
ASF criteria for voting on a <a
href="http://www.apache.org/dev/release.html#management";>release</a>.</p>
-<p>Membership of the PMC is by invitation only and must be approved by a
consensus approval of active PMC members. Upon acceptance of the invitation to
become a PMC member, it is the accepting memberâs responsibility to update
his/her status on the Accumulo web page accordingly.</p>
-<p>A PMC member is considered emeritus, meaning inactive, by his or her own
declaration or by not contributing in any form to the project for over six
months. Emeritus members will be recognized by the PMC on the Accumulo web
page, in honor of their past contributions. Emeritus members retain all voting
and commit rights associated with their former designation and can move
themselves out of emeritus status by sending an announcement of their return to
the developer mailing list. It will be the returning member's responsibility to
update his/her status on the web page accordingly.</p>
+<p>Membership of the PMC is by invitation only and must be approved by a
consensus approval of active PMC members. Upon acceptance of the invitation to
become a PMC member, it is the accepting memberâs responsibility to update
their status on the Accumulo web page accordingly.</p>
+<p>A PMC member is considered emeritus, meaning inactive, by their own
declaration or by not contributing in any form to the project for over six
months. Emeritus members will be recognized by the PMC on the Accumulo web
page, in honor of their past contributions. Emeritus members retain all voting
and commit rights associated with their former designation and can move
themselves out of emeritus status by sending an announcement of their return to
the developer mailing list. It will be the returning member's responsibility to
update their status on the web page accordingly.</p>
<p>The chair of the PMC is appointed by the ASF board. The chair is an office
holder of the Apache Software Foundation (Vice President, Apache Accumulo) and
has primary responsibility to the board for the management of the projects
within the scope of the Accumulo PMC. The chair reports to the board quarterly
on developments within the Accumulo project.</p>
<p>When the current chair of the PMC resigns, the PMC votes to recommend a new
chair using consensus approval, but the decision must be ratified by the Apache
board.</p>
<h2 id="release-manager">Release Manager</h2>
@@ -181,7 +181,7 @@ stability, and robustness of both code a
<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, 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>
+<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>
<table>
