incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r373686 - in /incubator/public/trunk/site-author/projects: agila/index.xml geronimo/geronimo-proposal.xml geronimo/index.xml
Date Tue, 31 Jan 2006 03:33:48 GMT
Author: crossley
Date: Mon Jan 30 19:33:43 2006
New Revision: 373686

URL: http://svn.apache.org/viewcvs?rev=373686&view=rev
Log:
Some extraneous project documents were converted to xdoc.

Modified:
    incubator/public/trunk/site-author/projects/agila/index.xml
    incubator/public/trunk/site-author/projects/geronimo/geronimo-proposal.xml
    incubator/public/trunk/site-author/projects/geronimo/index.xml

Modified: incubator/public/trunk/site-author/projects/agila/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/agila/index.xml?rev=373686&r1=373685&r2=373686&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/agila/index.xml (original)
+++ incubator/public/trunk/site-author/projects/agila/index.xml Mon Jan 30 19:33:43 2006
@@ -1,51 +1,50 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <document>
-  <header>
-    <title>Apache Agila</title>
+  <properties>
+    <title>Apache Agila
+</title>
     <authors>
-      <person name="The Apache Incubator Project"
-        email="general@incubator.apache.org" />
+      <person email="general@incubator.apache.org" name="The Apache Incubator Project"/>
     </authors>
-    <abstract>Apache Agila - Open Source BPM</abstract>
-  </header>
+    <abstract>Apache Agila - Open Source BPM
+</abstract>
+  </properties>
   <body>
-    <section>
-    <title>Overview</title>
-      <p>
-	Apache Agila is a new donation to the Apache Software Foundation consisting of a 
-	lightweight BPM engine and auxiliary services.
-      </p>
-
-      <p>
-       Agila has been accepted by the Apache Jakarta PMC for inclusion into the 
-       Jakarta project.  Once the requirements for incubation are complete, the 
-       community and code will move to Jakarta.
-      </p>
-
+    <section id="Overview">
+      <title>Overview
+</title>
+      <p>Apache Agila is a new donation to the Apache Software Foundation
+consisting of a lightweight BPM engine and auxiliary services.
+</p>
+      <p>Agila has been accepted by the Apache Jakarta PMC for inclusion into
+the Jakarta project. Once the requirements for incubation are
+complete, the community and code will move to Jakarta.
+</p>
     </section>
+    <section id="How+do+I+get+Involved%3F">
+      <title>How do I get Involved?
+</title>
+      <p>Join the mailing lists. To subscribe, send empty email to ...
+</p>
+      <ul>
+        <li>agila-dev-subscribe@incubator.apache.org
+</li>
+        <li>agila-user-subscribe@incubator.apache.org
+</li>
+      </ul>
+      <p>Browsable mail archives are not yet established, so see the actual
+archives, e.g.
 
-    <section>
-      <title>How do I get Involved?</title>
-
-	<p>
-          Join the mailing lists. To subscribe, send empty email to ...
-        </p>
-        <ul>
-          <li>agila-dev-subscribe&#64;incubator.apache.org</li>
-          <li>agila-user-subscribe&#64;incubator.apache.org</li>
-        </ul>
-        <p>Browsable mail archives are not yet established, so see the actual archives, e.g.
-        <code>http://incubator.apache.org/mail/agila-dev/</code>
-        </p>
+        <code>http://incubator.apache.org/mail/agila-dev/
+</code>
+      </p>
+      <p>Please keep checking the Agila project
 
-        <p>
-           Please keep checking the Agila project
-           <link href="../agila.html">status page</link>
-            and the general&#64;incubator mail list for
-           information on progress of resource setup.
-       </p>
+        <a href="../agila.html">status page
+</a>and the general@incubator mail list for information on progress of
+resource setup.
 
+      </p>
     </section>
   </body>
 </document>

Modified: incubator/public/trunk/site-author/projects/geronimo/geronimo-proposal.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/geronimo/geronimo-proposal.xml?rev=373686&r1=373685&r2=373686&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/geronimo/geronimo-proposal.xml (original)
+++ incubator/public/trunk/site-author/projects/geronimo/geronimo-proposal.xml Mon Jan 30 19:33:43 2006
@@ -1,321 +1,251 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <document>
-    <header>
-        <title>Proposal for an Apache J2EE Server Project</title>
-        <authors>
-            <person name="The Apache Incubator Project"
-                email="general@incubator.apache.org" />
-        </authors>
-        <abstract>Apache Geronimo - J2EE Container</abstract>
-    </header>
-    <body>
-
-    <section>
-    <title>Submission Date and Submitters</title>
-    <p>
-    05 Aug 2003 : Geir Magnusson Jr., James Strachan and Richard Monson-Haefel
-    </p>
+  <properties>
+    <title>Proposal for an Apache J2EE Server Project
+</title>
+    <authors>
+      <person email="general@incubator.apache.org" name="The Apache Incubator Project"/>
+    </authors>
+    <abstract>Apache Geronimo - J2EE Container
+</abstract>
+  </properties>
+  <body>
+    <section id="Submission+Date+and+Submitters">
+      <title>Submission Date and Submitters
+</title>
+      <p>05 Aug 2003 : Geir Magnusson Jr., James Strachan and Richard
+Monson-Haefel
+</p>
     </section>
