xml-general-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From curc...@apache.org
Subject cvs commit: xml-site/sources/website whoweare.xml news.xml mission.xml mail.xml library.xml guidelines.xml
Date Tue, 18 Sep 2001 19:45:02 GMT
curcuru     01/09/18 12:45:01

  Modified:    sources/website whoweare.xml news.xml mission.xml mail.xml
                        library.xml guidelines.xml
  Various updates for news; clarify and expand on mailing lists;
  included copy of and reference to the charter; many more minor edits
  Revision  Changes    Path
  1.10      +10 -1     xml-site/sources/website/whoweare.xml
  Index: whoweare.xml
  RCS file: /home/cvs/xml-site/sources/website/whoweare.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- whoweare.xml	2001/03/27 23:37:36	1.9
  +++ whoweare.xml	2001/09/18 19:45:01	1.10
  @@ -6,7 +6,7 @@
           The <em>xml.apache.org</em> project operates on a meritocracy: the
more you do,
           the more
  -        responsibility you will obtain. This page lists all of the people who have gone
  +        responsibility you can obtain. This page lists all of the people who have gone
           extra mile and are Committers or members of the Project Management Committee.
           If you would like to get involved, the first step is to join the <link
  @@ -26,6 +26,15 @@
            <li>Dirk-Willem Van Gulik
             <jump href="mailto:dirkx@webweaving.org">dirkx@webweaving.org</jump></li>
        </ul>    </s2>
  +  <s2 title="Committers">
  +    <p>
  +      Committers are people with write access to their project's CVS 
  +      repository.  New Committers to each project are nominated by and 
  +      voted into a project by that project's current committers.  For more 
  +      details on getting involved see the <link idref="roles">roles</link>.
  +    </p>
  +  </s2>
     <s2 title="Advisors">
  1.9       +72 -20    xml-site/sources/website/news.xml
  Index: news.xml
  RCS file: /home/cvs/xml-site/sources/website/news.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- news.xml	2001/08/10 11:21:14	1.8
  +++ news.xml	2001/09/18 19:45:01	1.9
  @@ -3,78 +3,130 @@
   <s1 title="News and Status">
  -  <s2 title='Xerces 2.0.0 (beta) is released'>
  -   <p>
  -    The beta release for Xerces2 marks the first step in producing the
  -    next generation of Xerces XML parser technology. Xerces2 beta is
  -    available from the <jump href='/dist/'>download pages</jump>.
  -   </p>
  +  <s2 title="Current News">
  +    <p>Committers should feel free to update these pages with relevant 
  +    news about their projects.  Be sure to see the information about updating 
  +    the xml.apache.org website in the <link idref="guidelines">guidelines</link>.
  +    </p>
  +      <s3 title='Xerces 2.0.0 (beta) is released'>
  +       <p>
  +        The beta release for Xerces2 marks the first step in producing the
  +        next generation of Xerces XML parser technology. Xerces2 beta is
  +        available from the <jump href='/dist/'>download pages</jump>.
  +       </p>
  +      </s3>
  +    <ul>
  +      <li>xml-commons subproject is formed! (Summer-01)
  +      <br/>
  +      A new subproject focusing on sharing common XML code and interfaces, etc. 
  +      was formed recently.  For details, look in the xml-commons repository, 
  +      in the general@xml.apache.org mailing list, or the commons-dev@xml.apache.org 
  +      mailing list.
  +      </li>
  +      <li>Xalan-J was nominated for an award! (Summer-01)
  +      <br/>
  +Dear Apache XML Project, 
  +Congratulations! JavaWorld has selected the Apache XML Project's Xalan-Java
  +1.2.2 as a finalist in the Best Java-XML Application category of our
  +Editors' Choice Awards. Established in 1997, the awards recognize those innovative companies,
  +organizations, and individuals committed to developing new Java tools and
  +technologies that drive the platform forward. More than 100 products and
  +technologies were nominated by vendors, readers, as well as JavaWorld
  +editors and writers. We'll publish the complete list of finalists in each
  +category by 5 p.m. PDT on Friday, May 4 (go to:
  +As a finalist, members of your product team will be invited to attend
  +JavaWorld's Editors' Choice Awards ceremony at the JavaOne Conference and
  +Expo from June 4-8 in San Francisco, where a winner in each category will
  +be announced. 
  +Regards, Scott Plamondon
  +Senior Editor
  +      </li>
  +      <li>Batik was nominated for an award! (Sep-01)
  +      <br/>Some details were posted on<jump href="http://marc.theaimsgroup.com/?l=xml-apache-general&amp;m=99973420212175&amp;w=2">the
general mailing list</jump></li>
  +    </ul>
  -  <s2 title="Batik Status: Source Code and Binaries Available">
  +  <s2 title="Project Status">
  +  <s3 title="Batik Status: Source Code and Binaries Available">
         Batik, the Java Based toolkit for applications that want to use images in
         the Scalable Vector Graphics (SVG) format is finally available on our
         <jump href="/dist/">download pages</jump>!
  -  </s2>
  +  </s3>
  -  <s2 title="Xang - Source code for XPages from Datachannel released">
  +  <s3 title="Xang - Source code for XPages from Datachannel released">
         Xang, the new code name of the XPages project from DataChannel is 
         currently available in source form for download. Check out the
         <jump href="/dist/">download pages</jump> for the source.
  -  </s2>
  +  </s3>
  -  <s2 title="Crimson - Source code for Project X from Sun released">
  +  <s3 title="Crimson - Source code for Project X from Sun released">
         Crimson, the code name of the XML Parser Project X from Sun is 
         currently available in source form for download. 
         Check out the
         <jump href="/dist">download pages</jump> for the source.
  -  </s2>
  +    <p>The current production release is Crimson 1.1.2beta2(Sep-01).
  +    Work on Crimson is mostly limited to bugfixing; discussions take place on general@xml.apache.org.</p>
  +  </s3>
  -  <s2 title="Xerces status: Source Code and Binaries Available">
  +  <s3 title="Xerces status: Source Code and Binaries Available">
         Xerces XML parsers in Java, C++, Perl, and COM are currently available in 
         source code and binary form. Check out the
         <jump href="/dist/">download pages</jump> for binaries 
         and source!
  -  </s2>
  +    <p>The current production release is Xerces-J 1.4.3 (Sep-01).
  +    Work on 1.x is mostly limited to bugfixing; most of the Xerces community 
  +    is moving forward with Xerces 2.x codebase.</p>
  +  </s3>
  -  <s2 title="Xalan Status: Source Code and Binaries Available">
  +  <s3 title="Xalan Status: Source Code and Binaries Available">
         Xalan XSLT stylesheet processor in Java is currently available in 
         source code and binary form. Check out the
         <jump href="/dist/">download pages</jump> for binaries and
  -  </s2>
  +  </s3>
  -  <s2 title="Cocoon Status: Source Code and Binaries Available">
  +  <s3 title="Cocoon Status: Source Code and Binaries Available">
         Cocoon, the XML-based web publishing solution in Java, are available.
         Check out the <jump href="/dist/">download pages</jump> for binaries
         and sources.
  -  </s2>
  +  </s3>
  -  <s2 title="FOP Status: Source Code and Binaries Available">
  +  <s3 title="FOP Status: Source Code and Binaries Available">
         FOP, the XSL:FO formatting objects processor in Java, is currently available in 
         source code and binary form. Check out the
         <jump href="/dist/">download pages</jump> for binaries and
  +  </s3>
  -  <s2 title="In the News">
  +  <s2 title="Past News">
           Apache forms xml.apache.org --
  1.4       +220 -16   xml-site/sources/website/mission.xml
  Index: mission.xml
  RCS file: /home/cvs/xml-site/sources/website/mission.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mission.xml	2000/12/04 15:19:04	1.3
  +++ mission.xml	2001/09/18 19:45:01	1.4
  @@ -2,25 +2,223 @@
   <!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
   <s1 title="Project Mission">
  -  <s2 title="Mission">
  +  <s2 title="Mission/Charter">
  -      The mission of the <em>xml.apache.org</em> project is:
  +      <em>The most current copy of our charter can always be found 
  +      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.      
  -    <ul>
  -      <li>
  -        to provide commercial-quality standards-based XML solutions that are 
  -        developed in an open and cooperative fashion,
  -      </li> 
  -      <li>
  -        to provide feedback to standards bodies (such as IETF and W3C) from 
  -        an implementation perspective, and
  -      </li> 
  -      <li>
  -        to be a focus for XML-related activities within Apache projects
  -      </li>
  -    </ul>
  +    <source>
  +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
  +(both independent and company-affiliated experts), who use the
  +Internet to communicate, plan, and develop XML software and related
  +This charter briefly describes the mission, history, organization, and
  +processes of the project.
  +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
  +has great potential to improve the functionality and use of
  +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.
  +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
  +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.
  +This project was established under the direction of the newly-formed
  +Apache Software Foundation in August 1999 to facilitate joint
  +open-source development.
  +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
  +   world.
  +8) 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
  +In the unlikely event that a member of the PMC becomes disruptive to
  +the process or ceases to contribute for an extended period, said
  +member may be removed by unanimous vote of remaining PMC members.
  +The 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.
  +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.
  +A new subproject proposal is submitted to the PMC, accepted by majority
  +committer vote, and then subject to final approval by the PMC.
  +Each subproject has a set of committers. Committers are developers 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
  +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.
  +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.
  +The xml.apache.org project site must provide the following:
  +Bug Database -- This is a system for tracking bugs and feature
  +Subproject Source Repositories -- These are several CVS repositories
  +containing both the source code and documentation for the
  +subprojects. Each subproject will have a set of committers to its
  +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
  +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
  +intended for discussions that cross subprojects.
  +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.
  +All contributions to the xml.apache.org project adhere to the "ASF
  +Source Code License." All further contributions must be made under the
  +same terms. All contributions must contain the following copyright
  +notice: [This changes now that the license is available]
  +Copyright (c) {date} {name of contributor} and others. All rights
  +reserved. This program and the accompanying materials are made
  +available under the terms of the ASF Source Code License, as found in
  +the file ASF.code.license.html that is included in this distribution.
  +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
  +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
  +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.
  +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
  +    </source>
  +  </s2>
  +  <s2 title="Projects">
  -      The <em>Apache XML Project</em> currently consists of seven sub- 
  +      The <em>Apache XML Project</em> currently consists of a number of sub-

         projects, each focused on a different aspect of XML:
  @@ -44,6 +242,12 @@
           <em>Batik</em> - A Java based toolkit for Scalable Vector Graohics
  +      </li> 
  +      <li>
  +        <em>Axis</em> - A Java based implementation of SOAP
  +      </li> 
  +      <li>
  +        <em>Commons</em> - A meta-project of common XML-oriented code
  1.11      +85 -29    xml-site/sources/website/mail.xml
  Index: mail.xml
  RCS file: /home/cvs/xml-site/sources/website/mail.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- mail.xml	2001/02/20 18:33:15	1.10
  +++ mail.xml	2001/09/18 19:45:01	1.11
  @@ -6,21 +6,53 @@
       Every volunteer project obtains its strength from the people involved in 
       it. Mailing lists provide a simple and effective communication 
  -    <br/>
  +  </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 should look over the resources in 
  -    the Reference Library section.
  +    the Reference Library 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.
  +  <s2 title="Usage Notes">
  +    <p>
  +      Archives are generally named after the project they're about (duh!) 
  +      with a suffix that denotes the subjects covered.  Common suffixes are:
  +      <br/>
  +      <code>*-dev</code> &nbsp;&nbsp;&nbsp;&nbsp; Developer
