Wikipedia:Arbitration/Requests/Clarification and Amendment

Use this section to request clarification or amendment of a closed Arbitration Committee case or decision.

• Requests for clarification are used to ask for further guidance or clarification about an existing completed Arbitration Committee case or decision.
• Requests for amendment are used to ask for an amendment or extension of existing sanctions (for instance, because the sanctions are ineffective, contain a loophole, or no longer cover a sufficiently wide topic); or appeal for the removal of sanctions (including bans).

To file a clarification or amendment request: (you must use this format!)

1. Choose one of the following options and open the page in a new tab or window:
   • Click here to file a request for clarification of an arbitration decision or procedure.
   • Click here to file a request for amendment of an arbitration decision or procedure (including an arbitration enforcement action issued by an administrator, such as a contentious topics restriction).
2. Save your request and check that it looks how you think it should and says what you intended.
3. If your request will affect or involve other users (including any users you have named as parties), you must notify these editors of your submission; you can use {{subst:Arbitration CA notice|SECTIONTITLE}} to do this.
4. Add the diffs of the talk page notifications under the applicable header of the request.

Clarification and Amendment archives
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126

This is not a discussion. Please do not submit your request until it is ready for consideration; this is not a space for drafts, and incremental additions to a submission are disruptive.

Arbitrators or Clerks may summarily remove or refactor discussion without comment.

Requests from blocked or banned users should be made by e-mail directly to the Arbitration Committee.

Only Arbitrators and Clerks may remove requests from this page. Do not remove a request or any statements or comments unless you are in either of these groups. There must be no threaded discussion, so please comment only in your own section. Archived clarification and amendment requests are logged at Wikipedia:Arbitration/Index/Clarification and Amendment requests. Numerous legacy and current shortcuts can be used to more quickly reach this page:

Clarification and Amendment archives
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126

Arbitration Committee proceedings

• recent changes
• purge this page
• view or discuss this template

Case requests

Request name	Motions	Initiated	Votes
Persistent WP:IDONTLIKEIT behavior in WP:NCROY discussions		10 May 2024	0/4/0

[edit]

Open cases

Case name	Links	Evidence due	Prop. Dec. due
Venezuelan politics	(t) (ev / t) (ws / t) (pd / t)	20 Apr 2024	04 May 2024

[edit]

Recently closed cases (Past cases)

Case name	Closed
Conflict of interest management	13 Apr 2024
Mzajac	7 May 2024

Clarification and Amendment requests

Request name	Motions	Case	Posted
Clarification request: Article titles and capitalisation	Motion	(orig. case)	16 January 2017
Clarification request: Palestine-Israel articles 3	none	(orig. case)	21 January 2017
Clarification request: Palestine-Israel articles 3 (2)	none	(orig. case)	10 February 2017

Arbitrator motions

No arbitrator motions are currently open.

Requests for clarification and amendment

Clarification request: Article titles and capitalisation

Initiated by SMcCandlish at 15:57, 16 January 2017 (UTC)

Case or decision affected

Article titles and capitalisation arbitration case (t) (ev / t) (w / t) (pd / t)

List of any users involved or directly affected, and confirmation that all are aware of the request:

• SMcCandlish (talk · contribs · deleted contribs · logs · filter log · block user · block log) (initiator)

Confirmation that all parties are aware of the request

This isn't about any parties in particular. While Thryduulf is mentioned (and pinged), I make no allegations about the admin's judgement or actions (I agree with his scope determination, though not with his desire to apply it to the party at the ANI in question.)

Statement by SMcCandlish

Please clarify whether WP:ARBATC's discretionary sanctions rule (which may need to be clarified) applies to all discussions about "the English Wikipedia Manual of Style and article titles policy, broadly construed" including WP:Requested moves discussions or not. I think that they must, since these are the distributed locus of the vast majority of title and style disputes on Wikipedia, as well as of most of the aspersions cast and other incivility about those things. The majority of {{DS/alert|at}} templates I've delivered have been in response to AGF, NPA, CIVIL, and ASPERSIONS problems in RMs.

Arb Thryduulf at ANI very recently said he would, if not INVOLVED, have discretionarily sanctioned someone for alleged RM-related disruption, under ARBATC specifically. However, I'm also aware of at least one previous case or ARCA in which it was strongly argued but perhaps not formally decided that RM was somehow exempt from ARBATC. I would urge that ARBATC's broad construal of scope include RM, or there was little point in enacting it. There's very little disputation that would trigger ARBATC at places like WT:AT or WP:MOS, and only very sporadically about article content, but almost daily about moves. If anything, that problem has notably worsened over the last two years, probably emboldened by lack of DS enforcement, even as "style" dispute has receded elsewhere, system-wide. While a large proportion of requested moves involve a "style" matter (WP:MOS-connected or not), even those that don't – about things like WP:PRIMARYTOPIC, disambiguation, WP:CONCISE, etc. – are still within the WP:AT remit. I.e., if it's at RM, it is about "article titles policy, broadly construed" by definition (and also often about the MoS).

