Return-Path:
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 10059 invoked from network); 6 May 2003 10:38:51 -0000
Received: from exchange.sun.com (192.18.33.10)
by daedalus.apache.org with SMTP; 6 May 2003 10:38:51 -0000
Received: (qmail 28692 invoked by uid 97); 6 May 2003 10:40:52 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org
Received: (qmail 28685 invoked from network); 6 May 2003 10:40:52 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
by nagoya.betaversion.org with SMTP; 6 May 2003 10:40:52 -0000
Received: (qmail 9893 invoked by uid 500); 6 May 2003 10:38:49 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe:
List-Subscribe:
List-Help:
List-Post:
List-Id: "Jakarta Commons Developers List"
Reply-To: "Jakarta Commons Developers List"
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 9882 invoked by uid 500); 6 May 2003 10:38:49 -0000
Received: (qmail 9879 invoked from network); 6 May 2003 10:38:49 -0000
Received: from icarus.apache.org (208.185.179.13)
by daedalus.apache.org with SMTP; 6 May 2003 10:38:49 -0000
Received: (qmail 12118 invoked by uid 1289); 6 May 2003 10:38:49 -0000
Date: 6 May 2003 10:38:49 -0000
Message-ID: <20030506103849.12117.qmail@icarus.apache.org>
From: rdonkin@apache.org
To: jakarta-commons-cvs@apache.org
Subject: cvs commit: jakarta-commons/xdocs charter.xml
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
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 @@
-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 @@
It is expected that the scope of packages may sometimes overlap.
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.
- A CVS repository will be available to all Jakarta committers as a workplace for new packages or other projects.
+ 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 @@
Should other Jakarta subprojects move their utility packages to the Commons?
-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
+
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.
What will be listed in the Commons directory?
@@ -354,7 +354,7 @@
If Jakarta adopts an open-door policy for all its subprojects, then of course the Commons will follow suit.
-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
+
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.
Why not just do this within Avalon, or another existing subproject?
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org