accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From md...@apache.org
Subject svn commit: r1574612 - /accumulo/site/trunk/content/bylaws.mdtext
Date Wed, 05 Mar 2014 18:44:59 GMT
Author: mdrob
Date: Wed Mar  5 18:44:59 2014
New Revision: 1574612

URL: http://svn.apache.org/r1574612
Log:
Improve descriptions of Committer/PMC; change business days to real days.

Modified:
    accumulo/site/trunk/content/bylaws.mdtext

Modified: accumulo/site/trunk/content/bylaws.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/bylaws.mdtext?rev=1574612&r1=1574611&r2=1574612&view=diff
==============================================================================
--- accumulo/site/trunk/content/bylaws.mdtext (original)
+++ accumulo/site/trunk/content/bylaws.mdtext Wed Mar  5 18:44:59 2014
@@ -16,8 +16,6 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-# Apache Accumulo Project Bylaws
-
 This is version 0 of the bylaws. This draft has not yet been accepted by the Accumulo Project
and only exists for voting purposes.
 
 # Introduction
@@ -50,21 +48,36 @@ A committer is considered emeritus, mean
 
 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.
 
-All Apache committers are required to have a signed [Contributor License Agreement](http://www.apache.org/licenses/icla.txt)
on file with the Apache Software Foundation. There is a [Committer FAQ](http://www.apache.org/dev/committers.html)
which provides more details on the requirements for committers.
+All Apache committers are required to have a signed [Contributor License Agreement](http://www.apache.org/licenses/icla.txt)
(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 [Committer
FAQ](http://www.apache.org/dev/committers.html) which provides more details on the requirements
for committers. 
 
 It is the custom of the Accumulo project to also invite each committer to become a member
of the Accumulo PMC.
 
 ## Project Management Committee
 
-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:
+The role of the PMC from a Foundation perspective is [oversight](http://apache.org/foundation/how-it-works.html#pmc).
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.
+
+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.
+
+The responsibilities of the PMC include:
 
-* Deciding what is distributed as products of the Apache Accumulo project. In particular
all releases must be approved by the PMC.
-* Maintaining the project's shared resources, including the codebase repository, mailing
lists, and websites.
+* Deciding what is distributed as products of the Apache Accumulo project.
+* Maintaining the project's shared resources, including the code repository, mailing lists,
and websites.
 * Speaking on behalf of the project.
 * Resolving license disputes regarding products of the project.
 * Nominating new PMC members and committers.
 * Maintaining these bylaws and other guidelines of the project.
 
+In particular, PMC members must understand both our project's criteria and ASF criteria for
voting on a [release](http://www.apache.org/dev/release.html#management).
+
 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.
 
 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.
@@ -128,7 +141,7 @@ This section describes the various actio
     <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>



Mime
View raw message