-
-<section>
-    <title>Section 0 : Rationale</title>
-
-    <p>
-    The Java 2, Enterprise Edition (J2EE) platform is employed widely by
-    organizations implementing enterprise applications. It is commonly used in
-    business-to-consumer and most recently in Web service deployments.  Most of
-    the largest business organizations today have deployed applications on a
-    J2EE platform.
-    </p>
-
-    <p>
-    While the J2EE specification is implemented by a number of large and small
-    vendors, there is no open source J2EE container available with a BSD or
-    BSD-derived licence nor is there an open source project today that provides
-    a fully compliant implementation.  Verifiable compliance with the J2EE
-    specification is important to business because it ensures that applications
-    deployed by developers are portable and interoperable across J2EE providers.
-    As a result organizations large and small have felt compelled to pay
-    thousands of dollars to commercial vendors in order to deploy applications
-    based on J2EE compliant servers.
-    </p>
-
-
-    <p>
-    The Apache foundation supports several projects that implement pieces of the
-    J2EE platform such as Servlets, JSP, Tag Libraries, and a Web services
-    stack. However, Apache does not currently support a J2EE project.
-    </p>
-
-    <p>
-    The aim of the project is to produce a large and healthy community of J2EE
-    developers tasked with the development of an open source, certified J2EE
-    server which is ASF licensed and passes Sun's TCK reusing the best ASF/BSD
-    licensed code available today and adding new code to complete the J2EE
-    stack.
-    </p>
-</section>
-
-<section>
-    <title>Section 0.1 : criteria</title>
-
-    <p>
-    We feel that this project has a good chance for success as the following
-    project aspects are carefully considered :
-    </p>
-
-    <ul>
-    <li>
-    Meritocracy: The project will be meritocratic - the usual Apache
-    meritocracy rules would apply.
-    </li>
-
-    <li>
-    Community: The user community for this project is potentially massive.
-    The initial developer community for this project consists of developers from
-    Apache,  Castor, JBoss, mx4j, and OpenEJB projects. The aim is for this
-    community to grow considerably once this project goes public.
-    </li>
-
-    <li>
-    Core Developers: The initial developers are listed below and consist of
-    some existing Apache committers together with committers from Castor,
-    JBoss, mx4j  and OpenEJB.  We believe that as the project grows, the modular
-    nature of the J2EE stack will require steady expansion of the committer
-    group that is considered 'core' - thus providing a healthier, more robust
-    developer community.
-    </li>
-
-    <li>
-    Alignment: There is clear alignment with many existing Apache projects.
-    From Jakarta projects such as Tomcat, James and log4j initially as well as
-    possibly others along the way. J2EE now includes a web services stack and so
-    there will be some alignment with the WS project, Axis in particular, along
-    with the reuse of several XML projects. In addition the J2EE Server project
-    may reuse other ASF/BSD licensed code which is not currently hosted in
-    source form at Apache such as (at time of writing) mx4j, openjms and tyrex.
-    </li>
-    </ul>
-
-    <p>
-    However we see the J2EE Server project as a separate project to existing
-    Apache projects, serving two primary roles
-    </p>
-
-    <ul>
-    <li>
-    integration of various existing and new code bases into a J2EE stack,
-    with those codebases existing both inside and outside of the project
-    </li>
-    <li>
-    certification of the J2EE stack
-    </li>
-    </ul>
-
-    <p>
-    Note that the J2EE server project can happily support competition within the
-    J2EE services stack (for example, offering choices for elements such as the
-    servlet engine like Tomcat or Jetty, or some new JTA implementation versus
-    Tyrex or some new JMS implementation versus OpenJMS etc).
-    </p>
-</section>
-
-<section>
-    <title>Section 0.2 :  warning signs</title>
-
-    <p>
-    We feel that this project has a good chance for success as the following
-    warning signs do not apply to the project we are proposing :
-    </p>
-
-    <ul>
-    <li>
-    Orphaned products: This project is starting with a new code base together
-    with reusing lots of the currently available high quality J2EE open source
-    code out there which is ASF/BSD licensed.
-    </li>
-    <li>
-    Inexperience with open source: The initial community is made up of
-    existing Apache, Castor, JBoss, mx4j , and OpenEJB committers.
-    </li>
-    <li>
-    Homogeneous developers: The current list of committers represents
-    developers from various backgrounds and open source projects, employed by
-    various companies and based around the globe in the US, Europe, Asia and
-    Australia.  There will be no majority bloc, at least from the start.
-    </li>
-    <li>
-    Reliance on salaried developers: None of the initial developers are
-    currently paid to work on the J2EE project.
-    </li>
-    <li>
-    No ties to other Apache products: The J2EE Server project is
-    complementary to existing technologies at Apache. Indeed it will integrate
-    many of those technologies in an effort to provide a code base that can be
-    J2EE certified according to the JCP process.
-    </li>
-    <li>
-    A fascination with the Apache brand: The committers are interested in
-    developing a healthy open source community around an ASF/BSD licensed J2EE
-    certified server, whether Apache is the right place or not.  The aspects of
-    Apache that attract this effort are the experienced stewardship of open
-    source projects by the ASF, the non-profit status of the ASF for TCK
-    certification, and the existing Java community that has been a longstanding
-    part of the ASF.
-    </li>
-    </ul>
-</section>
-
-<section>
-    <title>Section 1 : scope of the project</title>
-
-    <p>
-    There are two main aspects to this Apache project :
-    </p>
-
-    <ul>
-    <li>
-    a complete J2EE certified server which is fully ASF/BSD licensed and
-    backed by a healthy open source community.
-    </li>
-    <li>
-    to create a fully modular J2EE stack so that the Apache community can use
-    whichever parts of the J2EE stack they require separate from the J2EE server
-    project.
-    </li>
-    </ul>
-</section>
-
- <section>
-<title>Section 2 : initial source from which the project is to be populated</title>
-
-    <p>
-    There are several potential initial contributions. Upon formation of the
-    project our first action will be an open, public call for contribution and
-    comment from the J2EE community.  Because of recent circumstances in the
-    J2EE OSS community, all code proposed for inclusion must be publicly
-    reviewed and open to public comment.
-    </p>
-</section>
-
-<section>
-    <title>Section 3: identify the ASF resources to be created</title>
-
-    <section>
-        <title>Section 3.1 : mailing lists</title>
-
+    <section id="Section+0+%3A+Rationale">
+      <title>Section 0 : Rationale
+</title>
+      <p>The Java 2, Enterprise Edition (J2EE) platform is employed widely by
+organizations implementing enterprise applications. It is commonly
+used in business-to-consumer and most recently in Web service
+deployments. Most of the largest business organizations today have
+deployed applications on a J2EE platform.
+</p>
+      <p>While the J2EE specification is implemented by a number of large and
+small vendors, there is no open source J2EE container available with
+a BSD or BSD-derived licence nor is there an open source project
+today that provides a fully compliant implementation. Verifiable
+compliance with the J2EE specification is important to business
+because it ensures that applications deployed by developers are
+portable and interoperable across J2EE providers. As a result
+organizations large and small have felt compelled to pay thousands of
+dollars to commercial vendors in order to deploy applications based
+on J2EE compliant servers.
+</p>
+      <p>The Apache foundation supports several projects that implement pieces
+of the J2EE platform such as Servlets, JSP, Tag Libraries, and a Web
+services stack. However, Apache does not currently support a J2EE
+project.
+</p>
+      <p>The aim of the project is to produce a large and healthy community of
+J2EE developers tasked with the development of an open source,
+certified J2EE server which is ASF licensed and passes Sun's TCK
+reusing the best ASF/BSD licensed code available today and adding new
+code to complete the J2EE stack.
+</p>
+    </section>
+    <section id="Section+0.1+%3A+criteria">
+      <title>Section 0.1 : criteria
+</title>
+      <p>We feel that this project has a good chance for success as the
+following project aspects are carefully considered :
+</p>
+      <ul>
+        <li>Meritocracy: The project will be meritocratic - the usual Apache
+meritocracy rules would apply.
+</li>
+        <li>Community: The user community for this project is potentially
+massive. The initial developer community for this project consists of
+developers from Apache, Castor, JBoss, mx4j, and OpenEJB projects.
+The aim is for this community to grow considerably once this project
+goes public.
+</li>
+        <li>Core Developers: The initial developers are listed below and consist
+of some existing Apache committers together with committers from
+Castor, JBoss, mx4j and OpenEJB. We believe that as the project
+grows, the modular nature of the J2EE stack will require steady
+expansion of the committer group that is considered 'core' - thus
+providing a healthier, more robust developer community.
+</li>
+        <li>Alignment: There is clear alignment with many existing Apache
+projects. From Jakarta projects such as Tomcat, James and log4j
+initially as well as possibly others along the way. J2EE now includes
+a web services stack and so there will be some alignment with the WS
+project, Axis in particular, along with the reuse of several XML
+projects. In addition the J2EE Server project may reuse other ASF/BSD
+licensed code which is not currently hosted in source form at Apache
+such as (at time of writing) mx4j, openjms and tyrex.
+</li>
+      </ul>
+      <p>However we see the J2EE Server project as a separate project to
+existing Apache projects, serving two primary roles
+</p>
+      <ul>
+        <li>integration of various existing and new code bases into a J2EE stack,
+with those codebases existing both inside and outside of the project
+</li>
+        <li>certification of the J2EE stack
+</li>
+      </ul>
+      <p>Note that the J2EE server project can happily support competition
+within the J2EE services stack (for example, offering choices for
+elements such as the servlet engine like Tomcat or Jetty, or some new
+JTA implementation versus Tyrex or some new JMS implementation versus
+OpenJMS etc).
+</p>
+    </section>
+    <section id="Section+0.2+%3A++warning+signs">
+      <title>Section 0.2 : warning signs
+</title>
+      <p>We feel that this project has a good chance for success as the
+following warning signs do not apply to the project we are proposing :
+</p>
+      <ul>
+        <li>Orphaned products: This project is starting with a new code base
+together with reusing lots of the currently available high quality
+J2EE open source code out there which is ASF/BSD licensed.
+</li>
+        <li>Inexperience with open source: The initial community is made up of
+existing Apache, Castor, JBoss, mx4j , and OpenEJB committers.
+</li>
+        <li>Homogeneous developers: The current list of committers represents
+developers from various backgrounds and open source projects,
+employed by various companies and based around the globe in the US,
+Europe, Asia and Australia. There will be no majority bloc, at least
+from the start.
+</li>
+        <li>Reliance on salaried developers: None of the initial developers are
+currently paid to work on the J2EE project.
+</li>
+        <li>No ties to other Apache products: The J2EE Server project is
+complementary to existing technologies at Apache. Indeed it will
+integrate many of those technologies in an effort to provide a code
+base that can be J2EE certified according to the JCP process.
+</li>
+        <li>A fascination with the Apache brand: The committers are interested in
+developing a healthy open source community around an ASF/BSD licensed
+J2EE certified server, whether Apache is the right place or not. The
+aspects of Apache that attract this effort are the experienced
+stewardship of open source projects by the ASF, the non-profit status
+of the ASF for TCK certification, and the existing Java community
+that has been a longstanding part of the ASF.
+</li>
+      </ul>
+    </section>
+    <section id="Section+1+%3A+scope+of+the+project">
+      <title>Section 1 : scope of the project
+</title>
+      <p>There are two main aspects to this Apache project :
+</p>
+      <ul>
+        <li>a complete J2EE certified server which is fully ASF/BSD licensed and
+backed by a healthy open source community.
+</li>
+        <li>to create a fully modular J2EE stack so that the Apache community can
+use whichever parts of the J2EE stack they require separate from the
+J2EE server project.
+</li>
+      </ul>
+    </section>
+    <section id="Section+2+%3A+initial+source+from+which+the+project+is+to+be+populated">
+      <title>Section 2 : initial source from which the project is to be populated
+</title>
+      <p>There are several potential initial contributions. Upon formation of
+the project our first action will be an open, public call for
+contribution and comment from the J2EE community. Because of recent
+circumstances in the J2EE OSS community, all code proposed for
+inclusion must be publicly reviewed and open to public comment.
+</p>
+    </section>
+    <section id="Section+3%3A+identify+the+ASF+resources+to+be+created">
+      <title>Section 3: identify the ASF resources to be created
+</title>
+      <section id="Section+3.1+%3A+mailing+lists">
+        <title>Section 3.1 : mailing lists
+</title>
         <ul>
-        <li>
-            geronimo-dev
-        </li>
-        <li>
-             geronimo-user
-        </li>
+          <li>geronimo-dev
+</li>
+          <li>geronimo-user
+</li>
         </ul>
-    </section>
-
-    <section>
-        <title>Section 3.2: CVS repositories</title>
-
+      </section>
+      <section id="Section+3.2%3A+CVS+repositories">
+        <title>Section 3.2: CVS repositories
+</title>
         <ul>
-        <li>
-            geronimo
-        </li>
+          <li>geronimo
+</li>
         </ul>
-    </section>
-
-    <section>
-        <title>Section 3.3: Bugzilla</title>
-
+      </section>
+      <section id="Section+3.3%3A+Bugzilla">
+        <title>Section 3.3: Bugzilla
+</title>
         <ul>
-        <li>
-            geronimo
-        </li>
+          <li>geronimo
+</li>
         </ul>
-
-        <p>
-        Though would there be an issue with using JIRA?
-        </p>
+        <p>Though would there be an issue with using JIRA?
+</p>
+      </section>
+    </section>
+    <section id="Section+4%3A+identify+the+initial+set+of+committers">
+      <title>Section 4: identify the initial set of committers
+</title>
+      <p>The committers are listed below, along with the open source
+project(s) where they also have commit privileges.
+</p>
+      <ul>
+        <li>Bruce Snyder (Castor JDO)
+</li>
+        <li>Dain Sundstrom (JBoss)
+</li>
+        <li>David Blevins (OpenEJB)
+</li>
+        <li>David Jencks (JBoss)
+</li>
+        <li>Geir Magnusson Jr. (Apache)
+</li>
+        <li>Greg Wilkins (JBoss/Jetty)
+</li>
+        <li>James Strachan (Apache)
+</li>
+        <li>Jan Bartel (JBoss/Jetty)
+</li>
+        <li>Jason Dillon (JBoss)
+</li>
+        <li>Jeremy Boynes (JBoss)
+</li>
+        <li>Jim Jagielski (Apache)
+</li>
+        <li>Jules Golsnell (JBoss/Jetty)
+</li>
+        <li>Richard Monson-Haefel (OpenEJB)
+</li>
+        <li>Remigio Chirino (JBoss)
+</li>
+        <li>Simone Bordet (mx4j)
+</li>
+      </ul>
+    </section>
+    <section id="Section+5%3A+identify+apache+sponsoring+individual">
+      <title>Section 5: identify apache sponsoring individual
+</title>
+      <ul>
+        <li>Ceki Gulcu
+</li>
+        <li>Geir Magnusson Jr.
+</li>
+        <li>James Strachan
+</li>
+        <li>Jim Jagielski
+</li>
+      </ul>
     </section>
