Timeline for Why is there suddenly a flood of Close votes in the review queue?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 26, 2017 at 14:03 | history | edited | ale | CC BY-SA 3.0 |
added 205 characters in body
|
| Dec 25, 2017 at 18:10 | history | tweeted | twitter.com/StackWebApps/status/945356036784914437 | ||
| Dec 23, 2017 at 6:19 | comment | added | Andrew T. | Just a bystander, but could you provide some links to these reviews for examples? I don't have enough rep to review close votes, but reading pnuts' comment above, I'm afraid there's a misunderstanding because you mentioned that "there are upvotes and multiple answers". | |
| Dec 21, 2017 at 22:37 | answer | added | ChrisFMod | timeline score: 7 | |
| Dec 21, 2017 at 20:43 | comment | added | jonsca Mod | @pnuts ?? It's a useful close reason, it's just not meant to be a "catch all" as you have coined it. When I had asked people to use prefab close reasons, it was to keep better track of things such as the number of web development questions that were being asked rather than to abolish custom close reasons entirely. | |
| Dec 21, 2017 at 15:59 | comment | added | jonsca Mod | We're getting slightly more participation in the queues, which is good, but I'd love it it more people got involved with it to help democratize the situation you've mentioned. I'd prefer to get myself out of the queue almost completely, but that hasn't been feasible in 4+ years. | |
| Dec 21, 2017 at 15:56 | comment | added | jonsca Mod | I agree that this is pointless. Asking for clarification on ancient questions and then VTCing because that information is not given is not productive. | |
| Dec 21, 2017 at 13:06 | history | asked | ale | CC BY-SA 3.0 |