Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate actions, if any, that should be taken in regard to the change in close votes threshold #33

Open
Zvax opened this issue Dec 4, 2019 · 4 comments
Labels
GitHub Discussion This needs refinement prior to being appropriate for a room meeting topic. Discuss/refine it here. Monitor issue Issue should be monitored and more data collected prior to being suitable for a room meeting.

Comments

@Zvax
Copy link

Zvax commented Dec 4, 2019

SO is lowering the votes threshold to close and reopen questions.

As an obvious effect, it is now easier to close questions. It is common to post cv-pls requests in the SOCVR. These together, might mean that there is now a very potent effect to posting cv-pls requests, and it's possible but not necessary that changes in policy be needed?

There was already some discussion about it in chat (message from TylerH):

@NathanOliver-ReinstateMonica @chipster Yeah; no change should be necessary for the room at least for a week or so. The queue should start to drop a bit, though, and eventually the room will thin out too re: outstanding requests. But we'll still probably run out of CVs as frequently. Currently we tend to have more requests than can be fulfilled in a given day.

The goal of this issue is that this topic be brought to the attention of the meeting, not to imply that any change should be undertaken.

@machavity machavity added the suggested-topic This is a topic being suggested for a future room meeting. label Dec 4, 2019
@ComputerBytez
Copy link

Ugh. Beat me to it :D . Note that there has been some more discussion about it other than the message you linked to, but that is easy to find in the transcript as it happened around the time the message you linked to was posted.

I've already given my 2 cents (I'm Chipster, btw. I'm sure that's not very apparent from my Github username), but I will say again that I think we should wait a bit to discuss this until the effects (if any) on room operations is more apparent. However, we don't really know when a room meeting will take place, and it'd probably be good to not forget about it.

@Tyler-H
Copy link

Tyler-H commented May 18, 2020

As part of this, we should touch on the "recent activity" rule #12 and whether it is still needed now that questions are more quickly closed due to the 3CV change. See the beginning of a short conversation on it here: https://chat.stackoverflow.com/transcript/message/49408500#49408500

@makyen
Copy link

makyen commented May 19, 2020

The definition of "recent activity" has been updated to mean within the last 6 months. This should give us more information as to what level of requests we'll be getting with that particular requirement relaxed.

@codygray
Copy link

I think the room over the past several months has been doing exceptionally well in keeping up with requests. The backlog seems small, and most of the requests that do not get actioned seem to be cases where reviewers aren't sure closure is even appropriate.

However, I'm not sure to what extent the room's recent ability to keep up with requests is due to the threshold being lowered to 3, or a certain moderator who visits the room and hammers all the things.

@makyen makyen added GitHub Discussion This needs refinement prior to being appropriate for a room meeting topic. Discuss/refine it here. Monitor issue Issue should be monitored and more data collected prior to being suitable for a room meeting. and removed suggested-topic This is a topic being suggested for a future room meeting. labels Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GitHub Discussion This needs refinement prior to being appropriate for a room meeting topic. Discuss/refine it here. Monitor issue Issue should be monitored and more data collected prior to being suitable for a room meeting.
Development

No branches or pull requests

6 participants