The confusion arises because the exact wording is unfortunate, and easily WP:GAMEd: "Standard discretionary sanctions are authorized for all pages related to the English Wikipedia Manual of Style and article titles policy, broadly construed." The gaming is that while WP:RM per se is obviously within the scope of article titles policy, the RM discussions themselves take place on individual article (or non-article) talk pages, and they aren't technically "pages related to" AT or MoS. The intent of the provision was clearly to curtail style-and-title conflict, and it fails to do this as long as it is actively gameable as inapplicable to nasty behavior in RMs, or (more often) admins are uncertain they can enforce the DS in an RM discussion and so do nothing, or perhaps wag a finger. I rely on our principle (mentioned at GAMING, WP:LAWYER, WP:CONSENSUS, and I think WP:PROCESS and WP:POLICY) that WP's rules are interpreted and intended to be interpreted as to their intent and spirit, and their role in the project as facilitators of getting the work done, not with any eye to finding loopholes and escape clauses to exploit. There seems no "danger" in clarifying that the scope of the DS includes RM discussions, since everyone gets at least one {{Ds/alert}} before DS can apply to them anyway. I.e., anyone being a WP:JERK in RM gets away with it at least once until brought up to speed that it's not acceptable. And the behaviors in question aren't acceptable anyway, per the policies and behavioral guidelines the DS would be used to enforce.

The problem can be fixed by amending "all pages related to" to "all discussions related to". This would also have the side benefit of curtailing ARBATC-scope verbal abuse in user talk, ANI, and other venues, where it is also frequent. I believe that a great deal of title-and-style strife will evaporate, replaced by civil, reasoned discussion that focuses on policy and sources instead of personalities and WP:GREATWRONGS / WP:TRUTH grandstanding, if civility policies are more actively enforced in RMs. All it takes is a one-word, common-sense amendment. It would also be more consistent with other DS cases, which don't have special exemptions for RM or any other particular forum, but apply to the topic generally.

Responses to commenters

@Andrew Dingley: The fact that an admin's DS-related comment in a particular case conflicts with previous admin comments in the other direction is why I seek clarification is neither here nor there. Your conspiracy theory cannot possibly be true; while I agree with Dicklyon about many things, we disagree about others. I'm seeking clear applicability of DS to RM given doubts about the matter, even though an admin in question wanted to apply them to a person you presume to be my lock-step ally. All of this has been long on my mind, since reading the ARCA request that RGloucester re-identified; recent events simply bring it to mind afresh. Instead of making up fantasies about my motives without any evidence, actually read what I've written and take it at face value. PS: You complaining about and misinterpreting a routine notice isn't other editors accusing me of harassment [that entire thread was hatted quite rapidly, too].  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  21:38, 16 January 2017 (UTC)

