On Wed, 4 Dec 2002 23:43, Leo Sutic wrote: > > From: Peter Donald [mailto:[EMAIL PROTECTED]] > > > > Hi, > > > > One of the problems that has plagued Avalon is the result of one-man > > codebases. I propose we remove almost all of these withing > > the next month. > > They can be moved to jakarta-commons, the incubator or to > > sourceforge as the > > developer wishes. > > > > Thoughts/Votes? > > What codebases do you refer to?
Well all the ones that cause conflict are one-man codebases so they are the primary ones I want to see removed. That way Avalon can not be used as a distribution point for pet projects and more importantly it is not seen to be a personal playground. Removing all these things would mean a reduction in problems IMHO - especially if people are forced to develope them elsewhere and only when they have the support of the whole Avalon community are they allowed to return. Other non-controvertial codebases can end up in sandbox if needs be but that needs to be something that is approved by all committers or not. So the codebases that are essentially one man shoes include the following. Note that I marked those with a * that I think should move out. naming/ * policy/ * assembly/ * extension/ * (though we need to provide migration path out) bzip2/ * info/ * cache/ interceptor/ * tar/ * threadcontext/ * jprocess/ * tweety/ containerkit/ * converter/ * xfc/ csframework/ loader/ * zip/ * meta/ * I think tweety should be removed as a codebase and integrated into Avalon/Framework as a documentation artefact rather than as a codebase. XFC is too important as it provides a migration path from ECM to fortress to move out. csframework causes no problems so let it stay IMHO. In -apps CVS there is probably other codebases that can be migrated to sandbox or out but the only one that I believe causes any heartburn is the enterprise stuff so the rest can stay (in sandbox if necessary). -- Cheers, Peter Donald "The ability to quote is a serviceable substitute for wit." -- Maugham -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
