Timeline for Close the loop on "Too Broad"; make the close reason's actual intent reflected in its message
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:36 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Mar 20, 2017 at 10:31 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Mar 20, 2017 at 9:43 | history | edited | CommunityBot |
replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/
|
|
| Mar 3, 2017 at 17:03 | history | migrated | from meta.stackoverflow.com (revisions) | ||
| May 26, 2016 at 21:43 | comment | added | TylerH | I'm not crazy about the tutorial message, but it could conveniently link to our Documentation site once that's out of beta. | |
| May 26, 2016 at 19:34 | comment | added | Martin Verjans | I like the idea of "It's the first time you ask on this tag, do you want to get a tutorial ?" | |
| May 26, 2016 at 19:13 | comment | added | Makoto | My counterargument to your point being made (which is still valid) is that the closure is intended to help save those questions which are worth saving anyway; you'll never be able to redeem someone who asks if they can ask a question about "where to start" and think that it'd be welcomed warmly or that this sort of question could be "improved". I do wonder if "concisely focused" is enough to curb "where do I start"-type questions, but perhaps more wordsmithing is required... | |
| May 26, 2016 at 18:30 | history | answered | brichins | CC BY-SA 3.0 |