4 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Copied from http://meta.stackexchange.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queueReduce the number of reviews needed to complete an item in the CV queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stata stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

Copied from http://meta.stackexchange.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

Copied from Reduce the number of reviews needed to complete an item in the CV queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

3 Migration of MSO links to MSE links
source | link

Copied from http://meta.stackoverflow.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queuehttp://meta.stackexchange.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stata stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

Copied from http://meta.stackoverflow.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

Copied from http://meta.stackexchange.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

    Post Made Community Wiki by Matt
2 added 161 characters in body
source | link

Copied from http://meta.stackoverflow.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

Copied from http://meta.stackoverflow.com/questions/208563/reduce-the-number-of-reviews-needed-to-complete-an-item-in-the-cv-queue


There are currently 95.3k items in the Close Vote queue, and 2 items in the Reopen Votes queue.

The number of reviews needed to close a question from the CV queue is 5, which is ridiculously high. Here's a stat:

In the past 90 days, 46,506 close flags have been processed; 45,707 were marked as "helpful" (resulted in at least one close vote) and 34,000 have resulted in questions being closed.

That's 73% accuracy from <3k users flagging; i.e. the people we believe to be least-able to recognise a close-worthly question are already getting 3/4 of them right... do we really need a further 5 >3k users to back them up?


Here's my actual :

Let's find a number n, such that requiring only n reviews to end a review results in the same action being taken as requiring 5 reviews, y% of the time.

If we require only 3 reviews instead of 5, and we end up with the same outcome 95/90% of the time as we would do using 5 reviewers, why aren't we doing that already? Yes, I just made those numbers up. Shog help me..


For those that are dubious as to whether this would open the floor for questions wrongly getting closed, let me calm you down with this;

  • Firstly, don't forget that we have the ability to "Vote not to Close" in the review queue. In the normal question view we don't have this. This is why the bar to close can be lower inside the queue than it is out of it, because people can vote for both sides.

  • Secondly, my feature-request is not too different to how we already handle the Suggested Edits queue, and a wrong suggested edit is just as reversible as a incorrectly closed question. Hell, we even have a re-open queue; and it's empty. Let's use it.

If you're still struggling, then how about I knock you clean out by suggesting we add the ability to flag a question for reopening. This would force the question into the reopen queue, and handle the small percentage of questions that incorrectly get closed. It would also allieviate a proportion of the flags moderators have to deal with at the moment. If we're worried about the question-owner spamming the flagging option, only enable it for non-owners.

1
source | link