Board Thread:Community Discussions/@comment-26047195-20150723034158

So I've felt with some CM RfR's, especially with some recent ones, that they suddenly gain too many hasty supports (oftentimes due to manipulative advertising) and end all too soon without giving some users enough time to reconsider their vote, or for other users to notice the request and submit their vote. Take note of what the policy currently states:


 * The duration of a request may not exceed 10 days, and should usually last at least 5 days. A request must have a clear consensus in order to be closed prior to 10 days.
 * A request is not required to last 5 days if the following requirements are met:
 * If the request has 10 or more oppositions, with at least a 75% majority oppose.
 * If the request has the required number of supporting votes (listed below), and at least an 85% majority support.




 * For a request to pass, the candidate must have at least 25 supporting votes, with at least 75% support out of the total supporting and opposing votes.

I see several RfR's come and go in a matter of /hours/, simply because they hit 20-ish supports before 3 or more opposes get in. Support reasons are blunt and lacking in significant reason for supporting, and a good handful of users, admins included, don't even get to provide their say in the matter if they didn't get on that day. We shouldn't want to make hasty decisions, especially decisions placing people in positions of authority. For this reason I propose that we place a 48-hour minimum closing requisite on RfR's to ensure that well-thought-out votes will be cast, and that more members of the community will be able to submit their opinions on the request. If it hasn't been clear enough already, my proposition is that:

'''A RfR must be open for a minimum of 48 hours before closing due to majority of supporting or opposing votes. '''

Share your thoughts on the matter and stay civil about it, /please/.  