8

Currently, the system is largely in favor of voting to close a question, rather than leaving it open, for two main reasons:

  1. There is a "close" button on question posts, but no "leave open" directly available. If you feel a question must be left open, you need to go to the review queue (this is apparently "by design" - see this old post, but it is not explained why).
  2. There is no way to see the number of "leave open" votes cast, but you can see the number of "close" votes (see this other post).

The problem is, I often see questions that are initially wrongly formulated and look like off-topic question (typically, let's say, a shopping question - I'm primarily active on the electrical engineering site - that looks like "what chip would do [this thing I need]"). After a few close votes and a few comments indicating it's off-topic, OP edits the post and states he doesn't need a specific IC, but is interested in knowing, more generally, "how can I achieve [this thing I need]". Not off-topic anymore.

Then, from the review queue, users see that close votes have already been cast, read the post too quickly (being biased by the information shown), and cast additional votes and it gets closed. Really. They do that. And I want to scream "read carefully, it's not off-topic anymore"!

Leaving a comment does not work. I tried it a few times, it gets buried, and, if there were already a few comments posted, it is not even shown by default.

The most consistent way to solve this would probably be to show a "leave open" button at the bottom of posts for which there are close votes, and indicate the number "leave open" votes cast, like for "close". This would make the reviewers stop a bit before clicking "close", since there is not a single obvious path to follow anymore.

But maybe there are other ways, like clearly indicating that the post has been edited after close votes have started being cast.

How could we better balance "leave open" and "close" voting?

5
  • 3
    There is a "close" button on question posts, but no "leave open" directly available - because doing nothing (which is easier than clicking "close") means exactly that, no?
    – Oded
    Jan 24, 2017 at 10:07
  • 1
    @Oded But I thought clicking "leave open" from review actually did something. Like if there is three such votes, the post is not shown in review anymore, which discourages additional close votes. Am I wrong?
    – dim
    Jan 24, 2017 at 10:10
  • 1
    Well, I was responding to your point about the link on the post itself in the question page, not the review queues. In the review queues it does have meaning.
    – Oded
    Jan 24, 2017 at 10:12
  • Then, to make it clearer, I assumed this hypothetical button to have the same behavior as from review. So, now, maybe the label should express something more clear, but that is another matter.
    – dim
    Jan 24, 2017 at 10:14
  • 2
    If we do this, then why not replicate the whole review queue UI in the question page? The review queue UI is separate for a reason - lets keep it that way. The point of "keep open" in the review queue is to counteract someone voting to close - that's how questions get on to the queue, after all.
    – Oded
    Jan 24, 2017 at 10:22

2 Answers 2

2

This would make the reviewers stop a bit before clicking "close", since there is not a single obvious path to follow anymore.

I never vote to close a question because someone else did, so the number of close votes is totally meaningless to me. It merely indicates the status of the question at this moment.

Hiding that number or showing a secondary (functionally meaningless) number next to it to indicate the number of uses who wanted to keep it open doesn't help a bit in my decision to close it or not. If you want the secondary number to be actually functional: that is already declined here.

8
  • 3
    "I never vote to close a question because someone else did". This is what everybody should do. I can guarantee this is not what everybody does.
    – dim
    Jan 24, 2017 at 10:11
  • 1
    So why do you think that secondary number changes that? Jan 24, 2017 at 10:13
  • 3
    Because if people are currently biased by the number of close votes (which they are), they will also be biased by the number of "leave open" votes, and it will balance itself.
    – dim
    Jan 24, 2017 at 10:15
  • 2
    You think they are biased. Jan 24, 2017 at 10:21
  • 1
    "Leave open" votes aren't functionally meaningless; they don't directly counteract close votes but they do kick a post out of review
    – Cai
    Jan 24, 2017 at 10:57
  • Hey, you didn't have to delete that other answer of yours just because the downvotes, IMO it's totally fine and sometimes even good to have two different opinions. Unless you changed your mind about the idea itself? Jan 24, 2017 at 15:33
  • Basically it was the same answer, but I guess they didn't like my proposition, which is okay by me. Ah well, let's undelete it @Sha Jan 24, 2017 at 15:34
  • Hmm... on first and second look your answer appears as "no, it's not fine to have it", takes a third reading to get this is just your personal preference so you don't actually say "no, it's not fine to have it". Well, still worth keeping in my opinion. :) Jan 24, 2017 at 15:37
2

I largely agree with your analysis. The "pile-on" of close votes can get particularly impactful now, as some stacks are moving to a 3-votes-to-close system.

Not showing the number of close votes on the questions would mean viewers are making completely independent choices about close votes. Problems with doing that are that questioners would then need a mechanism to see whether their questions are attracting close votes (a real issue), and that the info would be available through the question timeline and, of course, the review queue (not a real issue, as those aren't likely to cause the impromptu pile-ons we're talking about)

2
  • Is there any evidence these... "pile-on" scenarios are largely resulting in invalid closures? I'd assume not... given there's also likely no real evidence of "pile-on" close voting existing.
    – Kevin B
    Jul 12, 2022 at 18:22
  • 1
    @KevinB. I'm not going to go gather evidence, but will suggest instead that this will vary by stack. There are certainly high volume stacks with a high noise content that need fast closes. These aren't the sites with a problem. Jul 12, 2022 at 19:35

You must log in to answer this question.

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