Regardless of the direction this takes I think I and others are going to want to be involved with the effort. Hopefully we can all put in our two cents to make it the de facto standard as Apache product no matter where (in which Apache project) or how it is built. I'm all for putting it into the incubator.
I can't wait until it starts up. Alex > > From: Leo Simons <[EMAIL PROTECTED]> > Date: 2003/11/12 Wed AM 11:07:21 EST > To: [EMAIL PROTECTED] > Subject: Re: [PROPOSAL] Avalon Components project > > Stephen McConnell wrote: > > The proposal is a Avalon Component project here at Apache - seperate but > > aligned with Avalon. > <snip/> > > In this scenario - the new project would establish a PMC responsible for > > oversite, content would be licensed under ASL, and the relationship > > between Avalon and the new project would include our focus on the tools > > and technologies dealing with aspects such as technical complicance, > > validation test suites, component repository tools, etc. > > overhead! I've got no time for another PMC :D > > Seriously, I think a smart plan is to see what flows from the > [EMAIL PROTECTED] discussion, see what kind of code we want to have > in merlin based on that, and perhaps decouple a large part of that and > combine it with other code efforts in a new project that starts off in > the incubator. > > A possible destination for that would be under ant, under maven, under > avalon, or TLP. > > - LSD > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
