forrest-svn mailing list archives

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

Add words about legal shelter.

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 23:27:58 2004
@@ -84,7 +84,7 @@
           invited to become committers. After a successful vote, they are
           provided with a user account and commit access to the source
           repository, which enables them to be far more productive.
-          This is 
+          This is recognition of long term commitment - 
           <link href="">meritocracy</link>
           - they are given more responsibility and can do more work.
         (more <link href="">info</link>)
@@ -92,7 +92,11 @@
           All Apache committers are required to have a signed Contributor
           License Agreement (CLA) recorded on file with the Apache Software
-          Foundation. The
+          Foundation. One of the
+          <link href="">reasons</link>
+           that the ASF was created was to "provide a means for individual
+           volunteers to be sheltered from legal suits directed at the
+           Foundation's projects". The
           <link href="">Committer FAQ</link>
           provides more details about the requirements for committers.
@@ -109,7 +113,7 @@
         Apache Forrest codebase and community.
         (more <link href="">info</link>)
-        <p>The Project Management Committer responsibilities include:</p>
+        <p>The Project Management Committee responsibilities include:</p>
           <li>Keeping oversight of the commit log messages and ensuring that
            the codebase does not have copyright and license issues.</li>
@@ -117,6 +121,7 @@
             including other supporting software that is re-distributed.</li>
           <li>Deciding what is distributed as products of the project.
             In particular all releases must be approved by the PMC.</li>
+          <li>Guide the direction of the project.</li>
           <li>Maintaining the project's shared resources, including the
             codebase repository, mailing lists, websites.</li>
           <li>Speaking on behalf of the project.</li>
@@ -138,12 +143,6 @@
           to the board. Ultimately, however, it is the board's responsibility
           who it chooses to appoint as the PMC chair.
-        <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;
-           etc.).
-        </fixme>

View raw message