forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r406561 - /forrest/trunk/site-author/content/xdocs/guidelines.xml
Date Mon, 15 May 2006 07:00:19 GMT
Author: crossley
Date: Mon May 15 00:00:18 2006
New Revision: 406561

Link to an important email thread by Roy explaining PMCs and decision making.
Add some clarifications resulting from various recent discussions.
Reinforce that for us "committer" is equivalent to "PMC member".
Explain that individuals are not expected to be involved in every aspect.
Add note about looking out for holidays when voting.


Modified: forrest/trunk/site-author/content/xdocs/guidelines.xml
--- forrest/trunk/site-author/content/xdocs/guidelines.xml (original)
+++ forrest/trunk/site-author/content/xdocs/guidelines.xml Mon May 15 00:00:18 2006
@@ -98,7 +98,7 @@
     <link href="">PMC
member</link> |
     <link href="">ASF
-    <p>The current Apache Forrest committers and PMC members are
+    <p>The Apache Forrest committers and PMC members are
       <link href="site:who">listed</link>.
@@ -113,13 +113,23 @@
       See explanation of the role of the PMC in that resolution and also the
       <link href="">ASF Bylaws</link>
-    <link href="">How-it-works</link>.
+      <link href="">How-it-works</link>
+      and this
+      <link href="">mail
+    </p>
+    <p id="pmc-committers">
+      At Forrest, the group of PMC members essentially equates to the group of
+      committers. We encourage all committers to be PMC members. See explanation
+      <link href="#elect">below</link>. See the "<link href="site:who">who
we are</link>"
+      page for explanation of why some committers from the old project are not
+      PMC members.
       PMC members can be as active as they choose, with no pressure from the
       project. People can be quiet and speak up occasionally when they see a
       topic that motivates them enough to contribute to the discussion or to
-      cast a vote.
+      cast a vote. Individual PMC members do not need to be involved in every
+      aspect of the project. As a group, the PMC will maintain sufficient oversight.
     <p>The responsibilities of the PMC include:</p>
@@ -127,7 +137,10 @@
       ASF Bylaws, and with the ASF documentation and procedures
       in general.</li>
       <li>Keep oversight of the commit log messages and ensure that
-       the codebase does not have copyright and license issues.</li>
+       the codebase does not have copyright and license issues, and that the
+       project is heading in the desired direction.</li>
+      <li>Keep oversight of the mailing lists and community to ensure that
+       the <link href="#way">open development</link> ideals are upheld.</li>
       <li>Resolve license disputes regarding products of the project,
         including other supporting software that is re-distributed.</li>
       <li>Decide what is distributed as products of the project.
@@ -151,8 +164,9 @@
       consensus approval of the PMC members.
-      A PMC member is considered
-      "emeritus" by their own declaration
+      A PMC member is considered "emeritus" by their own declaration, e.g.
+      perhaps personal reasons. Please send a note to the PMC private mail list
+      and we will follow up to request acknowledgement of the Board.
       An emeritus member may
       request reinstatement to the PMC. Such reinstatement is subject to
       consensus approval of the PMC members. Membership of the PMC can be
@@ -195,15 +209,33 @@
     <section id="elect">
       <title>Electing new committers and PMC members</title>
+        When we see new people who are committed and consistent, we will discuss
+        each case to ensure that the PMC is in agreement. See the list of
+        <link href="site:committed">qualities</link> that we look for.
         We conduct the vote on the private PMC mailing list to enable a frank
-        discussion.
+        discussion and so that we do not conduct public discussions about people.
+      </p>
+      <p>
         In most cases we will be inviting people to go straight from developer
         to PMC member, i.e. they simultaneously become committer and PMC
-        member. However, there may be extraordinary cases where we want
-        limited work-related commit access (not also a PMC member).
+        member. We always want new committers to also be PMC members. Otherwise
+        they do not have a binding vote and so we would create classes of
+        committers. Another issue is
+        <link href="">indemnification</link>.
+        However, when we invite a new committer we do let them choose not to be
+        on the PMC, though we do not encourage that.
+      </p>
+      <p>
+        However, there may be extraordinary cases where we want
+        limited work-related commit access and so the committer is not also a
+        PMC member (e.g. perhaps temporary access for
+        <link href="">GSoC</link>).
         This will be resolved during the discussion and vote.
-        Notes about this process are in the "committers" svn in the
-        pmc/forrest/ directory.
+      </p>
+      <p>
+        PMC members can also see further
+        <link href="">notes</link>
+        about the process of electing new people.
@@ -528,6 +560,11 @@
         Votes relating to code changes are not subject to a strict timetable,
         but should be made as timely as possible.
+      <p>
+        Be careful about holidays when calling a vote. This is hard when we do
+        not know customs in every part of the world. So if someone knows that
+        there is a problem with the vote timing, then please say so.
+      </p>
     <section id="procedure">
@@ -535,7 +572,7 @@
         Discussion about the topic would have already happened in a [Proposal]
         email thread to express the issues and opinions. The [Vote] thread is
-        to ratify the proposal.
+        to ratify the proposal if that is felt to be necessary.
         The instigator sends the Vote email to the dev mailing list.

View raw message