+1 ----- Original Message ----- From: Scott Sanders <[EMAIL PROTECTED]> To: Jakarta Commons Developers List <[EMAIL PROTECTED]> Sent: Friday, March 29, 2002 7:54 PM Subject: [VOTE] Update charter to allow any Apache committer into the sandbox
Below is a diff of the proposed change to charter.xml. Basically says any Apache committer is allowed to work in the sandbox, instead of any Jakarta committer. The intention of this is that other Apache subprojects (xml), also have some useful java code. Here is my +1. Scott Sanders Index: charter.xml =================================================================== RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v retrieving revision 1.5 diff -u -r1.5 charter.xml --- charter.xml 13 Jan 2002 19:53:43 -0000 1.5 +++ charter.xml 29 Mar 2002 18:53:34 -0000 @@ -48,7 +48,7 @@ </p> <p> -The subproject will host a CVS repository available to all Jakarta +The subproject will host a CVS repository available to all Apache committers as a workplace for new packages or other projects. Before release to the public, code or documentation developed here must be sponsored by a Jakarta subproject. The sponsoring @@ -240,7 +240,7 @@ </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> - <li>A CVS repository will be available to all Jakarta committers as a workplace for new packages or other projects. + <li>A CVS repository will be available to all Apache committers as a workplace for new packages or other projects. Before release to the public, code or documentation developed here must be sponsored by Jakarta subproject. The sponsoring subproject(s) will distribute the code or documentation along with the @@ -327,7 +327,7 @@ <p><b>Should other Jakarta subprojects move their utility packages to the Commons?</b></p> -<p>They are welcome to do so. If they would like to experiment with refactoring a package outside their own CVS tree, they can setup s hop in the Commons sandbox. Any Jakarta committer is entitled to write access to this CVS repository upon request. They +<p>They are welcome to do so. If they would like to experiment with refactoring a package outside their own CVS tree, they can setup s hop in the Commons sandbox. Any Apache committer is entitled to write access to this CVS repository upon request. They could then decide to propose the package to the Commons, and thereby become committers to the Commons, or to move it back to their own CVS, and just list it in the Commons directory where other developers and users can find it.</p> <p><b>What will be listed in the Commons directory?</b></p> @@ -339,7 +339,7 @@ <p>If Jakarta adopts an open-door policy for all its subprojects, then of course the Commons will follow suit.</p> -<p>We do have an open-door policy for the sandbox CVS (jakarta-commons-sandbox). Any Jakarta committer is entitled to write access to the sandbox upon request, no vote required, no questions asked. Just subscribe to jakarta-commons-sandbox, and request +<p>We do have an open-door policy for the sandbox CVS (jakarta-commons-sandbox). Any Apache committer is entitled to write access to t he sandbox upon request, no vote required, no questions asked. Just subscribe to commons-dev, and request authorization.</p> <p><b>Why not just do this within Avalon, or another existing subproject?</b></p> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
