Timeline for answer to Could we have a reduced close vote requirement on "why isn't this code working"? by Reto Koradi
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 9, 2014 at 15:39 | comment | added | chrylis -cautiouslyoptimistic- | Disagree with the analysis. "Not enough information" is a lot more objective and specific than "too broad" or "opinion-based". | |
| Sep 9, 2014 at 6:11 | comment | added | Reto Koradi | @CodyGray: That's not exactly what I wrote. My main point was that doing this for only one specific close reason was arbitrary, and that there should be a broader discussion about the special powers of gold tag badge holders. Allowing them to close for all the provided reasons would be one option. | |
| Sep 8, 2014 at 6:40 | comment | added | Cody Gray Mod |
I read your answer as advocating for giving gold tag badge holders the ability to close questions for any of the canned reasons. Please post that as a new [feature-request] so that I may upvote it.
|
|
| Sep 8, 2014 at 4:28 | comment | added | Makoto | I'd counter that with saying that the idea behind close-as-duplicate was to provide question askers with a valid answer to their question (which had been asked already on the site). I view this proposal in the same way; it brings askers who don't post a lot of details to their question in line with what we want to see on the site. You could certainly argue that the trend is what you describe, and from an outside view, you're probably right. But, I'd like to give this privilege to a group of users that could be trusted. Doesn't have to be gold tag owners. | |
| Sep 7, 2014 at 19:06 | history | answered | Reto Koradi | CC BY-SA 3.0 |