Re: How to deal with unwilling devs?

Am Mittwoch, 29. Juli 2009 23:53:03 schrieb Andreas Pakulat:

> Thats his right, its his application (at least partly) and he can do
> whatever he wants with it.

No, it's not. Not even close. Thomas McGuire is the main dev. The name of that 
guy isn't even in KMail's credits window. Other than that: What's even the 
point of a usability team if nobody needs to care?


> You're kidding right? That bugreport has been filed about 10 days ago.
> Thats not even close to "ignore completely".

Enough time to at least change the bug status from UNCONFIRMED to NEW.


> Thats easy: Start a discussion on their mailinglist involving usability
> folks.

Why does the usability team run behind every other team? Why discuss a matter 
here first just to have the same discussion again there?


> Neither the HIG (note the word "Guideline" in it) nor any person
> can enforce such changes.

It is possible to enforce bug fixes (just watch the presentation of OpenBSD's 
release process that was posted a short while ago), however I'm not a fan of 
enforcing anything. I prefer encouraging.
Having the same discussion over and over again on the mailing list of each app 
that's affected of a usability issue is one way to encourage the devs, but 
with several hundred applications in KDE's SVN that way is hardly efficient.


>  you'll have to discuss with them what
> "the app" is. Especially in the case of kmail thats not quite easy as
> Christophe already hinted.

Yes, he hinted that there are technical difficulties with this bug. Technical 
difficulties however do not mean that this usability issue is invalid. It can 
mean that the priority is low, because porting to Akonadi and ironing out 
other bugs are more pressing aspects. Yes, that may be true, but declaring a 
bug as invalid has nothing to do with that.
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability