Return-Path: Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Delivered-To: mailing list dev@ant.apache.org Received: (qmail 42293 invoked by uid 500); 21 May 2003 12:23:36 -0000 Received: (qmail 42290 invoked from network); 21 May 2003 12:23:36 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 21 May 2003 12:23:36 -0000 Received: (qmail 16711 invoked by uid 1142); 21 May 2003 12:23:36 -0000 Date: 21 May 2003 12:23:36 -0000 Message-ID: <20030521122336.16710.qmail@icarus.apache.org> From: conor@apache.org To: ant-cvs@apache.org Subject: cvs commit: ant/proposal/ant-site/anakia/xdocs bylaws.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N conor 2003/05/21 05:23:36 Modified: proposal/ant-site/anakia/docs bylaws.html proposal/ant-site/anakia/xdocs bylaws.xml Log: Update proposal to remove RfR and add subproject creation clause Revision Changes Path 1.18 +106 -103 ant/proposal/ant-site/anakia/docs/bylaws.html Index: bylaws.html =================================================================== RCS file: /home/cvs/ant/proposal/ant-site/anakia/docs/bylaws.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -w -u -r1.17 -r1.18 --- bylaws.html 21 May 2003 06:08:57 -0000 1.17 +++ bylaws.html 21 May 2003 12:23:34 -0000 1.18 @@ -368,7 +368,7 @@ management of the projects within the scope of the Ant PMC. The chair reports to the board quarterly on developments within the Ant project. The PMC may consider the position of PMC chair annually and if - supported by 3/4 Majority may recommend a new chair to the board. + supported by 2/3 Majority may recommend a new chair to the board. Ultimately, however, it is the board's responsibility who it chooses to appoint as the PMC chair.

@@ -700,13 +700,16 @@ +

When the codebase for an existing, released product is to be - replaced with an alternative codebase. Alternative codebases - may be developed in the project's source code repository according - to the - - Rules for Revolutionaries. If such a vote fails to gain approval, - the existing code base will continue. + replaced with an alternative codebase. If such a vote fails to + gain approval, the existing code base will continue. +

+ +

+ This also covers the creation of new sub-projects + within the project +

@@ -375,13 +375,16 @@ Adoption of New Codebase +

When the codebase for an existing, released product is to be - replaced with an alternative codebase. Alternative codebases - may be developed in the project's source code repository according - to the - - Rules for Revolutionaries. If such a vote fails to gain approval, - the existing code base will continue. + replaced with an alternative codebase. If such a vote fails to + gain approval, the existing code base will continue. +

+ +

+ This also covers the creation of new sub-projects + within the project +

2/3 majority