On Wed, 2002-10-30 at 16:39, Stephen McConnell wrote: > 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.
hmm. I think we should try to grow back into that scope before we draft a proposal for the board :) Also, it would be beneficial if the "set of components" part of the goal is delegated to another body, be it apache commons, jakarta-commons or a new 'avalon component repository' as nicola recently suggested. Finally, avalon has had a bit of a de-facto incubation role (ie we host csframework...) which is something we should definately stop doing in favour of supporting the incubator project. I like the concept of "a project is something that generates a single release" some board members advocated on reorg :) cheers, Leo -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
