3.2 issues :(

Chris Lee clee at kde.org
Sun Jan 18 09:26:44 GMT 2004

Hash: SHA1

On Sunday 18 January 2004 1:59 am, Frans Englich wrote:
> On Sunday 18 January 2004 08:33, Dawit A. wrote:
> > On Sunday 18 January 2004 02:10, Frans Englich wrote:
> > > On Sunday 18 January 2004 08:01, George Staikos wrote:
> > > >     For some reason in HEAD the kicker clock (don't know when this
> > > > changed) has lost track of the fact that I like to see the date along
> > > > with the time.
> > >
> > > Yupp, that's a feature not a bug, some people would say. I changed(with
> > > consensus on kde-usability) a couple of weeks ago since it was too
> > > small and cluttered on 800x600 displays. BTW, you have the date as
> > > tooltip on clock.
> >
> > Please note that not everyone is subscribed to kde-usability.
> Keeping the maintainer informed is one thing but kde-usability exists for
> usability issues. If someone is not subscribed for whatever reasons, then
> that person simply misses the usability discussions, unfortunately. If
> kde-usability is not ment to be used for its purpose, it should be closed.


If you think that you can have a discussion on kde-usability and commit based
on a consensus there, without discussing the commit with an application's
maintainer, you are seriously mistaken.

There is no "sick hierarchy" or "corrupted power" involved, it's simply a
matter of respect which you seem to be lacking here. Changing defaults is ok,
assuming agreement on the usability list and permission from the maintainer
to commit, but changing existing settings is not to be done. There is a
technical framework that exists for this sort of change as well, in

You get into a much more difficult situation with unmaintained or infrequently
maintained applications - much of the apps in kdenonbeta, for example - but
Kicker is far from unmaintained. And I for one would revoke any commits made
to a module of mine if people just started committing to it without even
bothering to point me to discussion about potential changes.

This particular example shows a stunning lack of communication with the
application maintainer, and this is why you are lacking the "respect" that
you think you deserve. Unless you are the maintainer of the application, you
should not be committing to it without first at least notifying the
maintainer, let alone getting their approval. This is nothing new and it has
been standard practice for as long as I've been involved in KDE (and I've
violated it a couple of times myself and been rightfully blasted as well).

- -Chris
Version: GnuPG v1.2.4 (GNU/Linux)


More information about the kde-core-devel mailing list