Case clerks: SQL (Talk) & Cthomas3 (Talk) Drafting arbitrators: Joe Roe (Talk) & Premeditated Chaos (Talk) & Worm That Turned (Talk) |
Wikipedia Arbitration |
---|
|
Track related changes |
Preliminary statements by uninvolved editors at the ARCA |
---|
The following discussion has been closed. Please do not modify it. |
Statement by Doug WellerIt looks as though this problem is going to continue. It's been discussed for over a week at Wikipedia talk:Arbitration/Requests#Some issues relating to the IP area which I urge everyone to read (and User:Huldra has found a slew of articles that need templating and edit notices given the current sanctions). Towards the bottom of the thread I've tried to outline how I understand ARBPIA sanctions are meant to work. Doug Weller talk 05:36, 25 April 2019 (UTC)
Statement by HuldraThis is not related to the issue about parts/whole of the article being under ARBPIA, but it relates to the imbecile motion added March this year. Yes: imbecile! After that motion, no-one can be sanctioned for 1RR unless an admin has placed an edit notice on the article in question. Since there are thousands of articles, and only a few hundred of them have edit notice, the result is that clear cut violations of the rules goes unpunished; see this example. So while "All Arab-Israeli conflict-related pages, broadly interpreted" are placed under "discretionary sanctions", the 1 RR rule has become unenforceable on most article. This is a totally untenable situation, I hope that arb.com either:
I would prefer that you chose option 1, that's because admins are not the best persons to see what is under ARBPIA, or not. Case in point: Solomon's Pools, where both, say, Icewhiz and I agree that it comes under ARBPIA, but "outside" admins have a difficulty in seeing that. (For those of you who don't know us: Icewhiz and I disagree about just about everything regarding the I/P area...) Huldra (talk) 21:07, 26 April 2019 (UTC) User:Ymblanter: All articles mentioned in Template:Palestinian Arab villages depopulated during the 1948 Palestinian exodus (and the Israeli localities on their land), all Palestinian localities on the West Bank; listed under Template:Governorates of the Palestinian Authority. I would also say all localities listed in [[Category:Arab localities in Israel]], and all localities in the Golan Heights: Syrian towns and villages depopulated in the Arab–Israeli conflict, and the places mentioned in it and Template:Golan Regional Council. Huldra (talk) 21:28, 26 April 2019 (UTC)
Well, I went to Wikipedia:Requests for permissions/Template editor, and got pagemover rights. So now I see a "Page notice" on my editing screen, where I can put ((ARBPIA 1RR editnotice)). I will advice everyone (who is not admins) to apply for this, Huldra (talk) 21:13, 1 May 2019 (UTC) Statement by Zero0000To editor SilkTork: I think you missed the point when you wrote "If someone feels that there is significant enough content which falls under a DS topic on a particular page/article then they can place a DS template." No they can't; only administrators and template editors can add the editnotice that arbcom decided is needed for enforcement. Zerotalk 10:50, 29 April 2019 (UTC) To editor BU Rob13: Before 500/30, IPs and new socks would cause disruption because they don't care about rules while the good editors trying to preserve article integrity were constrained by 1RR from reverting the disruption. The combination of 1RR and 500/30 has proved very beneficial to the area and I don't understand why you think removing 500/30 would be an improvement. Zerotalk 07:54, 11 May 2019 (UTC) Statement by Sir JosephI think that articles that are not broadly about the conflict should not be locked down under ECP, they can be locked down temporarily, they can be IP protected, etc and then when the vandalism passes, it's good to go. We should not have many articles under a patchwork of horrible ARBCOM rulings that are terribly confusing to enforce and understand. Sir Joseph (talk) 15:03, 29 April 2019 (UTC) Statement by DavidbenaI think that it is wise and pertinent that no-one can be sanctioned for 1RR unless an admin has placed an edit notice on the article in question. If the 1RR edit-notice were to apply to all articles in the I/P area, and if ordinary editors could add such notices, who would prevent them from adding these notices to every town and city in Israel (Palestine), irregardless of whether or not the town had been involved in the Israeli-Palestinian struggle? Editors would still find a way to include it, since both sides vie for the control of the same country. This would greatly impede progress and make the simple task of editing much more difficult, just as we found in the article Solomon's Pools, which to my dismay came to be associated with the Israeli-Palestinian conflict, although it has absolutely nothing to do with that conflict other than the fact that the pools lie within territory controlled by joint Israeli-Palestinian Authority officials. In my humble opinion, we should avoid making the task of editing bogged-down in red-tape and litigation, whenever possible, and only in those articles where by their nature they spark heated debate or POV views should these 1RR edit warnings be added.Davidbena (talk) 23:52, 29 April 2019 (UTC) Statement by GatoclassI have long argued that discretionary sanctions should be applied not only to articles within the topic area, broadly interpreted, but to edits clearly related to the topic area in question, regardless of whether the article topic itself is related. This is because the topic area to which discretionary sanctions apply can be referenced peripherally in almost any article (falafel, anyone?) If somebody is making edits somewhere, anywhere, that can be reasonably construed as pertaining to the topic area, then surely all the usual discretionary sanctions should be applied to those edits regardless of which article they were made in. It seems to me that if this approach were to be adopted, the regular tiresome debates about whether or not a given article belongs in the topic area could be avoided altogether. Gatoclass (talk) 12:29, 30 April 2019 (UTC)
Statement by Sandstein@AGK: In response to your question: yes, ArbCom rules in the I/P area are too complicated, to the point where I'm reluctant to help enforce them because of the likelihood that I'll do something wrong and/or need to spend too much time reading up on the rules. I agree that the relevant decisions should be reviewed. Off the cuff, it might be worth it to consider reverting to basic discretionary sanctions. That's because drive-by disrupters using new accounts can be easily dealt with without the need for complicated rules, and AE regulars who are playing long-term games with the I/P content are quite capable of gaming complicated rules to their advantage. I could be wrong, though, and maybe the rules are actually helpful. Hence the need for a review. Sandstein 09:27, 4 May 2019 (UTC) Statement by NableezyWP:NOTBURO. Yall have made this more complicated on each iteration. You have made it so what was intended to be a way of limiting edit-wars for the topic and limiting the sockpuppetry into one that on too many pages is unenforceable due to a technicality or not applicable because of this reasonably or broadly dispute. To me the answer here is obvious, divorce where extended-confirmed is applied (reasonably construed), but apply the rest of the prohibition to the larger set (broadly construed, with only the sections about the topic area covered). And remove the edit-notice requirement. What is important is that a person know that the edit is covered by the 1RR. Having the
Statement by IcewhizRob's suggestion to make 500/30 conditional on ECP being applied to the page makes sense. I would suggest making this a "package deal" with 1RR (so if ECP is applied - 1RR is always applied as well). If these are handed out on an article level on a very liberal basis (e.g. mere relation of a page to the conflict - assuming requests at RfPP will be handled quickly and promptly - even without evidence of disruption for "reasonably construed" (for "broadly construed" - one should have evidence of disruption)) - then the amount of disruption should be fairly low (and if a new editor hops around many unprotected pages doing un-constructive editing - regular DS would still apply). For new articles, all one has to do is ask at RfPP (e.g. diff for a new current event conflict article). The advantage to moving to a more normal (in relation to other topic areas) DS regime is that the current regime in ARBPIA is a rather severe roadblock for new editors, who can accrue sanctions at an alarming rate due to a mere misunderstanding of 500/30 and 1RR (which are even confusing to regulars (some long term editors diverge from AE norms in the parsing of "what is a revert") - let alone new comers). New Israeli or Palestinian editors invariably edit many pages that are "reasonably construed" (e.g. geographic locations, the country articles, all sorts of organizations) - even if their particular edits are not particularly conflict related (e.g. updating the head of the local council in a West Bank settlement after local elections) - the "survival rate" of such new editors on Wikipedia (without getting TBANNED from the topic area - and potential TBAN violations subsequently leading to blocks) is pretty low under the current sanctions regime - as they are able to edit non-ECP articles (running foul of 500/30 and often violating 1RR).Icewhiz (talk) 12:34, 12 May 2019 (UTC) Statement by SerialjoepsychoThe rules should apply where they apply naturally or rather the use of common sense is necessary. Every article need not be given a templet or protected simply because it dips it's toes in areas that are under sanctions. However when editors import the conflict into these articles due consideration should be given on a case by case basis for the appropriate action. An editor topic banned from ARBPIA related topics should be able to edit AIRBNB but they shouldn't be allowed to edit the portions of the article related to ARBPIA. Uninvolved admins also need the ability to take some appropriate form of action when the general disruption associated with articles under sanction is exported to articles that merely get their toes wet on the subject. I'd have to endorse a rewrite of these sanctions or any others that simplify them but they do need to have teeth.-Serialjoepsycho- (talk) 04:11, 23 May 2019 (UTC)
Statement by ZScarpiaI would like to check whether my understanding of the situation is correct and to clarify how the remedies would effect interaction with editors on pages which could not be reasonably construed as relating to the AI conflict. Two sets of sanctions affect the ARBPIA area, the general remedies (1RR and 500/30) and discretionary sanctions. The general remedies appy on pages which could be 'reasonably construed' as relating to the conflict. For them to apply, the ArbCom Arab-Israeli edit notice must be placed on affected 'pages'. Discretionary sanctions apply, more broadly, on pages which may be 'broadly construed' as relating to the conflict. The ArbCom Arab-Israeli enforcement notice may be placed on the talkpages of affected articles, but such a placement is not necessary for discretionary sanctions to apply. However, discretionary sanctions may not be applied unless editors are aware that discretionary sanctions are in place. The Airbnb article as a whole cannot be 'reasonably construed' as relating to the conflict and therefore the general sanctions do not apply to it, though part of it does and editing of that part may be subject to discretionary sanctions. If an editor who doesn't meet the 500/30 standard edits the part of the article which is conflict related or leaves conflict-related comments on the talkpage, how should (or may) another editor handle it if he or she thinks that those edits or comments are problematic? Similarly, how may it be handled if an editor makes more than one revert to the conflict-related material within a 24-hour period? Is all that can be legitimately done to give a warning that enforcement under discretionary sanctions may be sought (though, if enforcement was sought, there would be no bright lines and it would be up to individual admins to decide whether to apply 500/30 and 1RR)? ← ZScarpia 15:43, 27 June 2019 (UTC) Statement by RetroSince there's a motion to open ARBPIA4, it seems appropriate to mention a discussion I was involved in just today related to another aspect of the previous decision. There seems be some ambiguity regarding whether 500/30 should be preemptively applied to pages clearly entirely related to the Arab-Israeli conflict. Local practice at RfPP has generally been to avoid preemptively protecting, following a 2017 discussion. This local practice seems to contradict the General Prohibition, which states: The state of current practice suggests a clarification regarding this prohibition's interaction with WP:PREEMPTIVE is needed at the very least. If the committee is considering a new case, this is probably an opportunity to review how practical these measures are for administrators to implement and how easy they are to understand (echoing concerns expressed above). Doug Weller also mentioned related concerns in their 12 May 2019 comment above. Retro (talk | contribs) 01:47, 18 July 2019 (UTC) Statement by Maile66Whatever you decide, please put it in a table format, easily accessible to any and all. As is, this policy is explained differently in separate places. It's been open to individual interpretation by whomever applies it, and, therefore, challenged by non-admin users who feel it is applied unnecessarily. We need something concise, easy to read, and very clear about what the policy is. The current policy is rather ambiguous. — Maile (talk) 11:11, 18 July 2019 (UTC) Question from User:MJLWhile the motion below is still on track to be passed, I would like to ask how this would affect the decision of Antisemitism in Poland as it still awaits a proposed decision? I know during the workshop period, TonyBallioni suggested a broader remedy be applied to the topic of Antisemitism. Is this related? ¯\_(ツ)_/¯ –MJL ‐Talk‐☖ 20:27, 22 July 2019 (UTC) |
We are well past the scheduled start date. Buffs (talk) 19:52, 2 October 2019 (UTC)
|suspended=true
from the entry for this case in Template:ArbComOpenTasks/Cases? — Newslinger talk 00:51, 6 October 2019 (UTC)
The workshop phase of the Palestine-Israel articles 4 arbitration case will be extended to November 1, 2019. All interested editors are invited to submit comments and workshop proposals regarding and arising from the clarity and effectiveness of current remedies in the ARBPIA area. For the Arbitration Committee, Kevin (aka L235 · t · c) 07:38, 25 October 2019 (UTC)
Proposed decision to be posted by 13 Nov 2019expectation be updated? — xaosflux Talk 13:32, 23 November 2019 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Remedy 1 of the Palestine-Israel articles 4 case is amended by inserting, at the end of the list titled "ARBPIA", the following list item:
the existing remediesrather than
the following existing remedies(emphasis added), I think that'd have been reasonable. ~ Amory (u • t • c) 18:27, 22 December 2019 (UTC)
The rule saying that "The templates may be added to primary articles by any user, but may only be removed by an uninvolved administrator." raises the real possibility that articles will be tagged that are not really with the scope of primary articles, including with the intent of making it harder to disagree with that editor. We have seen examples of articles that were tagged incorrectly. I understand that one can always ask an uninvolved admin to remove it, but those will probably decide to err on the side of caution, once the template has been added, so that doesn't really solve the problem. Then again, I am not sure there is an alternative. Debresser (talk) 21:44, 4 January 2020 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Initiated by Nableezy at 06:04, 20 May 2020 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Confirmation that all parties are aware of the request
I'd like some clarification on the awareness requirements for the 1RR. My reading of Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 4#ARBPIA General Sanctions is that the only thing that requires awareness are sanctions enacted under 5A (discretionary sanctions by an uninvolved administrator), and that the 1RR is a general sanction that does not require formal awareness of the discretionary sanctions for the topic area and that users may be blocked for violating that sanction without any formal alert (obviously a request to self-revert being offered). Is that correct, or is formal notification of the discretionary sanctions required prior to any violation of the 1RR required?
In the case of articles with an ARBPIA editnotice, that notice whacks you in the face as soon as you hit the "edit" button. So I wouldn't oppose a ruling that the existence of the notice implies awareness of the sanctions. Zerotalk 07:15, 20 May 2020 (UTC)
I’ll ping Callanecc on this as he’s been helpful explaining this before, but traditionally the understanding was that the General Prohibition was not DS, but a direct sanction from ArbCom. As such, it did not require formal DS awareness. From a practicality perspective, yeah, this is helpful to not be DS. No one isn’t warned first, and most people in these areas know the rules and the formal notification doesn’t accomplish much. For 500/30 in particular, requiring the same requirements of DS could actively work against the sanction. We do have editors who intentionally search for pages not under ECP so they can edit them because they’re that passionate about the issue. Enforcing 500/30 with the page level requirements for DS would effectively make it protection-only, which would cause issues. Blocks for 500/30 aren’t that common, but we do need them as a tool, and the DS awareness criteria there would work against the intent of the sanction: to prevent new editors from causing disruption in this area, which is very difficult to define and preemptively protect. TonyBallioni (talk) 16:35, 20 May 2020 (UTC)
Feels strange commenting here! Exactly as Tony said, sanctions that ArbCom imposes directly (as in not by an admin under DS) operate with a separate system of rules. Unless the ArbCom decision requires that a warning be given before a sanction is imposed then a warning is ArbCom-mandated. However, a best practice approach would require that before being sanctions an editor knows what they're doing is wrong. If they're attempting to, for example, game the system as Tony suggests then they definitely know what they're doing is wrong and can be sanctioned without a formal warning having been given. Just regarding Zero0000's point above, it's important to consider that people editing using the mobile interface won't be shown the edit notice so that needs to be considered if using only that to determine whether the editor knows about the sanctions and so should be sanctioned or not. Callanecc (talk • contribs • logs) 09:08, 22 May 2020 (UTC)
Just a short note that I read the first three arbcom member comments here and I am... very positively surprised. In my professional view as a sociologist who studied, among other things, ArbCom, English Wikipedia is way too into punitative blocks, with prevention being sidelined. To hear three members of ArbCom say otherwise, and do it very clearly, is very refreshing. --Piotr Konieczny aka Prokonsul Piotrus| reply here 06:09, 24 May 2020 (UTC)
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.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Initiated by Zero0000 at 17:15, 18 June 2020 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Confirmation that all parties are aware of the request
In accordance with the ARBPIA General Sanctions,
non-extended-confirmed editors are permitted to edit talk pages of ARBPIA articles under certain conditions. However, "This exception does not apply to other internal project discussions such as AfDs, WikiProjects, RfCs, noticeboard discussions, etc."
. My question is: Is a formal move proposal, as made using the ((requested move)) template, an example of "other internal project discussions"?
My opinion is that a move proposal is very similar to an RfC and so should be treated the same.
Thanks for your time. Zerotalk 17:15, 18 June 2020 (UTC)
To editor Bradv: I think your interpretation of "content" is narrower than intended. The very fact that the rules for talk space editing, AfDs, etc, are called "exceptions" proves that "content" is intended to include them. I believe that "content" just means "all content" in the ordinary English sense and it isn't a specific reference to article space. Zerotalk 04:14, 30 June 2020 (UTC)
Also, there is nothing to stop non-ECs from discussing the topic of an on-going RfC on the talk page; they are only prohibited from taking part in the RfC itself. I believe this is important because of the number of new accounts or IPs that come out of nowhere just to "vote" in RfCs. I expect that a large fraction are socks, people editing while logged out, or people responding to off-wiki canvassing. Zerotalk 05:04, 30 June 2020 (UTC)
The question came up here, I thought RM is not allowed and at first @El C: thought it was OK and then decided it wasn't. Perhaps it should be made clear that it is not allowed (in practice, it is similar to an RFC).Selfstudier (talk) 18:10, 22 June 2020 (UTC)
I see RMs as being very similar to RfCs in nature, so my feeling is that if RfCs are disallowed, RMs should be as well. The question of how to title an article is, after all, an "internal project discussion". Beyond My Ken (talk) 01:46, 29 June 2020 (UTC)
I've been following this clarification request since the beginning, and it seems like bradv pointed out interesting information that the 500/30 restriction applies to editing content only. So as worded, non-500/30 users may participate in "other internal project discussions".
Now let's look at WP:ARBPIA3, finding of fact No. 3
3) The Palestine-Israel topic area has been continuously plagued by sockpuppetry. (Kingsindian's Evidence)
- Passed 11 to 0 at 15:21, 22 November 2015 (UTC)
Okay, that was from ~4.5 years ago, but when you consider this to be a long-term problem, it's likely that the problem persist.
So with this underlying fact and intention/principle, I think that the 500/30 restriction does apply to RM as well as other internal project or vote-like discussions in any ArbCom/community areas of conflict. Sockpuppetry is small, but when discovered, is huge. 01:00, 1 July 2020 (UTC)
There is a general legal principle that exceptions are to be construed narrowly. This is to provide legal certainty to people who might be affected. The topic in question is an exception to an exception, and the same principles apply.
I find the wording "such as AfDs, WikiProjects, RfCs, noticeboard discussions, etc." unclear. What are its boundaries? I suggest that "such as" be replaced by "including but not limited to".
In the case at hand, I consider that a WP:RM is of the same nature as the things already listed, and should be explicitly mentioned. Narky Blert (talk) 09:30, 12 July 2020 (UTC)
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.
editing content". There is an exception (extension?) to apply that rule to talk pages in the case of disruption, but that clause does not apply to "internal project discussions". As worded, this restriction does not prohibit new editors from participating in RMs, RfC, AfDs, or any other internal discussions, as they are not "editing content". If that was not the intent of the motion, it should be reworded. – bradv🍁 14:09, 29 June 2020 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Initiated by El C at 19:26, 21 February 2021 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
Confirmation that all parties are aware of the request
Following up on the query from Shrike (see conversation at: User talk:Shrike), I thought perhaps it would be prudent for the Committee to clarify whether logged warnings count as "sanctions being levied." I suspect what the answer to this is, but having it on the record is probably a good thing. As well, any elucidation Committee members can maybe provide on AWARE and topic area regulars, even if only in passing, would be welcome (sorry for the two-questions-in-one!). El_C 19:26, 21 February 2021 (UTC)
Warnings issued under earlier procedures are not sanctions, but, even if we were to take that excerpt out of whatever context, the distinction between logged and un-logged warnings isn't specified, anywhere that I've seen (possibly, I just missed it?). El_C 19:39, 21 February 2021 (UTC)
In the last twelve months, the editor has given and/or received an alert for the area of conflict; or"? --Shrike (talk) 19:36, 21 February 2021 (UTC)
Not really au fait with the nitty gritty but I don't think anyone needs to see that notice more than once or even at all, especially when you have those in-your-face notices at the articles themselves. Regulars know the score and newcomers are given an easier treatment.Selfstudier (talk) 16:41, 22 February 2021 (UTC)
We have IAR for a good reason and overturning a logged warning because someone was out of awareness by 10 days seems to be a good example of where the rules are completely disconnected from reality --Guerillero Parlez Moi 06:04, 28 February 2021 (UTC)
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.
When no actual violation occurred, or the consensus of uninvolved administrators is that exceptional circumstances are present, which would make the imposition of a sanction inappropriate, administrators may also close a report with no action; if appropriate, they may also warn or advise the editor being reported, in order to avoid further breaches.Warnings are therefore imposed when "the imposition of a sanction" is found to be "inappropriate" (or when "no actual violation occurred"). This suggests that warnings are not sanctions, and so currently do not count under the second point of Wikipedia:Arbitration Committee/Discretionary sanctions § Awareness. I think it'd be reasonable to amend it to allow warnings to count as sanctions, but I'd prefer to do a broader DS reform first. Best, KevinL (aka L235 · t · c) 21:12, 21 February 2021 (UTC)