Re: How to deal with unwilling devs?

Markus wrote:
> Yes, I made a mistake by selecting "Kontact". I thought that this means 
> KDEPIM 
> overall.
> However, KMail is obviously also wrong. Why did that guy change it to KMail 
> when at the same time he writes that it is independent from KMail?

"That guy" has a name. It's Christophe Giboudeaux.

While Composer is standalone, it's part of the KMail
codebase, and there's no separate product for it in
Bugzilla, so changing it to KMail was correct as the
issue pertains to the KMail codebase and Bugzilla
product.


> I never denied that. The issue is obviously more complex, but not invalid as 
> said by the bug report.

The reason the report is invalid is because rather
than reacting to Christophe's statements about the
nature of the Composer and making a constructive
debate of it, you presented your - underinformed -
stance as authoritative. Christophe was expecting
dialogue and got a summons. IOW, the problem, much
like what you display here by writing "that guy",
is your unfriendly and arrogant attitude. Posting
"How to deal with unwilling devs?" here after the
display in the bug report left me speechless for
quite a while. Fix your manners, and you're likely
to get further next time.


As for the actual issue, what it boils down to
is whether to spend effort on trying to wire
things up in such a way that Ctrl+Q in Composer
quits Kontact/KMail when it was opened from those
and otherwise Compose when it's being run stand-
alone. And if the answer to that is yes, how it
can actually be realized on a tech level.


-- 
Regards,
Eike Hein, hein@xxxxxxx
_______________________________________________
kde-usability mailing list
kde-usability@xxxxxxx
https://mail.kde.org/mailman/listinfo/kde-usability