You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general-cvs@xml.apache.org by bl...@apache.org on 2003/08/31 14:30:11 UTC
cvs commit: xml-site/src/documentation/content/xdocs mission.xml
blautenb 2003/08/31 05:30:11
Modified: src/documentation/content/xdocs mission.xml
Log:
Updated for newly approved charter
Revision Changes Path
1.2 +181 -126 xml-site/src/documentation/content/xdocs/mission.xml
Index: mission.xml
===================================================================
RCS file: /home/cvs/xml-site/src/documentation/content/xdocs/mission.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mission.xml 25 Oct 2002 15:18:42 -0000 1.1
+++ mission.xml 31 Aug 2003 12:30:11 -0000 1.2
@@ -13,7 +13,9 @@
at </em>
<jump href="http://cvs.apache.org/viewcvs.cgi/xml-admin/charter.txt">http://cvs.apache.org/viewcvs.cgi/xml-admin/charter.txt</jump>;
however a recent copy is included herein.</p>
- <source>xml.apache.org is a collaborative software development project
+ <source>1 INTRODUCTION
+==============
+1.1 xml.apache.org is a collaborative software development project
dedicated to providing robust, full-featured, commercial-quality, and
freely available XML support on a wide variety of platforms. This
project is managed in cooperation with various individuals worldwide
@@ -21,12 +23,12 @@
Internet to communicate, plan, and develop XML software and related
documentation.
-This charter briefly describes the mission, history, organization, and
+1.2 This charter briefly describes the mission, history, organization, and
processes of the project.
-MISSION
-=======
-xml.apache.org exists to promote the use of XML. We view XML as a
+2 MISSION
+=========
+2.1 xml.apache.org exists to promote the use of XML. We view XML as a
compelling paradigm that structures data as information, thereby
facilitating the exchange, transformation, and presentation of
knowledge. The ability to transform raw data into usable information
@@ -34,164 +36,219 @@
information systems. We intend to build freely available XML
processing components in order to engender such improvements.
-xml.apache.org defines a set of components that exchange or deal with
-XML information sets. These components plug into each other using
-standard APIs (formal, de facto, or proposed). The components must be
-high performance, reliable, and easy to use. The components must be
-part of an underlying architectural orchestration that will allow them
-to work together without major negotiations or breakage.
+2.2 xml.apache.org defines a set of components that exchange or deal
+with XML information sets. Where appropriate, these components plug
+into each other using standard APIs (formal, de facto, or proposed).
+The components must be high performance, reliable, and easy to use.
+Where inter-related, the components must be part of an underlying
+architectural orchestration that will allow them to work together
+without major negotiations or breakage.
-We believe that the best way to define this XML information exchange
+2.3 We believe that the best way to define this XML information exchange
architecture is by having both individuals and corporations
collaborate on the best possible infrastructure, APIs, code, testing,
and release cycles. Components must be vendor neutral and usable as
core components for all.
-In order to achieve a coherent architecture between xml.apache.org
+2.4 In order to achieve a coherent architecture between xml.apache.org
components and other components and applications, standards (formal or
de facto) will be used as much as possible for both protocols and
-APIs. We will also allow the innovation of new protocols, APIs, and
-components in order to seed new concepts not yet defined by standards.
+APIs. Where appropriate, experiences and lessons learned will be fed
+back to standards bodies in an effort to assist in the development of
+those standards. We will also encourage the innovation of new
+protocols, APIs, and components in order to seed new concepts not
+yet defined by standards.
-HISTORY
-=======
-
-This project was established under the direction of the newly-formed
+3 HISTORY
+=========
+3.1 This project was established under the direction of the newly-formed
Apache Software Foundation in August 1999 to facilitate joint
open-source development.
-THE PROJECT MANAGEMENT COMMITTEE
-================================
-The xml.apache.org project is managed by a small, core group of
-contributors known as the Project Management Committee [PMC]. The PMC
-must have at least one officer from the Apache Board, who will be the
-Chairperson and report to the Apache Board. See
-http://www.apache.org/foundation/bylaws.html for reference.
-
-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).
-2) Facilitating code or other donations by individuals or companies.
-3) Resolving license issues and other legal issues.
-4) Approving new committers.
-5) Ensuring that administrative and infrastructure work is completed.
-6) Facilitating relationships among projects.
-7) Facilitating relationships between xml.apache.org and the external
+4 TERMS
+=======
+4.1 The ASF Board. The management board of the Apache Software
+Foundation.
+
+4.2 The Project. The Apache XML Project, referred to in this
+document as "xml.apache.org" or "the xml.apache.org project".
+
+4.3 Subproject. xml.apache.org is comprised of a number of subprojects;
+a subproject is responsible for a component or application whose scope
+is well defined.
+
+4.4 Contributor. Anyone who makes a contribution to the development
+of the xml.apache.org project or a subproject.
+
+4.5 Committer. Each subproject has a set of committers. Committers
+are contributors who have read/write access to the source code
+repository.
+
+5 THE PROJECT MANAGEMENT COMMITTEE
+==================================
+5.1 The xml.apache.org project is managed by a core group of
+contributors known as the Project Management Committee [PMC],
+with representation from all sub-projects.
+
+5.2 The activities of the PMC are coordinated by the Chairperson,
+who is an officer of corporation and reports to the Apache
+Board. The Chairperson will, on the request of the Apache Board,
+provide reports to the Board on issues related to the running of
+the xml.apache.org project.
+
+5.3 The PMC has the following responsibilities:
+
+a) Accepting new subproject proposals, formally submitting these
+ proposals for xml.apache.org committer vote, and creating the
+ subproject (see SUBPROJECTS below). This is done in collaboration
+ with the Incubator (see http://incubator.apache.org).
+b) Facilitating code or other donations by individuals or companies,
+ in collaboration with the Incubator.
+c) Resolving license issues and other legal issues in conjunction with
+ the ASF board.
+d) Ensuring that administrative and infrastructure work is completed.
+e) Facilitating relationships among projects and subprojects.
+f) Facilitating relationships between xml.apache.org and the external
world.
-8) Overseeing xml.apache.org to ensure that the mission defined in
+g) Overseeing xml.apache.org to ensure that the mission defined in
this document is being fulfilled.
-9) 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
-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. The goal is to keep
-the membership of the core group at four to seven people in order to
-minimize the bureaucratic overhead required to keep the project
-operational.
-
-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.
+h) Resolving conflicts within the project.
+i) Reporting to the ASF board (through the Chair) on the progress
+ of the project.
+
+5.4 Every 12 months, (or as required by the Board or PMC) each subproject
+of xml.apache.org will nominate 1-2 individuals to represent them on the
+PMC. To become a sub-project's representative on the PMC, an individual
+must be nominated by a contributor, unanimously approved by all PMC
+members, and approved by a two-thirds majority of the sub-project's
+active committers. In most cases, developers will have actively
+contributed to development for at least six months before being
+considered for membership on the PMC.
+
+5.5 In cases where the sub-project is unable to directly provide a
+representative on the PMC, another member of the PMC will be required
+to represent that sub-project on the PMC. This will be strongly
+discouraged. It is preferable that all sub-projects have direct
+representation on the PMC.
+
+5.6 Once the PMC selection process has completed, the PMC will provide
+a recommendation to the Apache Board for the position of Chairperson
+of the PMC.
+
+5.7 This recommendation will be made on the basis of an election held
+within the PMC. The election will be performed using a simple
+majority vote of PMC members.
+
+5.8 Upon agreement by the Apache Board, the recommended Chairperson will,
+if they are not already, be appointed an officer of the corporation.
+See http://www.apache.org/foundation/bylaws.html for more information.
+
+5.9 In the unlikely event that a member of the PMC becomes disruptive to
+the process, ceases to make codebase contributions for an extended
+period, or ceases to take part in PMC votes for an extended period of
+time, said member may be removed by unanimous vote of remaining PMC
+members.
-The PMC is responsible for maintaining and updating this
+5.10 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 active 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.
+6 SUBPROJECTS
+=============
+6.1 xml.apache.org is comprised of subprojects; a subproject is
+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.
+
+6.2 A new subproject proposal is submitted to the PMC, and then accepted
+by a majority xml.apache.org active committer vote.
+
+6.3 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
+subproject at any time and ask for a vote of all active committers, in
+which case a two-thirds majority must approve the change.
-A new subproject proposal is submitted to the PMC, accepted by majority
-committer vote, and then subject to final approval by the PMC.
+7 CONTRIBUTORS
+==============
+7.1 Like all Apache projects, the XML project is a meritocracy -- the more
+work you do, the more you are allowed to do. Contributions will include
+participating in mailing lists, reporting bugs, providing patches and
+proposing changes to a product.
-COMMITTERS
-==========
+7.2 Developers who make regular and substantial contributions may become
+committers as described below.
-Each subproject has a set of committers. Committers are developers who
+8 COMMITTERS
+============
+8.1 Each subproject has a set of committers. Committers are contributors who
have read/write access to the source code repository. New committers
-are added when a developer is nominated by a committer and approved by
-at least 50 percent of the committers for that subproject with no
+are added when a contributor is nominated by a committer and approved by
+at least 50 percent of the active committers for that subproject with no
opposing votes. 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.
-CONTRIBUTORS
-============
-Like all Apache projects, the XML project is a meritocracy -- the more
-work you do, the more you are allowed to do. Occasional contributors
-will be able to report bugs and participate in the mailing lists.
-
-Specific changes to a product proposed for discussion or voting on the
-appropriate development mailing list should be presented in the form
-of input to the patch command. When sent to the mailing list, the
-message should contain a subject beginning with [PATCH] and including
-a distinctive one-line summary that corresponds to the action item for
-that patch.
-
-Use the diff -u command from the original software file(s) to the
-modified software file(s) to create the patch. Patches should be
-submitted against the latest CVS versions of the software to avoid
-conflicts and ensure that you are not submitting a patch for a problem
-that has already been resolved.
-
-Developers who make regular and substantial contributions may become
-committers as described above.
-
-INFRASTRUCTURE
-==============
-The xml.apache.org project site must provide the following:
+8.2 For the purposes of voting, committers will be classed as "active" or
+"inactive". Only active committers will be included in the totals used to
+determine the success or failure of a particular vote.
+
+8.3 Committers remain active as long as they are contributing code or
+posting to the subproject mailing lists. If a committers has neither
+contributed code nor posted to the subproject mailing lists in 3
+months, the PMC representatives for that subproject will e-mail the
+committer, the subproject development list, and the PMC mailing list
+notifying the committer that they are going to be moved to inactive
+status. If there is no response in 72 hours, the committer will become
+inactive.
+
+8.4 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.
+
+9 INFRASTRUCTURE
+================
+9.1 The xml.apache.org project site must provide the following:
-Bug Database -- This is a system for tracking bugs and feature
+a) Bug Database -- This is a system for tracking bugs and feature
requests.
-Subproject Source Repositories -- These are several CVS repositories
+b) Subproject Source Repositories -- These are several repositories
containing both the source code and documentation for the
subprojects. Each subproject will have a set of committers to its
repository.
-Website -- An xml.apache.org website will contain information about
+c) Website -- An xml.apache.org website will contain information about
the xml.apache.org project, including documentation, downloads of
releases, and this charter. Each subproject will have its own website
with subproject information.
-PMC Mailing List -- This list is for PMC business requiring
+d) PMC Mailing List -- This list is for PMC business requiring
confidentiality, particularly when an individual or company requests
discretion. All other PMC business should be done on the general
mailing list.
-General Mailing List -- This mailing list is open to the public. It is
+e) General Mailing List -- This mailing list is open to the public. It is
intended for discussions that cross subprojects.
-Subproject Mailing Lists -- Each subproject should have a devoted mailing
+f) Subproject Mailing Lists -- Each subproject should have a devoted mailing
list. Many subprojects may wish to have both user and development
lists. The individual subprojects may decide on the exact structure of
their mailing lists.
-LICENSING
-=========
-All contributions to the xml.apache.org project adhere to the "ASF
+10 LICENSING
+===========
+10.1 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]
+same terms. All contributed files must contain the full text of the ASF
+Source Code License.
-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.
-
-THE DEVELOPMENT PROCESS
-=======================
-The development process is intentionally lightweight; like other
+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 code change. For efficiency, some code
@@ -200,19 +257,17 @@
changed as needed, with conflicts resolved by majority vote of the
committers.
-SUBPROJECT REQUIREMENTS
-=======================
-Each subproject must have a set of requirements as well as an
+12 SUBPROJECT REQUIREMENTS
+==========================
+12.1 Each subproject must have a set of requirements as well as an
up-to-date release plan and design document on its dedicated web page.
-It must be possible for each subproject to plug into the Gump nightly
-build system (see http://jakarta.apache.org/builds/gump). It is
-recommended that each subproject have a smoke-test system that works at
-least as a basic integration test.
-
-RELATIONSHIP TO OTHER APACHE PROJECTS
-=====================================
-The xml.apache.org project should work closely with other Apache
+12.2 It is recommended that each subproject have a smoke-test system
+that works at least as a basic integration test.
+
+13 RELATIONSHIP TO OTHER APACHE PROJECTS
+========================================
+13.1 The xml.apache.org project should work closely with other Apache
projects, such as Jakarta and the Apache Server, to avoid redundancy
and achieve a coherent architecture among xml.apache.org and these
projects.</source>
@@ -231,9 +286,6 @@
<em>Xalan</em> - XSLT stylesheet processors, in Java and C++
</li>
<li>
- <em>Cocoon</em> - XML-based web publishing, in Java
- </li>
- <li>
<em>FOP</em> - XSL formatting objects, in Java
</li><li><em>Forrest</em> - XML/XSLT project community websites</li>
<li>
@@ -250,6 +302,9 @@
</li>
<li>
<em>Commons</em> - A meta-project of common XML-oriented code
+ </li>
+ <li>
+ <em>Security</em> - Java and C++ libraries for encryption and signature functions
</li>
</ul>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: general-cvs-help@xml.apache.org