+1
Neil Graham wrote:
Hello all Xerces developers and XML PMC'ers,
I think we're finally at the point where we can vote to transform Xerces into a top-level project of the Apache Software Foundation. The text of the motion, to which I give my +1, is as follows:
The Xerces community recommends to the Apache Software Foundation Board that:
1. The top-level Xerces project contain the existing Xerces-J, Xerces-C and Xerces-P subprojects of the Apache XML project
2. The initial committers for this project be the existing committers of the Xerces-C, Xerces-J and Xerces-P subprojects
3. The initial PMC members for this project be:
Andy Clark Michael Glavassevich
Neil Graham
Berin Lautenbach
Gareth Reakes
Jason Stewart
thus representing each of Xerces-J, Xerces-C and Xerces-P.
4. The initial PMC Chairperson be Gareth Reakes.
5. The mission statement and charter for the new project will be as follows:
================================
1 INTRODUCTION
==============
1.1 Apache Xerces is a collaborative software development project
dedicated to providing robust, full-featured, commercial-quality, and
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
documentation.
1.2 This charter briefly describes the mission, history, organization, and processes of the project.
2 MISSION
=========
2.1 Apache Xerces 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
has great potential to improve the functionality and use of
information systems. We intend to build freely available XML
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). They are designed to be high performance, reliable, and easy to use. To facilitate easy porting of ideas between languages, the API's supported
should be as similar as possible, given the constraints of the languages and existing architectures. Apache Xerces parsers should also be designed
to work efficiently with other Apache projects that deal
with XML whenever possible.
2.3 We believe that the best way to further these goals 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.
2.4 In order to achieve a coherent architecture between Apache Xerces parsers
and other components and applications, standards (formal or
de facto) will be used as much as possible for both protocols and
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.
3 HISTORY ========= 3.1 The code base which formed the foundations of both the Xerces-Java and Xerces-C++ subprojects of the Apache XML Project was originally donated to Apache by IBM in 1999. Xerces-Perl came into existence as a subproject of the Apache XML project after the Xerces-C++ community had already matured to a significant extent. All three were subprojects of the Apache XML Project until late 2004. At this time, reflecting the growth in the Apache XML project and these communities themselves, Apache Xerces became a top-level Project of the Apache Software Foundation. Apache Xerces still shares much infrastructure with the Apache XML project and the other former subprojects of Apache XML that have become projects in their own right.
4 TERMS
=======
4.1 The ASF Board. The management board of the Apache Software Foundation.
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 composed of a number of subprojects which fit into one of two categories:
a) An XML parser implementation in some particular programming language. There may be 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) A set of components serving some purpose not directly pertinent to XML parsing, but which are used in related applications and are tightly bound, usually through internal
API's, to one (or more) 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.6 Committer. Apache Xerces 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 Apache Xerces project is managed by a core group of
committers known as the Project Management Committee [PMC],
which is composed of volunteers from among the active committers (see 8.3 below) from all subprojects. Each subproject must have
at least one representative on the PMC, to ensure active
supervision of the subproject.
5.2 The activities of the PMC are coordinated by the Chairperson,
who is an officer of the 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 Apache Xerces project.
5.3 The PMC has the following responsibilities:
a) Accepting new subproject proposals, voting on these proposals 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 subprojects and other Apache projects. f) Facilitating relationships between Apache Xerces and the external world. g) Overseeing Apache Xerces to ensure that the mission defined in this document is being fulfilled. h) Resolving conflicts within the project. i) Reporting to the ASF board (through the Chair) on the progress of the project.
5.4 In cases where the sub-project is unable to directly provide at least one representative on the PMC--implying that there are no active committers on that code base--then the subproject should be considered dormant, and any relevant Apache policies for dormant
projects should be implemented. At the least, the subproject's status should
be updated on its website.
5.5 Every 12 months, or at the request of the Board, the PMC will provide a recommendation to the Apache Board for the position of Chairperson of the PMC.
5.6 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.7 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.8 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.
5.9 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 approved by a two-thirds majority of all members of the PMC.
6 SUBPROJECTS ============= 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.2 A subproject may be removed by unanimous vote of the PMC, subject to the
approval of the ASF board.
7 CONTRIBUTORS
==============
7.1 Like all Apache projects, the Apache Xerces project is a meritocracy
-- Regards, Venu
---Quote for the week.----- Vision is the art of seeing the invisible. --Jonathan Swift
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
