forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: rev 21155 - forrest/trunk/src/documentation/content/xdocs
Date Sun, 13 Jun 2004 05:57:58 GMT
Author: crossley
Date: Sat Jun 12 22:57:57 2004
New Revision: 21155

Refine the "committers" section after discussion on forrest-dev

Modified: forrest/trunk/src/documentation/content/xdocs/guidelines.xml
--- forrest/trunk/src/documentation/content/xdocs/guidelines.xml	(original)
+++ forrest/trunk/src/documentation/content/xdocs/guidelines.xml	Sat Jun 12 22:57:57 2004
@@ -74,7 +74,7 @@
       <section id="committers">
-        <title>Committers</title>
+        <title>Project Management Committers</title>
           When developers remain with the project and demonstrate commitment
           to the project in various ways, then they will be noticed and
@@ -86,14 +86,6 @@
           - they are given more responsibility and can do more work.
-          The responsibilities of committers include:
-          </p>
-        <ul>
-          <li>Ensuring that they do not add code that has copyright and
-           license issues.</li>
-          <li>Keeping oversight of the commit log messages.</li>
-        </ul>
-        <p>
           All Apache committers are required to have a signed Contributor
           License Agreement (CLA) recorded on file with the Apache Software
           Foundation. The
@@ -106,14 +98,17 @@
         <title>Project Management Committee (PMC)</title>
         From a project management perspective, and as defined by the
-        <link href="">ASF bylaws</link>,
-        the project committers form the PMC. The committee is responsible
+        <link href="">ASF bylaws</link>,
+        the project committers form the Project Management Committee.
+        The PMC is responsible
         to the Board and the ASF for the management and oversight of the
         Apache Forrest codebase and community.
         (more <link href="">info</link>)
-        <p>The PMC responsibilities include:</p>
+        <p>The Project Management Committer responsibilities include:</p>
+          <li>Keeping oversight of the commit log messages and ensuring that
+           the codebase does not have copyright and license issues.</li>
           <li>Resolving license disputes regarding products of the project,
             including other supporting software that is re-distributed.</li>
           <li>Deciding what is distributed as products of the project.
@@ -139,7 +134,7 @@
           to the board. Ultimately, however, it is the board's responsibility
           who it chooses to appoint as the PMC chair.
-        <fixme author="anybody">
+        <fixme author="open">
           Add the reasons why committers would want to be on the PMC
           (e.g. legal protection; guide the direction of the project;
            recognition of a long term commitment;
@@ -152,7 +147,7 @@
       <title>Decision making</title>
       <section id="voting">
         <title>Voting procedures</title>
-        <fixme author="anybody">
+        <fixme author="open">
           Add content, probably borrow from other projects,
           like Ant and Incubator. Define +1, 0, -1, etc.
           Define situations that require voting (e.g. technical issues,

View raw message