twl         2003/03/25 15:50:44

  Modified:    .        charter.txt
  Log:
  Add committer deactivation wording
  
  Revision  Changes    Path
  1.9       +16 -8     xml-admin/charter.txt
  
  Index: charter.txt
  ===================================================================
  RCS file: /home/cvs/xml-admin/charter.txt,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- charter.txt       19 Mar 2003 19:50:55 -0000      1.8
  +++ charter.txt       25 Mar 2003 23:50:44 -0000      1.9
  @@ -78,9 +78,9 @@
   
   To become a member of the PMC, an individual must be nominated by a
   contributor, unanimously approved by all PMC members, and approved by
  -a two-thirds majority of xml.apache.org committers. In most cases, 
  -developers will have actively contributed to development for at least 
  -six months before being considered for membership on the PMC. 
  +a two-thirds majority of xml.apache.org active committers. In most
  +cases,  developers will have actively contributed to development for
  +at least six months before being considered for membership on the PMC. 
   
   In the unlikely event that a member of the PMC becomes disruptive to
   the process or ceases to make codebase contributions for an extended 
  @@ -92,8 +92,8 @@
   change to the development process necessitates a change to the
   charter. Changes must be unanimously approved by all members of the
   PMC. A contributor may challenge a change to the charter at any time
  -and ask for a vote of all xml.apache.org committers, in which case a
  -two-thirds majority must approve the change.
  +and ask for a vote of all xml.apache.org active committers, in which
  +case a two-thirds majority must approve the change.
   
   SUBPROJECTS
   ===========
  @@ -103,12 +103,12 @@
   for approving its own committers.
   
   A new subproject proposal is submitted to the PMC, and then accepted
  -by a majority xml.apache.org committer vote.
  +by a majority xml.apache.org active committer vote.
   
   A subproject may be removed by unanimous vote of the PMC, subject to the
   approval of the ASF board.  A contributor may challenge the removal of a 
  -subproject at any time and ask for a vote of all committers, in which 
  -case a two-thirds majority must approve the change.
  +subproject at any time and ask for a vote of all active committers, in
  +which case a two-thirds majority must approve the change.
   
   COMMITTERS
   ==========
  @@ -120,6 +120,14 @@
   opposing votes.  In most cases, new committers will already be
   participating in the development process by submitting suggestions
   and/or fixes via the bug report page or mailing lists.
  +
  +Committers remain active as long as they are contributing code or
  +posting to the subproject mailing lists.  If a committers has neither
  +contributed code nor posted to the subproject mailing lists in 3
  +months, the PMC reps for that subproject will e-mail the committer,
  +the subproject development list, and the PMC mailing list notifying
  +the committer that they are going to be moved to inactive status.  If
  +there is no response in 72 hours, the committer will become inactive.
   
   CONTRIBUTORS
   ============
  
  
  

---------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to