Re: Avalon Components (Re: Our site is too big)

Nicola Ken Barozzi wrote:
> I think that we should now decide where to put the Avalon components, if 
> in Apache Commons or Avalon Components.

I'm (still) strongly in favour of a _common_ repository for _common_ 
components, in that all of Jakarta Commons, and Apache Commons, and 
Avalon Commons, and Turbine Commons, and <whatever> Commons is the same 
common repository. It Just Makes Sense(tm).

CVS access is not the issue (if it works @ apache as it works for me at 
work, it is the simple editing of one file). What we need is community 
unification (to the extend feasible).

cheers,

- Leo