Hi,
Maybe it would be best to look at this from another perspective. There is only so much energy people can contribute to this project and there is significant chunk of "dead" code and/or non-excalibur-community code that is sucking energy away from the real work.
By "dead" code I mean stuff that was either forked out and is no longer actively developed, maintained and in some cases used. In these cases I think it makes sense to zap it from our repo and either archive it somewhere (if it is unused) or point users at replacement code (if it was forked).
* compatibility
==> commons-collections, spice-salt,
doug leas concrrent, spice-jndikit,
commons-cli
* configuration
==> spice-configkit for validation
... nuke the rest as it is unused?????
* event
==> d_haven-event
* i18n
==> spice-saltBy "non-excalibur-community" I mean things like xmlutil, store and/or sourceresolve. I haven't been active around here for ages but when I was these were mainly (only?) maintained by Cocoon people. In the long term it would seem to make sense that you move the code to where more interested parties are likely to work on it (ie back into cocoon). The fact that cocooners had (or still have?) access to excaliburs repo did not make them a part of this community and IIRC there was no real infusion of development energy.
As for the rest of the code I think it is important to determine exactly where it is used and what can be done to minimize the maintanence and/or development overhead.
Rather than doing it all in one shot lets take little steps and evolve the codebase incrementally.
-- Cheers,
Peter Donald "Now, now my good man, this is no time for making enemies." - Voltaire (1694-1778) on his deathbed in response to a priest asking that he renounce Satan.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
