svn commit: r900138 - in /websites/staging/accumulo/trunk/content: ./ bylaws.html

[bu...@apache.org]

Author: buildbot
Date: Wed Mar  5 17:08:14 2014
New Revision: 900138

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 17:08:14 2014
@@ -1 +1 @@
-1574568
+1574574

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 17:08:14 2014
@@ -112,12 +112,14 @@
 <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>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.
-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.</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>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>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>