@Exemplo347: It has nothing to do with you either, but with a conflict between what Thryduulf has said and what was said in the ARCA that RGloucester dug up [and various other admins' conflicting interpretations]. This couldn't be about you since no DS would be applying to you for anything you've posted, those things having been posted before you received a Ds/alert. As I said, the majority of the uncivil style/titles disputation is at RM not elsewhere, and the majority of Ds/alerts I leave relate to them. Not everything is about you.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  21:41, 16 January 2017 (UTC)

@BMK: I'm not making a complaint, against anyone [I'm studiously avoiding doing so; I don't even expect Thruduulf to recuse, but to give his views about why DS should apply to RM]. I'm asking for a scope clarification, because this question of ARBATC's actual scope keeps coming up for several years now, and different answers keep being given, including by Arbs. The ANI being referred to simply reminded me that this needs to be settled one way or the other. I'm really not very devious. I would think this is pretty obvious after over a decade here. I'm very direct and just call it like I see it, without much regard for "wikipolitics" (in fact, I like to short-circuit wikipoliticking as much as possible, because I think it's corrosive to the community and project, increasingly so as the editorial and admin pools condense. Or you can continue to make assumptions about my motives.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  07:48, 17 January 2017 (UTC)

@Calton: Mischaracterizing editors who disagree with you as like unto religious zealots is precisely the kind of personalization of style disputes that WP:ARBATC#All parties reminded is intended to address. Update: So was your "I feel pretty safe in ignoring anything you say as being wrong, self-serving, or intellectually dishonest" assumption of bad faith [1]. Your response here, again indicating a false belief that {{Ds/alert}} is a threat/warning about misconduct, not a notice of DS scope applicability, just proves my point further at WT:ARBCOM#Please fix the wording of Template:Ds/alert.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:30, 17 January 2017 (UTC) Updated 16:47, 17 January 2017 (UTC)

@Dicklyon: Agreed, though I'm primarily concerned about more unicvil statements that most of those quotes (e.g. referring to other editors as "obnoxious and ... twatty", "idiots", "fanatical enforcers", plus comments like "I don't give a shiny shit about civility when it comes to people like you"). This kind of behavior is common across all "style" disputes (MOS, AT, infoboxes, citation formatting, etc.), and would not be tolerated if it were about Palestine or GMOs or race.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  18:34, 17 January 2017 (UTC)

@Thryduulf: Sorry, I have not kept track of who's on or off ArbCom lately. :-) I generally agree strongly with your interpretation, yet ask you the same question I asked Euryalus, below. ARBATC is ARBATC, not "ARBMOS". Nothing has ever limited to the scope of ARBATC to MoS discussions and doing so here would actually be a much more major change in ARBATC scope and interpretation than applying ARBATC (to its full AT and/or MOS-related scope) regardless of venue including RM, as I've requested, per "broadly construed". While MoS-related incivility was mostly what I've been thinking of, people sometimes cross the line about other AT-related stuff, especially PRIMARY and disambiguation squabbles (the more the topic in question attracts fannishness, the higher the likelihood of hostile territorialism).  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  05:19, 18 January 2017 (UTC)

Responses to Arbs

@Newyorkbrad: I agree the level of disputation/striving is much greater at ANI, especially given the frequency with which it involves new editors (RM rarely does). But the level of incivility of a very predictable and consistent and continually ongoing kind, from particular parties, is much more apparent at RM, and has been on the increase for some time, turning into a sort of "this guideline will be applied over my dead body", RM-after-RM-after-RM tendentiousness. It could be another ArbCom case, but that would seem like a bunch of pointless drama if one one-word change to the original decision could permit admins to just deal with it at AE.  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  21:47, 16 January 2017 (UTC)

@Drmies: I'm loath to provide example diffs, because the kind I have in mind – in the AGF/CIVIL/NPA/ASPERSIONS vein especially, like labelling other editors "obsessive nutters" and implying various specific destructive or unhinged motives to them – would essentially be seen as trying to make disciplinary cases against specific editors (and might be likely to turn into them whether that were my intent or not). If I'd thought that route would be productive, I would have just opened an RfARB and named a bunch of parties [including all of the non-Arbs who have commented here so far as of 16:52, 17 January 2017 (UTC)]. I did consider it, but it seemed likely to generate heat without light.

@Euryalus: Why would that MoS line be drawn, when ARBATC is about disputes involving the article titles policy or the MoS (both are not required at once)? RM's are always about article titles, so they would always be under the "AT" in ARBATC. The original case had as much to do with MoS-unrelated AT conflict as MoS. The only block I've ever received was an ARBATC DS action for alleged disruption of RM a few years ago. So, DS have definitely been applied to RM before.
[I dispute the allegation behind the block, made by an admin who did not look into the background of the matter and just picked one side to muzzle – but the block was so short it was not effectively appealable; by the time AN concluded I had to refile at AE or ARCA, it was too late. The moves under discussion later went the way I had proposed. Later, the same admin tried to topic ban me, again under ARBATC, and again to silence one side of an equally heated debate, and derailed an ongoing ANEW in the process; AN retroactively voided his action, and the report I'd been making at ANEW was later taken seriously. Same admin was RfARBed around this time last year, with more complainants than I've ever seen with grievances against a single admin, though action was not taken at that time, on a technicality.]
I would like to have that block declared invalid if ARBATC is held to not apply to RM, since that "scarlet letter" has repeatedly been held against me in a punitive fashion. PS: I agree that different regimes of DS should be normalized into something consistent.

Newyorkbrad: If the onus is on me as the requester to make the case for this "expansion" (in my view, clarification) of the scope, I would add to what I've said already:

• The gist of the concerns, as expressed by someone above (and it seems consistent with comments in the old ARCA) is a "surprise ArbCom sanction" and "effectively plac[ing] thousands of pages under an ArbCom sanction". But that's doubly inaccurate.
  • There's nothing "surprise" about it if you must receive a Ds/alert before any DS can be applied; and AE tends not to act in applying DS after such a warning anyway, unless the case is egregious or it's a multi-time repeat problem after the Ds/alert. The number of editors likely to be affected by DS would probably be countable on a single hand, even a few years later, but the strife level should drop notably just from AE issuing a few admonitions.
  • It would not be placing "pages" under DS; this would have no effect on any discussion on any talk page unless that discussion in particular were a) about article titles or the MoS and b) rife with disruptive or uncivil behavior (which are against policy to begin with).
• One could stipulate that DS/alerts delivered before the scope clarification don't count (though this would be inconsistent with a previous ARCA decision that these notices cannot be rescinded or invalidated because they are just notices of scope, not conduct accusations or warnings).
• Finally, "broadly construed" has no applicable meaning if ARBATC is held to apply only to discussions at WT:AT, WT:MOS and the talk pages other naming convention and MoS sub-guidelines; that's narrowly construed by definition. The clear intent of that wording was to construe the scope as covering title and style discussions broadly. Even if I'm misreading the original intent, it seems obvious that extending, if you like, the scope to AT/MoS "discussions", rather than "pages", would have a civility-reinforcing effect at little if any cost.

 — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  16:25, 17 January 2017 (UTC)

Opabinia regalis: So, what, the current roiling pot of title- and style-related incivility and disruptive battlegrounding is going to continue forever, and worsen when people realize they're immune to DS if they do it at RM or otherwise away from WT:AT and WT:MOS? Are we supposed to open a new RfARB every time?  — SMcCandlish ☺ ☏ ¢ ≽^ʌⱷ҅_ᴥⱷ^ʌ≼  21:56, 18 January 2017 (UTC)

Statement by Andy Dingley

Of course this isn't "not about any parties in particular", it's a direct reaction to an ANI thread, WP:Administrators' noticeboard/Incidents#Page move ban, seeking a TBAN on Dicklyon (talk · contribs) for disruptive and over-simplistic pushing of a style guide over objectively sourced external uses with capitalisation. SMcCandlish's own behaviour and harassment of other editors has been questioned in the same thread. Andy Dingley (talk) 17:13, 16 January 2017 (UTC)