-</section>
-
-<section>
-    <title>Section 4: identify the initial set of committers</title>
-
-    <p>
-    The committers are listed below, along with the open source project(s) where
-    they also have commit privileges.
-    </p>
-
-    <ul>
-    <li>
-        Bruce Snyder (Castor JDO)
-    </li>
-    <li>
-        Dain Sundstrom (JBoss)
-    </li>
-    <li>
-        David Blevins (OpenEJB)
-    </li>
-    <li>
-        David Jencks (JBoss)
-    </li>
-    <li>
-        Geir Magnusson Jr. (Apache)
-    </li>
-    <li>
-        Greg Wilkins (JBoss/Jetty)
-    </li>
-    <li>
-        James Strachan (Apache)
-    </li>
-    <li>
-        Jan Bartel (JBoss/Jetty)
-    </li>
-    <li>
-        Jason Dillon (JBoss)
-    </li>
-    <li>
-        Jeremy Boynes (JBoss)
-    </li>
-    <li>
-        Jim Jagielski (Apache)
-    </li>
-    <li>
-        Jules Golsnell (JBoss/Jetty)
-    </li>
-    <li>
-        Richard Monson-Haefel (OpenEJB)
-    </li>
-    <li>
-        Remigio Chirino  (JBoss)
-    </li>
-    <li>
-        Simone Bordet (mx4j)
-    </li>
-    </ul>
-</section>
-
-<section>
-    <title>Section 5: identify apache sponsoring individual</title>
-
-    <ul>
-    <li>
-        Ceki Gulcu
-    </li>
-    <li>
-        Geir Magnusson Jr.
-    </li>
-    <li>
-        James Strachan
-    </li>
-    <li>
-        Jim Jagielski
-     </li>
-     </ul>
-</section>
-</body>
+  </body>
 </document>
-
-

Modified: incubator/public/trunk/site-author/projects/geronimo/index.xml
URL: http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/projects/geronimo/index.xml?rev=373686&r1=373685&r2=373686&view=diff
==============================================================================
--- incubator/public/trunk/site-author/projects/geronimo/index.xml (original)
+++ incubator/public/trunk/site-author/projects/geronimo/index.xml Mon Jan 30 19:33:43 2006
@@ -1,341 +1,429 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <document>
-  <header>
-    <title>Apache Geronimo</title>
+  <properties>
+    <title>Apache Geronimo
+</title>
     <authors>
-      <person name="The Apache Incubator Project"
-        email="general@incubator.apache.org" />
+      <person email="general@incubator.apache.org" name="The Apache Incubator Project"/>
     </authors>
-    <abstract>Apache Geronimo - J2EE Container</abstract>
-  </header>
+    <abstract>Apache Geronimo - J2EE Container
+</abstract>
+  </properties>
   <body>
-    <section>
-    <title>Overview</title>
-      <p>
-        Apache Geronimo is a new effort coordinated by the Apache Software Foundation to make a 
-        J2EE compatible container.  Please read the <link href="geronimo-proposal.html">proposal</link>
-        that started the project in the incubator.  We are also tracking our
-        <link href="site:projects/geronimo">status progressing through incubation</link>.
+    <section id="Overview">
+      <title>Overview
+</title>
+      <p>Apache Geronimo is a new effort coordinated by the Apache Software
+Foundation to make a J2EE compatible container. Please read the
+
+        <a href="geronimo-proposal.html">proposal
+</a>that started the project in the incubator. We are also tracking our
+
+        <a href="../../projects/geronimo.html">status progressing through incubation
+</a>.
+
       </p>