list - for technical questions about 
  +      the product, code patches, bug submissions about advanced functionality, etc.
  +      <br/>
  +      <code>*-user, *-users</code> &nbsp;&nbsp;&nbsp;&nbsp;
Users list - for general usage questions
  +      about the product from an end-users perspective
  +      <br/>
  +      <code>*-cvs</code> &nbsp;&nbsp;&nbsp;&nbsp; CVS commit
list - this is a read-only list that 
  +      sends out email with details of all checkins to that project's CVS repository
  +    </p>
  +    <p>
  +      The ezmlm mailing list controller accepts commands by sending emails 
  +      to <code>listname-command</code>, generally like the following:
  +      <br/>
  +      <code>*-subscribe</code> &nbsp;&nbsp;&nbsp;&nbsp; Subscribe
your current email address to the list
  +      <br/>
  +      <code>*-unsubscribe</code> &nbsp;&nbsp;&nbsp;&nbsp; UnSubscribe
your *current* email address from the list
  +      <br/>
  +      <code>*-help</code> &nbsp;&nbsp;&nbsp;&nbsp; get Help
on mailing list commands
  +    </p>
  +  </s2>
     <s2 title="Public archives">
  +    <p>
  +      Archives of many of the most popular xml.apache.org mailing lists 
  +      are kept at <jump href="http://marc.theaimsgroup.com/">http://marc.theaimsgroup.com/</jump>,
  +      which are organized by month and include search features for both subjects 
  +      and message text.  Many lists are also archived by other large 
  +      mailing list archive sites as well.
  +    </p>
  -      All the mailing lists are archived at
  -      <jump href="http://xml-archive.webweaving.org">http://xml-archive.webweaving.org</jump>
  -      and open to the public. This also includes the one way announcement 
  -      list and the 'commit' lists. The latter are automated mailing lists 
  -      which contain a record of any changes made to the source code, by whom 
  -      they where made and why.
  +      Many mailing lists are also archived at
  +      <jump href="http://archive.covalent.net/">http://archive.covalent.net/</jump>
  @@ -46,30 +78,25 @@
         <jump href="mailto:general-unsubscribe@xml.apache.org">Unsubscribe</jump>
  -      This list is for issues that span across all xml.apache.org projects. 
  +      This list is for issues that span across all xml.apache.org projects,
  +      whether technical or organizational. 
         Discussions about specific code bases should be redirected to one of 
         the codebase-specific lists below. An
         <jump href="http://xml-archive.webweaving.org/xml-archive-general">archive</jump>
         is kept.
  +      One exception is the xml-crimson codebase, which does not currently have it's own