Statement by RGloucester

The relevant past ARCA request that SMcCandlish said he could not find is here. The conclusion there was that these DS only apply to guideline and policy pages related to the MOS and AT. RGloucester — ☎ 18:42, 16 January 2017 (UTC)

• To the honourable members of the Arbitration Committee: Now that various individual arbitrators have stated a position on this matter, and given that there seem to be mixed messages apparent in their responses, perhaps the Committee could decide the scope of these sanctions together, with clarity, and publish an official clarification in the form of a motion. As it is now, it is quite clear that everyone has a different definition of how these sanctions should apply. That type of ambiguity should not be present in a DS regime. It isn't fair to editors, nor to administrators who must attempt to enforce such sanctions. I'm asking this with sincerity. The reason this issue has come up again is because the last clarification request, which I submitted, was essentially ignored. If the DS regime is meant to apply only to policy/guideline-type pages in the project space, then publish a motion to that effect. Likewise, if the scope is different, and includes RM discussions or whatever. Please do this, for the good of the encylopaedia. RGloucester — ☎ 19:58, 17 January 2017 (UTC)
• As I said above, it would be greatly appreciated by everyone if the Committee would pass a formal motion of clarification so that the scope of these sanctions is clear to all parties. This doesn't seem like a particularly complex matter, and it is one that only the Committee can address. Please do so. Letting this languish like the last clarification motion will only lead to further submissions at ARCA. RGloucester — ☎ 17:42, 30 January 2017 (UTC)

Statement by Exemplo347

I believe this to be in response to something I said to SMcCandlish, when he gave me an ArbCom notice for a page that was not under any ArbCom sanction and I told him I'd be ignoring it on that basis. I'm glad to see, from reading the relevant discussion, that the interpretation isn't as broad as SMcCandlish thinks it is - it would have effectively placed thousands of pages under an ArbCom sanction without any justification. I'd like to call upon SMcCandlish to remove any ArbCom notices he has mistakenly posted on user talk pages, and he should leave apologies in their place. Regards Exemplo347 (talk)

Further note: Interpreting the decision as suggested above by SMcCandlish would involve a lot more than just "changing one word" - like I've said, it will affect thousands of pages, putting every single discussion that involves any Manual of Style related issue under some sort of surprise ArbCom sanction that can be deployed by editors determined to press home their point. It will be a massive, sweeping change if it is decided that the ArbCom decision really IS that wide. This definitely isn't a simple case of changing a few words and sending us on our way. Exemplo347 (talk) 22:34, 16 January 2017 (UTC)

This appears to be a huge loophole that should be closed definitively. If a page is under an ArbCom sanction it should be correctly labelled on its talk page, and those that aren't marked as such should be implicitly not seen as being under ArbCom sanctions. Leaving it up to the interpretation of editors clearly isn't working. Exemplo347 (talk) 10:32, 17 January 2017 (UTC)

• Question So, is this issue going to be allowed to stagnate? There's a loophole that you could fly a 747 through & it needs to be rectified - it's no exaggeration to say that there could be hundreds of talk page discussions affected by an unintended, wide ranging scope that doesn't match any other ArbCom-related issue. Exemplo347 (talk) 19:37, 25 January 2017 (UTC)

Statement by Beyond My Ken

A couple of very quick points:

• SMcandlish's inquiry is clearly not a general one, but is obviously related to this ANI complaint about Dicklyon, in which SmCandlish has been active;
• The complaint against Dicklyon centers around an issue of capitalization, which is most definitely a MoS issue, and is specifically related to Dicklyon making controversial changes without using the RM process designed for such changes;
• This appears to me to be, as Andy Dingely wrote on AN/I, a case of SMcCandlish inappropriately forum shopping. I would urge that this complaint be shut down in favor of the AN/I complaint coming to fruition. If, at that time, SMcCandlish wishes to open a further complaint elsewhere, that would be fine. Beyond My Ken (talk) 05:55, 17 January 2017 (UTC)

Statement by Calton

Based on this ludicrous DIscretionary Sanctions warning that User:SMcCandlish left in response to this edit, I'd say that it's not just forum-shopping, but a lack of actual understanding of discretionary sanctions in general (and of this one in particular) which should lead to this request being rejected and User:SMcCandlish trouted with all due speed. --Calton | Talk 10:57, 17 January 2017 (UTC)

I notice that the fifth item Dicklyon quotes is mine. I also notice that he doesn't mention that it's a direct echo of SMcandlish's own rant, I have to wonder just what the hell it takes before it sinks in that WP has its own style manual, title policy, and naming conventions (and history of precedent in working out their interaction). How many chest-beating, territorial threat displays have to have cold water dumped on them... But I'm guessing some rants are more equal than others and are A-OK. --Calton | Talk 00:40, 18 January 2017 (UTC)

Statement by Dicklyon

I don't know if the DS was intended to apply to discussions invoking anti-MOS rants, but if so then the personalization and MOS-related mud slinging in the linked AN/I case would appear to make the warning relevent to participants who attacked me and the MOS as a unit:

• The MOS:CAPS (and MOS:everything else) army have driven enough editors who were far more productive than them away from Wikipedia
• Dicklyon just doesn't see this, he thinks all text strings must conform to some arbitrary MOS rule, no matter the context or consensus.
• I agree with Black Kite's impressions regarding the negative effect of the overly-pedantic MOS editors.
• that this thread exists is reason enough to show that Dicklyon's behaviour is disruptive
• ... simply a case of blindly following MOS (almost always a bad thing), ...
• I have to wonder when it will sink in that the MOS is a guideline and not a religious doctrine and that people like you and Dicklyon aren't its High Priests and Defenders of the Faith?
• it's high time that admins start to block editors who attempt to enforce MOS guidelines as if they were mandatory, which they are not

This was all posted as alternatives to saying anything that I actually did that was controversial, which I have repeatedly asked for there. It is as if some set of editors think that changes that bring things into closer conformity with the MOS are inherently controversial, even if very few get challenged. The inability of my accusers to say what edits of mine they would consider controversial, and this resort to MOS bashing instead, is rather infuriating, and I think that SMcCandlish meant to get them to think about that, even if he denies the warning was placed in response to any specific posts. Dicklyon (talk) 16:48, 17 January 2017 (UTC)

Response to Calton on the fifth one (which is now the sixth one since I added one): yes some MOS-related rants are more equal than others. These are ones that "attacked me and the MOS as a unit", as I said above. There was no call for you to respond to SMcCandlish's by attacking me with yours, even if his was meant to defend me. I have made no pretense of being anything like a "High Priest and Defenders of the Faith", and consider your comment a baseless slur, which matters a lot to me since it was in an AN/I section about me. It appears that you had no actual beef with me, but decided to attack me anyway, personally. That's why I listed your remark here. Dicklyon (talk) 00:07, 19 January 2017 (UTC)

Statement by Thryduulf (re article titles)

Firstly a quick clarification: I'm not an arbitrator, only a former one (and the relevant case here predates my time on the Committee). Also the ping didn't work (for whatever reason).