+      <p>For more information, please read the latest snapshot of the
 
-      <p>
-       For more information, please read the latest snapshot of the <link href="#FAQ">FAQ</link> below
-       or look at the <link href="http://wiki.apache.org/geronimo/">geronimo wiki</link>.
-     </p>
-
-     <p>
-       This is the official site for Geronimo while it's in the incubation phase at Apache. 
-       We have an alpha version of our 
-       <link href="http://www.apache.org/~jstrachan/geronimo/">future project site</link>.
-     </p>
-    
-    </section>
+        <a href="#FAQ">FAQ
+</a>below or look at the
 
-    <section>
-      <title>How do I get Involved?</title>
+        <a href="http://wiki.apache.org/geronimo/">geronimo wiki
+</a>.
 
-    <p>
-       <strong>Quick Summary</strong>   
-    </p>
-
-    <ul>
-      <li>
-        Subscribe to the <link href="#Mailing+Lists">mail lists</link>
-      </li>
-      <li>
-        Download code and materials from <link href="#Where+is+the+source+and+download%3F">CVS</link>
-      </li>
-      <li>
-         Read the <link href="#FAQ">FAQ</link>
-      </li>
-      <li>
-         Participate and contribute!
-      </li>
-    </ul>
-
-      <p>
-        The most important step is to join the <link href="#Mailing+Lists">mailing list</link>
-        It is not necessary to post a "Hi" message or to join the project.  By subscribing to
-        the list, you're joining the project.  After that, it is all down to participation.
       </p>
+      <p>This is the official site for Geronimo while it's in the incubation
+phase at Apache. We have an alpha version of our
+
+        <a href="http://www.apache.org/~jstrachan/geronimo/">future project site
+</a>.
 
+      </p>
+    </section>
+    <section id="How+do+I+get+Involved%3F">
+      <title>How do I get Involved?
+</title>
       <p>
-        As with all <link href="http://www.apache.org/">Apache</link> projects, the usual form is to get the
-        project's source via CVS tools, join the mailing list(s), find
-        something to do, and submit a patch to the mailing list for
-        their approval and application.
-      </p>
-      <p>
-        We assume that patch donators
-        are familiar with CVS, diff and patch.  If you are not
-        familiar with those tools, or want additional information
-        about how things work, here are some links:
+        <strong>Quick Summary
+</strong>
       </p>
       <ul>
-      <li>
-        <link href="http://www.apache.org/dev/contributors.html">Apache Contributors Technical Guide</link>
-      </li>
-      <li>
-        <link href="http://jakarta.apache.org/site/getinvolved.html">Jakarta's Get Involved page.</link>
-      </li>
+        <li>Subscribe to the
+
+          <a href="#Mailing+Lists">mail lists
+</a>
+        </li>
+        <li>Download code and materials from
+
+          <a href="#Where+is+the+source+and+download%3F">CVS
+</a>
+        </li>
+        <li>Read the
+
+          <a href="#FAQ">FAQ
+</a>
+        </li>
+        <li>Participate and contribute!
+</li>
       </ul>
+      <p>The most important step is to join the
+
+        <a href="#Mailing+Lists">mailing list
+</a>It is not necessary to post a "Hi" message or to join the project. By
+subscribing to the list, you're joining the project. After that, it
+is all down to participation.
 
-      <p>
-        Geronimo, if it passes the incubation stage, will become an
-        <link href="http://www.apache.org/">Apache</link> project.
-        As an Apache project, the Apache approach to open source community and
-        development will apply.  If you aren't familar with  how things are done
-        by Apache projects, please familiarize yourself with the information
-        available on the <link href="http://www.apache.org">site</link>.
-        Here are some good selections from the Jakarta project site that 
-        should help you understand the Apache community process :
       </p>
+      <p>As with all
 
+        <a href="http://www.apache.org/">Apache
+</a>projects, the usual form is to get the project's source via CVS
+tools, join the mailing list(s), find something to do, and submit a
+patch to the mailing list for their approval and application.
+
+      </p>
+      <p>We assume that patch donators are familiar with CVS, diff and patch.
+If you are not familiar with those tools, or want additional
+information about how things work, here are some links:
+</p>
       <ul>
         <li>
-          <link href="http://jakarta.apache.org/site/roles.html">Roles and Responsibilities</link>
+          <a href="http://www.apache.org/dev/contributors.html">Apache Contributors Technical Guide
+</a>
         </li>
         <li>
-          <link href="http://jakarta.apache.org/site/decisions.html">Decision Making</link>
+          <a href="http://jakarta.apache.org/site/getinvolved.html">Jakarta's Get Involved page.
+</a>
         </li>
+      </ul>
+      <p>Geronimo, if it passes the incubation stage, will become an
+
+        <a href="http://www.apache.org/">Apache
+</a>project. As an Apache project, the Apache approach to open source
+community and development will apply. If you aren't familar with how
+things are done by Apache projects, please familiarize yourself with
+the information available on the
+
+        <a href="http://www.apache.org">site
+</a>. Here are some good selections from the Jakarta project site that
+should help you understand the Apache community process :
+
+      </p>
+      <ul>
         <li>
-          <link href="http://jakarta.apache.org/site/source.html">Source Repositories</link>
+          <a href="http://jakarta.apache.org/site/roles.html">Roles and Responsibilities
+</a>
         </li>
-       </ul>
-
+        <li>
+          <a href="http://jakarta.apache.org/site/decisions.html">Decision Making
+</a>
+        </li>
+        <li>
+          <a href="http://jakarta.apache.org/site/source.html">Source Repositories
+</a>
+        </li>
+      </ul>
     </section>
