incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From leosim...@apache.org
Subject cvs commit: incubator/site/projects altrmi.cwiki geronimo.cwiki wsrp4j.cwiki juddi.cwiki directory.cwiki jaxme.cwiki lenya.cwiki xmlbeans.cwiki ftpserver.cwiki
Date Mon, 27 Oct 2003 14:20:40 GMT
leosimons    2003/10/27 06:20:40

  Modified:    site/projects altrmi.cwiki geronimo.cwiki wsrp4j.cwiki
                        juddi.cwiki directory.cwiki jaxme.cwiki lenya.cwiki
                        xmlbeans.cwiki ftpserver.cwiki
  Log:
  make it somewhat possible for people to find the
  project website; update formatting on the
  XmlBeans page.
  
  Revision  Changes    Path
  1.3       +5 -1      incubator/site/projects/altrmi.cwiki
  
  Index: altrmi.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/altrmi.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- altrmi.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ altrmi.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,7 @@
  +!Project Website
  +
  +The website for altrmi is at http://incubator.apache.org/altrmi/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,4 +89,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  
  1.3       +78 -74    incubator/site/projects/geronimo.cwiki
  
  Index: geronimo.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/geronimo.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- geronimo.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ geronimo.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,7 @@
  +!Project Website
  +
  +The website for Geronimo is at http://wiki.codehaus.org/geronimo/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,7 +89,7 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
   
   !Status
   {{{
  @@ -99,124 +103,124 @@
   To: geronimo-dev@incubator.apache.org
   Message-Id: <AC8D58FA-E0AE-11D7-B8F0-000393DB559A@coredevelopers.net>
   
  -The first month of our project has seen a deluge of volunteers, email 
  -and code.  Indeed, for the first few days we had so many volunteers 
  -that it was almost impossible to keep up with the influx.  Many of the 
  -initial volunteers stuck around and are actively participating.  The 
  -email volume of the last month is shocking.  We have had over three 
  -thousand messages on the list, and for the first few days we were 
  -getting hundreds of emails a day.  The volume has settled down to a 
  -much more manageable level, and the discussions have improved as a 
  -result.  It has been amazing to see the small code seed we started with 
  -grow into a two and a half megabyte source bundle.  Even with this 
  -massive growth, the code base has remained stable (the build has only 
  +The first month of our project has seen a deluge of volunteers, email
  +and code.  Indeed, for the first few days we had so many volunteers
  +that it was almost impossible to keep up with the influx.  Many of the
  +initial volunteers stuck around and are actively participating.  The
  +email volume of the last month is shocking.  We have had over three
  +thousand messages on the list, and for the first few days we were
  +getting hundreds of emails a day.  The volume has settled down to a
  +much more manageable level, and the discussions have improved as a
  +result.  It has been amazing to see the small code seed we started with
  +grow into a two and a half megabyte source bundle.  Even with this
  +massive growth, the code base has remained stable (the build has only
   been broken a few times).
   
  -Given these signs, we declare the state of the project to be healthy 
  +Given these signs, we declare the state of the project to be healthy
   and vibrant.
   
  -The momentum of the project is huge, and it appears we have reached the 
  -critical mass required for a success. However, we have some challenges 
  -to overcome.  One of these is the nature of discussions on the mailing 
  -list - we have had many bike shed type discussions thrashing minute 
  -details to death but choking out larger topics.  In some cases, this 
  -has resulted in contributors collaborating offline and major changes 
  -happening with little public discussion.  This issue is gradually 
  -working itself out, but we all need to be aware of this tendency and 
  +The momentum of the project is huge, and it appears we have reached the
  +critical mass required for a success. However, we have some challenges
  +to overcome.  One of these is the nature of discussions on the mailing
  +list - we have had many bike shed type discussions thrashing minute
  +details to death but choking out larger topics.  In some cases, this
  +has resulted in contributors collaborating offline and major changes
  +happening with little public discussion.  This issue is gradually
  +working itself out, but we all need to be aware of this tendency and
   work to keep discussions on the list more focused.
   
  -Another challenge facing us is how to grow the committer base.  There 
  -is some perception of a cathedral clique of insiders, whereas in 
  -reality, many of the project management issues have arisen because the 
  -current committers are not used to working together and are new to the 
  -Apache Way.  With the initial startup phase behind us, we will be 
  +Another challenge facing us is how to grow the committer base.  There
  +is some perception of a cathedral clique of insiders, whereas in
  +reality, many of the project management issues have arisen because the
  +current committers are not used to working together and are new to the
  +Apache Way.  With the initial startup phase behind us, we will be
   looking to expand the project rapidly over the next couple of months.
   
   
   
  -Geronimo is a complex project with many collaborating subsystems and 
  +Geronimo is a complex project with many collaborating subsystems and
   significant progress has been made in many areas.
   
   BUILD SYSTEM
  -Our build system came together surprisingly quickly.  We have support 
  -for multiple modules and an amazing auto-generated web site from maven. 
  -  Jason Dillon is currently working out the structure of our final 
  -build, and Dain Sundstrom and David Blevins will be setting up an 
  +Our build system came together surprisingly quickly.  We have support
  +for multiple modules and an amazing auto-generated web site from maven.
  +  Jason Dillon is currently working out the structure of our final
  +build, and Dain Sundstrom and David Blevins will be setting up an
   integration testing system next week.
   
   SPECIFICATION APIs
  -Some of the least exciting but most critical work has been the 
  -provision of unencumbered versions of the specification APIs. Credit 
  -goes to Maas van den Berg and Aaron Mulder for much of this work, with 
  -a special mention of Alex Blewitt for diligently building out the 
  +Some of the least exciting but most critical work has been the
  +provision of unencumbered versions of the specification APIs. Credit
  +goes to Maas van den Berg and Aaron Mulder for much of this work, with
  +a special mention of Alex Blewitt for diligently building out the
   JavaMail API which contains substantial concrete implementation.
   
   SERVICE FOUNDATION
  -Using JMX as a kernel technology has facilitated the manageability of 
  -the system.  A GeronimoMBean has been added, intended to be the basis 
  -for other services in Geronimo.  This MBean provides support for 
  -multiple managed objects and implements the managed object, state 
  -manageable and event provider interfaces from the J2EE Management 
  -specification.  Dain Sundstrom will be adding persistence capability, 
  +Using JMX as a kernel technology has facilitated the manageability of
  +the system.  A GeronimoMBean has been added, intended to be the basis
  +for other services in Geronimo.  This MBean provides support for
  +multiple managed objects and implements the managed object, state
  +manageable and event provider interfaces from the J2EE Management
  +specification.  Dain Sundstrom will be adding persistence capability,
   allowing the server configuration to be preserved between restarts.
   
   CONSOLE
  -A console subsystem is in progress with web and command-line based 
  -interfaces under development by N. Alex Rupp and Matt Kurjanowicz.  
  -There are also plans for a GUI console once a common structure has been 
  +A console subsystem is in progress with web and command-line based
  +interfaces under development by N. Alex Rupp and Matt Kurjanowicz.
  +There are also plans for a GUI console once a common structure has been
   determined.
   
   DEPLOYMENT
  -A common deployment architecture has been defined, supporting local and 
  -remote modules, dependencies between deployed components, and pluggable 
  -deployment strategies. Currently deployment is provided for service 
  -archives containing MBeans; support will be added soon for Web, EJB and 
  -Connector modules. Scanners have been implemented for both local and 
  +A common deployment architecture has been defined, supporting local and
  +remote modules, dependencies between deployed components, and pluggable
  +deployment strategies. Currently deployment is provided for service
  +archives containing MBeans; support will be added soon for Web, EJB and
  +Connector modules. Scanners have been implemented for both local and
   remote (WebDAV) filesystems.
   
   REMOTING
  -Hiram Chirino has implemented a remoting framework for routing 
  -invocation requests both within and between VMs, freeing containers 
  -from the need to handle wire protocols and failover.  The current code 
  -supports both synchronous and asynchronous communication and is built 
  -on NIO.  Future work will add IIOP support using the simple RMI/IIOP 
  +Hiram Chirino has implemented a remoting framework for routing
  +invocation requests both within and between VMs, freeing containers
  +from the need to handle wire protocols and failover.  The current code
  +supports both synchronous and asynchronous communication and is built
  +on NIO.  Future work will add IIOP support using the simple RMI/IIOP
   ORB, allowing us to meet the requirements of the J2EE specification.
   
   METADATA
  -We have defined a format for Geronimo-specific deployment descriptors 
  -and have added a basic object model for representing them in memory. A 
  -simple loader is in place based on Xerces and DOM, and investigation is 
  -proceeding into more effective XML binding based on the XMLBeans 
  -project. Aaron Mulder has been responsible for much of the initial 
  -implementation, and he is continuing work on J2EE Deployment (JSR 88) 
  +We have defined a format for Geronimo-specific deployment descriptors
  +and have added a basic object model for representing them in memory. A
  +simple loader is in place based on Xerces and DOM, and investigation is
  +proceeding into more effective XML binding based on the XMLBeans
  +project. Aaron Mulder has been responsible for much of the initial
  +implementation, and he is continuing work on J2EE Deployment (JSR 88)
   and Validation.
   
   CLIENT CONTAINER
  -Jeremy Boynes has implemented an Application Client Container as a 
  -starting point for enterprise container functionality.  This includes a 
  -simple implementation of the java:comp Environment Naming Context with 
  -support for env-entry and ejb-ref elements.  Basic interoperability 
  -with external J2EE servers has been tested and full support will come 
  +Jeremy Boynes has implemented an Application Client Container as a
  +starting point for enterprise container functionality.  This includes a
  +simple implementation of the java:comp Environment Naming Context with
  +support for env-entry and ejb-ref elements.  Basic interoperability
  +with external J2EE servers has been tested and full support will come
   with the introduction of IIOP remoting.
   
   SECURITY
  -A start has been made on security by David Blevins and Alan Cabrera in 
  -the form of a JACC (JSR 115) implementation which, combined with JAAS, 
  +A start has been made on security by David Blevins and Alan Cabrera in
  +the form of a JACC (JSR 115) implementation which, combined with JAAS,
   will provide a pluggable authentication and authorization framework.
   
   
   
  -With many of the basic services now in place, we expect to start work 
  -soon on the EJB containers and hopefully will have Session and BMP 
  +With many of the basic services now in place, we expect to start work
  +soon on the EJB containers and hopefully will have Session and BMP
   Entity support available within the next month.
   
  -In other areas, co-ordination has started with the OpenJMS and LDAPd 
  -projects to facilitate the integration of technology, and discussion 
  -has started with ObjectWeb to allow the sharing of technology between 
  +In other areas, co-ordination has started with the OpenJMS and LDAPd
  +projects to facilitate the integration of technology, and discussion
  +has started with ObjectWeb to allow the sharing of technology between
   the two projects.
   
  -This has been a phenomenal first month in which huge progress has been 
  -made. Much of the technical groundwork has now been laid and we can 
  +This has been a phenomenal first month in which huge progress has been
  +made. Much of the technical groundwork has now been laid and we can
   look forward to the challenges of the EJB and Connector subsystems.
   
   The Geronimo Project
  
  
  
  1.3       +5 -1      incubator/site/projects/wsrp4j.cwiki
  
  Index: wsrp4j.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/wsrp4j.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- wsrp4j.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ wsrp4j.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,7 @@
  +!Project Website
  +
  +The website for WSRP4J is at http://ws.apache.org/wsrp4j/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,4 +89,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  
  1.3       +6 -1      incubator/site/projects/juddi.cwiki
  
  Index: juddi.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/juddi.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- juddi.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ juddi.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,8 @@
  +!Project Website
  +
  +The website for jUDDI is still transferring to our servers. The old
  +website can be found at http://www.juddi.org/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,4 +90,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  
  1.2       +1 -1      incubator/site/projects/directory.cwiki
  
  Index: directory.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/directory.cwiki,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- directory.cwiki	23 Oct 2003 09:09:26 -0000	1.1
  +++ directory.cwiki	27 Oct 2003 14:20:40 -0000	1.2
  @@ -85,4 +85,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  
  1.3       +5 -1      incubator/site/projects/jaxme.cwiki
  
  Index: jaxme.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/jaxme.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- jaxme.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ jaxme.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,7 @@
  +!Project Website
  +
  +The website for JaxMe is at http://ws.apache.org/jaxme/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,4 +89,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  
  1.3       +5 -1      incubator/site/projects/lenya.cwiki
  
  Index: lenya.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/lenya.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- lenya.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ lenya.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,7 @@
  +!Project Website
  +
  +The website for Lenya is at http://cocoon.apache.org/lenya/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,4 +89,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  
  1.3       +17 -13    incubator/site/projects/xmlbeans.cwiki
  
  Index: xmlbeans.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/xmlbeans.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- xmlbeans.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ xmlbeans.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,4 +1,8 @@
  -Tasks for XMLBeans incubation.
  +!Project Website
  +
  +The website for XmlBeans is at http://xml.apache.org/xmlbeans/
  +
  +!Tasks for XMLBeans incubation.
   
   * Define incubation exit criteria
   * configure build to match ASF style
  @@ -10,7 +14,7 @@
   * build xmlbeans website
   
   ----
  -Tasks completed:
  +!Tasks completed:
   * create STATUS file in incubator-cvs
   * create mailing lists
   * create xml-xmlbeans CVS
  @@ -39,9 +43,9 @@
   * setup xmlbeans wiki area and refactor pages to there
   
   ----
  -Exit criteria (put an X next to item when it is complete):
  +!Exit criteria (put an X next to item when it is complete):
   
  -Identify the project to be incubated: XMLBeans
  +!Identify the project to be incubated: XMLBeans
   
     -- Make sure that the requested project name does not already exist
        and check www.nameprotect.com to be sure that the name is not
  @@ -64,7 +68,7 @@
        the fit with the ASF, and create the lists and modules under the
        incubator address/module names if accepted.
   
  -Interim responsibility:
  +!Interim responsibility:
   
     X- Who has been identified as the shepherd for the incubation?
   
  @@ -74,7 +78,7 @@
   
         incubator/projects/xmlbeans/STATUS
   
  -Copyright:
  +!Copyright:
   
     X- Have the papers that transfer rights to the ASF been received?
        It is only necessary to transfer rights for the package, the
  @@ -82,7 +86,7 @@
   
     X- Have the files been updated to reflect the new ASF copyright?
   
  -Verify distribution rights:
  +!Verify distribution rights:
   
     X- For all code included with the distribution that is not under the
        Apache license, do we have the right to combine with Apache-licensed
  @@ -92,7 +96,7 @@
        of the following approved licenses:  Apache, BSD, Artistic, MIT/X,
        MIT/W3C, MPL 1.1, or something with essentially the same terms?
   
  -Establish a list of active committers:
  +!Establish a list of active committers:
   
     X- Are all active committers in the STATUS file?
   
  @@ -100,7 +104,7 @@
   
     X- Have they submitted a contributors agreement?
   
  -Infrastructure:
  +!Infrastructure:
   
     X- CVS modules created and committers added to avail file?
   
  @@ -110,7 +114,7 @@
   
     X- Has the project migrated to our infrastructure?
   
  -Collaborative Development:
  +!Collaborative Development:
   
     X- Have all of the active long-term volunteers been identified
        and acknowledged as committers on the project?
  @@ -127,14 +131,14 @@
     -- Are the decision-making guidelines published and agreed to by
        all of the committers?
   
  -Organizational acceptance of responsibility for the project:
  +!Organizational acceptance of responsibility for the project:
   
     -- If graduating to an existing PMC, has the PMC voted to accept it?
   
     -- If graduating to a new PMC, has the board voted to accept it?
   
  -Incubator sign-off:
  +!Incubator sign-off:
   
     -- Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
   
  
  
  
  1.3       +5 -1      incubator/site/projects/ftpserver.cwiki
  
  Index: ftpserver.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/projects/ftpserver.cwiki,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ftpserver.cwiki	16 Oct 2003 18:10:53 -0000	1.2
  +++ ftpserver.cwiki	27 Oct 2003 14:20:40 -0000	1.3
  @@ -1,3 +1,7 @@
  +!Project Website
  +
  +The website for FTPServer is at http://incubator.apache.org/ftpserver/
  +
   !Identify the project to be incubated
   
   *Make sure that the requested project name does not already exist
  @@ -85,4 +89,4 @@
   !Incubator sign-off
   
   *Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
  
  
  

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


Mime
View raw message