KDE RC Authority
Thomas Zander
zander at planescape.com
Thu Jul 4 21:42:08 BST 2002
On Thu, Jul 04, 2002 at 01:37:11PM -0700, Neil Stevens wrote:
> On Thursday July 04, 2002 01:24, Dirk Mueller 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.
>
> There were two long threads of people trying to convince each other. It
> was so clearly split that everyone now is specifically trying to avoid
> having that discussion again.
There is no reason to argue if you have no intention to learn from it.
> So in an instance like this, why you should get to override a clear
> disagreement?
A disagreement is a status that can not maintain since it will cause unhappyness
and endless badgering in the community. Making a decision makes the one doing it
a clear target, but at least the majority will just go on with their work after
a healthy cursing.
> When did a purely organizational position become an
> executive one?
It isn't. Some people just have to take responsibility sometimes, I wouldn't
want to be in his shoes.
> It's been said that many KDE developers would fork KDE if an executive
> layer like the KDE Foundation were placed on top of KDE, making decisions
> about release. So why should an unelected RC get to make decisions we
> woudln't trust an elected board to make?
Did he?
Can you really claim that any actions our RC has done were not for the
betterment of KDE and the community?
If the releases had to be done according to the way you would want it would the
community be better off? Are you actually doing us a service with these
discussions?
--
Thomas Zander zander at planescape.com
We are what we pretend to be
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20020704/5e4cfe5e/attachment.sig>
More information about the kde-core-devel
mailing list