incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From leosim...@apache.org
Subject cvs commit: incubator STATUS
Date Mon, 27 Oct 2003 13:59:13 GMT
leosimons    2003/10/27 05:59:13

  Modified:    .        STATUS
  Log:
  - add some resolved items,
  - update committer info,
  - move some stuff around (less duplication, most important things at the top)
  - some typos and formatting
  
  Revision  Changes    Path
  1.19      +61 -25    incubator/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/incubator/STATUS,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- STATUS	23 Oct 2003 15:26:27 -0000	1.18
  +++ STATUS	27 Oct 2003 13:59:13 -0000	1.19
  @@ -5,27 +5,53 @@
   Wiki page: http://Nagoya.Apache.Org/wiki/apachewiki.cgi?ApacheIncubatorProjectPages
   
   [note: the Web site is the 'official' documentation; the wiki pages
  - are for collaborative development, including stuf destined for the
  + are for collaborative development, including stuff destined for the
    Web site.]
   
  -Open Items needing immediate resolution:
  -========================================
  +Pending Issues
  +==============
   
  -1. We need to be very very clear about what it takes to be accepted
  -   into the incubator.  It should be a very low bar to leap, possibly
  -   not much more than 'no problematic code' and the existence of a
  -   healthy community (we don't want to become a dumping ground).
  -
  -2. We need to be very very clear about what it takes for a podling
  -   to graduate from the incubator.  The basic requirements obviously
  -   include: has a home, either as part of another ASF project or as
  -   a new top-level project of its own; needs to be a credit to the
  -   ASF and function well in the ASF framework; ...
  +    o We need to be very very clear about what it takes to be accepted
  +      into the incubator.  It should be a very low bar to leap, possibly
  +      not much more than 'no problematic code' and the existence of a
  +      healthy community (we don't want to become a dumping ground).
  +
  +    o We need to be very very clear about what it takes for a podling
  +      to graduate from the incubator.  The basic requirements obviously
  +      include: has a home, either as part of another ASF project or as
  +      a new top-level project of its own; needs to be a credit to the
  +      ASF and function well in the ASF framework; ...
  +
  +    o Moving the bylaw documentation from the Wiki to the main site
  +
  +Resolved Issues
  +===============
  +
  +    o The policy documentation does not need ratification of changes
  +      if there seems consensus. Accordingly, the draft status of these
  +      documents can be removed and we will use the lazy "commit first,
  +      discuss later" mode common across the ASF for documentation
  +      (http://nagoya.apache.org/eyebrowse/BrowseList?listName=general@incubator.apache.org&by=thread&from=517190)
   
  +    o Coming up with a set of bylaws for the project
  +      (http://nagoya.apache.org/eyebrowse/BrowseList?listName=general@incubator.apache.org&by=thread&from=517190)
  +
  +    o All projects under incubation must use a STATUS file (or a
  +      status.xml file if the project prefers XML) that contains
  +      information the PMC needs about the project. This file must
  +      live at the root of the project cvs module
  +      (http://nagoya.apache.org/eyebrowse/BrowseList?listName=general@incubator.apache.org&by=thread&from=504543)
  +
  +    o Projects under incubation should display appropriate "disclaimers"
  +      so that it is clear that they are, indeed, under incubation
  +      (http://nagoya.apache.org/eyebrowse/BrowseList?listName=general@incubator.apache.org&by=thread&from=504543)
   
   The Incubation Process
   ======================
   
  +This tries to list all the actions items that must be complete for a project
  +before it can graduate from the incubator. It is probably incomplete.
  +
   Identify the project to be incubated:
   
     -- Make sure that the requested project name does not already exist
  @@ -113,7 +139,7 @@
   Incubator sign-off:
   
     -- Has the Incubator decided that the project has accomplished all
  -     of the above tasks? 
  +     of the above tasks?
   
   
   Incubator Project
  @@ -137,15 +163,24 @@
       o This status file is mailed to general@incubator.apache.org
         every Wednesday
   
  -Project committers (as of 2003-03-29):
  +Project committers (as of 2003-10-27):
  +
  +    Note that the most current information is always in the CVS
  +    avail file, and can be found using:
  +
  +        ssh cvs.apache.org
  +        cat /home/cvs/CVSROOT/avail | grep incubator
   
       o incubator-core:
         aaron,coar,fielding,fitz,gstein,hammant,jim,nicolaken,rubys,striker
   
       o incubator and incubator-site:
  -      {incubator-core},acoliver,bloritsch,dion,glongman,hlship,
  -      jefft,jvanzyl,leif,leosimons,medgar,mindbridge,nclayton,proyal,
  -      rana_b,rlewisshell,vinayc
  +      {incubator-core},acoliver,blautenb,bloritsch,dims,dion,geirm,glongman,
  +      hlship,jefft,jvanzyl,leif,leosimons,medgar,mindbridge,nclayton,noel,
  +      proyal,rana_b,rlewisshell,twl,vinayc
  +
  +    o incubator-altrmi:
  +      {incubator-core},acoliver,vinayc,leif,jefft,proyal,bloritsch
   
       o incubator-altrmi:
         {incubator-core},acoliver,vinayc,leif,jefft,proyal,bloritsch
  @@ -153,17 +188,18 @@
       o incubator-ftpserver:
         {incubator-core},rana_b,jvanzyl
   
  +    o incubator-geronimo:
  +      {incubator-core},gstein,geirm,ceki,jstrachan,jim,bsnyder,dain,djencks,
  +      gregw,janb,jdillon,jboynes,dblevins,chirino,jules,rmonson,ammulder,adc
   
   Release:
  -    none yet; still ramping up
   
  -Resolved Issues:
  -    none yet; still ramping up
  +    The Incubator Project doesn't do "releases" itself. Track of
  +    releases made by projects in the incubator is kept in the
  +    per-project status files.
   
  -Pending issues:
  -    o Coming up with a set of bylaws for the project
  +Possible topics for educational documents:
   
  -Possible topics for educational documents
       o A document which describes the 'ideal' way a project has to
         go to be successfully integrated into the ASF: the flow of the
         normal incubation process should be pictured
  
  
  

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


Mime
View raw message