Timeline for Let's not close fixable posts without explanation
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 21, 2019 at 0:01 | history | edited | CommunityBot | | |
| Aug 21, 2019 at 14:44 | comment | added | IEatBagels | @rolfl I meant questions that aren't a total mess that show no effort. I also disagree regarding the close reasons, the messages are very generic (so much that there is frequent confusion between "Unclear what you're asking" and "Lacks concrete context") and the comments user can add to explain why they VTC are usually much clearer in what needs to be fixed so that the post can be reopened. Also, especially for new users, I think it's better if they can fix their post before it is closed, because afterwards they may not bother doing it. | |
| Aug 20, 2019 at 11:05 | comment | added | Simon Forsberg | You are not the only one who has noticed this. It's been an increasing problem recently, I feel, and I'm glad that someone else brings up the topic on meta. | |
| Aug 20, 2019 at 10:59 | history | edited | Simon Forsberg | edited tags | |
| Aug 16, 2019 at 12:04 | comment | added | rolfl Mod | In your assessment, what does fixable mean? I agree that posts with easily fixable issues may need a comment, but in general, the close reason itself should be good enough, right? | |
| Aug 16, 2019 at 5:33 | comment | added | Martin R | Just mentioning that there is a list of Frequently Posted Comments on Meta, and Code Review Copy-Paste (compiled by Phrancis). They contain a list of canned comments which can be used for many off-topic questions. | |
| Aug 15, 2019 at 21:24 | answer | added | dfhwze | timeline score: 5 | |
| Aug 15, 2019 at 16:03 | comment | added | IEatBagels | @Mast I agree it should be the first reviewer, but if that person doesn't do it, the responsibility falls on the next reviewer IMO | |
| Aug 15, 2019 at 15:49 | comment | added | Mast Mod | And no, you're not the only one who has noticed. And when comments are left, some of them are next-to-useless. It could all be better. Although, honestly, with the blatantly off-topic ones I often don't even bother either. | |
| Aug 15, 2019 at 15:47 | comment | added | Mast Mod | "but out of 4 reviewers at least one of us should make the effort" actually the one who gets it into the review queue (first one to vote/flag) should leave the comment. | |
| Aug 15, 2019 at 15:00 | history | tweeted | twitter.com/StackCodeReview/status/1162016202622943233 | ||
| Aug 15, 2019 at 14:44 | comment | added | Peilonrayz Mod | Possibly related: one, two - should help us find similar questions. | |
| Aug 15, 2019 at 14:36 | history | edited | Vogel612Mod | edited tags | |
| Aug 15, 2019 at 14:29 | history | edited | IEatBagels | CC BY-SA 4.0 | added 77 characters in body |
| Aug 15, 2019 at 14:28 | comment | added | IEatBagels | @Peilonrayz Ehm that's embarrassing, I searched for the post in question because I remembered something about a post like this some day, but it seems like that that post might not exist.. I "hope" that the meta post will at least drag attention of some of the close voters, but indeed it's not like meta is read by that many people | |
| Aug 15, 2019 at 14:22 | comment | added | Peilonrayz Mod | "I know there's already been meta posts about this", do you have any links, so we can possibly explore old solutions - if there were any - and focus on how to fix this issue. However I wouldn't count on much, I don't think I've solved anything generic by ever coming to meta. | |
| Aug 15, 2019 at 14:15 | history | asked | IEatBagels | CC BY-SA 4.0 |