You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xerces.apache.org by mr...@apache.org on 2009/01/05 06:58:29 UTC
svn commit: r731460 [1/3] - in /xerces/site/trunk: ./ src/documentation/
src/documentation/classes/ src/documentation/content/
src/documentation/content/xdocs/ src/documentation/translations/
Author: mrglavas
Date: Sun Jan 4 21:58:28 2009
New Revision: 731460
URL: http://svn.apache.org/viewvc?rev=731460&view=rev
Log:
New forrest based website for the Xerces TLP. While constructing this I borrowed many
ideas and parts from other TLP sites around the ASF, particularly the XML, Web
Services and XML Graphics sites. Thanks to the folks who built these pieces before
me.
Added:
xerces/site/trunk/README.txt
xerces/site/trunk/forrest.properties
xerces/site/trunk/publish.xml
xerces/site/trunk/src/documentation/README.txt
xerces/site/trunk/src/documentation/classes/
xerces/site/trunk/src/documentation/classes/CatalogManager.properties
xerces/site/trunk/src/documentation/content/
xerces/site/trunk/src/documentation/content/mirrors.cgi
xerces/site/trunk/src/documentation/content/xdocs/
xerces/site/trunk/src/documentation/content/xdocs/charter.xml
xerces/site/trunk/src/documentation/content/xdocs/favicon.ico (with props)
xerces/site/trunk/src/documentation/content/xdocs/index.xml
xerces/site/trunk/src/documentation/content/xdocs/legal.xml
xerces/site/trunk/src/documentation/content/xdocs/library.xml
xerces/site/trunk/src/documentation/content/xdocs/mail.xml
xerces/site/trunk/src/documentation/content/xdocs/mirrors.html
xerces/site/trunk/src/documentation/content/xdocs/news.xml
xerces/site/trunk/src/documentation/content/xdocs/participate.xml
xerces/site/trunk/src/documentation/content/xdocs/repo.xml
xerces/site/trunk/src/documentation/content/xdocs/site.xml
xerces/site/trunk/src/documentation/content/xdocs/tabs.xml
xerces/site/trunk/src/documentation/content/xdocs/team.xml
xerces/site/trunk/src/documentation/skinconf.xml
xerces/site/trunk/src/documentation/translations/
xerces/site/trunk/src/documentation/translations/langcode.xml
xerces/site/trunk/src/documentation/translations/languages_en.xml
xerces/site/trunk/src/documentation/translations/languages_es.xml
xerces/site/trunk/src/documentation/translations/menu.xml
xerces/site/trunk/src/documentation/translations/menu_af.xml
xerces/site/trunk/src/documentation/translations/menu_de.xml
xerces/site/trunk/src/documentation/translations/menu_es.xml
xerces/site/trunk/src/documentation/translations/menu_it.xml
xerces/site/trunk/src/documentation/translations/menu_no.xml
xerces/site/trunk/src/documentation/translations/menu_ru.xml
xerces/site/trunk/src/documentation/translations/menu_sk.xml
xerces/site/trunk/src/documentation/translations/tabs.xml
xerces/site/trunk/src/documentation/translations/tabs_es.xml
xerces/site/trunk/status.xml
Added: xerces/site/trunk/README.txt
URL: http://svn.apache.org/viewvc/xerces/site/trunk/README.txt?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/README.txt (added)
+++ xerces/site/trunk/README.txt Sun Jan 4 21:58:28 2009
@@ -0,0 +1,20 @@
+How to manage the XML Graphics website
+=========================================
+
+
+* Make sure you have Apache Forrest 0.7 installed.
+ * FORREST_HOME must be set
+ * PATH should have an entry to Forrest's bin directory so you can easily run Forrest.
+
+* When you've made changes and are happy with the results you can use ForrestBot locally.
+ ForrestBot comes with Apache Forrest. ForrestBot will do a clean build of the site and
+ deploy it to svn.apache.org through Subversion. Simply run:
+
+ ant -f publish.xml
+
+ (PLEASE make sure you do this only on a Unix machine, since on Windows we will get a
+ mess of LF and CRLF line endings.)
+
+* When the site is uploaded to the SVN repository you need to "svn up" in the
+ /www/xmlgraphics.apache.org directory on people.apache.org.
+ Wait a few hours until the website is rsync'ed to the real web server.
\ No newline at end of file
Added: xerces/site/trunk/forrest.properties
URL: http://svn.apache.org/viewvc/xerces/site/trunk/forrest.properties?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/forrest.properties (added)
+++ xerces/site/trunk/forrest.properties Sun Jan 4 21:58:28 2009
@@ -0,0 +1,108 @@
+#=========================================================================
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#=========================================================================
+
+##############
+# Properties used by forrest.build.xml for building the website
+# These are the defaults, un-comment them if you need to change them.
+##############
+
+# Prints out a summary of Forrest settings for this project
+#forrest.echo=true
+
+# Project name (used to name .war file)
+#project.name=my-project
+
+# Specifies name of Forrest skin to use
+#project.skin=tigris
+#project.skin=crust
+project.skin=pelt
+
+# comma separated list, file:// is supported
+#forrest.skins.descriptors=http://forrest.apache.org/skins/skins.xml,file:///c:/myskins/skins.xml
+
+##############
+# behavioural properties
+#project.menu-scheme=tab_attributes
+#project.menu-scheme=directories
+
+##############
+# layout properties
+
+# Properties that can be set to override the default locations
+#
+# Parent properties must be set. This usually means uncommenting
+# project.content-dir if any other property using it is uncommented
+
+#project.status=status.xml
+#project.content-dir=src/documentation
+#project.raw-content-dir=${project.content-dir}/content
+#project.conf-dir=${project.content-dir}/conf
+#project.sitemap-dir=${project.content-dir}
+#project.xdocs-dir=${project.content-dir}/content/xdocs
+#project.resources-dir=${project.content-dir}/resources
+#project.stylesheets-dir=${project.resources-dir}/stylesheets
+#project.images-dir=${project.resources-dir}/images
+#project.schema-dir=${project.resources-dir}/schema
+#project.skins-dir=${project.content-dir}/skins
+#project.skinconf=${project.content-dir}/skinconf.xml
+#project.lib-dir=${project.content-dir}/lib
+#project.classes-dir=${project.content-dir}/classes
+#project.translations-dir=${project.content-dir}/translations
+
+##############
+# validation properties
+
+# This set of properties determine if validation is performed
+# Values are inherited unless overridden.
+# e.g. if forrest.validate=false then all others are false unless set to true.
+forrest.validate=false
+#forrest.validate.xdocs=${forrest.validate}
+#forrest.validate.skinconf=${forrest.validate}
+#forrest.validate.sitemap=${forrest.validate}
+#forrest.validate.stylesheets=${forrest.validate}
+#forrest.validate.skins=${forrest.validate}
+#forrest.validate.skins.stylesheets=${forrest.validate.skins}
+
+# *.failonerror=(true|false) - stop when an XML file is invalid
+#forrest.validate.failonerror=true
+
+# *.excludes=(pattern) - comma-separated list of path patterns to not validate
+# e.g.
+#forrest.validate.xdocs.excludes=samples/subdir/**, samples/faq.xml
+#forrest.validate.xdocs.excludes=
+
+
+##############
+# General Forrest properties
+
+# The URL to start crawling from
+#project.start-uri=linkmap.html
+# Set logging level for messages printed to the console
+# (DEBUG, INFO, WARN, ERROR, FATAL_ERROR)
+#project.debuglevel=ERROR
+# Max memory to allocate to Java
+#forrest.maxmemory=64m
+# Any other arguments to pass to the JVM. For example, to run on an X-less
+# server, set to -Djava.awt.headless=true
+#forrest.jvmargs=
+# The bugtracking URL - the issue number will be appended
+#project.bugtracking-url=http://issues.apache.org/bugzilla/show_bug.cgi?id=
+#project.bugtracking-url=http://issues.apache.org/jira/browse/
+# The issues list as rss
+#project.issues-rss-url=
+#I18n Property only works for the "forrest run" target.
+#project.i18n=true
Added: xerces/site/trunk/publish.xml
URL: http://svn.apache.org/viewvc/xerces/site/trunk/publish.xml?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/publish.xml (added)
+++ xerces/site/trunk/publish.xml Sun Jan 4 21:58:28 2009
@@ -0,0 +1,55 @@
+<?xml version="1.0"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!--
+This is the publishing file for ForrestBot.
+
+Running "ant -f publish.xml" will build the Xerces site and deploy it using SVN on xerces.apache.org.
+
+$Id: publish.xml 474340 2006-11-13 14:44:31Z jeremias $
+-->
+<project name="forrest-docs" default="main">
+
+ <property name="build.work-dir" location="./build/forrest/work"/>
+ <property name="build.log-dir" location="./build/forrest/log"/>
+
+ <property name="getsrc.local.root-dir" location="."/>
+ <!--property name="getsrc.svn.url" value="http://svn.apache.org/repos/asf/xerces/site"/-->
+ <target name="getsrc" depends="getsrc.clean-workdir, getsrc.local"/>
+
+ <target name="build.fixCRLF" depends="build.forrest">
+ <fixcrlf srcdir="./build/forrest-docs" eol="lf">
+ <include name="**/*.htm*"/>
+ <include name="**/*.css"/>
+ <include name="**/*.xsl*"/>
+ <include name="**/*.js"/>
+ <include name="**/*.rdf"/>
+ <include name="**/*.txt"/>
+ <include name="**/*.xml"/>
+ </fixcrlf>
+ </target>
+
+ <target name="build" depends="build.forrest, build.fixCRLF"/>
+
+ <import file="../deploy.svn.settings" optional="true"/>
+
+ <property name="deploy.svn.url" value="https://svn.apache.org/repos/asf/xerces/site/deploy/"/>
+ <target name="deploy" depends="deploy.svn"/>
+
+ <property environment="env"/>
+ <import file="${env.FORREST_HOME}/tools/forrestbot/core/forrestbot.xml"/>
+</project>
\ No newline at end of file
Added: xerces/site/trunk/src/documentation/README.txt
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/README.txt?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/README.txt (added)
+++ xerces/site/trunk/src/documentation/README.txt Sun Jan 4 21:58:28 2009
@@ -0,0 +1,7 @@
+This is the base documentation directory.
+
+skinconf.xml # This file customizes Forrest for your project. In it, you
+ # tell forrest the project name, logo, copyright info, etc
+
+sitemap.xmap # Optional. This sitemap is consulted before all core sitemaps.
+ # See http://forrest.apache.org/docs/project-sitemap.html
Added: xerces/site/trunk/src/documentation/classes/CatalogManager.properties
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/classes/CatalogManager.properties?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/classes/CatalogManager.properties (added)
+++ xerces/site/trunk/src/documentation/classes/CatalogManager.properties Sun Jan 4 21:58:28 2009
@@ -0,0 +1,40 @@
+#=========================================================================
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#=========================================================================
+
+#=======================================================================
+# CatalogManager.properties
+#
+# This is the default properties file for Apache Forrest.
+# This facilitates local configuration of application-specific catalogs.
+#
+# See the Apache Forrest documentation:
+# http://forrest.apache.org/docs/your-project.html
+# http://forrest.apache.org/docs/validation.html
+
+# verbosity ... level of messages for status/debug
+# See forrest/src/core/context/WEB-INF/cocoon.xconf
+
+# catalogs ... list of additional catalogs to load
+# (Note that Apache Forrest will automatically load its own default catalog
+# from src/core/context/resources/schema/catalog.xcat)
+# use full pathnames
+# pathname separator is always semi-colon (;) regardless of operating system
+# directory separator is always slash (/) regardless of operating system
+#
+#catalogs=/home/me/forrest/my-site/src/documentation/resources/schema/catalog.xcat
+catalogs=
+
Added: xerces/site/trunk/src/documentation/content/mirrors.cgi
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/mirrors.cgi?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/content/mirrors.cgi (added)
+++ xerces/site/trunk/src/documentation/content/mirrors.cgi Sun Jan 4 21:58:28 2009
@@ -0,0 +1,7 @@
+#!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+# python includes correctly)
+# Copied from Stefan's page on mirrors
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*
\ No newline at end of file
Added: xerces/site/trunk/src/documentation/content/xdocs/charter.xml
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/xdocs/charter.xml?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/content/xdocs/charter.xml (added)
+++ xerces/site/trunk/src/documentation/content/xdocs/charter.xml Sun Jan 4 21:58:28 2009
@@ -0,0 +1,465 @@
+<?xml version="1.0"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>The Apache Xerces Project - Charter</title>
+ <notice></notice>
+ <abstract></abstract>
+ </header>
+ <body>
+<section id="INTRODUCTION">
+<title>1 INTRODUCTION</title>
+<p>
+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.
+</p>
+<p>
+1.2 This charter briefly describes the mission, history, organization, and
+processes of the project.
+</p>
+</section>
+
+<section id="MISSION">
+<title>2 MISSION</title>
+<p>
+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.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+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.
+</p>
+<p>
+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.
+</p>
+
+</section>
+<section id="HISTORY">
+<title>3 HISTORY</title>
+<p>
+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.
+</p>
+
+</section>
+
+<section id="TERMS">
+<title>4 TERMS</title>
+<p>
+4.1 The ASF Board. The management board of the Apache Software
+Foundation.
+</p>
+
+<p>
+4.2 The Project. The Apache Xerces Project; intended
+to refer to the source code, website and community that are Apache Xerces.
+</p>
+
+<p>
+4.3 Subproject. Apache Xerces is composed of a number of subprojects
+which fit into one of two categories:
+</p>
+<p>
+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.
+</p>
+<p>
+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.
+</p>
+
+<p>
+4.4 Product. Some deliverable (usually a binary or source
+package) that a subproject releases to the public. Subprojects
+may have multiple products.
+</p>
+
+<p>
+4.5 Contributor. Anyone who makes a contribution to the development
+of the Apache Xerces project or a subproject.
+</p>
+<p>
+4.6 Committer. Apache Xerces has a set of committers. Committers
+are contributors who have read/write access to the source code
+repository.
+</p>
+
+</section>
+
+<section id="PMC">
+<title>5 THE PROJECT MANAGEMENT COMMITTEE</title>
+<p>
+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.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+5.3 The PMC has the following responsibilities:
+</p>
+
+<p>
+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
+ <a href='http://incubator.apache.org'>http://incubator.apache.org</a>).
+
+</p>
+<p>
+b) Facilitating code or other donations by individuals or companies,
+ in collaboration with the Incubator.
+</p>
+<p>
+c) Resolving license issues and other legal issues in conjunction with
+ the ASF board.
+</p><p>
+d) Ensuring that administrative and infrastructure work is completed.
+</p><p>
+e) Facilitating relationships among subprojects and other Apache projects.
+</p><p>
+f) Facilitating relationships between Apache Xerces and the external
+ world.
+</p><p>
+g) Overseeing Apache Xerces to ensure that the mission defined in
+ this document is being fulfilled.
+</p><p>
+h) Resolving conflicts within the project.
+</p><p>
+i) Reporting to the ASF board (through the Chair) on the progress
+ of the project.
+
+</p><p>
+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.
+
+</p><p>
+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.
+</p><p>
+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.
+
+</p><p>
+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 <a href='http://www.apache.org/foundation/bylaws.html'>
+http://www.apache.org/foundation/bylaws.html</a> for more information.
+</p><p>
+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.
+</p><p>
+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.
+
+</p>
+</section>
+
+<section id="SUBPROJECTS">
+<title>6 SUBPROJECTS</title>
+<p>
+6.1 When a new subproject proposal is submitted to the PMC, it
+may be accepted by a two-thirds vote of the PMC.
+
+</p><p>
+6.2 A subproject may be removed by unanimous vote of the PMC, subject to
+the approval of the ASF board.
+
+</p>
+</section>
+<section id="CONTRIBUTORS">
+<title>7 CONTRIBUTORS</title>
+<p>
+7.1 Like all Apache projects, the Apache Xerces 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.
+
+</p><p>
+7.2 In order to ensure that all code contained in the Apache
+Xerces project's code repository is free of licensing,
+intellectual property and patent issues, any developer wishing
+to contribute a new feature to Xerces must either sign:
+
+</p><p>
+a) If contributing as an individual, sign the "Individual
+ Contributor License Agreement (CLA)"
+ (<a href='http://www.apache.org/licenses/icla.txt'>http://www.apache.org/licenses/icla.txt</a>)
+ and file a copy with the Secretary of the Corporation; or
+</p><p>
+b) If making the contribution as part of their employment
+ responsibilities, sign the "Corporate CLA (CCLA)",
+ (<a href='http://www.apache.org/licenses/cla-corporate.txt'>http://www.apache.org/licenses/cla-corporate.txt</a>)
+ and file a copy with the Secretary of the Corporation.
+
+</p><p>
+7.3 If the contribution in question is a small bugfix, the
+contributor need not sign a CLA, but need only provide the
+following information, attaching it to the communication
+containing the patch:
+
+</p><p>
+a) Name and employer
+</p><p>
+b) Are you the author of the code being contributed?
+</p><p>
+c) Do you have the right to grant the copyright and patent
+ licenses for the contribution that are set forth in the ASF v.2.0
+ license (<a href='http://www.apache.org/licenses/LICENSE-2.0'>http://www.apache.org/licenses/LICENSE-2.0</a>)?
+</p><p>
+d) Does your employer have any rights to code that you have
+ written, for example, through your contract for employment? If
+ so, has your employer given you permission to contribute the code
+ on its behalf or waived its rights in the code?
+</p><p>
+e) Are you aware of any third-party licenses or other
+ restrictions (such as related patents or trademarks) that could
+ apply to your contribution? If so, what are they?
+
+</p><p>
+7.4 Contributors who make regular and substantial contributions may become
+committers as described below.
+
+</p>
+</section>
+
+<section id="COMMITTERS">
+<title>8 COMMITTERS</title>
+<p>
+8.1 Each subproject has a set of committers. Committers are
+contributors who have read/write access to the source code
+repository.
+
+</p><p>
+8.2 Normally, a new committer is added after a contributor has
+been nominated by a committer and approved by at least 50 percent
+of the active committers for that subproject with no opposing
+votes. In the case that a subproject has a very small number of
+active committers, the PMC may choose to require a PMC resolution
+to approve the nomination of a contributor by one of the active
+committers in that subproject. All committers must have a signed
+Contributor License Agreement on file with the Secretary of the
+Corporation. Since, in most cases, contributors will already
+have contributed significant amounts of code, this should usually
+have been done before nomination.
+
+</p><p>
+8.3 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.
+
+</p><p>
+8.4 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, and
+only active committers are part of the PMC.
+
+</p><p>
+8.5 Committers remain active as long as they are contributing code or
+posting to the subproject mailing lists. If a committer has neither
+contributed code nor posted to the subproject mailing lists in 3
+months, the PMC chair may 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, and may be removed from the PMC mailing list.
+
+</p><p>
+8.6 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.
+
+</p>
+</section>
+<section id="INFRASTRUCTURE">
+<title>9 INFRASTRUCTURE</title>
+<p>
+9.1 The Apache Xerces project relies on the Apache XML project
+and the Apache Infrastructure project for the following:
+
+</p><p>
+a) Bug Database -- This is a system for tracking bugs and feature
+ requests.
+
+</p><p>
+b) Subproject Source Repositories -- These are several repositories
+ containing both the source code and documentation for the
+ subprojects.
+
+</p><p>
+c) Website -- A <a href='http://xerces.apache.org'>xerces.apache.org</a>
+ website will contain information about
+ the Apache Xerces project, including documentation, downloads of
+ releases, and this charter. Each subproject will have its own website
+ with subproject information.
+
+</p><p>
+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.
+
+</p><p>
+e) General Mailing List -- This mailing list is open to the public. It is
+ intended for discussions that cross subprojects.
+
+</p><p>
+f) Subproject Mailing Lists -- Each subproject should have at least one
+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.
+
+</p>
+</section>
+<section id="LICENSING">
+<title>10 LICENSING</title>
+<p>
+10.1 All contributions to the Apache Xerces project adhere to the
+Apache Software Foundation License, v.2.0
+(<a href='http://www.apache.org/licenses/LICENSE-2.0'>http://www.apache.org/licenses/LICENSE-2.0</a>)?
+All further contributions must be made under the
+same terms.
+
+</p><p>
+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; see sections 7.2 and 7.3.
+
+</p>
+</section>
+<section id="PROCESS">
+<title>11 THE DEVELOPMENT PROCESS</title>
+<p>
+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.
+
+</p>
+</section>
+<section id="REQUIREMENTS">
+<title>12 SUBPROJECT REQUIREMENTS</title>
+<p>
+12.1 Each subproject should have a set of requirements as well as an
+up-to-date release plan and design document on its dedicated web page.
+
+</p><p>
+12.2 It is recommended that each subproject have a smoke-test system
+that works at least as a basic integration test.
+
+</p>
+</section>
+<section id="RELATIONSHIP">
+<title>13 RELATIONSHIP TO OTHER APACHE PROJECTS</title>
+<p>
+13.1 The Apache Xerces project should work closely with other Apache
+projects, such as XML, Jakarta and the Apache Server, to avoid redundancy
+and achieve a coherent architecture among Apache Xerces and these
+projects.
+
+</p>
+
+</section>
+ </body>
+</document>
\ No newline at end of file
Added: xerces/site/trunk/src/documentation/content/xdocs/favicon.ico
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/xdocs/favicon.ico?rev=731460&view=auto
==============================================================================
Binary file - no diff available.
Propchange: xerces/site/trunk/src/documentation/content/xdocs/favicon.ico
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: xerces/site/trunk/src/documentation/content/xdocs/index.xml
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/xdocs/index.xml?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/content/xdocs/index.xml (added)
+++ xerces/site/trunk/src/documentation/content/xdocs/index.xml Sun Jan 4 21:58:28 2009
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>The Apache Xerces Project - xerces.apache.org</title>
+ </header>
+ <body>
+ <section>
+ <title>Welcome to the Apache Xerces Project</title>
+ <p>The <em>Apache Xerces Project</em> is responsible for software
+ licensed to the <a href="http://www.apache.org/">Apache Software Foundation</a>
+ intended for the creation and maintenance of:</p>
+ <ul>
+ <li>XML parsers</li>
+ <li>related software components</li>
+ </ul>
+ </section>
+ <section>
+ <title>Apache Xerces Project - Current Projects</title>
+ <p>The <em>Apache Xerces Project</em> currently consists of the following sub-projects, each focused on the development of XML parsers
+ and related components in various languages:</p>
+ <ul>
+ <li><em><a href="ext:xerces-c">Apache Xerces C++</a></em> - A processor for parsing, validating, serializing and manipulating XML, written in C++</li>
+ <li><em><a href="ext:xerces2-j">Apache Xerces2 Java</a></em> - A processor for parsing, validating, serializing and manipulating XML, written in Java</li>
+ <li><em><a href="ext:xerces-p">Apache Xerces Perl</a></em> - A processor for parsing, validating, serializing and manipulating XML, written in Perl</li>
+ <li><em><a href="ext:xml-commons">Apache XML Commons</a></em> - A collection of XML components and utilities, including a catalog resolver and various XML APIs</li>
+ </ul>
+ <section id="xerces-c">
+ <title>Apache Xerces C++</title>
+ <p><script type="text/javascript" src="http://www.ohloh.net/p/3465/widgets/project_users_logo.js"/></p>
+ <p>Xerces-C++ is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability to read
+ and write XML data. A shared library is provided for parsing, generating, manipulating, and validating XML documents. Xerces-C++ is faithful to the XML
+ 1.0 and 1.1 recommendations and many associated standards.</p>
+ <p>The parser provides high performance, modularity, and scalability. Source code, samples and API documentation are provided with the parser. For
+ portability, care has been taken to make minimal use of templates, no RTTI, and minimal use of #ifdefs.</p>
+ <p>Find out more about <a href="ext:xerces-c">Apache Xerces C++</a>.</p>
+ </section>
+ <section id="xerces2-j">
+ <title>Apache Xerces2 Java</title>
+ <p><script type="text/javascript" src="http://www.ohloh.net/p/3466/widgets/project_users_logo.js"/></p>
+ <p>Xerces2 Java is a library for parsing, validating and manipulating XML documents.</p>
+ <p>Xerces 2.x introduced the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely
+ modular and easy to program. XNI is merely an internal set of interfaces. There is no need for an XML application programmer to learn XNI if they only
+ intend to interface to the Xerces2 parser using standard interfaces like JAXP, DOM, and SAX. Xerces developers and application developers that need more
+ power and flexibility than that provided by the standard interfaces should read and understand XNI.</p>
+ <p>The latest version released, 2.9.1, provides support for the following standards and APIs:</p>
+ <ul>
+ <li>XML 1.0 (4th Edition)</li>
+ <li>Namespaces in XML 1.0 (2nd Edition)</li>
+ <li>XML 1.1 (2nd Edition)</li>
+ <li>Namespaces in XML 1.1 (2nd Edition)</li>
+ <li>W3C XML Schema 1.0 (2nd Edition)</li>
+ <li>XInclude 1.0 (2nd Edition)</li>
+ <li>OASIS XML Catalogs 1.1</li>
+ <li>SAX 2.0.2</li>
+ <li>DOM Level 3 Core, Load and Save</li>
+ <li>DOM Level 2 Core, Events, Traversal and Range</li>
+ <li>JAXP 1.3</li>
+ </ul>
+ <p>Find out more about <a href="ext:xerces2-j">Apache Xerces2 Java</a>.</p>
+ </section>
+ <section id="xerces-p">
+ <title>Apache Xerces Perl</title>
+ <p><script type="text/javascript" src="http://www.ohloh.net/p/12649/widgets/project_users_logo.js"/></p>
+ <p>XML::Xerces is the Perl API to the Apache project's Xerces XML parser. It is implemented using the Xerces C++ API, and it provides access to most of the
+ C++ API from Perl. Because it is based on Xerces-C, XML::Xerces provides a validating XML parser that makes it easy to give your application the ability to
+ read and write XML data. Classes are provided for parsing, generating, manipulating, and validating XML documents. XML::Xerces is faithful to the XML 1.0
+ and 1.1 recommendations and associated standards (DOM levels 1, 2, and 3, SAX 1 and 2, Namespaces, and W3C XML Schema).</p>
+ <p>The parser provides high performance, modularity, and scalability, and provides full support for Unicode. XML::Xerces implements the vast majority of the
+ Xerces-C++ API (if you notice any discrepancies please mail the list). The exception is some functions in the C++ API which either have better Perl counterparts
+ (such as file I/O) or which manipulate internal C++ information that has no role in the Perl module. The majority of the API is created automatically using
+ Simplified Wrapper Interface Generator (SWIG). However, care has been taken to make most method invocations natural to perl programmers, so a number of
+ rough C++ edges have been smoothed over (See the Special Perl API Features section).</p>
+ <p>Find out more about <a href="ext:xerces-p">Apache Xerces Perl</a>.</p>
+ </section>
+ <section id="xml-commons">
+ <title>Apache XML Commons</title>
+ <p><script type="text/javascript" src="http://www.ohloh.net/p/5471/widgets/project_users_logo.js"/></p>
+ <p>Apache XML Commons provides an Apache-hosted set of SAX, DOM and JAXP interfaces for use in other xml-based projects. It is also home to the XML Commons
+ Resolver, a component which can be used in a wide variety of XML parsing, processing and related programs to resolve various public or system identifiers into
+ accessible URLs for use by your application. The resolver supports several catalog types for mapping, including OASIS XML, OASIS TR 9401 and XCatalog styles.</p>
+ <p>Find out more about <a href="ext:xml-commons">Apache XML Commons</a>.</p>
+ </section>
+ </section>
+ </body>
+</document>
Added: xerces/site/trunk/src/documentation/content/xdocs/legal.xml
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/xdocs/legal.xml?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/content/xdocs/legal.xml (added)
+++ xerces/site/trunk/src/documentation/content/xdocs/legal.xml Sun Jan 4 21:58:28 2009
@@ -0,0 +1,47 @@
+<?xml version="1.0"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>The Apache Xerces Project - Legal Stuff</title>
+ <notice></notice>
+ <abstract></abstract>
+ </header>
+ <body>
+
+ <section id="Legal">
+ <title>Legal Stuff</title>
+ <p>All material on this website is Copyright (c) 1999-2009 The Apache Software Foundation. All Rights Reserved.</p>
+ </section>
+
+ <section id="MoreDetails">
+ <title>Details</title>
+ <p> For details look at the file: <a href="http://www.apache.org/licenses/">Licenses - The Apache Software Foundation</a>.</p>
+ </section>
+
+ <section id="Trademarks">
+ <title>Trademarks</title>
+ <p>IBM is a trademark of International Business Systems, Inc. Lotus is a trademark of Lotus Development Corporation. Sun and Sun
+ Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States
+ and other countries, exclusively licensed through X/Open Company, Ltd. Windows, WindowsNT, and Win32 are registered trademarks of
+ Microsoft Corp. Mac OS X and Macintosh are registered trademarks of Apple Computer, Inc. All other product names mentioned herein
+ and throughout the entire web site are trademarks of their respective owners.</p>
+ </section>
+
+ </body>
+</document>
Added: xerces/site/trunk/src/documentation/content/xdocs/library.xml
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/xdocs/library.xml?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/content/xdocs/library.xml (added)
+++ xerces/site/trunk/src/documentation/content/xdocs/library.xml Sun Jan 4 21:58:28 2009
@@ -0,0 +1,109 @@
+<?xml version="1.0"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>The Apache Xerces Project - Reference Library</title>
+ </header>
+ <body>
+ <section>
+ <title>Reference Library</title>
+ <p>
+ The <em>Apache Xerces Project</em> lives or fails based on its human resources. Users and
+ contributors alike help the project with ideas and brainpower. A common
+ foundation of knowledge is required to effectively participate in this virtual
+ community. The following is a list of documents that we have found helpful for us
+ and may be helpful to you:
+ </p>
+ </section>
+ <section>
+ <title>Technical Resources</title>
+ <p>
+ These resources are useful to read for anybody contributing source code to the project.
+ </p>
+ <ul>
+ <li>
+ <a href="http://svnbook.red-bean.com/">Version Control with Subversion</a>
+ <br/>
+ Written by Ben Collins-Sussman, Brian W. Fitzpatrick and C. Michael Pilato, this book
+ is the main manual for Subversion.
+ </li>
+ <li>
+ <a href="http://www.apache.org/dev/version-control.html#anon-svn">Apache guidance for Subversion</a>
+ <br/>
+ The Apache Guidelines for using Subversion. You should be familiar with them.
+ </li>
+ </ul>
+ </section>
+ <section>
+ <title>Source Code Philosophy Resources</title>
+ <p>
+ The following are a set of articles written about source code movements that help illustrate some
+ of the attributes of a collaborative project such as this. You may not agree with all of the points
+ of these articles, but an understanding of them will help in communicating with everyone on the project.
+ </p>
+ <ul>
+ <li>
+ <a href="http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/">The Cathedral and the Bazaar</a>
+ <br/>
+ Written by Eric S. Raymond, this is a must read for anyone willing to join or
+ support a volunteer project.
+ </li>
+ <li>
+ <a href="http://catb.org/~esr/writings/homesteading/homesteading/">Homesteading the Noosphere</a>
+ <br/>
+ Written by Eric S. Raymond, this is a sequel to "The Cathedral and the Bazaar". It
+ details the property and ownership customs of the open-source culture. This
+ analysis has larg implications for anyone interested in organizing large-scale
+ intellectual collaborations such as this project.
+ </li>
+ </ul>
+ </section>
+ <section>
+ <title>Important XML Standards</title>
+ <p>
+ The following are a set of standards and specifications that the various sub-projects of
+ Xerces implement. Having an understanding of some or all of these is important for anyone
+ contributing to the project.
+ </p>
+ <ul>
+ <li><strong>W3C XML Core</strong>:
+ <ul>
+ <li><a href="http://www.w3.org/TR/REC-xml/">XML 1.0</a></li>
+ <li><a href="http://www.w3.org/TR/xml11/">XML 1.1</a></li>
+ <li><a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML 1.0</a></li>
+ <li><a href="http://www.w3.org/TR/xml-names11/">Namespaces in XML 1.1</a></li>
+ <li><a href="http://www.w3.org/TR/xml-infoset/">XML Information Set</a></li>
+ <li><a href="http://www.w3.org/TR/xinclude/">XInclude 1.0</a></li>
+ </ul>
+ </li>
+ <li><strong>W3C XML Schema</strong>:
+ <ul>
+ <li><a href="http://www.w3.org/TR/xmlschema-0/">XML Schema 1.0 Part 0: Primer</a></li>
+ <li><a href="http://www.w3.org/TR/xmlschema-1/">XML Schema 1.0 Part 1: Structures</a></li>
+ <li><a href="http://www.w3.org/TR/xmlschema-2/">XML Schema 1.0 Part 2: Datatypes</a></li>
+ </ul>
+ </li>
+ <li><strong>W3C DOM</strong>: <a href="http://www.w3.org/DOM/DOMTR">DOM L1, L2 and L3 specifications</a></li>
+ <li><strong>SAX</strong>: <a href="http://www.saxproject.org/">Simple API for XML (SAX)</a></li>
+ <li><strong>JAXP (JSR 206)</strong>: <a href="http://www.jcp.org/en/jsr/detail?id=206">Java API for XML Processing (JAXP)</a></li>
+ <li><strong>StAX (JSR 173)</strong>: <a href="http://www.jcp.org/en/jsr/detail?id=173">Streaming API for XML (StAX)</a></li>
+ </ul>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Added: xerces/site/trunk/src/documentation/content/xdocs/mail.xml
URL: http://svn.apache.org/viewvc/xerces/site/trunk/src/documentation/content/xdocs/mail.xml?rev=731460&view=auto
==============================================================================
--- xerces/site/trunk/src/documentation/content/xdocs/mail.xml (added)
+++ xerces/site/trunk/src/documentation/content/xdocs/mail.xml Sun Jan 4 21:58:28 2009
@@ -0,0 +1,262 @@
+<?xml version="1.0"?>
+<!--
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+-->
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
+<document>
+ <header>
+ <title>The Apache Xerces Project - Mailing Lists</title>
+ </header>
+ <body>
+ <p>
+ Every volunteer project obtains its strength from the people involved in
+ it. Mailing lists provide a simple and effective communication
+ mechanism.
+ </p>
+ <p>
+ You are welcome to join any of these mailing lists (or all of them if
+ you wish). You can choose to lurk, or actively participate. It's up to
+ you. Before you join these lists, you may want to look over the resources
+ in the <a href="site:ref">Reference Library</a> section. As with any
+ mailing list, you should probably read any FAQ postings or simply read a
+ sampling of postings on the list before posting your first question.
+ </p>
+ <section id="usage">
+ <title>Usage Notes</title>
+ <p>
+ Archives are generally named after the project they're about (duh!)
+ with a suffix that denotes the subjects covered. Common suffixes are:
+ </p>
+ <ul>
+ <li>
+ <code>*-dev</code> Developer list - for technical questions about
+ the product, code patches, bug submissions about advanced functionality, etc.
+ </li>
+ <li>
+ <code>*-users</code> Users list - for general usage questions
+ about the product from an end-users perspective
+ </li>
+ <li>
+ <code>*-commits</code> commit list - this is a read-only list that
+ sends out email with details of all changes to that project's CVS, SVN or Wiki repository
+ </li>
+ </ul>
+ <p>
+ The ezmlm mailing list controller accepts commands by sending emails
+ to <code><listname>-command</code>, generally like the following:
+ </p>
+ <ul>
+ <li>
+ <code>*-subscribe</code> Subscribe your current email address to the list
+ </li>
+ <li>
+ <code>*-unsubscribe</code> UnSubscribe your <strong>current</strong> email address from the list
+ </li>
+ <li>
+ <code>*-help</code> get Help on mailing list commands
+ </li>
+ </ul>
+ <note label="Example">
+ If you want to unsubscribe from the Xerces General
+ mailing list you send an empty mail to <code>general-unsubscribe@xerces.apache.org</code>.
+ </note>
+ </section>
+ <section id="public_archives">
+ <title>Public Archives</title>
+ <p>
+ Archives of all public mailing lists can be found here:
+ </p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/">http://mail-archives.apache.org/mod_mbox/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/">http://xerces.apache.org/mail/</a> (gzipped mbox files)</li>
+ <li>
+ Some lists are also available from
+ <a class="fork" href="http://marc.info/">http://marc.info/</a>,
+ <a class="fork" href="http://www.mail-archive.com/">The Mail Archive</a>,
+ <a class="fork" href="http://www.gmane.com/">GMANE</a>,
+ <a class="fork" href="http://www.nabble.com/Xml-Graphics-f307.html">Nabble</a> and
+ <a class="fork" href="http://xerces.markmail.org/">MarkMail</a>.
+ </li>
+ </ul>
+ </section>
+ <section id="xerces-general">
+ <title>The Xerces General Discussion List</title>
+ <p>
+ <em>Low Traffic</em>
+ <a class="fork" href="mailto:general-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:general-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This list is for issues that span across all xerces.apache.org projects, whether technical
+ or organizational. Discussions about specific code bases should be redirected to one of the
+ Xerces sub-project-specific lists below.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-general/">http://mail-archives.apache.org/mod_mbox/xerces-general/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/general/">http://xerces.apache.org/mail/general/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-general.markmail.org/">http://xerces-general.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xerces-c-user">
+ <title>The Xerces C++ Users List</title>
+ <p>
+ <em>Medium Traffic</em>
+ <a class="fork" href="mailto:c-users-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:c-users-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is the list where users of the Xerces C++ XML parser
+ can meet and discuss questions, raise issues, etc.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-c-users/">http://mail-archives.apache.org/mod_mbox/xerces-c-users/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/c-users/">http://xerces.apache.org/mail/c-users/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-c-users.markmail.org/">http://xerces-c-users.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xerces-c-dev">
+ <title>The Xerces C++ Developers List</title>
+ <p>
+ <em>Medium Traffic</em>
+ <a class="fork" href="mailto:c-dev-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:c-dev-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is the list where participating developers of the Xerces C++ XML
+ parser meet and discuss issues, code changes/additions, etc. This list currently
+ also discusses the COM bindings to the Xerces C++ parser as well. The Perl
+ binding now has a separate mailing list (see below).
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-c-dev/">http://mail-archives.apache.org/mod_mbox/xerces-c-dev/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/c-dev/">http://xerces.apache.org/mail/c-dev/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-c-dev.markmail.org/">http://xerces-c-dev.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xerces-j-user">
+ <title>The Xerces Java Users List</title>
+ <p>
+ <em>Medium Traffic</em>
+ <a class="fork" href="mailto:j-users-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:j-users-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is the list where users of the Xerces Java XML parser
+ can meet and discuss questions, raise issues, etc.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-j-users/">http://mail-archives.apache.org/mod_mbox/xerces-j-users/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/j-users/">http://xerces.apache.org/mail/j-users/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-j-users.markmail.org/">http://xerces-j-users.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xerces-j-dev">
+ <title>The Xerces Java Developers List</title>
+ <p>
+ <em>Medium Traffic</em>
+ <a class="fork" href="mailto:j-dev-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:j-dev-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is the list where participating developers of the Xerces Java XML
+ parser meet and discuss issues, code changes/additions, etc.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-j-dev/">http://mail-archives.apache.org/mod_mbox/xerces-j-dev/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/j-dev/">http://xerces.apache.org/mail/j-dev/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-j-dev.markmail.org/">http://xerces-j-dev.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xerces-p-dev">
+ <title>The Xerces Perl Developers List</title>
+ <p>
+ <em>Low Traffic</em>
+ <a class="fork" href="mailto:p-dev-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:p-dev-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is the list where participating developers of the Xerces Perl binding for XML
+ parsing meet and discuss issues, code changes/additions, etc.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-p-dev/">http://mail-archives.apache.org/mod_mbox/xerces-p-dev/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/p-dev/">http://xerces.apache.org/mail/p-dev/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-p-dev.markmail.org/">http://xerces-p-dev.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xerces-commits">
+ <title>The Xerces Commits List</title>
+ <p>
+ <em>Medium Traffic</em>
+ <a class="fork" href="mailto:commits-subscribe@xerces.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:commits-unsubscribe@xerces.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is a read-only list that sends out e-mail notifications with details of all commits to the
+ Apache Xerces Java, Xerces C++ and Xerces Perl code repositories as well as notifications for
+ updates to the Xerces Wiki.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xerces-commits/">http://mail-archives.apache.org/mod_mbox/xerces-commits/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xerces.apache.org/mail/commits/">http://xerces.apache.org/mail/commits/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xerces-commits.markmail.org/">http://xerces-commits.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xml-commons-dev">
+ <title>The XML Commons Developers List</title>
+ <p>
+ <em>Low Traffic</em>
+ <a class="fork" href="mailto:commons-dev-subscribe@xml.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:commons-dev-unsubscribe@xml.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is the list for those interested and involved with the active development
+ of the XML Commons sub-project.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xml-commons-dev/">http://mail-archives.apache.org/mod_mbox/xml-commons-dev/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xml.apache.org/mail/commons-dev/">http://xml.apache.org/mail/commons-dev/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xml-commons-dev.markmail.org/">http://xml-commons-dev.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ <section id="xml-commons-commits">
+ <title>The XML Commons Commits List</title>
+ <p>
+ <em>Low Traffic</em>
+ <a class="fork" href="mailto:commons-cvs-subscribe@xml.apache.org">Subscribe</a>
+ <a class="fork" href="mailto:commons-cvs-unsubscribe@xml.apache.org">Unsubscribe</a>
+ </p>
+ <p>
+ This is a read-only list that sends out e-mail notifications with details of all commits to the
+ XML Commons code repository.
+ </p>
+ <p><strong>Archives:</strong></p>
+ <ul>
+ <li><a class="fork" href="http://mail-archives.apache.org/mod_mbox/xml-commons-cvs/">http://mail-archives.apache.org/mod_mbox/xml-commons-cvs/</a> (mod_mbox archives)</li>
+ <li><a class="fork" href="http://xml.apache.org/mail/commons-cvs/">http://xml.apache.org/mail/commons-cvs/</a> (gzipped mbox files)</li>
+ <li><a class="fork" href="http://xml-commons-cvs.markmail.org/">http://xml-commons-cvs.markmail.org/</a> (MarkMail archives)</li>
+ </ul>
+ </section>
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xerces.apache.org
For additional commands, e-mail: commits-help@xerces.apache.org