Timeline for How to respond to a rude bug report?
Current License: CC BY-SA 3.0
41 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2015 at 13:12 | comment | added | bye | Fix the bug. And be very, very grateful you don't work in a more customer-facing job such as a shop, because it's like standing next to a clown-car. There you have to be nice all the time, because the first time you even hint that they're a waste of oxygen they're going to be on to your manager and it'll just make it worse. | |
| Feb 24, 2015 at 12:23 | comment | added | user50236 | respond with the following principle: “It's better to keep your mouth shut and appear stupid than open it and remove all doubt” ― Mark Twain | |
| Feb 24, 2015 at 10:57 | answer | added | gnasher729 | timeline score: 0 | |
| Feb 24, 2015 at 8:05 | answer | added | tsundoku | timeline score: 2 | |
| Feb 24, 2015 at 3:16 | comment | added | BrianH | Gee, I was just going to suggest you try this: xkcd.com/1219 | |
| S Feb 24, 2015 at 0:22 | history | mod moved comments to chat | |||
| S Feb 24, 2015 at 0:22 | comment | added | user28988 | Comments are not for extended discussion; this conversation has been moved to chat. | |
| Feb 23, 2015 at 19:50 | answer | added | DoubleDouble | timeline score: 1 | |
| Feb 23, 2015 at 18:21 | comment | added | o0'. | Ask him if the caps-lock was already broken, or if this only happens when your application is running. | |
| Feb 23, 2015 at 14:08 | comment | added | aioobe | It's not an open source project though. | |
| Feb 23, 2015 at 13:59 | comment | added | Basile Starynkevitch | @StefanoSanfilippo: the OP mentions that the user is a CS student, so he is definitely qualified (a priori) to propose a patch! | |
| Feb 23, 2015 at 13:55 | comment | added | Stefano Sanfilippo | @BasileStarynkevitch imho the "patch or stfu" mentality of a large number of FOSS projects is what is actually killing them. You can't expect your users to be other than users, unless your projects targets a techinical audience. And even then you should realize that you can't expect other people to do your work. Using a framework and diving in the internals is not the same thing, especially when documentation is lacking. | |
| Feb 23, 2015 at 11:14 | answer | added | Justin | timeline score: 9 | |
| Feb 23, 2015 at 6:43 | comment | added | The111 | @Lilienthal the happy/right question is the best way to prevent spousal arguments. ;-) | |
| Feb 22, 2015 at 19:41 | history | protected | gnat | ||
| Feb 22, 2015 at 18:39 | answer | added | TessellatingHeckler | timeline score: 10 | |
| Feb 22, 2015 at 18:21 | comment | added | phresnel | @MichaelGrant: That would be a pretty nice answer if the software was sold at zero cost. I have to remember that :) | |
| Feb 22, 2015 at 13:51 | comment | added | Bleeding Fingers | fusion.net/story/42057/caps-lock | |
| Feb 22, 2015 at 13:24 | comment | added | aioobe | I'd feel both happy and right if I told the guy that rudeness won't get him far in life... Though I'm not sure it would be appreciated by him or my colleagues :P | |
| Feb 22, 2015 at 13:20 | comment | added | Lilienthal | I feel like I've already used this phrase on stackexchange to the point of triteness but it is once again relevant and good advice: "Would you rather be right, or happy?" | |
| Feb 22, 2015 at 12:53 | answer | added | Volker Siegel | timeline score: 4 | |
| Feb 22, 2015 at 10:11 | comment | added | Steven Lu | @EricLippert Thanks for that link! Great read. Awesome professionalism in the response to the report. I would say that the more serious the bug is, the more that any abusive invective from the bug reporter might be considered tolerable. If the reporter really is such an asshat, it sure wouldn't help you to respond by stooping to his level. | |
| Feb 22, 2015 at 6:13 | comment | added | Paul Draper | In my experience with MongoDB, that bug report is exactly what I would have thought, though it isn't exactly what I would have said. | |
| Feb 22, 2015 at 3:43 | comment | added | Zan Lynx | @EricLippert: That bug report was handled very professionally. Although I agree with the reporter: doing anything with buffers in C without checking values first IS utter plebbery. | |
| Feb 22, 2015 at 2:20 | comment | added | Navin | Fix the bug. You don't need to do anything else. | |
| Feb 22, 2015 at 2:09 | comment | added | Michael Grant | Offer a full refund. | |
| Feb 22, 2015 at 1:12 | answer | added | Be Kind To New Users | timeline score: 24 | |
| Feb 21, 2015 at 23:19 | comment | added | Ellen Spertus | Here's a great recent example of magnanimity: buzzfeed.com/alanwhite/… | |
| Feb 21, 2015 at 23:16 | answer | added | Peter | timeline score: 7 | |
| Feb 21, 2015 at 21:07 | comment | added | gnat | possible duplicate of Customer is “deeply disappointed” in software because of one bug. How to reply? | |
| Feb 21, 2015 at 19:29 | comment | added | user150273 | Fix the bug but respond with a sarcastic remark. | |
| Feb 21, 2015 at 18:30 | review | Close votes | |||
| Feb 24, 2015 at 1:55 | |||||
| Feb 21, 2015 at 18:11 | comment | added | gnat | related: Getting users to write decent and useful bug reports | |
| Feb 21, 2015 at 17:22 | history | tweeted | twitter.com/#!/StackProgrammer/status/569185285197725696 | ||
| Feb 21, 2015 at 16:41 | answer | added | abathur | timeline score: 12 | |
| Feb 21, 2015 at 16:08 | comment | added | Eric Lippert | Observe how this bug report is handled. jira.mongodb.org/browse/PYTHON-532 | |
| Feb 21, 2015 at 15:28 | comment | added | Basile Starynkevitch | If your app is free software, you could suggest the user to propose a patch and contribute to the source code. | |
| Feb 21, 2015 at 15:19 | answer | added | user22815 | timeline score: 69 | |
| Feb 21, 2015 at 15:19 | answer | added | Ross Patterson | timeline score: 1 | |
| Feb 21, 2015 at 13:58 | answer | added | Oded | timeline score: 103 | |
| Feb 21, 2015 at 13:54 | history | asked | aioobe | CC BY-SA 3.0 |