[EMAIL PROTECTED] wrote:
>
> > Ted Husted wrote:
> > >
> > > How about a commons-general list and a combined user/dev list for each
> > > package?
> > >
> > > jakarta-commons-general
> > > jakarta-commons-DBCP
> > > jakarta-commons-digester
>
> I would say -1 on separate CVS, +0 on separate dev/user/announce list,
> maybe later we can split dev ( or fork the most active components in
> separate lists ).
Why can't we have both? I just never get where you are coming from on
this. They aren't exclusionary.
We can have a separate CVS for multiple 'mini-projects', and one is for
Agora [ a big 'add-everyone-in-jakarta' free-for-all incubator], one for
Directory, and one is for the DBConnectionPool with it's committers, and
one for XML config, one for ...
I just don't understand why it's all or nothing.
Has it ever been a problem where someone with something to add to a
project wasn't able to participate?
>
> I don't mind a common mailing list that much, but I'm very much
> against separate CVS - I hope we'll end up with
> a significant number of components, many of them duplicated and with
> inter-dependencies.
Why? Then the whole purpose of productized, independant components goes
out the window - it would be just like we have now - a seething mass of
stuff that no one can dig out and use independant of the owning project.
(Yes, a gross generalization, but right more often than not...)
> I would like to have a single CVS tree to worry about,
> the jakarta-commons ( I'm talking as a library user ).
>
> Why not having a single CVS tree, with separate top-level dirs ?
> This seems to work fine in taglibs and catalina.
Because taglibs is a set of related items. Whats related about a DB
Connection Pool and a Testing Suite?
Why don't you do it in the Tomcat project then? Version issue? :)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
