Nicola Ken Barozzi wrote: > ... > > As it has been partially agreed on, but this still has to be fully > discussed, there seems to be a need to: > > 1) define more clearly the boundaries of framework, and make the new > repository a base for the new Avalon V, by deciding package by package, > class by class, what should go in there. The plans of Avalon5 should not > be of a rewrite but of a more clear definition of the framework, > especially with regards to info and meta concepts. We should really come > to a common base here.
Absolutely. > > 2) move the Components in a "common" repository where also non-Avalon > committers can partecipate easily. Be it in Apache Commons, in > Avalon-Commons, or wherever, I still see a need for such a repository, > that seems nice also for example to Turbine devs, OBJ devs, some Cocoon > devs I've talked to. > Yes, I think this is a very good idea. Actually it should make the build system easier as well. > 3) The containers that are in the works, as cool as they seem to be, > are still scratchpad stuff, and thus should be clearly put in a place > where it's clear to all. Current structure is really confusing, and > releases are a very important part of our system. > And personally I'm still wondering if we really need different implementations with different features. But this is another topic, we should discuss when it is time. Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
