> > So in a sense, Directory is another library project with open
> > rules (like agora). (Not sure if Agora was going to be a
> > Library peer in Jakarta-land, or a 'product peer' in Library-land.
>
> My biggest concern is that I don't understand the relationship between
> Library, Directory, Agora, and Avalon.
The proposed project ( library/directory/agora/whatever ) is indeed
similar with avalon in one of the goals - creating server side components.
( and also to jakarta-tools )
But IMHO the current proposal is closer to alexandria then avalon.
But what's special about the library/agora is that it proposes to
act as a common repository, managed in common by multiple projects. While
creating productized components is also a goal ( same as in Avalon ), the
sharing of components and inter-project dynamics are more important.
>From this point of view, avalon is one of the projects that will share
components - equal with all other projects where general-purpose code is
developed.
> Avalon has been in the process of splitting into multiple cvs repositories,
> using the naming convention of jakarta-avalon-xxx.
> It would be a simple matter to create a jakarta-avalon-dbpool.
If the goal would be to create a dbpool, maybe.
But we want to a way to collect, catalog and share multiple dbpools, and
eventually productize the best ones. Creating a new repository for each
component is not a good idea.
> I'd like to hear consensus with someone representing jakarta-avalon (i.e.,
> Peter Donald) before creating another subproject with overlapping goals.
I think the library's goal is to overlap with all jakarta projects :-)
And we'll need a bigger consensus - i.e. most jakarta projects should
participate in order for this to be a success.
Beeing "project-neutral" is important to create what we need.
Costin
