--- charter-original.txt 2004-05-21 13:33:40.899953800 -0400 +++ charter.txt 2004-05-21 13:38:17.970731800 -0400 @@ -2,8 +2,8 @@ ============== 1.1 Apache Xerces is a collaborative software development project dedicated to providing robust, full-featured, commercial-quality, and -freely available XML parsers on a wide variety of platforms supporting -several languages. This +freely available XML parsers and closely related technologies +on a wide variety of platforms supporting several languages. This project is managed in cooperation with various individuals worldwide (both independent and company-affiliated experts), who use the Internet to communicate, plan, and develop XML software and related @@ -20,7 +20,7 @@ knowledge. The ability to transform raw data into usable information has great potential to improve the functionality and use of information systems. We intend to build freely available XML -parsers in order to engender such improvements. +parsers and closely related technologies in order to engender such improvements. 2.2 The Apache Xerces parsers support standard APIs (formal, de facto, or proposed). @@ -50,10 +50,11 @@ ========= 3.1 The Apache Xerces project was originally part of the Apache XML Project. In early 2004, reflecting the growth both in the Apache -XML project and in Apache Xerces, Apache Xerces became a formal -project of the Apache Software Foundation. However, Apache Xerces still +XML project and in Apache Xerces, Apache Xerces became a top-level +Project of the Apache Software Foundation. However, Apache Xerces still shares much infrastructure with the Apache XML project and the -other subprojects of Apache XML that have become projects in their own right. +other former subprojects of Apache XML that have become projects in +their own right. 4 TERMS ======= @@ -63,14 +64,26 @@ 4.2 The Project. The Apache Xerces Project; intended to refer to the source code, website and community that are Apache Xerces. -4.3 Subproject. Apache Xerces is comprised of a number of subprojects, -corresponding to each of the languages for which a parser has been -produced. Currently, there are parsers for Java, C/C++ and Perl. +4.3 Subproject. Apache Xerces is comprised of a number of subprojects +which fit into one of two categories: -4.4 Contributor. Anyone who makes a contribution to the development +a) An XML parser implementation in some particular programming + language. There may multiple parsers for a given + language, if the API's the parsers support are sufficiently + dissimilar. At the time of writing, there is one parser for + each of Java, C/C++ and Perl. +b) Componentry that is not an XML parser, but involves related + applications and is tightly bound, usually through internal + API's, to one of the parser subprojects. + +4.4 Product. Some deliverable (usually a binary or source +package) that a subproject releases to the public. Subprojects +may have multiple products. + +4.5 Contributor. Anyone who makes a contribution to the development of the Apache Xerces project or a subproject. -4.5 Committer. Apache Xerces has a set of committers. Committers +4.6 Committer. Apache Xerces has a set of committers. Committers are contributors who have read/write access to the source code repository. @@ -139,13 +152,10 @@ 6 SUBPROJECTS ============= -6.1 Apache Xerces is composed of subprojects; a subproject is -responsible for an XML parser implementation in a particular language. - -6.2 A new subproject proposal is submitted to the PMC, and then accepted -by a two-thirds vote. +6.1 When a new subproject proposal is submitted to the PMC, it +may be accepted by a two-thirds vote of the PMC. -6.3 A subproject may be removed by unanimous vote of the PMC, subject to the +6.2 A subproject may be removed by unanimous vote of the PMC, subject to the approval of the ASF board. 7 CONTRIBUTORS @@ -164,14 +174,18 @@ have read/write access to the source code repository. New committers are added when a contributor is nominated by a committer, approved by at least 50 percent of the active committers for that subproject with no -opposing votes, and files a signed Contributor License Agreement with the Secretary of the Corporation. In most cases, new committers will already be participating in the development process by submitting suggestions -and/or fixes via the bug report page or mailing lists. +opposing votes, and files a signed Contributor License Agreement +with the Secretary of the Corporation. In most cases, new +committers will already be participating in the development +process by submitting suggestions and/or fixes via the bug report +page or mailing lists. 8.2 Although committers have write access to all Apache Xerces subprojects, they are only permitted to make changes to the subprojects to which they have been elected committers. A committer may be elected to multiple -subprojects, but, except that no new access need be granted, -the process is the same as for any other contributor. +subprojects, but, except that no new access need be grantedand +the CLA need not be updated, the process is the same as for any +other contributor. 8.3 For the purposes of voting, committers will be classed as "active" or "inactive". Only active committers will be included in the totals used to @@ -189,8 +203,8 @@ 8.5 An inactive status will not prevent a committer committing new code changes or posting to the mailing lists. Either of these activities will -automatically re-activate the committer for the purposes of voting, and necessitate -their addition to the PMC mailing list. +automatically re-activate the committer for the purposes of +voting, and necessitate their addition to the PMC mailing list. 9 INFRASTRUCTURE ================ @@ -229,18 +243,22 @@ same terms. All contributed files must contain the full text of the ASF Source Code License. -10.2 When a committer is considering integrating a contribution from a contributor who has no CLA on file with the Corporation, it is the responsibility of the committer, in consultation with the PMC, to conduct due diligence on the pedigree of the contribution under consideration. +10.2 When a committer is considering integrating a contribution +from a contributor who has no CLA on file with the Corporation, +it is the responsibility of the committer, in consultation with +the PMC, to conduct due diligence on the pedigree of the +contribution under consideration. 11 THE DEVELOPMENT PROCESS ========================== 11.1 The development process is intentionally lightweight; like other Apache projects, the committers decide which changes may be committed to the repository. Three +1 ('yes' votes) with no -1 ('no' votes or -vetoes) are needed to approve a significant code change. For efficiency, some code -changes from some contributors (e.g. feature additions, bug fixes) may -be approved in advance, in which case they may be committed first and -changed as needed, with conflicts resolved by majority vote of the -committers. +vetoes) are needed to approve a significant code change. For +efficiency, some code changes from some contributors (e.g. +feature additions, bug fixes) may be approved in advance, in +which case they may be committed first and changed as needed, +with conflicts resolved by majority vote of the committers. 12 SUBPROJECT REQUIREMENTS ==========================