The following is a proposed Wikipedia policy, guideline, or process. The proposal may still be in development, under discussion, or in the process of gathering consensus for adoption. |
Community discretionary sanctions are a form of general sanctions that can be authorised by the community for certain topic areas, group of pages or page which are especially contentious or experiencing sustained disruptive editing. They allow administrators the ability to impose sanctions and restrictions to make a more acceptable, collaborative editing environment.
Community discretionary sanctions are similar to the Arbitration Committee's discretionary sanctions however they have been modified for use by the community.
Community discretionary sanctions may be authorised by the community by a consensus of uninvolved editors, usually at the administrators' noticeboard. If it becomes apparent that discretionary sanctions are no longer necessary for a particular area of conflict, the community may revoke authorisation. Unless the community specifies otherwise, sanctions imposed prior to such a revocation remain in force.
Within an area of conflict, editors are expected to edit carefully and constructively, to not disrupt the encyclopedia, and to:
Certain pages (typically, CDS/E and AN) are used for the fair, well-informed, and timely resolution of community 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.
No editor may be sanctioned unless they are aware that community discretionary sanctions are in force for the area of conflict. An editor is aware if they have ever been sanctioned within the area of conflict (and at least one of such sanctions is current). An editor is also considered aware if in the last twelve months:
Any editor may advise any other editor that community 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 designed for each area of conflict (see Template:CDS) is placed unmodified on the talk page of the editor being alerted. A notification:
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.
When 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 community discretionary sanctions give administrators necessary latitude, they must not:
Administrators who fail to meet these expectations may be restricted from participating in community discretionsary sanctions enforcement or referred to the Arbitration Committee for further action. 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 enforcement nor reverse their own previous administrative actions.
Enforcing administrators must not be involved. They are accountable to the community, and must provide justification for any enforcement action they mete out. Participating in routine enforcement actions, enforcement discussions, or referring matters to the administrators' noticeboard does not render an administrator involved. Administrators may not adjudicate their own actions at any appeal, though they are encouraged to provide statements and comments to assist other administrators in reaching a conclusion.
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 after having been initially notified of the sanctions.
When considering whether an edit falls within an area of conflict, administrators should be guided by the principles outlined in the topic ban policy.
Any uninvolved administrator is authorised to impose revert and move restrictions, interaction bans (which can apply in all areas of Wikipedia), topic bans, and blocks of up to one year in duration, or any 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 AN or CDS/E. 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 community discretionary sanctions 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, which may be a link to community or administrative discussion, the appeal process and the page which details the sanctions and log. ####The templates **** and {{ uw-csblock}} may be used for notifying users of sanctions. 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, prohibitions on the addition or removal of certain content (except when consensus for the edit exists) or other reasonable measure that the enforcing administrator believes is necessary and proportionate for the smooth running of the project. 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.
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 notices, sanctions and page restrictions must be logged on the pages specified for that purpose. 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.
Appeals may be made only by the editor under sanction and only for a currently active sanction. The process has two possible stages, the editor may:
No administrator may modify a sanction placed by another administrator without:
Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new more restrictive sanction if fresh misconduct has taken place after the existing sanction was applied.
For an amendment or appeal request to succeed, the clear and substantial consensus of uninvolved editors at AN is required. If consensus at AN is unclear, the status quo prevails.
The following is a proposed Wikipedia policy, guideline, or process. The proposal may still be in development, under discussion, or in the process of gathering consensus for adoption. |
Community discretionary sanctions are a form of general sanctions that can be authorised by the community for certain topic areas, group of pages or page which are especially contentious or experiencing sustained disruptive editing. They allow administrators the ability to impose sanctions and restrictions to make a more acceptable, collaborative editing environment.
Community discretionary sanctions are similar to the Arbitration Committee's discretionary sanctions however they have been modified for use by the community.
Community discretionary sanctions may be authorised by the community by a consensus of uninvolved editors, usually at the administrators' noticeboard. If it becomes apparent that discretionary sanctions are no longer necessary for a particular area of conflict, the community may revoke authorisation. Unless the community specifies otherwise, sanctions imposed prior to such a revocation remain in force.
Within an area of conflict, editors are expected to edit carefully and constructively, to not disrupt the encyclopedia, and to:
Certain pages (typically, CDS/E and AN) are used for the fair, well-informed, and timely resolution of community 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.
No editor may be sanctioned unless they are aware that community discretionary sanctions are in force for the area of conflict. An editor is aware if they have ever been sanctioned within the area of conflict (and at least one of such sanctions is current). An editor is also considered aware if in the last twelve months:
Any editor may advise any other editor that community 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 designed for each area of conflict (see Template:CDS) is placed unmodified on the talk page of the editor being alerted. A notification:
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.
When 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 community discretionary sanctions give administrators necessary latitude, they must not:
Administrators who fail to meet these expectations may be restricted from participating in community discretionsary sanctions enforcement or referred to the Arbitration Committee for further action. 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 enforcement nor reverse their own previous administrative actions.
Enforcing administrators must not be involved. They are accountable to the community, and must provide justification for any enforcement action they mete out. Participating in routine enforcement actions, enforcement discussions, or referring matters to the administrators' noticeboard does not render an administrator involved. Administrators may not adjudicate their own actions at any appeal, though they are encouraged to provide statements and comments to assist other administrators in reaching a conclusion.
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 after having been initially notified of the sanctions.
When considering whether an edit falls within an area of conflict, administrators should be guided by the principles outlined in the topic ban policy.
Any uninvolved administrator is authorised to impose revert and move restrictions, interaction bans (which can apply in all areas of Wikipedia), topic bans, and blocks of up to one year in duration, or any 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 AN or CDS/E. 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 community discretionary sanctions 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, which may be a link to community or administrative discussion, the appeal process and the page which details the sanctions and log. ####The templates **** and {{ uw-csblock}} may be used for notifying users of sanctions. 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, prohibitions on the addition or removal of certain content (except when consensus for the edit exists) or other reasonable measure that the enforcing administrator believes is necessary and proportionate for the smooth running of the project. 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.
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 notices, sanctions and page restrictions must be logged on the pages specified for that purpose. 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.
Appeals may be made only by the editor under sanction and only for a currently active sanction. The process has two possible stages, the editor may:
No administrator may modify a sanction placed by another administrator without:
Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new more restrictive sanction if fresh misconduct has taken place after the existing sanction was applied.
For an amendment or appeal request to succeed, the clear and substantial consensus of uninvolved editors at AN is required. If consensus at AN is unclear, the status quo prevails.