I'd like to take this opportunity to mention the unconsider rules and a recent change to them. The unconsider option becomes available (to janitors) once there are 2 edit votes or 4 keep votes. 2 edit votes are required before a node appears on nodes requiring editing, and presumably the 4 keep votes limit is to discourage unconsidering before a reasonable amount of voting has occurred.
This has had the unfortunate consequence that nodes considered for reaping (which typically get only delete or keep votes) get "stuck" when there are enough keep votes to prevent reaping but not enough to allow unconsider. The rules have now changed to allow unconsider if a node has >= 5 delete votes but too many keeps to be reaped.
I second theorbtwo's concern that these kind of rules are in too many places in the code; they need to be moved to a single source.
In reply to Re: RFD: Raising the number of keep/edit votes needed to prevent a reaping.
by ysth
in thread RFD: Raising the number of keep/edit votes needed to prevent a reaping.
by davido
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |