This page is in preparation (Tony1).
This page in a nutshell: AdminReview is a process for dealing with users' grievances against (i) the use of administrator privileges in a way the user believes has breached policy and has been unfair to them, or (ii) the threat to use those privileges in such a way. AdminReview does not issue binding decisions, enforcement or judgements on any Wikipedian. Instead, it relies on the good faith of participants to achieve favourable outcomes. |
Administrators ("admins") are editors who have been given access to "tools" that are not available to others. The community places considerable trust in admins, who perform essential maintenance such as page protections and deleting material, as well as enforcing policies. In particular, they can disable the ability of users to edit the site ("blocking"). However, they occasionally make mistakes or fail to uphold the high standards they are held to.
Admins are required to follow a policy governing the exercise of their administrative privileges. AdminReview is a community-driven process to provide users with an independent review of administrative actions and behaviour, in a calm, deliberative manner. It is run by seven elected Coordinators (four non-admins and three admins) to provide an independent evaluation of events for users which have grievances against administrative actions or behaviour. The rules of AdminReview are embodied in a list of frequently asked questions (FAQs). Information about the Coordinators can be found here.
The goals of AdminReview are to:
It may be that the best way of launching AdminReview is as a subcommittee of delegates appointed by ArbCom, which is Wikipedia's peak body for ruling on user behaviour. This has yet to be determined.
Summary. A user with a grievance fills out a form (below) applying to have a case heard (Stage I). Two coordinators, one a non-admin, determine whether the case should proceed. If it does proceed (Stage II), those two coordinators issue a judgement. However, if they do not agree on the judgement or otherwise believe that it should be heard by all active coordinators, the case proceeds to Stage III.
[FLOWCHART GOES HERE]
In a little more detail, to be relocated somewhere: Users who believe that an admin action or behaviour has breached policy and has resulted in unfair treatment of themselves and/or other users may file a complaint (Stage 1); this must specify one or more of the codified "Specific policy requirements" set out below. If the Coordinator who takes on the case (the "Managing Coordinator") believes there is a prima facie case that the admin has breached a policy in such a way that has has been unfair to a user, the case proceeds to Stage 2 for investigation by the Managing Coordinator and one other Coordinator (at least one of the two must be a non-admin). Where they agree on a judgement and/or recommendation, this is issued and the case is moved to "Recent cases", from which it is deleted after seven days. Where the two Coordinators do not agree, the case proceeds to Stage 3, where all available Coordinators (a majority of whom must be non-admins) vote on a judgement and/or recommendation. Similarly, the case is moved to "Recent cases", from which it is deleted after seven days.
Click on "[edit]", then copy and paste the application form at the top of the list in Stage 1. Add the required information.
Notes:
[Complainants will paste their completed forms here:]
Management. Here, the Managing Coordinator is joined by another Coordinator; at least one of the two Coordinators is a non-admin. The statements and rejoinders in Stage 2 normally take less than five days, but may be extended by reasonable request.
Steps. The admin is invited to write a statement; the complainant may then post a rejoinder, and if this is done, the admin may post a rejoinder. Statements are normally up to 250 words long, and rejoinders normally up to 100 words. Each step ideally takes no longer than 24 hours. The timing of the Coordinators' decision is at their discretion; typically, it takes up to a few days after the completion of submissions by the parties.
Special applications. Either party may apply to the Managing Coordinator for leave to:
At the end of Stage 2, the two coordinators decide on either Option D, E or F.
Here, all available Coordinators — normally at least [five], of whom at least one is an admin and a majority are non-admins — form a judgement and make recommendations by majority vote; a tied vote is resolved in favour of the admin. The numbers for and against the decision will be published.
The Coordinators decide on either Option G or H.
The admin policy states that admins should:
All specific policy expectations are drawn from the Admin policy. The wording of the policy has been modified without intending any change to the meaning, to organise the expectations into themes and for ease of understanding; however, the wording at the policy page and in related ArbCom rulings is authoritative.
Complaints must identify, justify and provide diffs for breaches of one or more of these policy requirements.
(1) Site policies
(2) General behaviour
(3) Blocking
(4) Referral
(5) Conflict of interest
(6) Communication
(7) Accountability
(8) Edit-warring
(9) Breaches of trust
(10) Wheel-warring
The six coordinators are :
The Coordinators are elected by popular vote for staggered terms of 12 months; the first election is an exception, where the alpha tranche are elected for 24 months to begin the staggered process. Candidates must have at least 2000 edits at the time of nomination. Any Wikipedian with at least 150 edits may vote.
Some of the qualities coordinators require are similar to those of ArbCom Clerks. Candidates for the coordinator positions declare that they have the following qualities:
In the assessment of candidates, their evolved qualities are more important than measures such as historical block logs.
This page is in preparation (Tony1).
This page in a nutshell: AdminReview is a process for dealing with users' grievances against (i) the use of administrator privileges in a way the user believes has breached policy and has been unfair to them, or (ii) the threat to use those privileges in such a way. AdminReview does not issue binding decisions, enforcement or judgements on any Wikipedian. Instead, it relies on the good faith of participants to achieve favourable outcomes. |
Administrators ("admins") are editors who have been given access to "tools" that are not available to others. The community places considerable trust in admins, who perform essential maintenance such as page protections and deleting material, as well as enforcing policies. In particular, they can disable the ability of users to edit the site ("blocking"). However, they occasionally make mistakes or fail to uphold the high standards they are held to.
Admins are required to follow a policy governing the exercise of their administrative privileges. AdminReview is a community-driven process to provide users with an independent review of administrative actions and behaviour, in a calm, deliberative manner. It is run by seven elected Coordinators (four non-admins and three admins) to provide an independent evaluation of events for users which have grievances against administrative actions or behaviour. The rules of AdminReview are embodied in a list of frequently asked questions (FAQs). Information about the Coordinators can be found here.
The goals of AdminReview are to:
It may be that the best way of launching AdminReview is as a subcommittee of delegates appointed by ArbCom, which is Wikipedia's peak body for ruling on user behaviour. This has yet to be determined.
Summary. A user with a grievance fills out a form (below) applying to have a case heard (Stage I). Two coordinators, one a non-admin, determine whether the case should proceed. If it does proceed (Stage II), those two coordinators issue a judgement. However, if they do not agree on the judgement or otherwise believe that it should be heard by all active coordinators, the case proceeds to Stage III.
[FLOWCHART GOES HERE]
In a little more detail, to be relocated somewhere: Users who believe that an admin action or behaviour has breached policy and has resulted in unfair treatment of themselves and/or other users may file a complaint (Stage 1); this must specify one or more of the codified "Specific policy requirements" set out below. If the Coordinator who takes on the case (the "Managing Coordinator") believes there is a prima facie case that the admin has breached a policy in such a way that has has been unfair to a user, the case proceeds to Stage 2 for investigation by the Managing Coordinator and one other Coordinator (at least one of the two must be a non-admin). Where they agree on a judgement and/or recommendation, this is issued and the case is moved to "Recent cases", from which it is deleted after seven days. Where the two Coordinators do not agree, the case proceeds to Stage 3, where all available Coordinators (a majority of whom must be non-admins) vote on a judgement and/or recommendation. Similarly, the case is moved to "Recent cases", from which it is deleted after seven days.
Click on "[edit]", then copy and paste the application form at the top of the list in Stage 1. Add the required information.
Notes:
[Complainants will paste their completed forms here:]
Management. Here, the Managing Coordinator is joined by another Coordinator; at least one of the two Coordinators is a non-admin. The statements and rejoinders in Stage 2 normally take less than five days, but may be extended by reasonable request.
Steps. The admin is invited to write a statement; the complainant may then post a rejoinder, and if this is done, the admin may post a rejoinder. Statements are normally up to 250 words long, and rejoinders normally up to 100 words. Each step ideally takes no longer than 24 hours. The timing of the Coordinators' decision is at their discretion; typically, it takes up to a few days after the completion of submissions by the parties.
Special applications. Either party may apply to the Managing Coordinator for leave to:
At the end of Stage 2, the two coordinators decide on either Option D, E or F.
Here, all available Coordinators — normally at least [five], of whom at least one is an admin and a majority are non-admins — form a judgement and make recommendations by majority vote; a tied vote is resolved in favour of the admin. The numbers for and against the decision will be published.
The Coordinators decide on either Option G or H.
The admin policy states that admins should:
All specific policy expectations are drawn from the Admin policy. The wording of the policy has been modified without intending any change to the meaning, to organise the expectations into themes and for ease of understanding; however, the wording at the policy page and in related ArbCom rulings is authoritative.
Complaints must identify, justify and provide diffs for breaches of one or more of these policy requirements.
(1) Site policies
(2) General behaviour
(3) Blocking
(4) Referral
(5) Conflict of interest
(6) Communication
(7) Accountability
(8) Edit-warring
(9) Breaches of trust
(10) Wheel-warring
The six coordinators are :
The Coordinators are elected by popular vote for staggered terms of 12 months; the first election is an exception, where the alpha tranche are elected for 24 months to begin the staggered process. Candidates must have at least 2000 edits at the time of nomination. Any Wikipedian with at least 150 edits may vote.
Some of the qualities coordinators require are similar to those of ArbCom Clerks. Candidates for the coordinator positions declare that they have the following qualities:
In the assessment of candidates, their evolved qualities are more important than measures such as historical block logs.