Jump to content

User:Jéské Couriano/ArbCaseSum/08

From Wikipedia, the free encyclopedia

How to read the sections

[edit]
  • Decided: The calendar date (in UTC) when the case was decided. If the case did not reach a decision, it will be Closed instead. If the case involved an administrator "retiring", it will be "Deopped" instead.
  • Abbrev.: A shorthand abbreviation of the casename. See ArbCaseAbv for more details.
  • Type: The type of case it is:
  • Admin: A case centred around the conduct of one or more administrators.
  • Dispute: A case that examines an intractible dispute between two or more editors directly.
  • Editor: A case about the (non-administrative) misconduct of an editor.
  • Functionary: A case centred around misuse of Suppressor or Checkuser permissions.
  • Omnibus: A case about misconduct in a topic area writ large.
  • Other: Any case that doesn't fall into one of the categories above.
  • Scope: The overall scope of the case.
  • CT?: An indication of whether or not a case includes or included a discretionary sanctions or contentious topic remedy.
  • Remedy name: The name of the remedy (or a description of it, for earlier cases which did not have sectioned remedies).
  • Remedy (in modern terms): Basically my best attempt to explain, in plain English and modern understanding, what the remedy means.
  • If this section has a coloured background, the colour indicates its status or origin:
  • Yellow (#FFFF00) is a temporary injunction issued mid-case.
  • Blue (#00BFFF) is a post-close amendment or motion.
  • Red (#CD5C5C) is a remedy that has since been rescinded or otherwise is wholly reliant on previous remedies that are themselves rescinded.
  • Green (#32CD32) is a remedy whose wording was amended post-close, either due to an amendment/motion or due to changes in process (such as Discretionary Sanctions to Contentious Topic).
  • Brown (#D2691E) is suspended or in abeyence, usually as part of a period where a remedy has been appealed.
  • Amended/Enacted: If a remedy was added or amended post-close, this will be the calendar date (in UTC) when the remedy was modified or took effect.
  • Rescinded: If a remedy was terminated, this will be the calendar date (in UTC) when the remedy was ended.
  • Enforceable?: Indicates whether a given remedy can be invoked at WP:AE. Any remedy that predates April 2006 and was not still in force by then predates AE entirely.
  • Sup/Opp/Abs/Rcs: The vote totals for a remedy (Support, Oppose, Abstain, Recused).

Any case that has been courtesy-blanked or closed without action will be given a very brief description and nothing further.

John Buscema

[edit]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Editing of John Buscema In order to break an impasse caused by these two editors being unable to agree on how the article should be presented, Skyelarke and Tenebrae are each topic-banned from the John Buscema article (but not its talk page) for 3mo. Yes 8 0 0 0
Subsequent editing Once their topic-ban lapses, Skyelarke and Tenebrae are admonished to respect consensus developed in the interim concerning the basic structure of the article and the nature of the material that is included, including the number of images. No 7 1 1 0
Disruptive editing Skyelarke and Tenebrae may individually be summarily topic-banned from pages in the John Buscema topic area at administrator discretion. All such bans (and blocks arising from same) are to be logged on the case page. Yes 8 1 0 0

Jim62sch

[edit]
  • Decided: Jan. 09, 2008
  • Abbrev.: J62
  • Type: Editor
  • Scope: Jim62sch's off-wiki harassment of another user
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Jim62sch instructed Jim62sch may be summarily blocked if he makes an edit judged to be a threat, an attempt at harassment, or bullying. Block length is left to administrator discretion, and any such block must both be logged on the case page and brought to ArbCom's attention as soon as possible. Yes 10 0 0 0
Editors reminded Aside from reminding editors to be cautious when referring to an editor's real-world circumstances, they are also reminded about the prohibition on harassing and threatening other editors - with two enforcement provisions pointing out that (1) rank-and-file admins are allowed to summarily address on- and off-wiki harassment as they see fit and (2) egregious incidents are to be brought to ArbCom's attention immediately. No 10 0 0 0

John Gohde 2

[edit]
  • Decided: Jan. 12, 2008
  • Abbrev.: JG2
  • Type: Editor
  • Scope: John Gohde's conduct since JG.
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
John Gohde banned John Gohde is sitebanned 1yr. Again. Yes 12 0 0 0

Zeraeph

[edit]
  • Decided: Jan. 14, 2008

(This case has been courtesy-blanked for the privacy of its participants. Zeraeph was sitebanned 1yr,)

Dbachmann/Ancient Egyptian race controversy

[edit]
Remedy name Remedy (in modern terms) Enacted Rescinded Enforceable? Sup Opp Abs Rcs
Dbachmann reminded Dbachmann is admonished for misusing rollback and his admin tools in content disputes where he is a party. Rollback was, at this time, still only available to administrators. -- -- No 9 0 0 0
Article probation Anyone disrupting the Afrocentrism or Race of ancient Egyptians articles may be summarily topic-banned from either or both at administrator discretion. Any such bans (and blocks arising from same) are to be logged on the case page. -- Discretionary sanctions (January 2014) Yes 12 0 0 0
Discretionary sanctions (January 2014) Article probation is rescinded and replaced with a contentious topic designation. Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts pages and discussions related to the race of ancient Egyptians as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log, and for the first year they can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly. (See WP:Contentious topics for more details.)
Any remedies from the article probation that were still in force remain so and are still bound by the standard appeal procedures for enforcement. 		Jan. 10, 2014 Discretionary sanctions topic area changes (February 2022) Yes 10 0 0 0
Case renamed (January 2015) The case is renamed from "Dbachmann" to "Ancient Egyptian race controversy" to clarify the breadth of its scope. Jan. 27, 2015 -- N/A 10 1 0 0
Discretionary sanctions topic area changes (February 2022)[i] Discretionary sanctions (January 2014) is rescinded. Any sanctions still in force remain so and are bound by the standard appeal procedures for enforcement. Feb. 05, 2022 -- N/A 9 3 0 0

R. fiend

[edit]
  • Closed: Jan. 14, 2008

(Case closed after the subject of the case voluntarily surrendered his administrator userright. ArbCom also ruled that one of that administrator's blocks was unjustified.)

Palestine-Israel articles

[edit]

(The remedies below refer to "the PIA area", which refers to articles and discussions about the Israel-Arab conflict, broadly construed. The definition used here will not distinguish between core and related content as PIA4 does.)

Remedy name Remedy (in modern terms) Enacted Rescinded Enforceable? Sup Opp Abs Rcs
Discretionary sanctions/Appeal of discretionary sanctions Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts pages and discussions in the PIA area as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log, and for the first year they can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly.
(These two remedies combined are a Contentious Topic Designation v.1.0 and so are combined together for brevity.) 		-- PIA4 Yes 11/10[ii] 0 0 0 0
Working group ArbCom intends to convene a working group to find a way to, in light of this case, EE, AA2, and TRB, come up with some way to lower the considerable heat in topic areas about national, ethnic, and cultural areas of conflict. The working group may develop whatever recommendations it deems necessary to quell the disruption, even policy changes, ArbCom actions, etc.
In other words, ArbCom fails to realise the only way to deal with intractible ethnopolitical disputes such as these is to wait for them to come to a resolution in the real world and summarily block anyone trying to import them into Wikipedia on discovery in the meanwhile.		 -- -- N/A 10 0 0 0
Editors reminded ArbCom reminds editors that Wikipedia cannot, and should not be used to, resolve the real-world issues that give rise to these ethnopolitical disputes, and should only report on the issues and incidents neutrally.
(This remedy is marked as "vacated" per PIA4, but as it is merely an advisory remedy it has no impact from an enforcement standpoint to begin with.)		 -- -- No 11 0 0 0
Editors counseled ArbCom encourages editors who are Editing While Angry that it's often better to just walk away and spare your sanity rather than fall deep into the rabbit hole of personalising the dispute and adopting an extreme tribalist mindset.
(This remedy is marked as "vacated" per PIA4, but as it is merely an advisory remedy it has no impact from an enforcement standpoint to begin with.)		 -- -- No 10 0 0 0
Standard discretionary sanctions (This is an update to the contentious topics standard template and is effectively identical to Discretionary sanctions/Appeal of discretionary sanctions above.) Oct. 27, 2011 PIA4 Yes 14 0 0 0
General 1RR restriction All editors working in the PIA area, writ large, are under 1RR. Edits made to enforce the 500/30 restriction are exempt. Mar. 10, 2012
Amended 8 times 		PIA4 Yes 9 1 0 0
Syrian civil war articles ArbCom reverses a determination by an administrator that the Syrian civil war is in the PIA area, but leaves the 1RR and other sanctions associated with the designation in place for 30 days to allow for the community to come to an agreement on a contentious topic designation for the topic. July 21, 2017 -- N/A 10 1 0 0
Editors cautioned ArbCom warns editors that playing stupid games around what is and isn't a revert will result in winning stupid prizes. Nov. 21, 2018 -- No 8 1 0 0
Administrators encouraged Furthering the above, ArbCom is encouraging administrators to hand out said stupid prizes as they see fit if people attempt to debate the point. Nov. 21, 2018 -- No 8 1 0 0

Kingofmann

[edit]
  • Closed: Jan. 21, 2008

(Closed as moot after one party quit the project.)

Bluemarine

[edit]
  • Decided: Jan. 31, 2008
  • Abbrev.: BM

(This case has been courtesy-blanked for the privacy of its participants. ArbCom endorsed Bluemarine's community ban and issued an article probation, which has since been rescinded as redundant with an existing contentious topic designation. This case has enforcement threads.)

Internet Relay Chat

[edit]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Civility:Giano For the next year, Giano may be summarily blocked if he makes an edit judged to be incivil, a personal attack, or casting aspersions. Blocks are capped at 1w for the first five (and 1yr thereafter) and must be logged on the case page.
(Enforcement of this remedy was suspended on Nov. 23, 2008 after a controversial unblock.)		 Yes 7 3 0 1
IRC ArbCom declines to use this case to address problems with IRC channel policies, instead handling them separately (likely to gather information from IRC sysops beforehand). N/A 9 0 1 1
All parties cautioned ArbCom isn't a fan of all the drama-mongering on display here and admonishes everyone to not add their bit to a conversation if it isn't going to help resolve the problem. No 8 0 0 1
Editors are requested ArbCom makes it clear that edit-warring is unacceptable even if the page is a disputed policy/guideline page. No 7 1 0 1

Matthew Hoffman

[edit]
  • Closed: Feb. 13, 2008

(This case has been courtesy-blanked for the privacy of its participants. This case is a procedural cluster headache, and was declared as void ab initio in 2009 due to multiple breaches of Arbitration procedure that were prejudicial to one of the parties.)

Waterboarding

[edit]
  • Decided: Feb. 15, 2008
  • Abbrev.: WTB
  • Type: Dispute
  • Scope: Intractible disputes on Waterboarding
  • CT?: No[iv]
Remedy name Remedy (in modern terms) Rescinded Enforceable? Sup Opp Abs Rcs
Article probation Any editor disrupting articles about waterboarding or the controversy about it may be summarily topic-banned from those articles at administrator discretion. All such bans (and blocks arising from them) are to be logged on the case page. Nov. 15, 2015 Yes 7 0 0 0
General restriction Provided they have been alerted to the existence of this remedy, editors who make edits judged to be incivil, personal attacks, or casting aspersions in discussions related to waterboarding or its controversy may be summarily blocked. Blocks are capped at 1w for the first five and 1yr thereafter, and are to be logged, along with warnings, on the case page.
(This was seen as redundant with AP2's contentious topic designation and rescinded .) 		Feb. 04, 2022 Yes 7 0 0 0

JoshuaZ

[edit]
  • Decided: Feb. 05, 2008

(This case has no case page due to being conducted entirely in camera. JoshuaZ's administrator rights were revoked; he can only get them back by first appealing this case to ArbCom and then passing a subsequent Request for Adminship.)

New World Translation

[edit]
  • Closed: Mar. 01, 2008

(Closed for want of evidence.)

Episodes and characters 2

[edit]
  • Decided: Mar. 10, 2008
  • Abbrev.: E&C2
  • Type: Dispute
  • Scope: Continued disputes over television show episodes and characters since E&C
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Temporary Injunction All parties to this case are banned from making edits that create or reverse redirects and/or add or remove notability tags on articles about television show characters and episodes as long as this arbitration is live. Yes 4 0 0 0
TTN restricted TTN is banned from requesting or otherwise enacting deletion, redirection, or merge discussions about articles or project pages related to television show characters and episodes. This ban does not extend to merely participating in such discussions started by others. Breaches are to be met with blocks (capped at 1w for the first five and 1yr thereafter) and logged on the case page. Yes 9 1 0 0
Parties instructed and warned ArbCom tells the parties to stop it with the bickering and work collaboratively to develop a generally accepted and applicable approach to the topic area. No 9 1 0 0

Ehud Lesar block appeal

[edit]
  • Decided: Mar. 12, 2008
  • Abbrev.: ELBA
  • Type: Other
  • Scope: Ehud Lesar appealing a sockpuppetry block
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Ehud Lesar unbanned ArbCom and the Checkusers cannot prove beyond a shadow of a doubt that Ehud Lesar is a sockpuppet of AdilBaguirov or anyone else, and so vacate his block. He remains on notice of (and thus subject to) AA2 discretionary sanctions. N/A 9 0 1 0

Mantanmoreland

[edit]

(The following remedies refer to "the MM area", which encompasses naked short selling, Overstock.com, Patrick M. Byrne, Gary Weiss, and any closely related articles or discussions.)

  • Decided: Mar. 13, 2008
  • Abbrev.: MM
  • Type: Dispute
  • Scope: Conflict-of-interest editing centred around naked short selling and entities involved with same
  • CT?: No
Remedy name Remedy (in modern terms) Rescinded Enforceable? Sup Opp Abs Rcs
Editors instructed All editors, writ large, editing in the MM area are required to do so...
(1) from their main Wikipedia account,
(2) without using open proxies, anonymising services or other means of masking one's IP address,
(3) without engaging in any sort of advocacy or promotion, and
(4) after disclosing any connexion they have short of personally-identifying information to players in the real-life topic area.
Each of the affected articles' talk pages will have these restrictions listed as a talkpage notice.		 -- Yes 11 0 0 1
Article probation Provided the person being sanctioned has been alerted to this remedy's existence, users who disrupt the MM area may be summarily sanctioned at administrator discretion. Any sanctions issued this way (both directly and consequentially) must be logged on the case page. Nov. 19, 2015 Yes 11 0 0 1
Review of articles The underlying content dispute is remanded to the community, with ArbCom encouraging users who have no history in the MM area, no conflict of interest, and knowledge about the topic area to involve themselves in the process to make sure the articles are well-written and neutral in light of the revelations in the case. -- No 11 0 0 1
Mantanmoreland topic ban Mantanmoreland is indefinitely topic-banned from the MM area. -- Yes 9 0 0 1
Mantanmoreland instructed Mantanmoreland must edit Wikipedia from the Mantanmoreland account and no other, and cannot use any means of masking one's IP address while doing so. -- Yes 9 1 0 1

Franco-Mongol alliance

[edit]
  • Decided: Mar. 14, 2008
  • Abbrev.: FMA
  • Type: Editor
  • Scope: PHG's source fraud and original research in mediaeval history articles
  • CT?: No
Remedy name Remedy (in modern terms) Rescinded Enforceable? Sup Opp Abs Rcs
PHG restricted For the next year, PHG is topic-banned from articles in the mediaeval history and ancient history topic areas. Breaches are to be met with blocks (capped at 1w for the first five and 1yr thereafter) and logged on the case page. PHG Yes 8 0 0 1
PHG reminded PHG is reminded that content needs to be a fair and accurate summary of what the cited sources say. -- No 8 0 0 1
PHG encouraged PHG is encouraged to continue contributing to Wikipedia and Wikimedia projects in other ways, including by suggesting topics for articles, making well-sourced suggestions on talk pages, and continuing to contribute free-content images to Wikimedia Commons. -- No 8 0 0 1
PHG reminded: collaborative consensus PHG is reminded that Wikipedia operates on consensus and has little need or tolerance for "my way or the highway" types. -- No 8 0 0 1
PHG is required to provide a means for the Community to verify his sources.[sic] For the next year, PHG is required to either use sources widely available in English or have an ArbCom-approved mentor who can vet sources he does cite. In the case of a dispute over a citation, the mentor's opinion trumps PHG's. PHG Yes 8 0 0 1

Highways 2

[edit]
  • Decided: Apr. 07, 2008
  • Abbrev.: HW2
  • Type: Dispute
  • Scope: Disputes over WikiProject US Roads's scope and on the articles in its ambit
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Temporary Injunction All editors, writ large, are banned from editing WikiProject US Roads's scope, approach, and list of articles that fall under its purview as long as this case is active. Enforcement of this injunction is to be done by administrators with no connexion to the WikiProject or the locus of this case. Yes 4 0 0 1
Editors counselled All parties are reminded that walking away when you're getting frustrated is always an option if a discussion is starting to devolve. No 8 2 0 1
USRD members advised Members of WikiProject U.S. Roads are warned that they need to be able to support their claim that a pre-existing consensus exists by pointing to the discussions and debates where that consensus was established. No 7 0 0 1

September 11, 2001 conspiracy theories

[edit]

(As all remedies are imposition of a contentious topic declaration and standardisation updates to same, they will be merged into one for brevity.)

Remedy name Remedy (in modern terms) Rescinded Enforceable? Sup Opp Abs Rcs
Discretionary sanctions Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts pages and discussions about the September 11 attacks and related conspiracy theories as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log, and for the first year they can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly.
(This sanction was seen as redundant with AP2 and rescinded as a result.) 		Oct. 19, 2023 Yes 8 1 0 2

International Churches of Christ

[edit]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
TransylvanianKarl urged and instructed TransylvanianKarl is strongly encouraged to stop with the blind reverting and swot up on the English-language Wikipedia's standards and practices before continuing. It should be noted there is a language barrier here; TransylvanianKarl is hu-N and admitted he was having trouble understanding the relevant policies on en.wp. No 8 0 0 0
TransylvanianKarl restricted TransylvanianKarl must edit pages in the International Church of Christ topic area from that account and no other. Yes 8 0 0 0
Future disruptive editing Provided he has been warned beforehand, any administrator may sanction TransylvanianKarl if he is disruptive at their discretion. If this causes the situation to deteriorate or the situation is particularly egregious or intractible, any user may file a new Arbitration request provided 30 days have passed from this case's close. Yes 8 0 0 0
Assistance invited ArbCom encourages editors who can read/write Hungarian to help TransylvanianKarl understand the sanctions above and come to grips with en.wp's policies, including answering any questions he may have. N/A 8 0 0 0

Betacommand 2

[edit]
  • Decided: Apr. 13, 2008
  • Abbrev.: BC2
  • Type: Admin
  • Scope: Betacommand's overzealous enforcement of image policy, with and without bots
  • CT?: No

(As a post-case motion uses it, this summary will refer to Betacommand by his newer name Δ[v].)

Remedy name Remedy (in modern terms) Enacted Enforceable? Sup Opp Abs Rcs
Betacommand instructed Δ is banned from making personal attacks, hounding innocent editors, and having his bots deviate from the letter of their approvals. -- No[vi] 9 0 0 1
Betacommand and editors urged Δ is admonished for being snippy with good-faith questions from editors whose images he or his bot tags. He is also instructed to maintain an "opt-out" list for BetacommandBot to lessen the amount of unwanted and unnecessary pings. -- No 9 0 0 1
Editors advised Other editors are encouraged to participate in policy discussions related to the nonfree content policy and to challenge cases where actions were taken in error, but are also admonished for personalising the disputes and being abusive towards those attempting to enforce them in good faith, including bot operators. -- No 9 0 0 1
Community input The underlying content and policy disputes are remanded to the community, and particularly knowledgeable users familiar with scripting and botting on Wikipedia. -- N/A 9 0 0 1
Review and future remedies ArbCom reminds all participants that they reserve the right to revisit this situation if it doesn't improve. -- N/A 8 0 0 1
Modified by motion Δ is indefinitely topic-banned from any edit enforcing the non-free content criteria, broadly construed. At this point, Δ had already been placed under community sanctions banning him from running bots and placing him on civility parole. July 14, 2011 Yes 10 1 0 0

Strider12

[edit]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Strider12 banned Strider12 is sitebanned 1yr. Yes 9 0 0 0
Strider12 mentored When and if she returns after her ban, Strider12 will be provided with a mentor to help her get to grips with Wikipedia policy to a sufficient level that continued sanctions will not be necessary. No 9 0 0 0

Prem Rawat

[edit]
  • Decided: May 12, 2008
  • Abbrev.: PR
  • Type: Dispute
  • Scope: Persistent disruption on Prem Rawat
  • CT?: Dec. 20, 2012 - Oct. 10, 2023 (Motion)
Remedy name Remedy (in modern terms) Enacted Rescinded Enforceable? Sup Opp Abs Rcs
Article probation Any editor disrupting pages about Prem Rawat, broadly construed, may be summarily topic-banned from them (either individual pages or as a whole). Any bans (and blocks arising from same) are to be logged on the case page. -- Modified by motion Yes 9 1 0 1
Editors reminded ArbCom reminds editors who may have a conflict of interest with regards to Prem Rawat to reread the relevant policies. -- -- No 8 0 0 1
Modified by motion Article probation is rescinded and replaced with a contentious topic designation. Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts pages and discussions about Prem Rawat as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log, and for the first year they can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly.
Any sanctions from the probation that were still in force are automatically converted to discretionary sanctions and are bound by the standard appeal procedures for enforcement. 		Dec. 20, 2012 Oct. 10, 2023 Yes 11 0 0 0

Tango

[edit]
  • Decided: May 16, 2008
  • Abbrev.: Tng
  • Type: Admin
  • Scope: Tango's questionable and inappropriate blocks
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Tango desysopped Tango's administrator rights are revoked. They may regain them through a new, successful Request for Adminship or by appealing this remedy to ArbCom. N/A 7 2 0 2

CAMERA efforts on Wikipedia

[edit]
See also: Committee for Accuracy in Middle East Reporting in America § CAMERA campaign at Wikipedia
  • Decided: May 28, 2008
  • Abbrev.: PIL
  • Type: Other
  • Scope: Discretionary sanctions taken by administrators against an external conspiracy
  • CT?: No[viii]

(This case centres around the efforts of CAMERA to spin-doctor articles in the PIA area, and was kicked to ArbCom by editors enforcing PIA discretionary sanctions on accounts associated with them. Portions of the case were conducted in camera to avoid publicly connecting accounts to named people associated with CAMERA.)

Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Sanctions confirmed ArbCom confirms and endorses the various discretionary sanctions imposed by ChrisO, Future Perfect at Sunrise, and Moreschi to stymie the POV-pushing. N/A 8 0 0 0
General amnesty An amnesty is extended to everyone involved in CAMERA's campaign but not already sanctioned for their actions on-wiki. They are still considered to be aware of, and thus subject to, PIA discretionary sanctions. N/A 8 0 0 0
Community urged Any users who have information about similar external campaigns targeting Wikipedia are urged to forward [it] to the Committee for review. N/A 8 0 0 0
Hypnosadist admonished Hypnosadist is admonished for lack of professionalism and misrepresenting policy to users unfamiliar with Wikipedia. No 8 0 0 0

Footnoted quotes/Editing of Biographies of Living Persons

[edit]
  • Decided: June 16, 2008
  • Abbrev.: BLP
  • Type: Dispute
  • Scope: Disputes over interpretation of WP:BLP
  • CT?: Close - current

(All motions that merely update the CT templating are omitted.)

Remedy name Remedy (in modern terms) Enacted Enforceable? Sup Opp Abs Rcs
Special enforcement on biographies of living persons Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who posts unsourced claims about or concerning living/recently-departed people or who disrupts articles about same as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log, and for the first year they can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly. -- Yes 8 2 0 0
Alansohn restricted For the next year, Alansohn may be summarily blocked if he makes an edit judged to be incivil, a personal attack, or casting aspersions. Blocks are capped at 1wk for the first five (and 1mo thereafter) and must be logged at the case page/centralised log. -- Yes 8 0 0 0
Case renamed (January 2015) The case is renamed from "Footnoted quotes" to "Editing of Biographies of Living Persons" to clarify the breadth of its scope. Jan. 27, 2015 N/A 10 1 0 0

Homeopathy

[edit]
  • Decided: June 30, 2008
  • Abbrev.: HP
  • Type: Dispute
  • Scope: POV-pushing in support of homeopathy
  • CT?: Close - Nov. 30, 2014

(One motion that updates the CT templating will be omitted.)

Remedy name Remedy (in modern terms) Rescinded Enforceable? Sup Opp Abs Rcs
Discretionary sanctions Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts pages and discussions about homeopathy as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log, and for the first year they can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly.
(This remedy was seen as superseded by/redundant with PS and was rescinded.) 		Nov. 30, 2014 Yes 6 2 0 0
DanaUllman banned DanaUllman is sitebanned 1yr. -- Yes 9 0 0 0

Giovanni33

[edit]
  • Decided: July 06, 2008
  • Abbrev.: G33
  • Type: Editor
  • Scope: Giovanni33's relentless sock- and meatpuppetry
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Giovanni33 banned Giovanni33 is sitebanned 1yr. As he was (and still is) indefinitely community-banned, all this does is require him to appeal only thru ArbCom for the next year. No[ix] 9 0 0 0
Proxy accounts banned All accounts identified as likely sockpuppets or proxies of Giovanni33 in the findings of this decision, as well as any account subsequently identified by an administrator as a likely sockpuppet or proxy of him, are banned from Wikipedia until such time as the ban on Giovanni33 is lifted. No 9 0 0 0

Yorkshirian

[edit]
  • Decided: July 14, 2008
  • Abbrev.: YSH
  • Type: Editor
  • Scope: Yorkshirian's conduct overall
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Yorkshirian banned Yorkshirian is sitebanned 1yr. Yes 9 0 0 0

Geogre and William M. Connolley's administrative actions against Giano

[edit]
  • Decided: Aug. 22, 2008
  • Abbrev.: G-WMC
  • Type: Admin
  • Scope: Geogre's and William M. Connolley's administrator interactions with Giano
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Temporary Injunction Barring express permission from an Arbitrator, administrators are banned from blocking or unblocking Giano as long as this case is active. No 5 0 0 1
William M. Connolley and Geogre prohibited Both Connolley and Geogre are banned from taking any administrative actions with respect to Giano, including interceding in edit wars where he is a party (by protecting the page the edit war is on). No 7 0 1 1

Alastair Haines

[edit]
  • Decided: Sep. 11, 2008
  • Abbrev.: AH

(This case has been blanked as part of a remedy from a later Arbitration case. Three editors were placed on probation and 1RR, and are required to explain all reverts they make (barring obvious vandalism) on the affected page's talk page for 1yr; one of those three was also put under a civility parole. A one-way interaction ban was added in a post-case motion. This case has enforcement threads.)

Cla68-FeloniousMonk-SlimVirgin/The Omnibus Case

[edit]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Parties admonished and instructed The parties - Cla68, FeloniousMonk, SlimVirgin, JzG, and Viridae - are required to read all 20 principles and 7 findings of fact, go sit in a corner, and think long and hard about what they've done. No 9 0 0 0
Parties specifically instructed (This is the more-or-less the same as above, except as a bulleted list and in a much sterner grumpy-old-uncle "knock that shit off" tone.) No 9 0 0 1
Further review and sanctions ArbCom retains the right to revisit this case if the situation does not improve, but will not act on any requests to reopen/reexamine the matter for 30d to give things time to settle down and improve. N/A 8 1 0 1
Other editors counseled (This is more-or-less the same as Parties admonished and instructed except aimed at other parties to the disputes that gave rise to this case.) No 9 0 0 1
FeloniousMonk desysopped FeloniousMonk's administrator rights are revoked. He may get them back either through a new, successful Request for Adminship or by appealing this remedy to ArbCom. N/A 8 0 0 1
Duration of case acknowledged The Committee acknowledges the extraordinary duration of this case. Whilst there have been reasons for this to arise, an overall apology is due, and given.
The case was filed on May 16, 2008, and so lasted a little over four months from start to finish - of which remedies weren't considered until the case was already three and a half months old (Aug. 30, based upon the proposed decision page). The situation was such that a proposal to close the case with no action attracted a lot of comments on the case's workshop page, with the proposer arguing that the process had been "derailed". Part of the reason for the length is because another case had been merged into it - JzG and Viridae's at best tangentially-related dispute - which led to the Arbitrators being unprepared for the overwhelming amounts of work needed to reconcile two cases with similar behaviour but different motivations and loci into one case that could address both issues. Compared to other long cases (the five-and-a-half-month long SCI, particularly) the main reason this case ultimately was little more than wrist-slaps, a deopping, and a sigh of relief for Kirill Lokshin (the recusal) is because the case merger robbed it of any chance of clearly focusing on the issues leading to either dispute.		 No 5 1 2 1

Sarah Palin protection wheel-war

[edit]
  • Decided: Oct. 20, 2008
  • Abbrev.: SPWW
  • Type: Admin
  • Scope: Wheel-warring over protection levels on Sarah Palin
  • CT?: No[iv]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Parties instructed ArbCom again tells the parties to a case to read the sizeable lists of principles and findings of fact, then go off into a corner to think about what they've done. No 8 0 0 0
Jossi admonished Jossi is admonished for using his tools for wheel-warring, for actions going against the existing consensus, and in matters where he is a party, with a further warning that another incident like this puts his tools at risk. No 7 0 0 0
MZMcBride admonished MZMcBride " " " " " " " "-", " " " " " " ", " for blatantly disregarding Arbitration remedies. As with Jossi, he is warned another incident like this puts his tools at risk. No 7 0 0 0
Ongoing BLP discussion Since ArbCom cannot force policy onto Wikipedia, discussions on how to improve WP:BLP are remanded to the community. N/A 8 0 0 0

Abtract-Collectonian

[edit]
  • Decided: Oct. 29, 2008
  • Abbrev.: A-C
  • Type: Editor
  • Scope: Abtract's harassment of Collectonian[x] and Sesshomaru in spite of a community-imposed interaction ban
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Temporary Injunction For the duration of this case, Collectonian, Sesshomaru, and Abtract are all under mutual interaction bans (Abtract with both Collectonian and Sesshomaru), as was worked out by the community before the case. (In essence, ArbCom is endorsing the existing community sanction.)
On a somewhat related note, Abtract refused to participate in the case due to objecting to an Arbitration clerk cutting down his opening statement to the usual word limits. 		Yes 4 0 0 0
Abtract restricted Abtract may be summarily blocked if they make an edit judged to be incivil, a personal attack, or casting aspersions. They are also under a one-way interaction ban from Collectonian. Breaches are to be met with blocks (length left to administrator discretion) and logged on the case page. Yes 6 0 0 0
Interpretation of restrictions Any attempts by Abtract to game around the edges of his ban to continue to harass Collectonian (or anyone else) will be considered a breach of the ban. Yes 6 0 0 0
Collectonian urged Collectonian is urged to continue to avoid any unnecessary interaction with Abtract. No 6 0 0 0

SlimVirgin-Lar

[edit]
  • Decided: Oct. 30, 2008
  • Abbrev.: SV-L
  • Type: Functionary
  • Scope: Potential misuse of Checkuser by Lar
  • CT?: No

(This case's Evidence and Workshop phases were conducted in camera.)

Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Users reminded ArbCom admonishes the people who made a public hue and cry about the case rather than [use] suitable dispute resolution process[es] given the privacy implications. No 7 0 0 0
CheckUser operators reminded The Committee reminds all operators of the CheckUser tool that it is imperative that they make every effort to abide strictly by the Wikimedia Foundation Privacy Policy at all times.[link added] No 7 0 0 0

Kuban kazak

[edit]
  • Decided: Dec. 05, 2008
  • Abbrev.: Kbn
  • Type: Editor
  • Scope: Kuban kazak's harassment of another editor
  • CT?: No[xi]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Kuban kazak banned Kuban kazak is sitebanned 1yr. Yes 7 0 0 0

Cold fusion

[edit]
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Pcarbonn topic-banned For the neat year, Pcarbonn is topic-banned from the cold fusion topic area. Breaches are to be met with blocks, capped at 1w for the first five (and 1mo thereafter) and logged on the case page. Yes 7 1 0 0

Piotrus 2/Eastern European disputes

[edit]
  • Decided: Dec. 23, 2008
  • Abbrev.: EED
  • Type: Omnibus
  • Scope: Continued issues in the Eastern Europe topic area since EE
  • CT?: No[xiii]
Remedy name Remedy (in modern terms) Enacted Enforceable? Sup Opp Abs Rcs
Alden Jones mentored Alden Jones will be given a mentor who will help him understand and comply with Wikipedia policies. -- No 9 0 0 0
Alden Jones restricted Alden Jones is indefinitely under 1RR/week and must explain every revert he makes (except for obvious vandalism) on the talk page of the affected article. Breaches are to be met with blocks, capped at 1w for the first five (and 1yr thereafter) and logged on the case page. -- Yes 7 0 0 0
Boodlesthecat banned Boodlesthecat is sitebanned 1yr. -- Yes 7 0 0 0
Deacon of Pndapetzim admonished Deacon of Pndapetzim is admonished to avoid edit-warring.[userlinks template omitted] -- No 6 2 0 0
Greg park avenue banned Greg park avenue is sitebanned 1yr. -- Yes 7 0 0 0
Irpen restricted (Iban) Irpen and Piotrus are being urged to accept a mutual interaction ban on pain of ArbCom issuing a formal one. -- No 8 1 0 0
Irpen restricted (1RR) Irpen is indefinitely under 1RR/week and must explain every revert they make (except for obvious vandalism) on the talk page of the affected article. Breaches are to be met with blocks, as detailed in Alden Jones restricted. -- Yes 6 2 0 0
Lokyz admonished Lokyz is admonished to avoid edit-warring.[userlinks template omitted] -- No 6 0 0 0
Lokyz restricted Lokyz may be summarily blocked if he makes a comment judged to be incivil, a personal attack, or casting aspersions. Blocks are administered as detailed in Alden Jones restricted. -- Yes 6 0 0 0
Piotrus urged (See Irpen restricted (Iban)) -- No 8 0 0 0
Piotrus cautioned Piotrus is warned against using his administrator tools in a dispute where he is a party. -- No 7 1 0 0
Piotrus admonished Piotrus is admonished to avoid edit-warring.[userlinks template omitted] -- No 8 0 0 0
Poeticbent mentored Poeticbent will be given a mentor who will help them understand and comply with Wikipedia policies. -- No 7 0 0 0
Relata refero admonished Relata refero is admonished to avoid edit-warring.[userlinks template omitted] -- No 7 1 0 0
Editors reminded ArbCom reminds editors that Wikipedia cannot, and should not be used to, resolve the real-world issues that give rise to these ethnopolitical disputes, and should only report on the issues and incidents neutrally. -- No 7 0 0 0
Editors counseled ArbCom encourages editors who are Editing While Angry that it's often better to just walk away and spare yuour sanity rather than fall deep into the rabbit hole of personalising the dispute and adopting an extreme tribalist mindset. -- No 7 0 0 0
#wikipedia-en-admins users reminded ArbCom reminds the administrators who use the #wikipedia-en-admins channel on Freenode (now Libera) that discussions on IRC are by default off-wiki and cannot be used as a substitute for on-wiki discussions when determining consensus, blocking users that aren't being blatantly disruptive, or otherwise taking controversial or likely-to-be-controversial administrative actions. -- No 4 0 5 0
Arbitration enforcement reform Recognising that Arbitration enforcement is not in a good state - especially with discretionary sanctions now a factor - ArbCom will open a formal request for comment to consider changes in how enforcement should be handled going forward. -- N/A 8 0 0 0
Content dispute resolution reform Further to the above, since much of the issues that led to this case are intractible content disputes that the standard processes cannot reasonably resolve, ArbCom will open a community discussion to determine how content dispute resolution processes can be improved. -- N/A 8 0 0 0
Arbitration guides Following the conclusion of this case, the Committee will publish guides to presenting evidence and using the workshop page. -- N/A 8 0 0 0
Case rename The case is renamed from "Piotrus 2" to "Eastern European disputes" to clarify the breadth of its scope. Jan. 02, 2009 N/A 12 0 1 0

Footnotes

[edit]
  1. ^ Passed as part of a package of motions intended to eliminate unused contentious topic regimes.
  2. ^ 11 supports for the CT declaration and 10 supports for the separate appeal procedure
  3. ^ Since has become a section on the main IRC page
  4. ^ a b Locus of case falls entirely into AP2.
  5. ^ Pronounced "delta"
  6. ^ This case lacks any enforcement provisions.
  7. ^ Locus of case falls entirely into the AB area
  8. ^ Locus of case falls entirely into the PIA area.
  9. ^ As he is community-banned, AE threads are not needed if there is a question over an account's connexion to him or a need for an immediate block.
  10. ^ User has invoked their right to vanish.
  11. ^ Locus of case falls mainly into the EE area
  12. ^ Locus of case falls entirely into the PS area.
  13. ^ Locus of case falls entirely within EE area
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Jéské_Couriano/ArbCaseSum/08&oldid=1255927169"