Re: cvs commit: jakarta-avalon/src/proposal/avalon5 discussion-points.txt

In article <[email protected]>, "Peter Donald"
<[email protected]> wrote:
>...
>>   Topic: Should we unify the CVS structures? Explanation:
>>       We currently have ~9 CVS structures.  The purpose was to separate
>>       the different projects and make it very clear what code belongs
>>       to which project. That project also helps us identify areas of
>>       tight coupling and what projects depend on which other projects. 
>>       That can still be done in one CVS structure, using directories to
>>       distinguish the projects.
>>   PRO:
>>       bloritsch - We have some projects that are no
>>           longer supported or needed (like Testlet). It would be a good
>>           way to clean out the cruft, and help manage the focus and
>>           scope of Avalon.
> 
> Maybe we should wait for subversion (subversion.tigris.org) - it looks
> like a much better tool and if we go to that we can do the big
> re-arrange then.

The infrastructure guys keep threatening to set this up. Hopefully, it
will happen soon. I'm biased, of course :-), but I'd definitely recommend
it for any ASF project wanting to switch.

>>   Topic: Should we make the Avalon maling lists from
>>          avalon.apache.org?
>>   Explanation:
>>       We are currently our own entity.  We are not a Jakarta project
>>       any more.  I would suggest the mailing lists (in addition to
>>       [email protected]): developers@, users@,
>>   	cvs@, and possibly general@ and announce@.

dev@ is the standard name.

Cheers,
-g

--
Greg Stein, http://www.lyra.org/