Author: buildbot
Date: Wed Mar 5 18:45:05 2014
New Revision: 900148
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 5 18:45:05 2014
@@ -1 +1 @@
-1574574
+1574612
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 5 18:45:05 2014
@@ -91,8 +91,7 @@
<div id="content">
<h1 class="title">Apache Accumulo Bylaws</h1>
- <h1 id="apache-accumulo-project-bylaws">Apache Accumulo Project Bylaws</h1>
-<p>This is version 0 of the bylaws. This draft has not yet been accepted by
the Accumulo Project and only exists for voting purposes.</p>
+ <p>This is version 0 of the bylaws. This draft has not yet been accepted
by the Accumulo Project and only exists for voting purposes.</p>
<h1 id="introduction">Introduction</h1>
<p>This document defines the bylaws under which the Apache Accumulo project
operates. It defines the roles and responsibilities of the project, who may
vote, how voting works, how conflicts are resolved, etc.</p>
<p>Accumulo is a project of the <a
href="http://www.apache.org/foundation/";>Apache Software Foundation</a>. The
foundation holds the copyright on Apache code including the code in the
Accumulo codebase. The <a
href="http://www.apache.org/foundation/faq.html";>foundation FAQ</a> explains
the operation and background of the foundation.</p>
@@ -108,18 +107,30 @@
<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>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> on file with the Apache Software Foundation. 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>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 Project Management Committee (PMC) is responsible to the ASF Board of
Directors (âthe Boardâ) for the management and oversight of the Apache
Accumulo codebase. The responsibilities of the PMC include:</p>
+<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
+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
+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>
+<p>The responsibilities of the PMC include:</p>
<ul>
-<li>Deciding what is distributed as products of the Apache Accumulo project.
In particular all releases must be approved by the PMC.</li>
-<li>Maintaining the project's shared resources, including the codebase
repository, mailing lists, and websites.</li>
+<li>Deciding what is distributed as products of the Apache Accumulo
project.</li>
+<li>Maintaining the project's shared resources, including the code repository,
mailing lists, and websites.</li>
<li>Speaking on behalf of the project.</li>
<li>Resolving license disputes regarding products of the project.</li>
<li>Nominating new PMC members and committers.</li>
<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>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>
@@ -166,7 +177,7 @@
<th>Description</th>
<th>Approval</th>
<th>Binding Votes</th>
- <th>Minimum Length (days)</th>
+ <th>Min. Length (days)</th>
<tr><td>Code Change</td>
<td>A change made to a codebase of the project. This includes source code,
documentation, website content, etc.</td>
<td>Lazy approval, moving to consensus approval if a -1 is received.</td>
