> And just how many competing products and integral architectures is > Cocoon endorsing, publishing and supporting? Just how many mail servers > is the James community supporting? How many different component > architecture is Turbine backing (as opposed to the number of > architectures they have to deal with).
Fallacy. I was talking about *community* and not about *product*. > And how does this impact a community. It means that the community is a > community because is bound be a single idea, a vision, an ideal - call > it what you want. Agreed. > Put in place one solution. Solution for whom, for God's sake. Thats the point: for a very particullar audience who wants to feel using a J2EE like container. > Kill the rest and you change the equation. And push your decision through their trhoat. > I'm not concerned about > people leaving because we take a decision. I am > concerned about people leaving because we don't a decision. Maybe the majority thinks Merlin SHOULD be the future of Avalon, the *reference* implementation. I'm included in this group. But I - and others I think - disagree that it will happen as the way it is *now*. And when Aaron says: I don't want the damn repository you'll came with "whats the *real* reason to not want it". Your words: "Merlin needs to be break down 'til it becomes Avalon". For every day it seems like to more and more distant goal. And you take the defensive when someone says "I don't want the repository!" Go it? > So lets get to the point. One product architecture. One product > implementation. If someone doesn't like that product then they need to > get their butt in gear and do something about it. And a united community > will make sure it evolve. Ok, will do. > Now is the time to make that decision. Now its time to get consensus. Please, get your butt in gear and make your proposal. -- hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
