Board Thread:Community Discussions/@comment-26908198-20150727013747/@comment-26047195-20150727150754

Derpulse wrote: Luke McSwagger99 wrote: For Fortress, Vonness, and whoever else would be concerned with an overload of votes:

If this idea were to come into effect, then I would propose that we do the RfR voting in pieces. Doing revotes for 20 or so CM's at a time would be highly impractical, and users would be annoyed to the point where they would hardly care to put time into thoughtful votes or to vote at all. My suggestion would be that we arrange it in a way where only 3 CM votes are done together for a 48-hour segment. After that segment, we would move on to another batch of 3 CM's to vote on. This way, the process would be spread out over about 2 weeks of time. Not only would we avoid having an overload of votes, but we also wouldn't have issues with losing a handful of CM's at once should there be many opposes. Lol what happened  to every vote must last 5 days The policy states that:

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.

The "48 hour segment" thing was just a suggestion that I personally would find practical for the situation. This vote will soon establish for us a minimum of time before RfR's can close due to the reasons that normally cause them to end before 5 days' time which I have just mentioned.