User:Nosebagbear/Recall

This page details the Recall methodology for my (Nosebagbear's) administrator userrights.

I agreed to recall during my RfA, which would then be followed by a Community discussion of several recall methods. All were firmly denied for myriad issues. This somewhat had the effect of discouraging me, having highlighted potential flaws. Nevertheless, I've attempted to create a method that includes some safeguards. This means it is more complicated than some recall criteria, but far less than others. Given how serious being recalled is for me, I hope that you are willing to concede some reading and some rules a fair trade.

This option is in addition to alternate desysop routes, including ARBCOM and any standard community-recall method.

Triggering

 * Triggering the recall process can be done by 10 individuals signing their names below.
 * Editors must meet the following criteria:
 * Have 1000 edits and have an account at least 6 months old
 * Never have undertaken paid editing
 * Never have been blocked (either directly or as part of an ANI discussion) by me, except where such blocks were overturned as bad blocks
 * Not have been blocked in the last year, or received an ANI/AE/Arbcom warning or admonishment in the previous 6 months. Warnings issued by an individual editor are not an impediment.


 * Editors must provide a reason(s) that they, or another individual, have discussed with me in good faith beforehand. The reason must have occurred within the previous 3 months.

Alternate resolution limitations

 * A reason that is discussed on a proper Community board and decides an (in)action was specifically correct will not be accepted.
 * A reason (including any combination raised in evidence) that is discussed by ARBCOM will be taken as a final judgement. In effect, ARBCOM overrules the recall process, so if they decide I was at fault, but only to the tune of an admonition, can't then be submitted again as a Recall trigger (unless I do something else, in which case obviously editors are completely free to consider a "net weight" issue).
 * In progress ARBCOM cases must conclude before Recall is triggered, but any time-limits will be "tolled".

Recall Process

 * If the criteria are met (or if I think they're clearly going to be met), I will do one of the following within 10 days:
 * Resign (under a cloud)
 * Submit to a desysop RfA as created by a community consideration, should such a method exist at the time, using whatever criteria are standard.
 * Submit to a Recall RfA - decided under the usual criteria for passing an RfA
 * Set-up a "Recall RfC", most likely at AN - a consensus to remove would trigger my resignation
 * Request an Arbcom case into my actions - this has been considered but not executed before, but should it appear possible I reserve the right to "trial by court martial".

Should I attempt to use a method, and it not prove viable (e.g. ARBCOM refusing to hear a case), then another method will be selected within 72 hours.

Misc

 * If a signature has been there a month, and 10 signatures haven't been reached, it will be removed.
 * I will endeavour to find several individuals who can "clerk" an RfC, preferably admins or arbcom clerks who I do not have either a particularly close or negative link with.
 * Reasons must be based purely off on-wiki visible community discussions.

Amendments

 * Except as required by policy changes, any amendment to reduce the scope of this recall will be posted to WP:AN and will take effect 30 days later. Any individuals currently having requested recall will be notified about the proposal by a ping.
 * Any amendment to expand the scope (e.g. lowering the number of editors required for listing) can be made immediately.