http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #5 from Anastasius Focht focht@gmx.net 2008-03-16 07:51:27 --- Hello,
it seems I have caused some discussion with my comments [ironic sic!]. I'm not subscribed to any mailing list at all but I do read them sometimes ...
I don't like backstabbing talk so let's just clear things up here - although bugzilla is the wrong place for this (no, I won't subscribe).
To english readers: the german comment "Wenn ich sowas lese, vergeht mir echt die Lust ..." can be literally translated to "When I read such things, the joy of continuing my work is declining".
First: I'm not a wine developer at all (by definition). I'm a software engineer/expert who happens to be attracted by various problems/challenges surrounding the wine project. My goals/intentions are different from the majority of wine users/developers.
I usually have a rather stressful 10 hour job which differs from the work here (customers demanding quality software solutions for their problems). When I find some time in the evening or on weekends, I spend my already limited spare time on tracking down interesting problems/bugs which sometimes require a lot of knowledge and experience.
You might have seen me on various bugzilla reports, commenting/explaining issues, offering workarounds/fixes. See, I put considerable work into this: endless debugging sessions, writing analysis, offering solutions - frankly speaking: heart and soul.
That are several cases where only few people can actually judge the amount of work that is needed to solve specific problems. In fact if you see various patches/workarounds they might look easy at first glance but until you get there, many obstacles had to be overcome.
Granted, you might not understand the specific problems/explanations/issues regarding the bugs at all. That's ok because they are usually aimed at developers or for my own documenting purposes. On several occurrances, I even need to defend my findings/conclusions a second, a third time, putting additional hours into because the problem/fix might not be that obvious at all (hard to verify).
I wrote this analysis after the usual 10 hour work day and additional hours devoted to various projects of my interest. You frankly dismissed my writeup with "No, XP config doesn't work" and "Is this patch useful at all?" after putting the usual heart and soul into this ... I felt attacked, my work degraded.
I've experienced this several times, users make the *same* obvious errors again and again, working an tainted ~/.wine, not specifying combination of native overrides (guesswork), using old wine version and so on. Do you actually can imagine how much additional time I waste sometimes to verify my work over and over again because of such "false positive" reports? This time is lost for no good.
But even then I try to act polite, pointing out the obvious errors (see that .NET 2.0 bug, where the user actually admitted his fault, congratulating the wine people). I can understand people like Vitaly Margolen who was constantly working in this area of conflict, overreacting sometimes.
You seem to be a regular user contributor with a certain level of experience on how to file bug reports, testing bugs/patches with new releases, giving feedback. I don't expect you to understand the problem at all but I expect some level of professionalism which follows the *basic* wine guidelines.
If you actually felt attacked I apologize. Though I don't really see any abusive tone when re-reading my post, maybe I should explicitly add "irony" tags next time. But again: the joy of solving riddles is actually one of the main reasons I stayed here for some time. Don't make the joy go away...
Regards