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]