mailing list.
     <s2 title="The Xerces Developer List (obsolete)">
  -      <em>Medium Traffic</em>
  -      <jump href="mailto:xerces-dev-subscribe@xml.apache.org">Subscribe</jump>
  -      <jump href="mailto:xerces-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
  -      <br/>
  -      <em>CVS Commit</em>
  -      <jump href="mailto:xerces-cvs-subscribe@xml.apache.org">Subscribe</jump>
  -      <jump href="mailto:xerces-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
  +      <em>Low Traffic - Obsolete</em>
  +      mailto:xerces-dev-subscribe@xml.apache.org
  +      mailto:xerces-dev-unsubscribe@xml.apache.org
         <em>This list has now been split into separate lists for Java, C++, and Perl
parser efforts. 
         Everybody should switch to one of the specific mailing lists below.</em>
  -      Archives of the
  -      <jump href="http://xml-archive.webweaving.org/xml-archive-xerces">developers</jump>
  -      mailing list is still available.
  @@ -159,28 +186,57 @@
  +  <s2 title="The Xalan-J Users List">
  +    <p>
  +      <em>Medium Traffic</em>
  +      <jump href="mailto:xalan-j-users-subscribe@xml.apache.org">Subscribe</jump>
  +      <jump href="mailto:xalan-j-users-unsubscribe@xml.apache.org">Unsubscribe</jump>
  +    </p>
  +    <p>
  +      This is the list where all users can discuss general usage questions 
  +      about the <jump href="xalan-j/">java version of Xalan</jump>.  For detailed
