svn commit: r314812 - /forrest/site/guidelines.html

[cr...@apache.org]

Author: crossley
Date: Wed Oct 12 00:34:16 2005
New Revision: 314812

URL: http://svn.apache.org/viewcvs?rev=314812&view=rev
Log:
Automatic publish from forrestbot

Modified:
    forrest/site/guidelines.html

Modified: forrest/site/guidelines.html
URL: http://svn.apache.org/viewcvs/forrest/site/guidelines.html?rev=314812&r1=314811&r2=314812&view=diff
==============================================================================
--- forrest/site/guidelines.html (original)
+++ forrest/site/guidelines.html Wed Oct 12 00:34:16 2005
@@ -197,6 +197,9 @@
 <li>
 <a href="#report">Quarterly reports to ASF Board</a>
 </li>
+<li>
+<a href="#elect">Electing new committers and PMC members</a>
+</li>
 </ul>
 </li>
 <li>
@@ -393,10 +396,23 @@
         <a href="http://www.apache.org/foundation/board/calendar.html">
         board meeting</a>. Our reporting schedule is: Feb, May, Aug, Nov.
       </p>
+<a name="N100C6"></a><a name="elect"></a>
+<h3 class="underlined_5">Electing new committers and PMC members</h3>
+<p>
+        We conduct the vote on the private PMC mailing list to enable a frank
+        discussion.
+        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).
+        This will be resolved during the discussion and vote.
+        Notes about this process are in the "committers" svn in the
+        pmc/forrest/ directory.
+      </p>
 </div>
 
   
-<a name="N100C7"></a><a name="decision"></a>
+<a name="N100D1"></a><a name="decision"></a>
 <h2 class="underlined_10">Decision making</h2>
 <div class="section">
 <p>
@@ -410,7 +426,7 @@
       Most day-to-day operations do not require explicit voting - just get on
       and do the work. See the "Lazy approval" type described below.
     </p>
-<a name="N100D3"></a><a name="voting"></a>
+<a name="N100DD"></a><a name="voting"></a>
 <h3 class="underlined_5">Voting</h3>
 <p>
         Certain actions and decisions regarding the project are made by votes
@@ -499,7 +515,7 @@
         typically take the form of a veto (-1) in reply to the commit message
         sent when the commit is made.
       </p>
-<a name="N10137"></a><a name="approvals"></a>
+<a name="N10141"></a><a name="approvals"></a>
 <h3 class="underlined_5">Types of approval</h3>
 <p>
         Different actions require different types of approval:
@@ -565,7 +581,7 @@
 </tr>
       
 </table>
-<a name="N1018A"></a><a name="veto"></a>
+<a name="N10194"></a><a name="veto"></a>
 <h3 class="underlined_5">Vetoes</h3>
 <p>
         A valid veto cannot be over-ruled, it can only be withdrawn by its issuer.
@@ -587,7 +603,7 @@
         If a veto is not withdrawn, the action that has been vetoed must
         be reversed in a timely manner.
       </p>
-<a name="N1019D"></a><a name="actions"></a>
+<a name="N101A7"></a><a name="actions"></a>
 <h3 class="underlined_5">Actions</h3>
 <p>
         This section describes the various actions which are undertaken within
@@ -751,7 +767,7 @@
 </tr>
       
 </table>
-<a name="N10299"></a><a name="timeframe"></a>
+<a name="N102A3"></a><a name="timeframe"></a>
 <h3 class="underlined_5">Voting timeframes</h3>
 <p>
         Votes are normally open for a period of one week to allow all active voters
@@ -761,7 +777,7 @@
         Votes relating to code changes are not subject to a strict timetable,
         but should be made as timely as possible.
       </p>
-<a name="N102A3"></a><a name="procedure"></a>
+<a name="N102AD"></a><a name="procedure"></a>
 <h3 class="underlined_5">Voting procedure</h3>
 <p>
         Discussion about the topic would have already happened in a [Proposal]
@@ -780,7 +796,7 @@
         At the end of the vote period, the instigator tallies the number of
         final votes and reports the results.
       </p>
-<a name="N102B7"></a><a name="ultimatum"></a>
+<a name="N102C1"></a><a name="ultimatum"></a>
 <h3 class="underlined_5">Ultimatum and breakdown</h3>
 <p>
         For breakdown situations and those requiring unanimous consensus,
@@ -791,7 +807,7 @@
 </div>
 
   
-<a name="N102C2"></a><a name="communication"></a>
+<a name="N102CC"></a><a name="communication"></a>
 <h2 class="underlined_10">Communication channels</h2>
 <div class="section">
 <p>
@@ -819,7 +835,7 @@
 </div>
 
   
-<a name="N102D5"></a><a name="code"></a>
+<a name="N102DF"></a><a name="code"></a>
 <h2 class="underlined_10">Code management</h2>
 <div class="section">
 <p>