Peter Donald wrote:
On Wed, 30 Oct 2002 22:53, Leo Simons wrote:
options to make it less icky:
- jakarta PMC votes on releases (not really a practical option)
- avalon gets a board-installed PMC which votes on releases
- destroy avalon (rather not)
No option is currently viable at the moment. Currently Avalon has no scope
boundaries and thus would not make a good top level project.
The first paragraph of the Avalon home page declares:
The Avalon project is an effort to create, design, develop and
maintain a common framework and set of components for applications
written using the Java language.
This seems to me to define a scope and boundaries which are generally
recognized within the Apache community. Yes, the above could be refined
but that is part of the process of preparing a proposal to the Apache
Board.
Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
