martinc     02/01/13 11:53:43

  Modified:    xdocs    charter.xml
               docs     charter.html
  Log:
  Updated Commons guidelines to require majority approval for new package
  proposals to be accepted.
  
  Revision  Changes    Path
  1.5       +5 -5      jakarta-commons/xdocs/charter.xml
  
  Index: charter.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- charter.xml       11 Dec 2001 08:12:04 -0000      1.4
  +++ charter.xml       13 Jan 2002 19:53:43 -0000      1.5
  @@ -232,11 +232,11 @@
     <li>Volunteers become committers to this subproject in the same way they are 
entered to any Jakarta subproject. Being a committer in another Jakarta subproject is 
not a prerequisite.</li>
     <li>Each committer has karma to all the packages, but committers are required to 
add their name to a package's status file before their first commit to that 
package.</li>
     <li>The committers shall elect a committee of three committers to provide general 
oversight, in the style of the Jakarta PMC.</li>
  -  <li>New packages may be proposed to the Jakarta Commons mailing list. To be 
accepted, a package proposal must receive a positive super-majority vote of the 
subproject committers. Proposals are to identify the
  -    rationale for the package, its scope, its interaction with other packages and 
products, the Commons resources, if any, to be created, the initial source from which 
the package is to be created, and the initial set of committers.
  -    <ol>
  -      <li>The whole number of positive votes needed for a super majority is 
calculated by dividing the total number of active subproject committers by four, 
multiplying by three, and rounding to the nearest whole number (&gt;= .5 rounds 
up).</li>
  -    </ol>
  +  <li>New packages may be proposed to the Jakarta Commons mailing list. To be 
accepted, a package proposal must receive majority approval of the subproject 
committers. Proposals are to identify the rationale
  +    for the package, its scope, its interaction with other packages and products, 
the Commons resources, if any, to be created, the initial source from which the 
package is to be created, and the initial set of committers.
  +    <ul>
  +      <li>As stated in the Jakarta guidelines, an action requiring majority 
approval must receive at least 3 binding +1 votes and more +1 votes than -1 votes.</li>
  +    </ul>
     </li>
     <li>It is expected that the scope of packages may sometimes overlap.</li>
     <li>Anyone may propose a new package to the Commons, and list themselves as the 
initial committers for the package. The vote on the proposal is then also a vote to 
enter new committers to the subproject as needed.</li>
  
  
  
  1.21      +6 -6      jakarta-commons/docs/charter.html
  
  Index: charter.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/docs/charter.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- charter.html      11 Dec 2001 08:12:32 -0000      1.20
  +++ charter.html      13 Jan 2002 19:53:43 -0000      1.21
  @@ -327,11 +327,11 @@
     <li>Volunteers become committers to this subproject in the same way they are 
entered to any Jakarta subproject. Being a committer in another Jakarta subproject is 
not a prerequisite.</li>
     <li>Each committer has karma to all the packages, but committers are required to 
add their name to a package's status file before their first commit to that 
package.</li>
     <li>The committers shall elect a committee of three committers to provide general 
oversight, in the style of the Jakarta PMC.</li>
  -  <li>New packages may be proposed to the Jakarta Commons mailing list. To be 
accepted, a package proposal must receive a positive super-majority vote of the 
subproject committers. Proposals are to identify the
  -    rationale for the package, its scope, its interaction with other packages and 
products, the Commons resources, if any, to be created, the initial source from which 
the package is to be created, and the initial set of committers.
  -    <ol>
  -      <li>The whole number of positive votes needed for a super majority is 
calculated by dividing the total number of active subproject committers by four, 
multiplying by three, and rounding to the nearest whole number (&gt;= .5 rounds 
up).</li>
  -    </ol>
  +  <li>New packages may be proposed to the Jakarta Commons mailing list. To be 
accepted, a package proposal must receive majority approval of the subproject 
committers. Proposals are to identify the rationale
  +    for the package, its scope, its interaction with other packages and products, 
the Commons resources, if any, to be created, the initial source from which the 
package is to be created, and the initial set of committers.
  +    <ul>
  +      <li>As stated in the Jakarta guidelines, an action requiring majority 
approval must receive at least 3 binding +1 votes and more +1 votes than -1 votes.</li>
  +    </ul>
     </li>
     <li>It is expected that the scope of packages may sometimes overlap.</li>
     <li>Anyone may propose a new package to the Commons, and list themselves as the 
initial committers for the package. The vote on the proposal is then also a vote to 
enter new committers to the subproject as needed.</li>
  @@ -505,7 +505,7 @@
                   </td></tr>
                   <tr><td colspan="2">
                       <div align="center"><font color="#525D76" size="-1"><em>
  -                    Copyright &#169; 1999-2001, Apache Software Foundation
  +                    Copyright &#169; 1999-2002, Apache Software Foundation
                       </em></font></div>
                   </td></tr>
               </table>
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to