Avalon Community at large! I have tried to stay out of the subject of Fortress/ECM future as much as possible. I have finally made my own conclusions from reading all the opinions about the subject, so now let me throw another spanner into the machinery, which I believe to be compatible with _everyone's_ wishes and desires... :o)
If Fortress/ECM is 'not good enough for ASF' (Leo Simons' words) and that the ASF Board has quite large reservations about a codebase "move" distinct from a "fork" to a home outside ASF, then let's consider another twist to the same story. Fortress/ECM IS at the moment part of ASF, i.e. "good enough" at its current home. Let it stay here in Avalon! No fork, no move, no transfer, nothing but evolution of the existing codebase. And INSTEAD we request Merlin to be promoted to a TLP (Top Level Project), with an initial PMC and developer base of; - Stephen McConnell - Niclas Hedhman - Alex Karasulu - Andreas Oberhack - Timothy Bennett - J Aaron Farr (did I forget anyone?) Those Avalon PMC members with a Merlin-only interest resigns from Avalon PMC, and a restoration of the Avalon PMC is conducted, to something like; - J Aaron Farr - Leo Simons - Leo Sutic - Berin Loritsch - Hammett - Carsten Ziegler - Noel Bergman and possibly the rest of the BOP gang... (PeterD is an issue beyond my comprehension and the BOP gang need to sort that out. Personally, I think he is a very good resource, that get things done.) IMHO, this is the most sensible conclusion of achieving the goals that most people seems to agree with; 1. Multiple containers create unbearable tensions and lack of focus. 2. Forking is not good, and forking to outside ASF creates many 'issues'. 3. The best interest of the USERS in all categories. 4. The best interest of ASF (no codebase is leaving or terminated). 5. Putting history behind us. Execution ========= 1. Merlin becomes a TLP with the help of [EMAIL PROTECTED] 2. Merlin codebase and documentation is moved. 3. Avalon maintain Merlin as a "Related Projects" or similar. 4. Merlin will still depend on Avalon, and will maintain its links. 4. http://avalon.apache.org/merlin and a few others are maintained as redirects. 5. Possibly some other details needs resolution, like which pieces are actually moved, what shall we do with the org.apache.avalon package names used in Merlin sub-parts, and will any Merlin committers remain committers at Avalon... World Peace and Extinction of All Diseases will follow... What do you all think? Niclas P.S. Please observe that this is a crosspost to 3 lists. Any replies should be made to [EMAIL PROTECTED] ONLY, so if you are interested in posting and reading more about this proposal, please subscribe to that list by sending a mail to mailto:[EMAIL PROTECTED] -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
