Motions
Discretionary sanctions (2014)
(Nutshell and preamble)Definitions
AuthorisationDiscretionary sanctions may be authorised either as part of the final decision of an arbitration case or by committee motion. When it becomes apparent that discretionary sanctions are no longer necessary for a particular area of conflict, only the committee may rescind the authorisation of them, either at the request of any editor at ARCA or of its own initiative. Unless the committee specifies otherwise, after rescinding the authorisation all sanctions remain in force. A log of the areas of conflict for which discretionary sanctions have been authorised is maintained at the discretionary sanctions main page. Guidance for editors
Within the area of conflict, editors are expected to edit carefully and constructively, to not disrupt the encyclopedia, and to:
Any editor whose edits do not meet these requirements may wish to restrict their editing to other topics in order to avoid the possibility of sanctions.
Certain pages (typically, AE, AN, and ARCA) are used for the fair, well-informed, and timely resolution of discretionary sanction enforcement cases. Editors participating in enforcement cases must disclose fully their involvement (if any). While good-faith statements are welcome, editors are expected to discuss only evidence and procedure; they are not expected to trade insults or engage in character assassination. Insults and personal attacks, soapboxing and casting aspersions are as unacceptable in enforcement discussions as elsewhere on Wikipedia. Uninvolved administrators are asked to ensure that enforcement cases are not disrupted; and may remove statements, or restrict or block editors, as necessary to address inappropriate conduct. Awareness and alertsNo editor may be sanctioned unless they are aware that discretionary sanctions are in force for the area of conflict. An editor is aware if they were mentioned by name in the applicable Final Decision or have ever been sanctioned within the area of conflict (and at least one of such sanctions has not been successfully appealed). An editor is also considered aware if in the last twelve months:
Any editor may advise any other editor that discretionary sanctions are in force for an area of conflict. However, these only count as the formal notifications required by this procedure if the standard template message – currently {{Ds/alert}} – is placed unmodified on the talk page of the editor being alerted. An alert:
As {{Ds/alert}} template is part of this procedure, it may be modified only with the committee's explicit consent. Editors issuing alerts are expected to ensure that no editor receives more than one alert per area of conflict per year. Any editor who issues alerts disruptively may be sanctioned. Role of administratorsWhen deciding whether to sanction an editor, and which sanctions may be appropriate, the enforcing administrator’s objective should be to create an acceptable collaborative editing environment for even our most contentious articles. To this end, administrators are expected to use their experience and judgment to balance the need to assume good faith, to avoid biting genuine newcomers and to allow responsible contributors maximum editing freedom with the need to keep edit-warring, battleground conduct, and disruptive behaviour to a minimum. While discretionary sanctions give administrators necessary latitude, they must not:
Administrators who fail to meet these expectations may be subject to any remedy the committee consider appropriate, including desysopping. Administrative actions may be peer-reviewed using the regular appeal processes. To act in enforcement, an administrator must at all relevant times have their access to the tools enabled. Former administrators – that is, editors who have temporarily or permanently relinquished the tools or have been desysopped – may neither act as administrators in arbitration enforcement nor reverse their own previous administrative actions. Expectations of administratorsEnforcing administrators are accountable and must explain their enforcement actions; and they must not be involved. Prior routine enforcement interactions, prior administrator participation in enforcement discussions, or when an otherwise uninvolved administrator refers a matter to AE to elicit the opinion of other administrators or refers a matter to the committee at ARCA, do not constitute or create involvement. Administrators may not adjudicate their own actions at any appeal though they are encouraged to provide statements and comments to assist in reaching a determination. Enforcing administrators are expected to exercise good judgment by responding flexibly and proportionately when they intervene. When dealing with first or isolated instances of borderline misconduct, informal advice may be more effective in the long term than a sanction. Conversely, editors engaging in egregious or sustained misconduct should be dealt with robustly. Placing sanctions and page restrictions
When considering whether edits fall within the scope of discretionary sanctions, administrators should be guided by the principles outlined in the topic ban policy.
Any uninvolved administrator is authorised to place: revert and move restrictions, interaction bans, topic bans, and blocks of up to one year in duration, or other reasonable measure that the enforcing administrator believes is necessary and proportionate for the smooth running of the project. Prior to placing sanctions that are likely to be controversial, administrators are advised to elicit the opinions of other administrators at AE. For the avoidance of doubt, enforcing administrators are not authorised to issue site bans; to require the removal of user rights that cannot be granted by an administrator or to restrict their usage; nor to enforce discretionary sanction beyond their reasonable scope. The enforcing administrator must provide a notice on the sanctioned editor’s talk page specifying the misconduct for which the sanction has been issued as well as the appeal process. The enforcing administrator must also log the sanction.
Any uninvolved administrator may impose on any page or set of pages relating to the area of conflict semi-protection, full protection, move protection, revert restrictions, and prohibitions on the addition or removal of certain content (except when consensus for the edit exists). Editors ignoring page restrictions may be sanctioned by any uninvolved administrator. The enforcing administrator must log page restrictions they place. Best practice is to add editnotices to restricted pages where appropriate, using the standard template ({{ds/editnotice}}).
Should any editor ignore or breach any sanction placed under this procedure, that editor may, at the discretion of any uninvolved administrator, receive a fresh further sanction. The further sanction must be logged on the appropriate page and the standard appeal arrangements apply.
All sanctions and page restrictions must be logged on the pages specified for the purpose in the authorising motion or decision. Whenever a sanction or page restriction is appealed or modified, the administrator amending it must append a note recording the amendment to the original log entry. While sanctions and page restrictions are not invalidated by a failure to log, repeated failure to log may result in sanctions. The log location may not be changed without the consent of the committee. Appeals and modifications [placeholder][reserved for the Standard appeals and modifications provision] ContinuityNothing in this current version of the discretionary sanctions process constitutes grounds for appeal of a remedy or restriction imposed under prior versions of it. All sanctions and restrictions imposed under earlier versions of this process remain in force. Warnings issued under earlier procedures are not sanctions and become alerts for twelve months from the date of the passing of the motion authorising this procedure, then expire. Appeals open at the time this version is adopted will be handled using the prior appeals procedure, but this current process will thereafter govern appeals. |
Motion: Discretionary sanctions (2014)
Proposed: That the updated Discretionary sanctions procedure above supersedes and replaces all prior discretionary sanction provisions with immediate effect;
- Support:
- After a year long review, I guess this is ready, Roger Davies talk 14:11, 2 May 2014 (UTC)
- This is certainly ready. AGK [•] 14:15, 2 May 2014 (UTC)
- With great thanks to Roger, AGK and all who participated in the review. WormTT(talk) 14:16, 2 May 2014 (UTC)
- T. Canens (talk) 14:28, 2 May 2014 (UTC)
- My thanks to everyone who led and participated in the extensive discussions. Newyorkbrad (talk) 14:32, 2 May 2014 (UTC)
- With a special hat tip to Roger and AGK for having the patience to see this through, and a normal hat tip to everyone who participated. --Floquenbeam (talk) 15:25, 2 May 2014 (UTC)
- Salvio Let's talk about it! 15:44, 2 May 2014 (UTC)
- Der Wohltemperierte Fuchs(talk) 17:31, 2 May 2014 (UTC)
- Thank you to all who put in the many hours of work on this. GorillaWarfare (talk) 22:04, 2 May 2014 (UTC)
- Excellent work, Roger and everyone involved. Seraphimblade Talk to me 22:09, 2 May 2014 (UTC)
- Echoing the above, I know a lot of work went into this and it is much appreciated. Beeblebrox (talk) 04:01, 3 May 2014 (UTC)
- NativeForeigner Talk 18:36, 3 May 2014 (UTC)
- Oppose:
- Abstain:
- Comments:
DS (2014) housekeeping provisions
|
Motion: DS (2014) housekeeping provisions
Proposed: That the housekeeping provisions be implemented with immediate effect;
- Support:
- Roger Davies talk 14:11, 2 May 2014 (UTC)
- AGK [•] 14:15, 2 May 2014 (UTC)
- With great thanks to Roger, AGK and all who participated in the review. WormTT(talk) 14:17, 2 May 2014 (UTC)
- Recused with respect to the last sentence of the fifth bullet point. Support otherwise. T. Canens (talk) 14:29, 2 May 2014 (UTC)
- Newyorkbrad (talk) 14:32, 2 May 2014 (UTC)
- Actually, I have some substantial changes I'd like to propose... (just kidding) --Floquenbeam (talk) 15:27, 2 May 2014 (UTC)
- Salvio Let's talk about it! 15:44, 2 May 2014 (UTC)
- Der Wohltemperierte Fuchs(talk) 16:40, 2 May 2014 (UTC)
- GorillaWarfare (talk) 22:04, 2 May 2014 (UTC)
- Seraphimblade Talk to me 22:11, 2 May 2014 (UTC)
- Beeblebrox (talk) 04:02, 3 May 2014 (UTC)
- NativeForeigner Talk 18:36, 3 May 2014 (UTC)
- Oppose:
- Abstain:
- Comments:
Standard appeals and modification provision
Appeals and modifications
Appeals may be made only by the editor under sanction and only for a currently active sanction. The process has three possible stages (see "Important notes" below). The editor may:
No administrator may modify a sanction placed by another administrator without:
Administrators modifying sanctions out of process may at the discretion of the committee be desysopped. Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied. Important notes:
|
Motion: Appeals and modifications
Proposed: That the updated Appeals and modifications provision become the standard provision and replace all prior discretionary sanction appeal provisions with immediate effect;
- Support:
- Yep, Roger Davies talk 14:11, 2 May 2014 (UTC)
- AGK [•] 14:15, 2 May 2014 (UTC)
- With great thanks to Roger, AGK and all who participated in the review. WormTT(talk) 14:17, 2 May 2014 (UTC)
- Newyorkbrad (talk) 14:33, 2 May 2014 (UTC)
- T. Canens (talk) 14:33, 2 May 2014 (UTC)
- --Floquenbeam (talk) 15:27, 2 May 2014 (UTC)
- Salvio Let's talk about it!
- Der Wohltemperierte Fuchs(talk) 17:15, 2 May 2014 (UTC)
- NativeForeigner Talk 19:03, 2 May 2014 (UTC)
- GorillaWarfare (talk) 22:05, 2 May 2014 (UTC)
- Seraphimblade Talk to me 22:13, 2 May 2014 (UTC)
- Beeblebrox (talk) 04:03, 3 May 2014 (UTC)
- Oppose:
- Abstain:
- Comments: