http://bugs.winehq.org/show_bug.cgi?id=21736
--- Comment #17 from Robert H. Dinah rhdinah@yahoo.com 2011-11-30 11:32:19 CST --- (In reply to comment #16)
(In reply to comment #15)
Remember this is WINE's bug, not mine ... it was submitted in good faith ... on my time and at my expense ... ignoring bugs does not fix them ... true? It was not submitted because I needed a fix ... it was submitted to improve the code ... your code ...
We aren't ignoring it. We asked you to retest it, you didn't, then you badmouthed us when we said you weren't responsive. You followed up with an ad hominem attack. If you're trolling, it's succeeding. If we've lost a friend, well, you haven't shown any friendliness here.
We aren't ignoring it.
And I quote: "Closing. No need to reopen. It will be ignored anyway. Consider this your refund."
We asked you to retest it, you didn't
Yes and no ... true I didn't test it with a development version, because I didn't wish to corrupt my machine with sub-alpha code ... as I mentioned I use my machine in my work. However I DID TEST IT on each and every new production release of WINE ... and it never worked ... and the request did not say to report back the results. In my eyes testing with a development release for something as simple as a keyboard accelerator ... when clearly it wasn't being addressed all along ... made it appear to put the onus back on me ... which created frustration. In development shops I've worked it was never the responsibility of the bug submitter to test or debug his bug. Of course when I was assigned a bug that was particularly difficult to reproduce I would engage the submitter to reproduce the bug so that I could do so in like manner at my desk as a developer. And that is the reason for my statement: "It is difficult for me to understand the underpinnings and mentality of WINE's quality assurance procedures".
When my manager asked me to test something I would. If he asked me to report back by some time I would. Otherwise I'd not bother him in his busy day unless he specifically asked me what happened on the test.
then you badmouthed us when we said you weren't responsive.
No I "badmouthed" you when for apparently no reason the words "non-responsive" and "abandoned" came out the middle of nowhere in my email ... without a previous kind message to me of any potential status that I may have observed. Should the team have asked me to test code with specific debugging code addressing this bug I would have created a test machine to do so gladly. Had they asked and delivered development code to me with debugging symbols in it I would have attempted to debug it for you. Since I am a Windows and Unix developer myself this would have been easy, however, like you all I am a very busy person. [sigh ... why am I writing this?]
"If you're trolling"
Name calling is not nice.
"Other then rant your comment 4 contained no useful information whatsoever."
Agreed, but the tone of this is not nice.
"Adding a comment to the bug is enough, don't change an originally reported
Wine version. Please read once again comment #5, and follow the request there."
IMHO what I consider a properly made polite statement.
"If you are not happy with the service, feel free to ask for a refund."
An overused, shameful and insulting statement ... especially considering who made it.
"you haven't shown any friendliness here"
Looking back on the thread I concur ... most of them were made in frustration ... should this have insulted your team ... I apologize ... however as documented above ... and again looking back on the thread ... neither does the WINE team.
One more thing, please:
"You should probably check who you telling this to."
If Jesus or God had spoken to me I would have known it AND they would have told me they were Jesus or God. Other people because of their status don't impress me and I certainly don't raise them up and onto a pedestal. Nevertheless I still would invite, expect and return intelligent, polite conversation and due respect.