Revision as of 19:35, 20 November 2024 editLevivich (talk | contribs)Extended confirmed users, Page movers40,421 edits Undid revision 1258630028 by Raladic (talk) I strongly disagree with making this page into a permanent wall of shame; no need to list closed petitions hereTag: Undo← Previous edit | Revision as of 04:11, 21 November 2024 edit undoThryduulf (talk | contribs)Oversighters, Administrators98,883 edits →Petition: per talk add a couple of sentences regarding invalid petitionsNext edit → | ||
Line 19: | Line 19: | ||
If a petition reaches the required twenty five signatures within thirty days, it should be closed. The subject is then required to make a re-request for adminship or stand as a candidate in an ]. The same requirement exists when a petition is closed early at the subject's request or if they agree to make a re-request for adminship; it should also be closed early if they resign their adminship. A petition that has been open for thirty days and has not gained the required number of signatures should be closed without requiring the subject to make re-request for adminship. | If a petition reaches the required twenty five signatures within thirty days, it should be closed. The subject is then required to make a re-request for adminship or stand as a candidate in an ]. The same requirement exists when a petition is closed early at the subject's request or if they agree to make a re-request for adminship; it should also be closed early if they resign their adminship. A petition that has been open for thirty days and has not gained the required number of signatures should be closed without requiring the subject to make re-request for adminship. | ||
<!--Invalid petitions --> | |||
If a petition is opened contrary to the requirements for opening a petition for any reason that cannot be quickly and easily fixed, it may be closed by any editor other than the subject administrator. Such invalid petitions are treated as never having existed for the purposes of determining when a new petition may be initiated and do not affect the subject's status as an administrator in any way. | |||
<div style="max-width: fit-content;margin-inline: auto"> | <div style="max-width: fit-content;margin-inline: auto"> | ||
<inputbox> | <inputbox> |
Revision as of 04:11, 21 November 2024
"WP:RECALL" redirects here. For voluntary recall, see WP:Administrators open to recall. For previous failed proposals, see WP:History of de-adminship proposals § Proposed processes.This page documents a procedural policy of Misplaced Pages. It documents various processes by which the English Misplaced Pages operates. | Shortcuts |
You are invited to refine and workshop proposals to the recall process at Misplaced Pages:Administrator recall/Reworkshop. After the reworkshop is closed, the proposals will be voted on at an RfC. |
Administrator recall is a process by which the community can require an administrator to make a re-request for adminship (RRfA) to retain their administrative privileges. It is one of several ways that adminship can be reviewed or removed.
In most cases, disputes with administrators should be resolved with the normal dispute resolution process outlined at WP:Administrators § Grievances by users ("administrator abuse"). Other methods of dispute resolution should be attempted before a recall petition is initiated.
Petition
Any extended confirmed editor may start a petition for an active administrator to make a re-request for adminship if they believe that the administrator has lost the trust of the community. The petition may not be created within twelve months of the administrator's last successful request for adminship, request for bureaucratship, or re-request for adminship, or within twelve months of the administrator being elected an administrator or elected to the Arbitration Committee. If a petition fails, another petition to recall the same administrator may not be started for six months from the date the last one was closed.
The editor who starts the petition must notify the administrator on their user talk page using the {{subst:Admin recall notice}} template. They must also post a notice to the administrator's noticeboard using the {{subst:Admin recall notice/AN}} template.
Any extended confirmed editor may add their signature to a petition, with or without reasoning. An editor can sign no more than five active petitions. Any editor may comment in a discussion section on the recall petition page. Any signature or comment may be struck based on the same criteria used during requests for adminship.
If a petition reaches the required twenty five signatures within thirty days, it should be closed. The subject is then required to make a re-request for adminship or stand as a candidate in an administrator election. The same requirement exists when a petition is closed early at the subject's request or if they agree to make a re-request for adminship; it should also be closed early if they resign their adminship. A petition that has been open for thirty days and has not gained the required number of signatures should be closed without requiring the subject to make re-request for adminship.
If a petition is opened contrary to the requirements for opening a petition for any reason that cannot be quickly and easily fixed, it may be closed by any editor other than the subject administrator. Such invalid petitions are treated as never having existed for the purposes of determining when a new petition may be initiated and do not affect the subject's status as an administrator in any way.
Current petitions
This section is transcluded from Misplaced Pages:Administrator recall/Current. (edit | history)This is a list of open administrator recall petitions and petitions that passed the threshhold for recall in the past 30 days so the administrator may run for Re-request for Adminship.
- none currently
Closed petitions
A list of closed recall petitions and resulting RRfAs may be found at Misplaced Pages:Administrator recall/Closed petitions.
Re-request for adminship
ShortcutAn administrator seeking to retain administrative privileges must have their re-request for adminship (RRfA) transcluded to Misplaced Pages:Requests for adminship within thirty days of the close of a successful recall petition. If an administrator election is scheduled within those thirty days, they may stand in it instead.
A RRfA follows the same process as a request for adminship, but with lower thresholds for passing. In an RRfA, any administrator who obtains at least 60% support will retain their administrator role. If the administrator receives between 50 and 60% support, the community's consensus will be determined by the bureaucrats. If the administrator runs in an administrator election instead of initiating a re-request for adminship, they must obtain at least 55% support to retain their administrative privileges.
The bureaucrats are responsible for ensuring that an RRfA is started within a reasonable time frame. If this does not happen, they may remove the administrator privileges at their discretion. Should the administrator fail to pass an RRfA or administrator election, bureaucrats may remove their privileges.
Notes
- The status of an administrator who:
- has been notified about pending procedural removal of administrative privileges due to insufficient activity and whose status is listed as "Pending" in a way consistent with the administrator policy, or
- has been totally inactive for at least 3 months (Misplaced Pages:List of administrators/Inactive is a periodically updated list of administrators who have not edited in the last 3 months)
See also
- Misplaced Pages:Administrator recall/RfCs – list of RFCs that led to creation of this process (as well as ongoing and proposed RfCs for amendments)
- Misplaced Pages:Administrators open to recall – voluntary recall procedure adopted by some administrators
- Misplaced Pages:History of de-adminship proposals – history of previous attempts to create an administrator recall process
- Misplaced Pages:Administrator recall/Reworkshop – page to propose and refine changes to rework Administrator recall