incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From field...@apache.org
Subject cvs commit: incubator/projects/tapestry STATUS
Date Thu, 13 Mar 2003 01:18:14 GMT
fielding    2003/03/12 17:18:14

  Modified:    projects/tapestry STATUS
  Log:
  Howard, edit the STATUS file to reflect reality.
  
  Revision  Changes    Path
  1.2       +36 -1     incubator/projects/tapestry/STATUS
  
  Index: STATUS
  ===================================================================
  RCS file: /home/cvs/incubator/projects/tapestry/STATUS,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- STATUS	4 Jan 2003 23:53:42 -0000	1.1
  +++ STATUS	13 Mar 2003 01:18:14 -0000	1.2
  @@ -27,3 +27,38 @@
   Resolved Issues:
       none yet
   
  +From: "Howard M. Lewis Ship" <hlship@attbi.com>
  +Date: Mon Mar 10, 2003  3:58:22  PM US/Pacific
  +To: <general@incubator.apache.org>
  +Subject: [STATUS] Tapestry [LACK-OF] Progress
  +Reply-To: general@incubator.apache.org
  +
  +How, exactly, is Tapestry ever expected to exit the proposal stage?
  +
  +Despite repeated attempts, Tapestry is NOT in BugZilla.  We're still forced
  +to use SourceForge for bug tracking.
  +
  +Tapestry's mailing lists are not getting archived any more (not since 2/21).
  +
  +Nobody seems to know ANY of the procedures for getting things done.  Nothing
  +is documented.  Simple things like the correct way to distribute a release
  +(including signing and mirroring) are just "known" by the right people ...
  +and I don't even know who is in the know.
  +
  +Andrew and Dion have been helpful, both before the move and after.
  +
  +The only other accomplishment of the incubation process has been a code
  +audit that resulted in a shuffling of the libraries checked into CVS and
  +distributed with the framework.
  +
  +Jakarta infrastructure is non-existent. Worse, the Jakarta culture
  +erroneously expects things to get done based on e-mails, rather than
  +something organized, like using BugZilla to track infrastructure requests. 
  +
  +The Incubator team has yet to provide a time table or a check list to
  +indicate what the exit criteria are.  In terms of Tapestry's commitments to
  +the Incubator, it looks like we're more than there (based on
  +http://incubator.apache.org/process.html).  In terms of Incubator's
  +commitments to Tapestry ... that is, to assist Tapestry in moving into
  +Jakarta, fitting in, and accessing infrastructure; very little has been
  +accomplished.
  
  
  

Mime
View raw message