commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject cvs commit: jakarta-commons/xdocs charter.xml
Date Tue, 06 May 2003 10:38:49 GMT
rdonkin     2003/05/06 03:38:48

  Modified:    xdocs    charter.xml
  Log:
  Changed charter as per successful VOTE. We now allow any Apache committers to use the sandbox
(upon request).
  
  Revision  Changes    Path
  1.7       +4 -4      jakarta-commons/xdocs/charter.xml
  
  Index: charter.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/xdocs/charter.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- charter.xml	23 Aug 2002 04:53:46 -0000	1.6
  +++ charter.xml	6 May 2003 10:38:48 -0000	1.7
  @@ -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
  @@ -246,7 +246,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
  @@ -342,7 +342,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 shop 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 shop 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>
  @@ -354,7 +354,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 the sandbox upon request, no vote required,
no questions asked. Just subscribe to jakarta-commons-sandbox, and request
   authorization.</p>
   
   <p><b>Why not just do this within Avalon, or another existing subproject?</b></p>
  
  
  

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


Mime
View raw message