> From: Stephen McConnell [mailto:[EMAIL PROTECTED] > > You missed the fact that the meta package was pulled out of > Merlin and > was pushed and prodded and worked over as a container independent > meta-info facility that was voted on, released by the community and > published by the PMC.
I didn't miss that, and that's where our interpretations diverge. Pulled out of merlin, yes. Worked over, yes. Released by PMC (nobody else can release stuff), yes. Voted the framework-level metainfo package in its current form? No. If there is such a vote, or a discussion leading to a consensus to that effect, I must admit to having slept through it and I'll get with the program. But just because something is released by the PMC doen't mean that it has become framework-level. In that case, we'd all be using ECM semantics and rules. (Since we've also released Phoenix, that would mean some kind of paradox.) So that's why I asked for a link to the vote and / or discussion. Can Avalon/Meta be the framework-wide metainfo package? Sure. In its current form? I don't really want that. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