-    <section>
-      <title>Mailing Lists</title>
-      <p>
-        Apache Geronimo has two mailing lists of interest, the 
-        geronimo-dev list, where all the discussion 
-        occurs, and the geronimo-cvs list, which receives commit mails each 
-        time a commit is made to the incubator-geronimo <link href="#Where+is+the+source+and+download%3F">CVS</link> module.
+    <section id="Mailing+Lists">
+      <title>Mailing Lists
+</title>
+      <p>Apache Geronimo has two mailing lists of interest, the geronimo-dev
+list, where all the discussion occurs, and the geronimo-cvs list,
+which receives commit mails each time a commit is made to the
+incubator-geronimo
 
-      </p>
+        <a href="#Where+is+the+source+and+download%3F">CVS
+</a>module.
 
-      <p>
-        You can subscribe to the mailing lists by sending an email to
-        one or both of the following addresses : 
       </p>
+      <p>You can subscribe to the mailing lists by sending an email to one or
+both of the following addresses :
+</p>
       <ul>
-        <li><link href="mailto:geronimo-dev-subscribe@incubator.apache.org">geronimo-dev-subscribe@incubator.apache.org</link></li>
-        <li><link href="mailto:geronimo-cvs-subscribe@incubator.apache.org">geronimo-cvs-subscribe@incubator.apache.org</link></li>
+        <li>
+          <a href="mailto:geronimo-dev-subscribe@incubator.apache.org">geronimo-dev-subscribe@incubator.apache.org
+</a>
+        </li>
+        <li>
+          <a href="mailto:geronimo-cvs-subscribe@incubator.apache.org">geronimo-cvs-subscribe@incubator.apache.org
+</a>
+        </li>
       </ul>
-
-	<p>
-          To send a message to the Geronimo mailing list without subscribing, try the following link:
-      </p>
+      <p>To send a message to the Geronimo mailing list without subscribing,
+try the following link:
+</p>
       <ul>
-        <li><link href="mailto:geronimo-dev@incubator.apache.org">geronimo-dev@incubator.apache.org</link></li>
+        <li>
+          <a href="mailto:geronimo-dev@incubator.apache.org">geronimo-dev@incubator.apache.org
+</a>
+        </li>
       </ul>
       <p>
-          <strong>However</strong>,
-          unless you subscribe to the list, you may not get a response.  Subscribing to the list
-          is how you join the project, and follow events.
+        <strong>However
+</strong>, unless you subscribe to the list, you may not get a response.
+Subscribing to the list is how you join the project, and follow
+events.
+
       </p>
-      <p>
-          There is also a <link href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=140">mailing list archive</link>,
-          where you can catch up on prior discussion.
+      <p>There is also a
+
+        <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=140">mailing list archive
+</a>, where you can catch up on prior discussion.
+
       </p>
     </section>
+    <section id="The+Wiki">
+      <title>The Wiki
+</title>
+      <p>The project Wiki is
 
-    <section>
-      <title>The Wiki</title>
-      <p>
-         The project Wiki is <link href="http://wiki.apache.org/geronimo/">here</link>.
-      </p>
-     </section>
+        <a href="http://wiki.apache.org/geronimo/">here
+</a>.
 
-    <section>
-      <title>Where is the source and download?</title>
-      <p>
-        We have a number of code donations "on deck" which are being
-        evaluated. Once those donations are processed, then they will
-        be checked into the Apache Geronimo CVS module.
-      </p>
-      <p>
-        The CVS module is named <code>incubator-geronimo</code>. Here is
-        an example of checking out Apache Geronimo with the CVS
-        command-line client:
-      </p>
-      <source>
-$ export CVSROOT=:pserver:anoncvs@cvs.apache.org:/home/cvspublic
-$ cvs login
-Logging in to :pserver:anoncvs@cvs.apache.org:2401/home/cvspublic
-CVS password:
-$ cvs checkout incubator-geronimo
-...
-      </source>
-      <note>
-        Use "anoncvs" for the anoncvs user's CVS password.
-      </note>
-      <p>
-        The code can be browsed through ViewCVS at
-        <link href="http://cvs.apache.org/viewcvs/incubator-geronimo/">http://cvs.apache.org/viewcvs/incubator-geronimo/</link>.
       </p>
     </section>
+    <section id="Where+is+the+source+and+download%3F">
+      <title>Where is the source and download?
+</title>
+      <p>We have a number of code donations "on deck" which are being
+evaluated. Once those donations are processed, then they will be
+checked into the Apache Geronimo CVS module.
+</p>
+      <p>The CVS module is named
+
+        <code>incubator-geronimo
+</code>. Here is an example of checking out Apache Geronimo with the CVS
+command-line client:
+
+      </p>
+      <source xml:space="preserve">$ export CVSROOT=:pserver:anoncvs@cvs.apache.org:/home/cvspublic $
+cvs login Logging in to
+:pserver:anoncvs@cvs.apache.org:2401/home/cvspublic CVS password: $
+cvs checkout incubator-geronimo ...
+</source>
+      <note>Use "anoncvs" for the anoncvs user's CVS password.
+</note>
+      <p>The code can be browsed through ViewCVS at
 
-    <section>
-    <title>FAQ</title>
+        <a href="http://cvs.apache.org/viewcvs/incubator-geronimo/">http://cvs.apache.org/viewcvs/incubator-geronimo/
+</a>.
 
-<note>
-    Updated : 2003-08-07 1500 GMT
+      </p>
+    </section>
+    <section id="FAQ">
+      <title>FAQ
+</title>
+      <note>Updated : 2003-08-07 1500 GMT
 </note>
+      <note>The following is a snapshot from the FAQ on the Apache Wiki. It's
+here for your convenience, but may be out of date at any moment. For
+updated information, please go to the
 
-<note>
-The following is a snapshot from the FAQ on the Apache Wiki.  It's here for your convenience, but may be out of date at any moment.  
-For updated information, please go to the
-<link href="http://wiki.apache.org/geronimo/">geronimo wiki</link>.
-</note>
+        <a href="http://wiki.apache.org/geronimo/">geronimo wiki
+</a>.
 
