You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-cvs@jakarta.apache.org by ba...@apache.org on 2004/08/18 03:25:41 UTC

cvs commit: jakarta-site2/docs/site management.html

bayard      2004/08/17 18:25:41

  Modified:    xdocs/site management.xml
               docs/site management.html
  Log:
  Update to the Jakarta charter as voted on: http://nagoya.apache.org/eyebrowse/ReadMsg?listName=general@jakarta.apache.org&msgNo=16737
  
  Revision  Changes    Path
  1.8       +27 -25    jakarta-site2/xdocs/site/management.xml
  
  Index: management.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/xdocs/site/management.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- management.xml	17 Mar 2004 08:22:56 -0000	1.7
  +++ management.xml	18 Aug 2004 01:25:40 -0000	1.8
  @@ -25,14 +25,7 @@
     <section name="Project Management Committee Bylaws">
   <p>
   The Project Management Committee (PMC) was formed by the ASF Board
  -in September 1999.  The number of PMC seats is set at seven.  Annually,
  -all seven seats will be up for renewal.  The ASF board will be asked to
  -provide a person or persons to administer the nominations and a
  -subsequent ballot. The administrator(s) will determine the mechanics of
  -the voting procedures.  Any committer to any Jakarta code base will be
  -eligible to vote.  Once the new PMC is in place, the first order of
  -business will be to determine a chairperson from amongst their ranks.
  -The chairperson must then be ratified by resolution of the ASF Board.
  +in September 1999, and is responsible to the ASF Board for oversight of the project.
   The list of current members can be found in our
   <a href="../credits/whoweare.html"> Project Credits</a>.
   </p>
  @@ -48,15 +41,13 @@
   </p>
   
   <p>
  -The PMC is answerable to the Apache Board with its Chairman serving as
  +The PMC is answerable to the ASF Board with its Chairman serving as
   primary liaison.
   </p>
   
   <p>
  -<b>Meetings</b><br/> The PMC <a href="pmc/index.html">meets monthly</a>
  -with a majority of its members to discuss issues, determine strategic
  -direction, and forward progress. These meetings may take place online,
  -via teleconference, or via other means deemed effective by the PMC.
  +<b>Board reports</b><br/> 
  +Quarterly, the PMC is responsible for sending a report to the ASF Board.
   </p>
   
   <p>
  @@ -67,21 +58,32 @@
   </p>
   
   <p>
  -In the event that the number of members drops below 7, the remaining PMC
  -members may choose to elect a new member to serve out the remainder of
  -the annual term.  In order to be elected, a
  -person must have served as a <a href="roles.html">Committer</a> and be
  -nominated by a PMC Member. Once nominated, all of the PMC will vote
  -and those receiving a 3/4 positive vote will become a member.
  +Committers are nominated for the PMC by an existing PMC member and a vote then follows.
   </p>
   
  +<p><b>Voting</b><br /> 
  +Binary PMC voting is a majority-approval variant, with a minimum of 3 +1s 
  +required and at least 3/4 of the votes being +1. This voting style is used 
  +for anything with a yes/no, two-option choice; such as PMC member voting 
  +or changes to this document. 
  +</p>
  +
  +<p>
  +Non-binary voting currently relies on community agreement; such as voting 
  +on the recommendation of a chairman to the board. 
  +</p>
  +
  +<p>A week is deemed a fair length for a vote. </p>
  +
  +<p>Subprojects of Jakarta use other voting variants, described on the <a href="decisions.html">Decisions</a> page. </p> 
  +
   <p>
  -<b>Creation of subprojects</b><br/> PMC members may propose the creation
  -of new subprojects.  Proposals are to contain the scope of the project,
  -identify the initial source from which the project is to be populated,
  -identify the mailing list(s) if any which are to be created, and
  -identify the initial set of committers.  Creation of a new subproject
  -requires approval by 3/4 vote of the PMC.
  +<b>Creation of subprojects</b><br/> 
  +The Apache Incubator is the primary source of new subprojects for Jakarta, 
  +though the PMC may choose to waive this if the Incubator PMC is agreeable.  
  +A common example of this is when an existing subproject contains a component 
  +which wishes to become a full subproject. In such cases, there is unlikely 
  +to be a need for incubation.
   </p>
     </section>
   
  
  
  
  1.94      +24 -26    jakarta-site2/docs/site/management.html
  
  Index: management.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/docs/site/management.html,v
  retrieving revision 1.93
  retrieving revision 1.94
  diff -u -r1.93 -r1.94
  --- management.html	15 Jun 2004 14:22:22 -0000	1.93
  +++ management.html	18 Aug 2004 01:25:41 -0000	1.94
  @@ -224,14 +224,7 @@
           <blockquote>
                                       <p>
   The Project Management Committee (PMC) was formed by the ASF Board
  -in September 1999.  The number of PMC seats is set at seven.  Annually,
  -all seven seats will be up for renewal.  The ASF board will be asked to
  -provide a person or persons to administer the nominations and a
  -subsequent ballot. The administrator(s) will determine the mechanics of
  -the voting procedures.  Any committer to any Jakarta code base will be
  -eligible to vote.  Once the new PMC is in place, the first order of
  -business will be to determine a chairperson from amongst their ranks.
  -The chairperson must then be ratified by resolution of the ASF Board.
  +in September 1999, and is responsible to the ASF Board for oversight of the project.
   The list of current members can be found in our
   <a href="../credits/whoweare.html"> Project Credits</a>.
   </p>
  @@ -245,14 +238,12 @@
   success of the project.
   </p>
                                                   <p>
  -The PMC is answerable to the Apache Board with its Chairman serving as
  +The PMC is answerable to the ASF Board with its Chairman serving as
   primary liaison.
   </p>
                                                   <p>
  -<b>Meetings</b><br /> The PMC <a href="pmc/index.html">meets monthly</a>
  -with a majority of its members to discuss issues, determine strategic
  -direction, and forward progress. These meetings may take place online,
  -via teleconference, or via other means deemed effective by the PMC.
  +<b>Board reports</b><br /> 
  +Quarterly, the PMC is responsible for sending a report to the ASF Board.
   </p>
                                                   <p>
   <b>Membership</b><br /> PMC members may resign at any time. The Chairman
  @@ -261,20 +252,27 @@
   vote of the PMC.
   </p>
                                                   <p>
  -In the event that the number of members drops below 7, the remaining PMC
  -members may choose to elect a new member to serve out the remainder of
  -the annual term.  In order to be elected, a
  -person must have served as a <a href="roles.html">Committer</a> and be
  -nominated by a PMC Member. Once nominated, all of the PMC will vote
  -and those receiving a 3/4 positive vote will become a member.
  +Committers are nominated for the PMC by an existing PMC member and a vote then follows.
   </p>
  -                                                <p>
  -<b>Creation of subprojects</b><br /> PMC members may propose the creation
  -of new subprojects.  Proposals are to contain the scope of the project,
  -identify the initial source from which the project is to be populated,
  -identify the mailing list(s) if any which are to be created, and
  -identify the initial set of committers.  Creation of a new subproject
  -requires approval by 3/4 vote of the PMC.
  +                                                <p><b>Voting</b><br /> 
  +Binary PMC voting is a majority-approval variant, with a minimum of 3 +1s 
  +required and at least 3/4 of the votes being +1. This voting style is used 
  +for anything with a yes/no, two-option choice; such as PMC member voting 
  +or changes to this document. 
  +</p>
  +                                                <p>
  +Non-binary voting currently relies on community agreement; such as voting 
  +on the recommendation of a chairman to the board. 
  +</p>
  +                                                <p>A week is deemed a fair length for a vote. </p>
  +                                                <p>Subprojects of Jakarta use other voting variants, described on the <a href="decisions.html">Decisions</a> page. </p>
  +                                                <p>
  +<b>Creation of subprojects</b><br /> 
  +The Apache Incubator is the primary source of new subprojects for Jakarta, 
  +though the PMC may choose to waive this if the Incubator PMC is agreeable.  
  +A common example of this is when an existing subproject contains a component 
  +which wishes to become a full subproject. In such cases, there is unlikely 
  +to be a need for incubation.
   </p>
                               </blockquote>
           </p>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: site-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: site-cvs-help@jakarta.apache.org