cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bentley, Tim" <>
Subject RE: Central repository for taglibs
Date Thu, 29 Mar 2001 23:58:52 GMT
Alternatively, do you need multiple committing accounts?  Since nobody seems
to know how many people are working on/would wish to contribute taglibs,
maybe you can afford to start out with a central figure who does the
committing.  Contributors can email new taglibs or diffs.  Something like
this method would be required for new taglibs anyway, as they'd have to be
checked for conformance and quality.  

If this one person gets too swamped, then you'll know you're onto something
and can take appropriate steps.  I tend to follow Uli's way of thinking - I
don't think the critical mass is there yet - but even if that's wrong, I
think sticking the project off on SourceForge or somewhere will guarantee it
dies.  Without high visibility and a perceived closeness to Cocoon, Cocoon
users (especially newer ones, who have their work cut out just figuring out
how to get the thing running) are just going to ignore it.

Just my opinion....

Tim Bentley

> On Thu, Mar 29, 2001 at 01:55:05AM -0500, Donald Ball wrote:
> > On Thu, 29 Mar 2001, Jeff Turner wrote:
> > 
> [..] 
> > > A separate repository is an obvious need. Taglib 
> committers are usually not
> > > Cocoon committers.
> > 
> > i tend to concur. i don't know how willing the pmc will be 
> to hand out
> > commit accounts freely to anyone with a logicsheet though. 
> the asf is
> > pretty tight about security, with just cause - imagine what 
> a cracker
> > could do if he could get malicious code in to either the 
> cvs source tree
> > (unlikely) or the packages in the downloads area. using a 
> sourceforge-like
> > entity might be the easiest way to at least get this 
> started. i can ask
> > the pmc though.
> I can see their point. I wonder how jakarta-taglibs got started.
> Perhaps Craig McClanahan twisted some arms ;)
> OTOH, I agree with Ulrich that any taglibs project without 
> the blessing
> of Apache, and without esql, hasn't much chance of gaining momentum.
> So to get started, how does this sound: we create a 
> sourceforge project,
> populate it with all taglibs whose authors give consent 
> (incl. esql and
> ones bundled with Cocoon). Then let this run for three months 
> or so. If
> by then the project is still alive, stable, and of sufficient quality,
> ask the PMC to vote on it's inclusion in

Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message