-<p>
-These are questions that have come up on the mailing list so far.  They are unofficial, but are best efforts by community members to record useful answers.
-</p>
-<p>
-Some questions are unanswered as yet.  Have an answer?  Please discuss it on the mailing list, and record the conclusion here.
-</p>
-<p>
-<strong>Q: I'd like to find out more and help etc. What do I do next?</strong>
-</p>
-<p>
-A: Participation on the project is via the mailing list and the source code repository.  You join by joining the mailing list, and by participating in discussion. You help by contributing your ideas, enthusiasm, code, documentation, tests, and intangibles. 
-</p>
-<p>
-The fundamental tenet of the ASF is that Great Communities build great code. The emphasis is on Community; the code comes from that. If you want to help, just join the mailing list, see what needs to be done, and do it. 
-</p>
-<p>
-Welcome.  :-)
-</p>
-<p>
-<strong>Q: Where is the mailing list?  How do I subscribe?</strong>
-</p>
-<p>
-A: The mailing list is geronimo-dev@incubator.apache.org.  You subscribe by sending e-mail to <link href="mailto:geronimo-dev-subscribe@incubator.apache.org">[geronimo-dev-subscribe@incubator.apache.org]</link>.
-</p>
-<p>
-<strong>Q: Is there an archive?</strong>
-</p>
-<p>
-A: <link href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=140">[Apache J2EE Archives]</link>
-</p>
-<p>
-<strong>Q: Can you mail me if you're interested in me helping.</strong>
-</p>
-<p>
-A: That's not how open source communities generally work. To the people who have asked to be contacted if Apache are interested, it's unlikely that this will happen with all the huge interest that this has generated. Better to stay in touch with the mailing list.
-</p>
-<p>
-<strong>Q: Where is the Apache CVS module</strong>
-</p>
-<p>
-A: incubator-geronimo <link href="http://cvs.apache.org/viewcvs/incubator-geronimo">[Browse CVS]</link>
-</p>
-<p>
-<strong>Q: The CVS module is empty, is there an issue</strong>
-</p>
-<p>
-A: No. The initial committers have not publicly released the base code. Be patient.
-</p>
-<p>
-<strong>Q: Will it involve JBoss code.</strong>
-</p>
-<p>
-A: No.
-</p>
-<p>
-This is a new Apache project, running under Apache guidelines.  The Apache Software Foundation accepts only voluntary contributions of material from authors who possess the legal right to donate it.
-</p>
-<p>
-<strong>Q: Will it &lt;insert some technical phrase here&gt;?</strong>
-</p>
-<p>
-A: It's probably worth holding these questions off for the moment.  This project is bringing together members and contributions from many existing J2EE communities, and is just starting to come together.
-</p>
-<p>
-<strong>Q: What are the rules for Geronimo?</strong>
-</p>
-<p>
-A: See the <link href="http://incubator.apache.org/">[Apache Incubator]</link> web site.
-</p>
-<p>
-<strong>Q: What's the website?</strong>
-</p>
-<p>
-A: <link href="http://incubator.apache.org/projects/geronimo.html">[Apache J2EE Project]</link>
+      </note>
+      <p>These are questions that have come up on the mailing list so far.
+They are unofficial, but are best efforts by community members to
+record useful answers.
 </p>
-<p>
-<strong>Q: What tools do I need to learn?</strong>
+      <p>Some questions are unanswered as yet. Have an answer? Please discuss
+it on the mailing list, and record the conclusion here.
 </p>
-<p>
-A: CVS. patch. Using a mail list.
+      <p>
+        <strong>Q: I'd like to find out more and help etc. What do I do next?
+</strong>
+      </p>
+      <p>A: Participation on the project is via the mailing list and the
+source code repository. You join by joining the mailing list, and by
+participating in discussion. You help by contributing your ideas,
+enthusiasm, code, documentation, tests, and intangibles.
 </p>
-<p>
-<strong>Q: Relationship to JBoss and in particular, the JBoss source base.</strong>
+      <p>The fundamental tenet of the ASF is that Great Communities build
+great code. The emphasis is on Community; the code comes from that.
+If you want to help, just join the mailing list, see what needs to be
+done, and do it.
 </p>
-<p>
-A: Several (former) JBoss committers are Geronimo committers. The JBoss codebase cannot, and will not, be used, at all (it is LGPL).
+      <p>Welcome. :-)
 </p>
-<p>
-<strong>Q: Does Geronimo replace Tomcat, JSTL etc.</strong>
+      <p>
+        <strong>Q: Where is the mailing list? How do I subscribe?
+</strong>
+      </p>
+      <p>A: The mailing list is geronimo-dev@incubator.apache.org. You
+subscribe by sending e-mail to
+
+        <a href="mailto:geronimo-dev-subscribe@incubator.apache.org">[geronimo-dev-subscribe@incubator.apache.org]
+</a>.
+
+      </p>
+      <p>
+        <strong>Q: Is there an archive?
+</strong>
+      </p>
+      <p>A:
+
+        <a href="http://nagoya.apache.org/eyebrowse/SummarizeList?listId=140">[Apache J2EE Archives]
+</a>
+      </p>
+      <p>
+        <strong>Q: Can you mail me if you're interested in me helping.
+</strong>
+      </p>
+      <p>A: That's not how open source communities generally work. To the
+people who have asked to be contacted if Apache are interested, it's
+unlikely that this will happen with all the huge interest that this
+has generated. Better to stay in touch with the mailing list.
 </p>
-<p>
-A: No. Geronimo includes other services like Tomcat or Jetty for the web container, OpenJMS for the JMS, Tyrex for the transaction manager etc. So Geroimo focusses on being the J2EE container allowing other services to drop in via JMX.
+      <p>
+        <strong>Q: Where is the Apache CVS module
+</strong>
+      </p>
+      <p>A: incubator-geronimo
+
+        <a href="http://cvs.apache.org/viewcvs/incubator-geronimo">[Browse CVS]
+</a>
+      </p>
+      <p>
+        <strong>Q: The CVS module is empty, is there an issue
+</strong>
+      </p>
+      <p>A: No. The initial committers have not publicly released the base
+code. Be patient.
 </p>