It has been my impression that discussions related to the manual of style, in whatever venue, are covered by the ARBATC DS authorisation, and that at least one editor has been previously sanctioned regarding their editing of requested moves (possibly Born2cycle but I don't have time to check right now). This I think would tally with Euryalus's feelings that the DS apply to RM discussions where the manual of style is a principle issue (e.g. whether railway line articles should be at "X Line" or "X line" per WP:MOSCAPS) but not to move discussions for other reasons (e.g. that currently happening at Talk:Revolution (Beatles song)). Thryduulf (talk) 19:14, 17 January 2017 (UTC)

@Opabinia Regalis: Determining the scope is very easy - if the rationale given for the move is to conform to a MoS guideline (often, but not exclusively, capitalisation) or the manual of style guidelines are used as a rationale to oppose a proposed move then it is within the scope of the DS. Communicating this should be very simple - (a) notify the MoS regulars via MoS talk page post(s), and (b) notify the participants of the discussions where it is relevant, most easily by a template similar to the ones that are placed on article pages. I do not see how this would be a massive expansion in either scope or intended scope.

@all arbitrators: Given though that we have arbitrators coming to exactly opposite interpretations of what the intent was and the scope currently is, I have to echo RGloucester's call for a formal clarification motion. Thryduulf (talk) 01:39, 18 January 2017 (UTC)

@Opabinia regalis: just fixing the ping. Thryduulf (talk) 01:40, 18 January 2017 (UTC)

This seems to have stalled a bit, so please could we have a formal clarification about what the scope actually is - this section has some pretty clear evidence that it is needed. Thryduulf (talk) 02:02, 25 January 2017 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

Article titles and capitalisation: Clerk notes

This area is used for notes by the clerks (including clerk recusals).

Article titles and capitalisation: Arbitrator views and discussion

• I've just taken a look at the proposed decision page in the original case (which is where arbitrators comment on the principles, findings, and remedies as they cast their votes), and it appears clear that the intent at the time of the case was to apply DS to discussions relating to the policy and guidelines pages themselves, not to individual article and talk pages. The specific question of whether the DS would apply to a move request discussion was not raised or considered. These DS have been in place for almost five years and I'd be interested in whether they have been invoked in that context before, but from what has been posted so far it looks like the answer is no. Whether the scope of the DS should be extended to include every RM discussion is a different question, and the burden of persuasion is on those seeking the change. I'm aware from various AN/ANI threads that there have been flare-ups in this area, including at least one that is ongoing, but would one say that the typical contested RM discussion is more contentious than, say, the typical contested deletion discussion? Newyorkbrad (talk) 19:29, 16 January 2017 (UTC)
• Reading over the PD I see NYB's point, and I think it's in the spirit of the decision to have DS apply to discussions. What's interesting in Wikipedia:Arbitration/Requests/Case/Article_titles_and_capitalisation/Proposed_decision#Discretionary_sanctions is a short bit of discussion between AGK and Courcelles, though that didn't extend into the wording that's being discussed here. I've seen a few RM discussions in the last years, and none that I recall were derailed or devolved into chaos and incivility because of these specific concerns--but that may not mean much. I do not in principle disagree with the proposal (or a similar proposal) though I am interested in seeing just a few examples to prove the need for it. Drmies (talk) 23:17, 16 January 2017 (UTC)
• From a reading of Courcelles' comment at the PD, and also from what is hopefully a commonsense interpretation, the DS seem intended to apply to applicable discussions where MOS issues were the central theme. In this instance the DS would apply to an RM discussion only where the principal issue in that discussion was directly related to the MOS. The DS would not apply to other RM discussions, akin to the way topic bans apply to parts of articles directly related to that topic, but not necessarily to every other part of the same article. That's an interpretation for this ARCA; on a related note we will one day need to consider the advisability of so many DS regimes, collectively applied to so many WP pages. -- Euryalus (talk) 04:38, 17 January 2017 (UTC)
• My take is that DS would apply if the crux of the issue with the name change of an article was directly related to capitalization. Cas Liber (talk · contribs) 19:36, 17 January 2017 (UTC)
• Hmmm. I expected this to be an obvious one - it seems fairly clear to me that the intended scope was discussions on the MOS pages (and related policies, etc), not discussions about applications of the MOS in individual cases. I think the latter interpretation would vastly expand the scope of DS in a way that is nearly impossible to apply objectively (how do you decide when a discussion is "directly" related?) and similarly difficult to communicate to editors who are not regular participants in the RM process. Providing such an expansion as a de facto response to a specific incident involving a specific editor would be an overreaction. Opabinia regalis (talk) 00:50, 18 January 2017 (UTC)
• Looking back at the workshop, it appears Guerillero introduced the central language around this remedy and it was intended to prevent "MOS pages from being a battleground". On the PD talk, AGK commented, "the reference to "MOS" is a drafting error; when we say MOS, we mean WP:TITLE". The wording wasn't corrected to make this distinction, so it was either expanded to encompass and effectively seek to counter a wide range of MOS incidents, or it was simply missed. As it's written now, it states all MOS pages and WP:TITLE. I would say this ambiguity still narrows it down to the Wikipedia space and principally discussions pages, but whether it's confined to WT:MOS and WT:TITLE was not explicitly expressed. It seems to me, if the nucleus of the RM discussion was MOS or TITLE related, then I can easily see how someone could interpret these DS as being applicable. The fact that MOS is so broad is somewhat troubling because it potentially casts this DS net very wide. Mkdw ^talk 06:07, 19 January 2017 (UTC)
• I agree with Opabinia regalis that this should obviously not apply to individual move discussions. Looking at Mkdw's point just above, I interpret this to refer to the MOS with respect to titles and capitalization only. I read "to the English Wikipedia Manual of Style and article titles policy," as a single phrase. If we need to expand this further, we would need to discuss it. In fact, at the AfDs on Infoboxes, we made specific provisions for that part of the MOS. DGG ( talk ) 22:48, 19 January 2017 (UTC)
• I also don't see this as applicable to move discussions, particularly with no evidence to suggest that there has been a problem related to this PD. Doug Weller talk 15:28, 26 January 2017 (UTC)

Motion: Article titles and capitalization

In remedy 4.2 of the 2012 Article titles and capitalisation case, standard discretionary sanctions were authorized for all pages related to the English Wikipedia Manual of Style and article titles policy, broadly construed. By way of clarification, the scope of this remedy refers to discussions about the policies and guidelines mentioned, and does not extend to individual move requests, move reviews, article talk pages, or other venues at which individual article names may be discussed. Disruption in those areas should be handled by normal administrative means.

Enacted: Kevin (aka L235 · t · c) 03:15, 11 February 2017 (UTC)

Support

1. Opabinia regalis (talk) 05:50, 2 February 2017 (UTC)
2. This is my understanding of the existing decision. If a pattern emerges of serious problems in these discussions, an amendment request could be filed—but I very sincerely hope that won't be necessary. Newyorkbrad (talk) 17:29, 2 February 2017 (UTC)
3. Doug Weller talk 19:06, 2 February 2017 (UTC)
4. This was the intent at the time. Kirill Lokshin (talk) 21:39, 2 February 2017 (UTC)
5. I find it less easy to judge the "intent at the time", but I prefer to play it conservatively and not extend until an amendment is proposed--or, "per NYB". Drmies (talk) 04:54, 3 February 2017 (UTC)
6. DGG ( talk ) 03:41, 6 February 2017 (UTC)
7. In order to move this along. -- Euryalus (talk) 12:26, 7 February 2017 (UTC)
8. When we are looking at what previous ArbCom's have proposed and passed, I always have looked to the discussion surrounding it. Several explanations have appeared throughout this ARCA, and it's not specifically clear in this case which means we should be going for the strictest application of the motion/remedy/whatever passed at the time. As for any potential DS expansion, I always need evidence that the modified topic area has been disrupted, which we don't have here. The 2015 ARCA was clear, maybe not sufficiently clear, so that leaves me at a support for this motion. I also see a negative light shining in from the ANI here that any addition to the DS would be used to subvert community consensus or lack-there-of. -- Amanda (aka DQ) 06:47, 10 February 2017 (UTC)
9. Mostly per Newyorkbrad. Ks0stm ^{(T•C•G•E)} 11:32, 10 February 2017 (UTC)

Oppose

1. We're already at majority but I think there could have been specific and isolating wording allowing ARBATC discretionary sanctions for project space request move discussions where MOS and TITLE is the principal issue. I would have hoped that discretionary sanctions in this context would be only applied where absolutely necessary and appropriately following 'awareness' and other provisions. In the original case, requested move discussions were cited by several editors as being areas where MOS and TITLE disputes have occurred. In reading the 2015 ARCA and previous discussions, this issue has been brought up more than once and clarified that they were only meant for the project space. It would have been helpful to know if ARBATC discretionary sanctions have been routinely applied at requested move discussions (in the project space) and whether or not these discretionary sanctions have likely kept disputes from occurring. Without further input or information, I'm uncertain whether this clarification will re-open a venue for MOS and TITLE disputes to occur. I do think the community did need clarification on this issue which passing this clarifiation will hopefully provide and that "broadly construed" was far too wide and could have been used to implement sanctions well beyond the intended scope. Mkdw ^talk 07:30, 8 February 2017 (UTC)

Abstain

Comments

The comments above seem to be somewhat split, so we might as well just count noses. For my part, I can't really see authorizing DS on this broad of a scale as a de facto response to a specific incident. Opabinia regalis (talk) 05:50, 2 February 2017 (UTC)

Clarification request: Palestine-Israel articles 3

Initiated by Hijiri88 at 13:35, 21 January 2017 (UTC)

Case or decision affected

Palestine-Israel articles 3 arbitration case (t) (ev / t) (w / t) (pd / t)

• General Prohibition

List of any users involved or directly affected, and confirmation that all are aware of the request:

• Hijiri88 (talk · contribs · deleted contribs · logs · filter log · block user · block log) (initiator)

Statement by Hijiri88

How does the GP work when an IP or new account makes off-topic edits relate to the Arab-Israeli conflict in articles that are not inherently related to the conflict? Is permanent (or even temporary) extended-confirmed protection appropriate?

This came up recently at Arab Jews. I am not sure if my concern technically applies to that article or not, since the article does seem to be related to the Arab-Israeli conflict by definition (even though I recognize that there have been Jews in Arabia for as long as there have been Jews).

But if this hasn't already come up and been formally clarified, it's almost certain to come up at some point.

The discussion on the Arab Jews article involved a number of specific users but I'm not sure if I should name them as "parties" to this ARCA request as I'm asking for general clarification and not asking for sanctions or anything like that.

Hijiri 88 (聖やや) 13:35, 21 January 2017 (UTC)

And I just made two minor tweaks to the article Edward Said before it occurred to me that technically that article is also covered under the GP (it even includes a full sub-section called "Palestinian National Council"). It has been edited by IPs, and probably also new accounts, dozens if not hundreds of times since the GP was put in place, but were these violations? As currently worded, is the GP even technically enforceable? Is putting such a high level of protection on such a broad swath of articles feasible or even desirable? Sorry if these questions have already been answered; I haven't been following this thread. Hijiri 88 (聖やや) 11:27, 31 January 2017 (UTC)

Statement by BU Rob13

Long story short, this is the "any page" vs. "any edit" issue of the last ARCA which was pushed to the side so as not to omnibus things. Perhaps it's time to make that small change? I would recommend doing the following two things:

1. Expand the prohibition from "any page" to "any page or edit". Note that just "any edit" leaves a lot of room for interpretation with edits on pages that have substantial information on the conflict but where the edit itself does not, so keeping "any page" in there seems necessary.
2. Note that extendedconfirmed protection as an arbitration enforcement action is not appropriate for pages that are just victims of occasional off-topic editing. This doesn't necessarily have to be part of the remedy itself, but it should be made plain in the arbitrator opinions below, at the very least. We wouldn't want random BLPs of Israeli or Palestinian individuals to become indefinitely extendedconfirmed protected under this remedy only because a single IP editor makes an off-topic edit about the conflict.

~ Rob₁₃^Talk 02:36, 22 January 2017 (UTC)

Statement by Iazyges

I agree with BU Rob on the any page vs any edit idea. I also think any unrelated page that come to be the subject of vandalism should only go up to semi-protection, unless the volume of vandalism would be enough to merit protection in its own right. Iazyges Consermonor Opus meum 04:14, 25 January 2017 (UTC)

Statement by Thryduulf (re Palestine-Israel)

If the change is made (I don't have a strong opinion about whether it should) I think it important that Abrcom make it clear the language is that edits made by users not meeting the threshold "can" or "may" be reverted not "must" be reverted. For example a typographical fix, vandalism reversal or unambiguous BLP correction should not be reverted solely because of the person making the edit. Thryduulf (talk) 11:33, 27 January 2017 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

Palestine-Israel articles 3: Clerk notes

This area is used for notes by the clerks (including clerk recusals).

Palestine-Israel articles 3: Arbitrator views and discussion

• I don't want to see ECP extended to pages where the Arab-Israel topic is not the prime concern of the article, but I would support the suggested change from "any page" to "any page or edit". Probably with the proviso that any editor not reaching 500/30 can be reverted without it being considered edit-warring and that a notice should then be placed on that editor's talk page (whether or not they are an IP) explaining the sanctions. Doug Weller talk 15:47, 26 January 2017 (UTC)
• I still don't like this idea and still haven't seen any evidence that it's necessary. I'd be more inclined to make this change given some examples of cases where IPs or new accounts are disrupting non-PIA-related articles with PIA-related edits in ways that can't reasonably be controlled by normal editing. One or two borderline cases aren't enough justification for such a broad expansion. Opabinia regalis (talk) 01:21, 2 February 2017 (UTC)
• Would support the concept if there was sufficient evidence of a problem. Absent some notable or systemic examples of disruption we don't have enough to justify the change. -- Euryalus (talk) 09:46, 2 February 2017 (UTC)
• While I am not opposed in principle to such an extension, I also don't yet see this as warranted, and it might open up Pandora's box with DS used as a bludgeoning device. I much rather trust the judgment of administrators and the community using the regular means. Drmies (talk) 04:47, 3 February 2017 (UTC)

---

Clarification request: Palestine-Israel articles 3 (2)

Initiated by BU Rob13 at 16:59, 10 February 2017 (UTC)

Case or decision affected

Palestine-Israel articles 3 arbitration case (t) (ev / t) (w / t) (pd / t)

List of any users involved or directly affected, and confirmation that all are aware of the request:

• BU Rob13 (talk · contribs · deleted contribs · logs · filter log · block user · block log) (initiator)
• SoWhy (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Confirmation that all parties are aware of the request

• SoWhy

Statement by BU Rob13

See the conversation surrounding Regularization Bill here. Multiple administrators have interpreted the most recent change to WP:ARBPIA3#500/30 to mean that extended confirmed protection should only be used on articles in the topic area if edits by new editors or IPs come from multiple sources, are frequent, and are sustained (as we would do for normal disruption). Having been around for the last ARCA, this was plainly not the intent. As Guerillero said last time around "The ban is not optional." Please clarify that the first method of enforcement should be ECP, with other alternatives more suitable to instances where an editor is editing across many articles or where ECP is otherwise not effective or sufficient. ~ Rob₁₃^Talk 16:59, 10 February 2017 (UTC)

Just noting the last (and most recent) discussion posted below by NeilN closed with consensus to protect pages as soon as the restriction is violated, but not before. That's all I'm asking for clarification in favor here - that the pages should be protected if the restriction is violated. ~ Rob₁₃^Talk 17:15, 10 February 2017 (UTC)

@SoWhy: The wording states that those secondary options are to be used when ECP is not feasible, not when the secondary options are feasible. Could you clarify why ECP wouldn't have prevented the disruption/wasn't feasible? ~ Rob₁₃^Talk 19:09, 10 February 2017 (UTC)

Statement by SoWhy

The current wording of WP:ARBPIA3#500/30 is

“ All IP editors, accounts with fewer than 500 edits, and accounts with less than 30 days tenure are prohibited from editing any page that could be reasonably construed as being related to the Arab-Israeli conflict. This prohibition is preferably enforced by the use of extended confirmed protection, but where that is not feasible, it may also be enforced by reverts, page protections, blocks, the use of pending changes, and appropriate edit filters. ” — WP:ARBPIA3#500/30 (emphasis added)

Neither this wording nor the two previous ones (which explicitly used "may be enforced by reverts, page protections, blocks, the use of pending changes, and appropriate edit filters") contains a rule that ECP has to be used to enforce the prohibition, just that it's preferred. In this case there was only one editor who could have been dealt with individually, without the need to lock down the page.

That said, I have no particular opinion on the topic itself and I'd be fine if WP:ARBPIA3#500/30 was clarified to read "has to be enforced". Regards SoWhy 18:11, 10 February 2017 (UTC)

• @BU Rob13: The current consensus (cf. the links NeilN provided and also at the recent AN/I thread) seems to be that ECP should be used "liberally but not automatically" (to borrow Airplaneman's phrase) when it comes to this particular topic ban, i. e. iff there has been a disruption. At the time of the protection request, the article in question was newly created by a relatively new user and then stubyfied without a disruption in sight. The new user in this case didn't know about the ArbCom ruling and edited in good faith as far I can tell, so it was not a violation and thus no need to apply ECP. If the Committee believes this particular motion should apply to all articles, even before disruption happened, then yes, clarification is required since the current wording allows the interpretation we have seen become consensus (and which I based my decision on). And if your strict interpretation is to be the correct one, ArbCom should just protect all such pages preemptively and be done with it. But since they haven't done so in the past, it was a reasonable assumption by myself (and many others) that ArbCom didn't want to demolish the third pillar before disruption actually occurs. Regards SoWhy 21:24, 10 February 2017 (UTC)

Statement by NeilN

Past admin discussions:

• Wikipedia_talk:Requests_for_page_protection/Archive_8#WP:ARBPIA3_and_protection
• Wikipedia_talk:Requests_for_page_protection/Archive_9#AE_protection_requests
• Wikipedia_talk:Requests_for_page_protection#Mass_request_on_pages_related_to_Arab-Israeli_conflict.28s.29

--NeilN ^{talk to me} 17:12, 10 February 2017 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

Palestine-Israel articles 3: Clerk notes

This area is used for notes by the clerks (including clerk recusals).

---