KDE RC Authority

Martijn Klingens klingens at kde.org
Thu Jul 4 22:49:48 BST 2002


On Thursday 04 July 2002 23:21, Dirk Mueller wrote:
> On Don, 04 Jul 2002, Neil Stevens wrote:
> > > PS: If you don't like that the release dude has the very last decision,
> > > then make sure that he doesn't get the chance having to decide this
> > > matter. It was outlined already: convincing the people here that your
> > > opinion on the "matter" is the right one.
> >
> > So in an instance like this, why you should get to override a clear
> > disagreement?  When did a purely organizational position become an
> > executive one?
>
> Jeez, I wasn't impling that. Maybe it would have been more clear to you if
> the above sentence reads "If you don't like that the release dude would get
> the very last decision.. "  Under no circumstance I ever claimed to have
> _executive rights_ over KDE. I really, really start to wonder why I have to
> repeat this over and over again, just for you.

If you can make a final decision you do have executive rights. I have to agree 
with Neil here. Where I don't agree with Neil is whether that's bad or not. 
Someone has to turn words into deeds or we're talking forever and nothing is 
done. If the RC is the one who does it, fine with me. It's often the boring 
job and if you're not careful it might get you flamed away as well.

Neil, do you think it's bad that someone finally decides after things are 
discussed? If so, how should we ever reach a decision then? Maintaining a 
status quo until everyone unanimously agrees is a utopia. It will stall the 
project and make nothing happen at all. Pure anarchy doesn't work, no matter 
how close you may get.

Martijn





More information about the kde-core-devel mailing list