-<p>
-<strong>Q: What other projects will Geronimo reuse?</strong>
+      <p>
+        <strong>Q: Will it involve JBoss code.
+</strong>
+      </p>
+      <p>A: No.
 </p>
-<p>
-A: We suspect in the grand scheme of things to reuse various existing open source projects. Anything which has a suitable BSD / ASF licence is up for grabs. e.g. the following is a likely list of the things well be using (though in no way is this definitive)...
+      <p>This is a new Apache project, running under Apache guidelines. The
+Apache Software Foundation accepts only voluntary contributions of
+material from authors who possess the legal right to donate it.
 </p>
-<p>
-From the ASF licenced projects...
+      <p>
+        <strong>Q: Will it &lt;insert some technical phrase here&gt;?
+</strong>
+      </p>
+      <p>A: It's probably worth holding these questions off for the moment.
+This project is bringing together members and contributions from many
+existing J2EE communities, and is just starting to come together.
 </p>
+      <p>
+        <strong>Q: What are the rules for Geronimo?
+</strong>
+      </p>
+      <p>A: See the
+
+        <a href="http://incubator.apache.org/">[Apache Incubator]
+</a>web site.
+
+      </p>
+      <p>
+        <strong>Q: What's the website?
+</strong>
+      </p>
+      <p>A:
 
-<ul>
-<li> MX4J for JMX </li>
-  <li> Tomcat or Jetty for Web Container </li>
-  <li> Axis for Web Services Stack </li>
-  <li> James for email </li>
-  <li> OJB for JDO </li>
-  <li> commons-jndi for JNDI  </li>
-</ul>
-<p>
-As well as some non-ASF licenced stuff which is BSD licenced
+        <a href="http://incubator.apache.org/projects/geronimo.html">[Apache J2EE Project]
+</a>
+      </p>
+      <p>
+        <strong>Q: What tools do I need to learn?
+</strong>
+      </p>
+      <p>A: CVS. patch. Using a mail list.
 </p>
-<ul>
-<li> OpenJms for JMS </li>
-<li> Tyrex for Transaction Manager </li>
-</ul>
-<p>
-As well as the usual infrastructure...
+      <p>
+        <strong>Q: Relationship to JBoss and in particular, the JBoss source base.
+</strong>
+      </p>
+      <p>A: Several (former) JBoss committers are Geronimo committers. The
+JBoss codebase cannot, and will not, be used, at all (it is LGPL).
 </p>
-<ul>
-<li> commons-logging / log4j for logging </li>
-<li> Xerces for XML parsing </li>
-<li> maybe more of JakartaCommons as needed </li>
-<li> Maven for building the distributions &amp; website </li>
-<li>JUnit for unit testing </li>
-</ul>
-<p>
-(1)  There is currently a JNDI implementation in Tomcat's CVS. It might be better to move this to Jakarta Commons so we can all work &amp; extend it - there are various features from Jetty and OpenEjb we'd like to add?
+      <p>
+        <strong>Q: Does Geronimo replace Tomcat, JSTL etc.
+</strong>
+      </p>
+      <p>A: No. Geronimo includes other services like Tomcat or Jetty for the
+web container, OpenJMS for the JMS, Tyrex for the transaction manager
+etc. So Geroimo focusses on being the J2EE container allowing other
+services to drop in via JMX.
 </p>
-<p>
-<strong> Q: Administration Overview such as an amalgamation of many projects or one large project with subject areas.</strong>
+      <p>
+        <strong>Q: What other projects will Geronimo reuse?
+</strong>
+      </p>
+      <p>A: We suspect in the grand scheme of things to reuse various existing
+open source projects. Anything which has a suitable BSD / ASF licence
+is up for grabs. e.g. the following is a likely list of the things
+well be using (though in no way is this definitive)...
 </p>
-<p>
-<strong>Q: Timeline to 1.0 (what does it include).</strong>
+      <p>From the ASF licenced projects...
 </p>
-<p> 
-<strong>Q: Will Geronimo be compliant with Sun's CTS.</strong>
+      <ul>
+        <li>MX4J for JMX
+</li>
+        <li>Tomcat or Jetty for Web Container
+</li>
+        <li>Axis for Web Services Stack
+</li>
+        <li>James for email
+</li>
+        <li>OJB for JDO
+</li>
+        <li>commons-jndi for JNDI
+</li>
+      </ul>
+      <p>As well as some non-ASF licenced stuff which is BSD licenced
 </p>
-<p> 
-<strong>Q: What is Geronimo's Architectural vision and what does the back plane look like (i.e., is it JMX based?).</strong>
+      <ul>
+        <li>OpenJms for JMS
+</li>
+        <li>Tyrex for Transaction Manager
+</li>
+      </ul>
+      <p>As well as the usual infrastructure...
 </p>
-<p> 
-<strong>Q: What standards are targeted and which are under active development?</strong>
+      <ul>
+        <li>commons-logging / log4j for logging
+</li>
+        <li>Xerces for XML parsing
+</li>
+        <li>maybe more of JakartaCommons as needed
+</li>
+        <li>Maven for building the distributions &amp; website
+</li>
+        <li>JUnit for unit testing
+</li>
+      </ul>
+      <p>(1) There is currently a JNDI implementation in Tomcat's CVS. It
+might be better to move this to Jakarta Commons so we can all work &amp;
+extend it - there are various features from Jetty and OpenEjb we'd
+like to add?
 </p>
+      <p>
+        <strong>Q: Administration Overview such as an amalgamation of many projects
+or one large project with subject areas.
+</strong>
+      </p>
+      <p>
+        <strong>Q: Timeline to 1.0 (what does it include).
+</strong>
+      </p>
+      <p>
+        <strong>Q: Will Geronimo be compliant with Sun's CTS.
+</strong>
+      </p>
+      <p>
+        <strong>Q: What is Geronimo's Architectural vision and what does the back
+plane look like (i.e., is it JMX based?).
+</strong>
+      </p>
+      <p>
+        <strong>Q: What standards are targeted and which are under active development?
+</strong>
+      </p>
     </section>
   </body>
 </document>



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


Mime
View raw message