Timeline for Please Remove "Bug Report" Close
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 14:35 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 31, 2014 at 13:51 | comment | added | Braiam | That's a poor example that you have selected. Through the first instance was a bug in Natty (which was also shared with Debian) it can have other causes that are not bugs, well, they are technically bugs in the mirrors the users are using and they should fix it. I've searched instances where this happen in anything but Ubuntu repositories, and I've found that my observations are correct. You think the experts that answers questions should answer them instead of doing something more meaningful? You will drive them away. And how about if the bug isn't reported "yet". What will you answer? | |
| Mar 31, 2014 at 13:48 | comment | added | Oli Mod | A quick Data.SE query shows the view count it's closer to 200,000. That's not an infallible number by any stretch (and this is rather a extreme example) but this is why I'm saying everything I'm saying about this. Reason over rules. | |
| Mar 31, 2014 at 13:27 | comment | added | Oli Mod | And yet there are at least 100,000 views on MergeList and its duplicates. A bug answered my way that both provides a workaround and pushes the user in the right direction. If that answer didn't exist, how many of those 100,000 views would be yet another duplicate asking? And yes, duplicates are better than off-topic because they hang around and push the next person in the right direction. | |
| Mar 31, 2014 at 13:07 | comment | added | Braiam | Oh come on, the amount of duplicates tells you that people isn't finding what they are looking for. We should stop with that madness, and tell the how-to do stuff or why's it happens. Bugs be kept in bugs trackers as our rules and several other meta Q's says very clear. Why you want go against the consensus? It's categorically said in the help center that "This is not the right place for: ... Bug reports". If you want to be helpful, write a custom close reason pointing to the bug report or just leave a comment. Why anyone should answer what shouldn't be asked here in first place? | |
| Mar 31, 2014 at 12:55 | comment | added | Oli Mod | Why do we need to do something with the question? By all means update the answer to say "This was fixed in vX.Y and should be in 14.04" but there's no need to do anything with the question. People who need it will find it and people who don't, wont. | |
| Mar 31, 2014 at 10:57 | comment | added | Braiam | Ok, once it gets fixed, what you think we do to the question? | |
| Mar 31, 2014 at 7:30 | comment | added | Oli Mod | Which is why we still link to the bug report so they can see how current things are. I've been over the "why answer" before but it essentially boils down to: If we can answer once well, of the next hundred people with the same problem, we can dupe-close 50 against the one answered one and the other 50 will —by the power of Grayskull— find one of the 51 existing and closed versions not need to ask again. This isn't something we can hope people stop posting completely (cite: Mergelist) so let's just deal with them in the most productive way possible (allowing that things still happen on LP). | |
| Mar 30, 2014 at 14:24 | comment | added | Braiam | I don't think we should answer them, a simple comment and closing is more appropriated. That will prevent real bugs from even entering the system and go directly to LaunchPad where people that can fix it, will fix it once and for all. Also, answering bugs will confuse users that will find a 3 yrs old question about a problem which resulted to be a "bug" and the report fixed, since it will make them believe they have the same problem when it could be a regression or another bug altogether. We are not to fix only OP problem, but answer questions that rest of the internet will find helpful. | |
| Mar 30, 2014 at 10:30 | history | answered | OliMod | CC BY-SA 3.0 |