Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 153 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Throughout the network, one of the biggest complaints is that questions that should stay open are getting closed and once they are closed they are too difficult to reopen. Personally I don't agree with that, but I see it often.

Even if you don't necessarily agree with that, it seems like a lot of people aren't 100% happy with he way close voting works. So here is my proposal:

We should be able to vote to close the same way we vote on questions and answers. There should be an upvote and a downvote (or something similar) and a question should only be closed (or put "on hold") if there is a NET total of 5 negative votes. Basically a user should be able to "cancel out" another user's close vote before the question gets closed. This way border-line questions don't get closed too quickly, if at all.

This isn't a very detailed idea, but I would like to know what the community thinks about the concept of cancelling downvotes before the question is closed. Thoughts?

share|improve this question
So, if a question continually falls back and forth between 4 and 5, it should constantly keep getting reopened and closed? – animuson Jun 28 '13 at 3:34
@animuson Very likely it would be closed once it reached 5 votes, and need to go through reopening (or achieve a net score of 0) to be reopened. – Emrakul Jun 28 '13 at 3:39
Alternate proposal: 2 votes to close. 200 to reopen. – Anthony Pegram Jun 28 '13 at 3:40
+1 I like the net -5 idea, and a numeric close-vote system (close = down, open = up) has been requested quite a lot already. – michaelb958 Jun 28 '13 at 4:22
@EmrakultheAeonsTorn (This is a different comment because I filled the last one with links and it was ~600 chars!) I agree with posts being stuck closed at -5 until they reach 0 again, if only to prevent flip-flopping as animuson described. – michaelb958 Jun 28 '13 at 4:30
up vote 11 down vote accepted

This idea has come up many, many times before. If you're focused on questions that shouldn't be closed, it's a very appealing notion: it makes it harder to close them.

Of course, it makes it harder to close questions that should be closed too, since even a minority of contrarian voters can increase the number of close-votes needed to close anything. And the truth is, it already takes a lot of work to close most questions.

...which, of course, is the intent. Originally, it was really easy to close questions. If you had the "close" privilege, you just clicked close and... it was closed. No muss, no fuss. Well, except that there was no need for any consensus on why anything should be closed and if you wanted to be an ass about it the system just went ahead and let you. So things got a bit harder and then a bit harder still, and realistically it's now slightly too hard in some scenarios and slightly too easy in others, but for the most part it seems to work (there's another suggestion floating around to scale the number of votes according to active users on a site that might help a bit, but in practice it's usually easier to get a moderator to handle the edge cases).

Point being, it's easy to make it harder to close things: increase the number of votes required, tie that number to the post's score, or views, or age, or whatever. Heck, if we're just concerned about popular questions getting closed, disallow closing anything with a score > 0.

But popularity doesn't necessarily equate to quality or usefulness or connection to the topic of the site. That's why closing (and re-opening) has always been separate from voting, limited to fewer participants with a larger stake in the site and stripped of the normal rules of anonymity that protect normal voters from scrutiny. Turn it into a parallel popularity contest and you might as well just not bother.

Oh, one last thing:

This way border-line questions don't get closed too quickly, if at all.

I believe it's generally more harmful for questions to be closed slowly than quickly. If someone makes a mistake, tell them right away - that way, they can learn from it and do better the next time around. Telling them days or months later doesn't help. Worse yet, if the question collects answers in this time then you're punishing them too. The biggest down-side of the view-based vote aging rule is that it can keep votes hanging around for years; at some point, this starts to just get silly. The close review queue changes should help with this eventually, but we have a rather large backlog to go through first.

share|improve this answer

Sorry, I'm not a fan.

Right now, less than 3,000 users (probably around 2,400 or so) even have the privilege to cast close votes. What you'd expect for a system like that to work is copious amounts of diligent participation. What I'm thinking is that there are users that have this privilege that just don't care, and will vote up/down on whatever they please, which will really skew the voting results.

Second, if a close vote is hotly contested, it can be brought up and discussed on the Meta site - which serves as a way to gain insight into why a question was closed, and give it a chance to be reopened.

Third, if the question is "borderline", what made it borderline in the first place? Wouldn't that, in and of itself, be worth revisiting the quality of the question?

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .