twl 2003/03/14 10:49:29
Modified: . charter.txt
Log:
Added Steven Noel's changes
Revision Changes Path
1.7 +11 -9 xml-admin/charter.txt
Index: charter.txt
===================================================================
RCS file: /home/cvs/xml-admin/charter.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- charter.txt 14 Mar 2003 18:45:59 -0000 1.6
+++ charter.txt 14 Mar 2003 18:49:29 -0000 1.7
@@ -59,17 +59,19 @@
1) Accepting new subproject proposals, formally submitting these
proposals for xml.apache.org committer vote, and creating the
- subproject (see SUBPROJECTS below).
-2) Facilitating code or other donations by individuals or companies.
+ subproject (see SUBPROJECTS below). This is done in collaboration
+ with the Incubator.
+2) Facilitating code or other donations by individuals or companies,
+ in collaboration with the Incubator.
3) Resolving license issues and other legal issues in conjunction with
the ASF board
-5) Ensuring that administrative and infrastructure work is completed.
-6) Facilitating relationships among projects and subprojects.
-7) Facilitating relationships between xml.apache.org and the external
+4) Ensuring that administrative and infrastructure work is completed.
+5) Facilitating relationships among projects and subprojects.
+6) Facilitating relationships between xml.apache.org and the external
world.
-8) Overseeing xml.apache.org to ensure that the mission defined in
+7) Overseeing xml.apache.org to ensure that the mission defined in
this document is being fulfilled.
-9) Resolving conflicts within the project.
+8) Resolving conflicts within the project.
To become a member of the PMC, an individual must be nominated by a
contributor, unanimously approved by all PMC members, and approved by
@@ -93,8 +95,8 @@
SUBPROJECTS
===========
xml.apache.org is comprised of subprojects; a subproject is
-responsible for component whose scope is well defined. Each
-subproject has its own set of developers, and is responsible
+responsible for component or application whose scope is well defined.
+Each subproject has its own set of developers, and is responsible
for approving its own committers.
A new subproject proposal is submitted to the PMC, and then accepted
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
