On Thu, 31 Oct 2002 03:01, Leo Simons wrote: > On Wed, 2002-10-30 at 15:21, 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. > > agreed! IOW, the legal argument is also a strong argument for setting up > firm scope boundaries. right?
Thats the first step in the process. Hence why I am involved in Apache Commons ;) > Looking at commits to logkit, I am not quite sure it would qualify > immediately. A lot of the work on logkit seems to be done by you. Do you > think there's enough actual active committers to form a solid logkit > PMC? (I'm not to worried about user base, or conforming to standard, or > any of those others.... :) possibly not. > what are your (and everyone's) thoughts on the content of avalon-apps? large chunks can move to different places. When we clean up the rest of Avalon we can start moving bits out. -- Cheers, Peter Donald ------------------------------------ The two secrets to success: 1- Don't tell anyone everything. ------------------------------------ -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
