just some snippets from recent discussions. steve: > > Perhaps you have not been tracking the work I have been doing on Merlin > > development? If you take the time and effort, you see that it is 100% > > compatible with compoents declared in containerkit.
pete: > false. steve: > > Do correct me if I wrong - but what I proposed is exactly those pieces > > that are common - a.k.a the same. This is not about dragging you in a > > direction - it is about moving forward in achiving concensus at the very > > lowest possible levels on how containers can work in a component > > interoperable fashion. That seems to me to be the priority. pete: > I don't really care whether merlin is compatible or not. If you want to make > it compatible then fine. If you want to deviate then that is fine aswell. pete: > Anyways I'll just go back to my "private garden", continue with my > "intellectual masturbation" and wait for the sky to fall. In 6 months we will > see whats what. > > Flame on. steve: > > Pete - do you think that's reasonable? pete: > I dont see any advantage for me in doing it that. Theres no chance of you ever > doing some of the things you want to do in anything I am involved with. You > dont seem to want to do it the way I have suggested, hence you will only end > up whining again. I think the best idea would be for you to do with merlin > whatever you want and be done with it. Regardless of who wins any discussion like this, the community looses. Statements in the line of "you'll need the PMC to get this to work" and "if you want to use what I write, go ahead" are counterproductive to the community as a whole. Regardless of the issue at hand, there's a big community involved with avalon, people depend on its developers to work together. If they can't do so, the community will sooner or later fall apart and we will all have failed. I will try and do everything possible to keep *that* from happening, even if it means lots of -1s on lots of stuff or talking to the PMC. We'll all start throwing -1s at each other which will lead to failure. IOW, the community as a whole wants agreement on the stuff being discussed, and if you won't reach it, all of it will be rejected. Which will lead to forking, competition, the community falling apart...and in the end a Services JSR that's just as bad as the logging API. This is not a playground. Stop behaving like a kid. - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
