bayard 2004/05/29 13:55:16
Modified: commons-build/xdocs charter.xml
Log:
outdated sections removed, version added, original linked to. All changes between
1.0 and 1.1 are effectively rolled into this 1.1 "release"
Revision Changes Path
1.12 +5 -59 jakarta-commons/commons-build/xdocs/charter.xml
Index: charter.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/commons-build/xdocs/charter.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- charter.xml 29 May 2004 20:45:18 -0000 1.11
+++ charter.xml 29 May 2004 20:55:16 -0000 1.12
@@ -24,11 +24,12 @@
<body>
-<section name="Charter">
+<section name="Charter (1.1)">
<p>
-The following charter for Jakarta Commons was approved by the Jakarta Project
-Management Committee on March 19, 2001.
+The following charter for Jakarta Commons was approved by the
+Jakarta Project Management Committee (PMC) on May 19, 2004. The original
+version, <a
href="http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-commons/commons-build/xdocs/charter.xml?content-type=text%2Fplain&rev=1.1";>1.0</a>,
was approved by the PMC on March 19, 2001.
</p>
<strong>(0) rationale</strong>
@@ -60,61 +61,9 @@
<p>
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
-subproject(s) will distribute the code or documentation along
-with the rest of their codebase.
</p>
-<strong>(2) identify the initial source from which the subproject is to be
populated</strong>
-
-<p>
-The initial packages would be based on existing ASF codebases,
-including those that provide services for DataSource/Database Pools,
-XML Configuration, Message Resources and i18n, JNDI and Naming, and
-Testing Suites. The initial committers have agreed to first create and maintain
-a Database Connection Pool package, along with related
-testing suites and subproject infrastructure.
-</p>
-
-<strong>(3) identify the initial Jakarta resources to be created </strong>
-
-<p>
-(3.1) mailing list(s)
-</p>
-
-<p>
-jakarta-commons
-</p>
-
-<p>
-(3.2) CVS repositories
-</p>
-
-<p>
-jakarta-commons<br/>
-jakarta-commons-sandbox
-</p>
-
-<p>
-(3.3) Bugzilla
-</p>
-
-<p>
-program - commons<br/>
-components - Web site, Directory, dbcp
-</p>
-
-<p>
-(3.4) Jyve FAQ (when available)
-</p>
-
-<p>commons-general<br/>
-commons-dbcp<br/>
-commons-sandbox
-</p>
-
-<strong>(4) identify the initial set of committers</strong>
+<strong>(2) identify the initial set of committers</strong>
<p>
Morgan Delagrange<br/>
Ted Husted<br/>
@@ -221,7 +170,6 @@
<li>The subproject will also provide a single JAR of all stable package releases.
It may also provide a second JAR with a subset of only JDK 1.1 compatible releases. A
gump of nightly builds will also be provided.</li>
<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 majority approval of the
subproject committers. Proposals are to identify the rationale for the
@@ -295,8 +243,6 @@
<p>For the time being, the package will use a root branch of the Jakarta-Commons
CVS.</p>
<p>(3.3) Bugzilla</p>
<p>The package should be listed as a component of under the Jakarta-Commons
Bugzilla entry.</p>
-<p>(3.4) Jyve FAQ (when available)</p>
-<p>commons-dbcp</p>
<p>(4) identify the initial set of committers to be listed in the Status File.</p>
<p>
Morgan Delagrange<br/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
