Re: How to deal with unwilling devs?

On Thursday, 2009-07-30, Markus wrote:
> 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.

This is a very naive position, especially regarding popular applications.
For example I haven't read any KDEPIM bugs for about a week and the folder of 
the mailinglist bug activitiy is sent to now contains 333 unread messages.

Developers of the affected applications rely on people from BugSquad and non-
core developers to triage this huge amount of reports and comments, so it is 
quite common that the first contact is one of those helpful folks.

If they have technical background in the application at hand, they might close 
a report. However, this doesn't mean that the developers didn't have a chance 
to decide differently, but that it might take longer for them to reach a state 
when they can take care of non-critical bugs (especially during Beta/RC 
times).

Now, for the specific problem at hand, a suggestion would be to always close 
the composer on CTRL+Q, since it seems to be a stand-alone application.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

signature.asc
Description: This is a digitally signed message part.

_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability