Paul Hammant wrote:
Leo,I said to Leo Simons that partitioning voting and committ priviliges would lead
to the mother of all bureaucracies - and I think your approach will fail for similar
reasons. An example: The use of release().
If I understand it correctly, Phoenix usage style do not provide for container-
managed pooling of instances, while ECM does.Fine.The ComponentManager/ServiceManager contract is mute on the point.
Does this mean that the question is local to Phoenix (i.e. can/should be
decided by those with Phoenix voting rights) or is it global to Avalon (i.e.
can/should be voted on by all)?And forced on all? EOB, Tweety, Plexus? No thanks.The second: If you limit voting rights to those who agree with the vision of
a component, then you are, in effect, deliberately setting up a group of
yes-men. Think about it: If only those that agree with your vision for Phoenix
get to vote about Phoenix things, where are you going to get opposition
from?Hmmm, and who are these yes-men?To put the above in a form blunt enough to be indistiguishable from rudeness:
Isn't your advocacy of "meritocracy" not just a way to set yourself up as
the uncontested ruler of Phoenix, and to get rid of Stephen? Isn't he what
you refer to as "hostile attacks"? Isn't that the problem?
Stephen has nothing to do with Phoenix and Peter nothing to do with Merlin. Fine!
From someone who has nothing to do with Phoenix: http://jakarta.apache.org/avalon/phoenix/guide-example-configuration.html (now I wonder - where did I get all of that insight?) :-)
If Phoenix/Merlin were hosted at SourceForge, would an Avalon dude have right of maint on that project? No, those communities are built, like ours. They invite people who've made a few patches to step up to committer. Funiliy enough those people tend to be people who use the project, but want a couple of small tweaks. The community grows from like minded people. That is exactly how this community, Avalon, was built. Unfortunately we have bucket loads of different things here. It is impossible for anyone to use Merlin, Fortress, Phoenix and ECM, let alone develop for them. We should behave in the same respectful way inside Avalon as we would do if they were truly different projects (Catalina @ Jakarta, EOB @ sourceforge).
I disagree - if they were truly different projects (and by implication - different communities), then there would be the grounds for seperating these communities though independent PMCs. If you really believe that Phoenix is an indepedent community then you free to work up concensus on that and submit a proposal to the Apache Board for a Phoenix PMC. That's what Apache structure and procedures provide - the framework to hande just such a thing.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
