At 04:01 1/3/01 -0800, [EMAIL PROTECTED] wrote:
>> > 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 )
ie Avalon has identical content but ...
>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.
different infrastructure. Since I think the infrastructure we create
will/should be integrated into all projects - what will happen when we
integrate it into Avalon? We will have two identical projects.
>Beeing "project-neutral" is important to create what we need.
This would be the only sticking point I see. It is unfortunate that other
projects are seen as "competitors" rather than "companions" but I guess
until this is "fixed" it could be an issue. However instead of starting
again I would prefer that we try to start fixing things now.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
