User:Lar/Accountability

To remind me not to take things too seriously around here!

If you have come here to place a request for a re-confirmation of my adminship, please note that, at my discretion,^[1] I will either:

seek community approval of my adminship through a modified RfC; (no consensus == no change) (see separate section for process)
choose to take the matter to ArbCom; (see separate section for process)
resign my powers "under a cloud"^[2] and possibly stand again for adminship at some later date of my choosing; (see separate section for process)

once the "six editors in good standing" count has been met using my own criteria^[3]
and the matter concerns use of my admin powers at this wiki rather than a non-admin editing concern (use the standard dispute resolution mechanisms), a use of CheckUser (use the ombudsman process, or take the matter to the Audit Subcommittee, as appropriate, if standard dispute resolution does not resolve the matter), or actions at another wiki (use the processes at that wiki).

The rest of this page fills out particulars and commits to certain processes in advance so as to reduce ambiguity or the possible perception that I will change the rules as I go along to get the desired outcome.^[4]

Note: This page has a talk page because I value input and feedback on this whole thing. There's some lively discussion there already, and you, gentle reader, are invited to comment as well.

The Recall Petition process

The petition shall operate as follows:

A clerk of my sole choosing, but chosen for ability to be impartial, will be selected by me to make sure that the petition process itself is smooth and that the requirements for petitioners are satisfied.
The petition start time will be constituted as when the first eligible petitioner announces intention to recall by posting on my talk page. Ineligible petitioners (as judged by me) will not start the process unless I choose to waive eligibility for that petitioner. Such waiver shall be binding. If it takes longer than 24 hours to find a clerk and begin the process, the petition start time will be constituted as when the page is created and ready for use.
A page in my user space will be created with sections for certified, unknown, and uncertified petitioners.
If attempts are made to delete the page, I will counter them to the best of my ability within the limits of policy and common practice (one recreate for a summary deletion, then I will work the MfD or DRV process as appropriate to argue for retention)... assistance in arguing the case for retention by those participating would be appreciated, but is not required as a condition of participation in the petition process. Deleting, or arguing for deletion of, the petition page by a petitioner, however, shall cause that petitioner to be disqualified from certification of the petition, unless I explicitly waive that disqualification. If the community ultimately deletes the page and it sticks I don't quite know what to do but will try to be reasonable.
Additional sections may be added as the community desires for comments of whatever sort. These shall have no bearing on the petition outcome except to sway public opinion. The clerk is empowered to enforce decorum at the clerk's (and my) discretion, subject of course to public opinion not looking kindly on suppression of expression.
I reserve the right to waive eligibility and numeric requirements at my sole discretion on a case by case basis. This means that I can deem a petition certified when it strictly would not have been. However this is only a waiver, it cannot make anyone ineligible or raise any numeric requirements. Waiver of requirements for one person does not waive them for others by default.
The clerk will move petitioner signatures from unknown to certified or uncertified based on eligibility.
After exactly 5 days the petition shall be over and the clerk shall carry out a tally of eligible petitioners. If at least 6 petitioners including the initiator are eligible, the petition shall be deemed certified and the next step of the process will be initiated. (the next step is one of the three, Modified RfC, self initiated RfAr, or resign "under a cloud"^[2] and stand for RfA at some later date of my choosing) as given above, at my choosing... the decision may be announced in advance of certification, at my option, but need not be.

The modified RfC process (choice 1)

This is one of the three possible "next steps" after a certified recall. The modified RfC will be constituted as follows:

A page in my userspace will be created.
Certification of the RfC will be waived.
If attempts are made to delete the page, I will counter them to the best of my ability within the limits of policy and common practice (one recreate for a summary deletion, then I will work the MfD or DRV process as appropriate to argue for retention)... assistance in arguing the case for retention by those participating would be appreciated but is not required as a condition of participation in the process. Arguing for deletion, however, shall cause that person's comments to be stricken or construed as favorable to retaining adminship, whichever is appropriate or more favourable to me, at my discretion. If the community ultimately deletes the page and it sticks I don't quite know what to do but will try to be reasonable.
A clerk of my sole choosing, but chosen for ability to be impartial, will be appointed to make sure that the RfC process itself goes smoothly, and to determine eligibility where appropriate. Preference would be given to the same clerk that clerked the petition, if that clerk is willing and if I feel they have done an adequate job.
The RfC will be started by referencing the entire text of the recall petition
Two questions will be included: Should I keep my adminship/Should I resign my adminship
Anyone qualified to vote in an ArbCom election, as construed in the most recent previous one to the initiation of the petition, or one then ongoing, whichever is more favourable (looser voting requirements), can sign under either of these two questions. Those not qualified will have their signatures and comments moved to sections that make it clear what their views are, but that do not count toward the total.
Any other sections desired may be added but will not have bearing on the outcome except to sway public opinion
At the end of exactly 5 days the modified RfC shall be over and the clerk shall carry out a tally of eligible commenters. If a simple majority to retain exists, I will not resign. If tied, or if a majority does not exist, I shall resign. Resignation shall be construed to have been "under a cloud"^[2], and if I wish to regain my adminship I will have to stand again via the normal RfA process.
Those that consider this not to be an RfC are welcome to give it whatever term they wish but these process steps will be used, and supersede standard RfC process where there is a conflict.
The conclusion of the RfC after the outcome is certified and my action is taken, if any, will conclude the matter as far as I am concerned, but the community is of course able to take whatever other steps they wish including starting a regular RfC, initiating an ArbCom case, etc.

The RfAr process (choice 2)

This is one of the three possible "next steps" after a certified recall. The RfAr will be initiated as follows:

