User:Floquenbeam/Recall
Getting rid of Floquenbeam - a how-to guide
[edit] | I guess this process is in flux, until a replacement for RFCU is found. You can choose between having an RFCU anyway, even though the process is deprecated (I won't hide behind the fact that it's been deprecated to weasel out of it), or a widely publicized discussion on a page in my user space, or a subpage at AN or ANI. Until I settle on something and put it here, it's your choice. --Floquenbeam (talk) 12:20, 9 December 2014 (UTC) |
The basic theory
[edit]If you believe I should no longer be an admin, discuss the problem with me first. If, after the discussion, you still feel I should not be an admin, file a normal WP:RFC/U or WP:RFC/ADMIN[1], and list as one of the desired outcomes that I resign my adminship[2]. If more than four editors in good standing[3] clearly support that outcome, I'll stop using any admin tools until the end of the RFC. If, at the end of the RFC, there's no consensus among editors in good standing for me to remain an admin, I'll resign[4]. No ArbCom case required. If I ever want to attempt to regain adminship, it will be via a new RFA. --Floquenbeam (talk) 22:05, 29 September 2011 (UTC)
A few details
[edit]- Since recall is voluntary, I reserve the right to modify this if I think I can improve it. But I promise not to fiddle with it if it appears a recall attempt is imminent.
- Since it is not unheard of to game a recall [link to a specific admin not included here to prevent drama]: to the extent that a bureaucrat is actually willing to do this, I authorize and request that any bureaucrat who thinks I'm not following this procedure in good faith go ahead and remove the admin bit without an RFC. If Future Me has sunk so low that I'd cheat to keep the bit, then Current Me doesn't want it.
The fine print
[edit]- ^ (following the normal rules and procedures for RFC's regarding certification, etc.)
- ^ The RFC does not have to be about my misuse of the admin tools; if I've lost your trust though non-admin behavior, that's a reasonable reason too.
- ^ "Editor in good standing" defined using what appears to be the de facto standard in these things: 500 edits outside their user space, and not currently blocked.
- ^ If there is no consensus, I'll still resign. If there's any dispute about whether there's a consensus or not (a meta-consensus, if you will), we can beg a bureaucrat to make the call; that's part of their job anyway.