technical questions, 
  +      please see the developer list below.
  +      <br/>
  +      Archives are kept at <jump href="http://marc.theaimsgroup.com/?l=xalan-j-users">http://marc.theaimsgroup.com/?l=xalan-j-users</jump>
  +    </p>
  +  </s2>
  +  <s2 title="The Xalan-C Users List">
  +    <p>
  +      <em>Low Traffic</em>
  +      <jump href="mailto:xalan-c-users-subscribe@xml.apache.org">Subscribe</jump>
  +      <jump href="mailto:xalan-c-users-unsubscribe@xml.apache.org">Unsubscribe</jump>
  +    </p>
  +    <p>
  +      This is the list where all users can discuss general usage questions 
  +      about the <jump href="xalan-c/">C++ version of Xalan</jump>. For detailed
technical questions, 
  +      please see the developer list below.
  +      <br/>
  +      Archives are kept at <jump href="http://marc.theaimsgroup.com/?l=xalan-c-users">http://marc.theaimsgroup.com/?l=xalan-c-users</jump>
(may not be active yet)
  +    </p>
  +  </s2>
     <s2 title="The Xalan Developer List">
  -      <em>Medium Traffic</em>
  +      <em>High Traffic</em>
         <jump href="mailto:xalan-dev-subscribe@xml.apache.org">Subscribe</jump>
         <jump href="mailto:xalan-dev-unsubscribe@xml.apache.org">Unsubscribe</jump>
  -      <em>CVS Commit</em>
  +      <em>CVS Commit (read-only)</em>
         <jump href="mailto:xalan-cvs-subscribe@xml.apache.org">Subscribe</jump>
         <jump href="mailto:xalan-cvs-unsubscribe@xml.apache.org">Unsubscribe</jump>
         This is the list where participating developers of the Xalan XSLT 
         stylesheet processor meet and discuss issues, code changes/additions, 
  -      etc. Subscribers to this list get notices of each and every code 
  -      change, build results, testing notices, etc. You are strongly adviced 
  -      to subcribe to both lists if you want to follow what is happening. An 
  -      archive of the
  -      <jump href="http://xml-archive.webweaving.org/xml-archive-xalan">developers</jump>
  -      and
  -      <jump href="http://xml-archive.webweaving.org/xml-archive-xalan-cvs">commit</jump>
  -      mailing list is kept. 
  +      etc. Subscribers to the -cvs list get notices of each and every code 
  +      change, build results, testing notices, etc.  Both of these lists 
  +      pertain to both the Java and C++ versions
  +      <br/>
  +      Archives are kept at <jump href="http://marc.theaimsgroup.com/?l=xalan-dev">http://marc.theaimsgroup.com/?l=xalan-dev</jump>
  +      and at <jump href="http://marc.theaimsgroup.com/?l=xalan-cvs">http://marc.theaimsgroup.com/?l=xalan-cvs</jump>
  +      <br/>
  +      For user-oriented questions, please see the appropriate User list above.
  1.4       +19 -0     xml-site/sources/website/library.xml
  Index: library.xml
  RCS file: /home/cvs/xml-site/sources/website/library.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- library.xml	2000/08/29 23:54:29	1.3
  +++ library.xml	2001/09/18 19:45:01	1.4
  @@ -58,5 +58,24 @@
  +    <s2 title="XML Resources">
  +      <p>A wide variety of XML-oriented resources are out on the net today.
  +      Just a few that we have found useful include:
  +      </p>
  +      <ul>
  +        <li><jump href="http://xml.org/">xml.org</jump><br/>
  +          An industry-sponsored portal with links, news, and a wide variety of resources
  +        </li>
  +        <li><jump href="http://xmlhack.com/">xmlhack </jump><br/>
  +          Find all the latest XML-related news stories here
  +        </li>
  +        <li><jump href="http://www.oasis-open.org/cover/">The XML Cover pages</jump><br/>
  +          Robin Cover's long-standing overview of all things XML
  +        </li>
  +        <li><jump href="http://www.xmlsoftware.com/">XMLSOFTWARE</jump><br/>
  +          A listing of various XML-related tools with brief reviews
  +        </li>
  +      </ul>
  +    </s2>
  1.3       +43 -0     xml-site/sources/website/guidelines.xml
  Index: guidelines.xml
  RCS file: /home/cvs/xml-site/sources/website/guidelines.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- guidelines.xml	1999/12/01 22:54:36	1.2
  +++ guidelines.xml	2001/09/18 19:45:01	1.3
  @@ -10,6 +10,15 @@
         and the procedures to follow for proposing and making changes to the 
         codebase of the Project.
  +    <note>
  +      Note that our sister project, jakarta.apache.org, is formulating 
  +      a number of other project-wide guidelines that the xml community may 
  +      wish to copy or modify.  In Sept-2001 there are also a number of 
  +      discussions on the general@xml.apache.org and commons-dev@xml.apache.org 
  +      mailing lists about other cross-project guidelines that we hope will 
  +      standardize our projects and make developing and using them easier.
  +      Stay tuned!
  +    </note>
         This is a living document. Changes can be made by the Project 
         Management Committee. 
  @@ -26,6 +35,40 @@
         <li><em><link idref="management">Project Management</link></em>
           Defines the roles and responsibilities of the Project Management
           Committee (PMC).</li>
  +      <li><em><link idref="mission">Our Mission / Charter</link></em>
  +        A copy of the Charter document for the xml.apache.org Project.</li>
  +  </s2>
  +  <s2 title="Website update guidelines">
  +    <p>
  +      As XML-oriented projects, so our website is also generated from 
  +      XML files.  While many similar websites may use servlets or a 
  +      system like Cocoon to generate their websites on-the-fly 
  +      from XML documents, we currently checkin source .xml files 
  +      of the documentation and then generate a static set of .html 
  +      files for most of this website.
  +    </p>
  +    <p>
  +      Briefly: the entire xml.apache.org website is stored in CVS repositories.
  +      Both the source .xml documents and the generated .html docs are checked in, 
  +      and the actual website itself is simply a checked-out copy of the repository.
  +    </p>
  +    <p>
  +      While each subproject's individual areas may be managed separately 
  +      (by that subproject's committers) the top-level of the website 
  +      should be managed through the xml-site repository.  Thus to change 
  +      any of the files at the root of http://xml.apache.org you should 
  +      first check out the xml-site repository from cvs.apache.org
  +    </p>
  +    <p>
  +      (for updating the top-level docs)
  +      <br/>Checkout the xml-site module (you only actually need a few subdirs; it's
quite large)
  +      <br/>Make updates to the .xml files in the xml-site/sources/website directory
  +      <br/>Go to the xml-site/sources directory locally and run website.bat
  +      <br/>Check that the .html structure in your local targets directory is built
  +      <br/>Checkin both your updated sources/ and targets/ trees as needed
  +      <br/>Login to xml.apache.org and cd to /www/xml.apache.org
  +      <br/>Do an update of directories there as needed
  +    </p>

To unsubscribe, e-mail: general-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: general-cvs-help@xml.apache.org

View raw message