incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject cvs commit: incubator-site/src/documentation/content/xdocs/projects geronimo-proposal.xml geronimo.xml
Date Fri, 08 Aug 2003 12:01:45 GMT
geirm       2003/08/08 05:01:45

  Modified:    src/documentation/content/xdocs/projects geronimo.xml
  Added:       src/documentation/content/xdocs/projects
                        geronimo-proposal.xml
  Log:
  update to geronimo.xml to remove reference to Hibernate (is LGPL) and add
  link for the proposal
  
  Revision  Changes    Path
  1.10      +10 -2     incubator-site/src/documentation/content/xdocs/projects/geronimo.xml
  
  Index: geronimo.xml
  ===================================================================
  RCS file: /home/cvs/incubator-site/src/documentation/content/xdocs/projects/geronimo.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- geronimo.xml	8 Aug 2003 10:53:47 -0000	1.9
  +++ geronimo.xml	8 Aug 2003 12:01:44 -0000	1.10
  @@ -14,7 +14,8 @@
       <title>Overview</title>
         <p>
           Apache Geronimo is a new effort coordinated by the Apache Software Foundation to
make a 
  -        J2EE compatible container.
  +        J2EE compatible container.  Please read the <link href="geronimo-proposal.html">proposal</link>
  +        that started the project in the incubator.
         </p>
   
         <p>
  @@ -22,7 +23,14 @@
          or look <link href="http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheJ2EE/FAQ">here</link>
for the live one.
        </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>
  +
       <section>
         <title>How do I get Involved?</title>
   
  @@ -289,7 +297,7 @@
     <li> Tomcat or Jetty for Web Container </li>
     <li> Axis for Web Services Stack </li>
     <li> James for email </li>
  -  <li> OJB or Hibernate for JDO </li>
  +  <li> OJB for JDO </li>
     <li> commons-jndi for JNDI  </li>
   </ul>
   <p>
  
  
  
  1.1                  incubator-site/src/documentation/content/xdocs/projects/geronimo-proposal.xml
  
  Index: geronimo-proposal.xml
  ===================================================================
  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
  <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>
      </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>
  
          <ul>
          <li>
              geronimo-dev
          </li>
          <li>
               geronimo-user
          </li>
          </ul>
      </section>
  
      <section>
          <title>Section 3.2: CVS repositories</title>
  
          <ul>
          <li>
              geronimo
          </li>
          </ul>
      </section>
  
      <section>
          <title>Section 3.3: Bugzilla</title>
  
          <ul>
          <li>
              geronimo
          </li>
          </ul>
  
          <p>
          Though would there be an issue with using JIRA?
          </p>
      </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>
  </document>
  
  
  
  
  

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


Mime
View raw message