Not sure that I like this. A proposal that’s 60 hours old should have been processed anyway, and stomping it doesn’t offer a mechanism to expedite that if it hasn’t happened - it still requires an admin to process it. This just means that, in some circumstances, the admin herder will be able to fail proposals that should have passed.

Josh, not sure what you’re talking about - a vetoed or failed proposal should not pass regardless of whether it’s been stomped.

Per Josh. I also don’t see how the Admin Herder can ensure what their supposed to ensure. Either he’s not an Admin and he can’t force other Admins to process the proposal whether he stomps it or not, or he his, and he doesn’t have to Stomp those Proposals to clear the Queue since it can be processed normally along with all older Proposals in the queue.

The Herder can stomp any proposal that’s been vetoed or self-killed. The 60 hours is just the trigger to show that he’s not been doing his job.

Yes, it is possible for a conspiracy of all the admins to force the Herder to not do his job, but I don’t see that happening without some major organization, and bureaucracies tend to break down internal organization by their nature :)

Ah, I mis-read, apologies.

CoV

An admin conspiracy could force /anything/, as CFJs and Proposals to remove it, or to add new admins, would just not be adminned. So saying “this is vulnerable to an admin conspiracy” is pointless.

CoV True, true! Also misread! =)

Symbolic