twl 2003/03/14 10:41:09
Modified: . charter.txt
Log:
Add Peter West's suggestions
Revision Changes Path
1.5 +19 -22 xml-admin/charter.txt
Index: charter.txt
===================================================================
RCS file: /home/cvs/xml-admin/charter.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- charter.txt 12 Mar 2003 23:27:50 -0000 1.4
+++ charter.txt 14 Mar 2003 18:41:09 -0000 1.5
@@ -58,10 +58,11 @@
The PMC has the following responsibilities:
1) Accepting new subproject proposals, formally submitting these
- proposals for committer vote, and creating the subproject (see
- SUBPROJECTS below).
+ proposals for xml.apache.org committer vote, and creating the
+ subproject (see SUBPROJECTS below).
2) Facilitating code or other donations by individuals or companies.
-3) Resolving license issues and other legal issues.
+3) Resolving license issues and other legal issues in conjunction with
+ the ASF board
4) Approving new committers.
5) Ensuring that administrative and infrastructure work is completed.
6) Facilitating relationships among projects.
@@ -73,30 +74,31 @@
To become a member of the PMC, an individual must be nominated by a
contributor, unanimously approved by all PMC members, and approved by
-a two-thirds majority of committers. In most cases, developers will
-have actively contributed to development for at least six months
-before being considered for membership on the PMC.
+a two-thirds majority of xml.apache.org committers. In most cases,
+developers will have actively contributed to development for at least
+six months before being considered for membership on the PMC.
In the unlikely event that a member of the PMC becomes disruptive to
-the process or ceases to contribute for an extended period, said
-member may be removed by unanimous vote of remaining PMC members.
+the process or ceases to make codebase contributions for an extended
+period, said member may be removed by unanimous vote of remaining PMC
+members.
The PMC is responsible for maintaining and updating this
charter. Development must follow the process outlined below, so any
change to the development process necessitates a change to the
charter. Changes must be unanimously approved by all members of the
PMC. A contributor may challenge a change to the charter at any time
-and ask for a vote of all committers, in which case a two-thirds
-majority must approve the change.
+and ask for a vote of all xml.apache.org committers, in which case a
+two-thirds majority must approve the change.
SUBPROJECTS
===========
-xml.apache.org is comprised of subprojects; a subproject is a
-component whose scope is well defined. Each subproject has its own
-set of developers.
+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.
-A new subproject proposal is submitted to the PMC, accepted by majority
-committer vote, and then subject to final approval by the PMC.
+A new subproject proposal is submitted to the PMC, and then accepted
+by a majority xml.apache.org committer vote.
A subproject may be removed by unanimous vote of the PMC, subject to the
approval of the ASF board. A contributor may challenge the removal of a
@@ -170,13 +172,8 @@
=========
All contributions to the xml.apache.org project adhere to the "ASF
Source Code License." All further contributions must be made under the
-same terms. All contributions must contain the following copyright
-notice: [This changes now that the license is available]
-
-Copyright (c) {date} {name of contributor} and others. All rights
-reserved. This program and the accompanying materials are made
-available under the terms of the ASF Source Code License, as found in
-the file ASF.code.license.html that is included in this distribution.
+same terms. All contributed files must contain the full text of the ASF
+Source Code License.
THE DEVELOPMENT PROCESS
=======================
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