I will initiate the case myself, perhaps with assistance from the petition clerk if the clerk is willing.
I will name myself and the certified petitioners as parties.
I will state that I feel sufficient notice has been given to all parties.
I will incorporate, by reference, the petition, and ask that arbcom consider it as evidence.
I will ask any arbitrators that were petitioners to recuse but leave that decision to their good judgement.
I will otherwise cooperate in whatever way possible, answering any questions asked to the best of my ability.
I reserve the right to present material in my own defense.
I reserve the right to suggest that other persons be named as parties.
I undertake to carry all this out in the shortest reasonably possible time consistent with external events.
Final determination of whether to take the case rests with ArbCom but I will strongly recommend that the case be taken and I would certainly appreciate (but not require) petitioners to also so strongly urge/recommend as well.
If ArbCom declines to take the case, that concludes the matter as far as I am concerned, but the community is of course able to take whatever other steps they wish including initiating other cases. I reserve the right, but not the obligation, to initiate either choice 1 or 3 in this case. (I will try to be reasonable)
If ArbCom takes the case, their judgement on principles, findings, and remedies will be binding on me, I will not work to circumvent them. The conclusion of the case will conclude the matter as far as I am concerned, but the community is of course able to take whatever other steps they wish including initiating other cases.

Resignation (choice 3)

This is one of the three possible "next steps" after a certified recall. The resignation shall be constituted as "under a cloud"^[2] meaning that a re RfA has standard success criteria as then constituted by the community and that withdrawing midway through is not an option for regaining admin status. Only a successful RfA will suffice. I may choose to stand again for RfA immediately, at some later date of my own choosing, or never, as I deem appropriate.

Grace period

Any change in any provision of this that makes it more stringent to qualify a petition or participate in any other part of the process, or more likely to lead to an outcome more favourable to me shall have a 2 week "grace period" during which any recall initiated will be under the old terms. Any change that is of the opposite sense (easier to qualify/participate, less favourable to me) shall go into effect immediately.

No Double Jeopardy

Once this process concludes for matters raised by petitioners during an instance of this process, I will not honor a second recall request regarding the same matters. If however new matters arise, the community is welcome to initiate another recall.

No vexatious litigants

No petitioner may initiate or support a petition for my recall more than three times in any 365 day period. This does not apply to participation in a modified RfC.

Severability

This is about my commitment to the community to be accountable, not about a category membership. Thus, the provisions of this page shall survive if, for example, the CAT:AOTR (or successor, whatever named) is deleted, renamed, listified. etc., and under any other reasonable circumstances. Only my explicitly stated withdrawal from this commitment itself will suffice.

No withdrawal

I do not intend to withdraw but that's an intent, not a promise. However, I promise not to withdraw to escape the consequences of this commitment. The only time I will withdraw from this category is if no recall is currently underway. This is subject to the same 2 week grace period as the eligibility or any other changes, so any withdrawal has at least 2 weeks to go into effect.

Notes

^ Remember, this is a voluntary action, and does not preclude an RfC or RfAr being initiated by others, should others feel they have no recourse.
^ ^a ^b ^c ^d This is the colloquial term for what is more formally described as "under controversial circumstances", see, for example this ArbCom principle
^
Lar's criteria include the requirements:
- that if the user calling for recall is an admin, the admin must themselves have been in this category for at least two weeks. This does not apply to non admins.
- that if the user calling for recall is a non admin, the user must have at least 4 months edit history under that ID or clearly connected and publicly disclosed related IDs, and at least 500 mainspace contributions, at least 100 of which must be substantive article improvements, and must have had no significant blocks for disruptive behaviour within the last 4 months.
Lar reserves the right to impose additional criteria at any time. However Lar commits that any criteria changes which remove anyone from the eligibility list will not go into effect until two weeks have elapsed from the time of the diff making the change (the "grace period"), to give folk time to get a recall started under the old criteria if they so desire, and further, that criteria will not be changed to remove anyone during the time of an active recall (starting from when notice is given by first petitioner, ending when the petition has been certified or decertified, in effect extending any 2 week grace period as necessary) Changes which only add eligibility, and do not remove anyone, are not subject to this limitation.
^ If you spot holes, now would be a good time to point them out so they can be fixed.

[1] Remember, this is a voluntary action, and does not preclude an RfC or RfAr being initiated by others, should others feel they have no recourse.

[cloud-2] This is the colloquial term for what is more formally described as "under controversial circumstances", see, for example this ArbCom principle

[3] Lar's criteria include the requirements:
that if the user calling for recall is an admin, the admin must themselves have been in this category for at least two weeks. This does not apply to non admins.

that if the user calling for recall is a non admin, the user must have at least 4 months edit history under that ID or clearly connected and publicly disclosed related IDs, and at least 500 mainspace contributions, at least 100 of which must be substantive article improvements, and must have had no significant blocks for disruptive behaviour within the last 4 months.
Lar reserves the right to impose additional criteria at any time. However Lar commits that any criteria changes which remove anyone from the eligibility list will not go into effect until two weeks have elapsed from the time of the diff making the change (the "grace period"), to give folk time to get a recall started under the old criteria if they so desire, and further, that criteria will not be changed to remove anyone during the time of an active recall (starting from when notice is given by first petitioner, ending when the petition has been certified or decertified, in effect extending any 2 week grace period as necessary) Changes which only add eligibility, and do not remove anyone, are not subject to this limitation.

[4] that if the user calling for recall is an admin, the admin must themselves have been in this category for at least two weeks. This does not apply to non admins.

[5] that if the user calling for recall is a non admin, the user must have at least 4 months edit history under that ID or clearly connected and publicly disclosed related IDs, and at least 500 mainspace contributions, at least 100 of which must be substantive article improvements, and must have had no significant blocks for disruptive behaviour within the last 4 months.

[4] If you spot holes, now would be a good time to point them out so they can be fixed.

[1]

[2]

[3]

[4]