Tapestry in BugZilla

["Howard M. Lewis Ship" <hl...@attbi.com>]

I'm off and running, adding an initial set of components.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: Andrew C. Oliver [mailto:acoliver@apache.org] 
> Sent: Tuesday, March 11, 2003 9:34 PM
> To: Pier Fumagalli
> Cc: Howard M. Lewis Ship
> Subject: Re: [Fwd: [STATUS] Tapestry [LACK-OF] Progress]
> 
> 
> Thanks Pier.
> 
> Pier Fumagalli wrote:
> 
> >The channels do work...
> >
> >I've given Howard administrator access quite some time ago... I just 
> >verified... He should be able to add/remove components and 
> stuff... I 
> >can't do more than that on Bugzilla for Tapestry... I don't 
> even know 
> >what Tapestry is... :-)
> >
> >    Pier
> >
> >On 11/3/03 14:47, "Andrew C. Oliver" <ac...@apache.org> wrote:
> >
> >  
> >
> >>Pier,
> >>
> >>Can you help (with bugzilla)?  These guys have made all the proper 
> >>request through the proper channels, but well, the proper channels 
> >>don't really work ;-)
> >>
> >>If you could help I'd really appreciate it.
> >>
> >>-Andy
> >>
> >>
> >>From: "Howard M. Lewis Ship" <hl...@attbi.com>
> >>Reply-To: general@incubator.apache.org
> >>Date: Mon, 10 Mar 2003 18:58:22 -0500
> >>To: <ge...@incubator.apache.org>
> >>Subject: [STATUS] Tapestry [LACK-OF] Progress
> >>
> >>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.
> >>
> >>--
> >>Howard M. Lewis Ship
> >>Creator, Tapestry: Java Web Components 
> >>http://jakarta.apache.org/proposals/tapestry
> >>
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >>
> >>    
> >>
> >
> >
> >
> >
> >  
> >
> 
>