User:ThatPeskyCommoner/Sandbox 3

Pesky's community de-admin process suggestion

This is probably a bit waffly, I've been awake most of the night mulling over ideas, so bear with me!

I'm seeing a possible process path here, which goes something like this:

Primary steps

 * Have a RfC/Admin process set up (please, easier than an RfC/U, which I found revoltingly user-unfriendly the only time I did it!)


 * Have an "Admin Break" option, which could be either voluntary or compulsory, working a bit like a topic ban, which would prevent admins using admin tools for a set period of time but not result in either permanent desysopping or having to re-run RfA

Process
Stage 1: Initial filer's request is notified on AN to get attention from the entire pool of admins (and others who watch AN)
 * It's there as a link for a week, or until stage 2 is achieved, whichever is the earlier. If stage 2 isn't reached within a week, it dies the death

Stage 2: It's certified by a minimum of two admins and one editor-in-good-standing

Stage 3: It then proceeds a bit like an RfC/U, widely advertised (watchlist notice? Maybe?) for a maximum of two weeks
 * This should include looking at alternatives to de-sysopping

Stage 4: If it seems clear that there's an apparent consensus (maybe reducing the usual bar to a 60/40 split, or something) for desysopping, compulsory Admin Break for a given period, or other possible sanctions (interaction ban, topic ban, etc.), then THAT goes to ArbCom for review and action
 * … at which point ArbCom would have to "take the case" and look at it (no opting out!)
 * ... and they could choose, if there seemed to be genuine concerns about anyone else involved in the RfC/Ad, to do further investigations
 * … but on the whole it would be handled like a motion, not a full case