Misplaced Pages

:Arbitration/Requests/Enforcement - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests

This is an old revision of this page, as edited by EtienneDolet (talk | contribs) at 08:03, 7 August 2016. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 08:03, 7 August 2016 by EtienneDolet (talk | contribs)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) "WP:AE" redirects here. For the guideline regarding the letters æ or ae, see MOS:LIGATURE. For the automated editing program, see WP:AutoEd.


Noticeboards
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles and content
Page handling
User conduct
Other
Category:Misplaced Pages noticeboards

    Click here to add a new enforcement request
    For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
    See also: Logged AE sanctions

    Important informationShortcuts

    Please use this page only to:

    • request administrative action against editors violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator,
    • request contentious topic restrictions against previously alerted editors who engage in misconduct in a topic area designated as a contentious topic,
    • request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or
    • appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators.

    For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard.

    Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with less than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions.

    To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}.

    Appeals and administrator modifications of contentious topics restrictions

    The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following:

    All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction.

    The appeal process has three possible stages. An editor appealing a restriction may:

    1. ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
    3. submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email.

    Appeals submitted at AE or AN must be submitted using the applicable template.

    A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted.

    Changing or revoking a contentious topic restriction

    An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies:

    • The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change, or is no longer an administrator; or
    • The contentious topic restriction was imposed (or last renewed) more than a year ago and:
      • the restriction was imposed by a single administrator, or
      • the restriction was an indefinite block.

    A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction:

    • a clear consensus of uninvolved administrators at AE,
    • a clear consensus of uninvolved editors at AN,
    • a majority of the Arbitration Committee, acting through a motion at ARCA.

    Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped.

    Standard of review
    On community review

    Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action was not reasonably necessary to prevent damage or disruption when first imposed, or
    3. the action is no longer reasonably necessary to prevent damage or disruption.
    On Arbitration Committee review

    Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action represents an unreasonable exercise of administrative enforcement discretion, or
    3. compelling circumstances warrant the full Committee's action.
    1. The administrator may indicate consent at any time before, during, or after imposition of the restriction.
    2. This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.
    Appeals and administrator modifications of non-contentious topics sanctions

    The Arbitration Committee procedures relating to modifications and appeals state:

    Appeals by sanctioned editors

    Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

    1. ask the enforcing administrator to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
    3. submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-en@wikimedia.org).
    Modifications by administrators

    No administrator may modify or remove a sanction placed by another administrator without:

    1. the explicit prior affirmative consent of the enforcing administrator; or
    2. prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

    Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

    Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

    Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

    Important notes:

    1. For a request to succeed, either
    (i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or
    (ii) a passing motion of arbitrators at ARCA
    is required. If consensus at AE or AN is unclear, the status quo prevails.
    2. While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.
    3. These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature.
    4. All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.
    Information for administrators processing requests

    Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give.

    A couple of reminders:

    • Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request.
    • When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X".
    • Enforcement measures in arbitration cases should be construed liberally to protect Misplaced Pages and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Misplaced Pages policies and guidelines; you may use administrative discretion to resolve it.
    • More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated.

    Closing a thread:

    • Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days.
    • Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct.
    • You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages.
    • Please log sanctions in the Arbitration enforcement log.

    Thanks again for helping. If you have any questions, please post on the talk page.

    Arbitration enforcement archives
    1234567891011121314151617181920
    2122232425262728293031323334353637383940
    4142434445464748495051525354555657585960
    6162636465666768697071727374757677787980
    81828384858687888990919293949596979899100
    101102103104105106107108109110111112113114115116117118119120
    121122123124125126127128129130131132133134135136137138139140
    141142143144145146147148149150151152153154155156157158159160
    161162163164165166167168169170171172173174175176177178179180
    181182183184185186187188189190191192193194195196197198199200
    201202203204205206207208209210211212213214215216217218219220
    221222223224225226227228229230231232233234235236237238239240
    241242243244245246247248249250251252253254255256257258259260
    261262263264265266267268269270271272273274275276277278279280
    281282283284285286287288289290291292293294295296297298299300
    301302303304305306307308309310311312313314315316317318319320
    321322323324325326327328329330331332333334335336337338339340
    341342343344345346

    Doc9871

    Doc9871 (talk · contribs) topic banned 1 month from all pages related to Donald Trump by Bishonen (talk · contribs), and is further warned that any disruption in the topic areas covered under Misplaced Pages:Arbitration/Requests/Case/American politics 2 will lead to an extension and/or broadening of the ban. The Blade of the Northern Lights (話して下さい) 21:07, 2 August 2016 (UTC)
    The following discussion has been closed. Please do not modify it.

    This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
    Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

    Request concerning Doc9871

    User who is submitting this request for enforcement
    Volunteer Marek (talk · contribs · deleted contribs · logs · filter log · block user · block log) 09:06, 1 August 2016 (UTC)
    User against whom enforcement is requested
    Doc9871 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

    Search CT alerts: in user talk history • in system log

    Sanction or remedy to be enforced
    Misplaced Pages:Arbitration/Requests/Case/American politics 2 :
    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

    On the talk page of Donald Trump

    1. Personal attack. Particularly strange since it was made right after I agreed with him
    2. Discussing editors rather than content. Assuming bad faith. Disruptive derailing of discussion. Note edit summary where he "clarifies" his "PA", which is an admittance that he is making personal attacks.
    3. Again, discussing editors rather than content. States that I "have no business editing this article" (because... he decided so)
    4. Threats and continued refusal to discuss content rather than editors
    5. Refusal to address the issue, restatement that he will "challenge" all my edits, pretty much states that they do not plan on abiding by 1RR on the article.
    6. Another personal attack. False claim.
    7. "Shut up. Signed: everybody". A very explicit personal attack.
    Note that most of these comments were made AFTER a notification of discretionary sanctions was issued:

    On the Donald Trump article itself. Please be aware that the article is under a 1RR restriction:

    1. 1st revert Note that the edit summary is false - the info is in fact in the source as has been pointed out prior to the edit on the talk page
    2. 2nd revert Note that the edit summary is false. In fact, it's ridiculously false since the text is in the source almost exactly the same (allowing for paraphrasing). For reference the source is here.
    3. 3rd revert Note that the edit summary is misleading (and nonconstructive). My source was an improvement over the previous source.
    4. 4th revert This edit summary makes absolutely no sense. What does "Nah. ..." mean? The claim is that the edit was "too sloppy" because of the use of a singular "period" rather than "periods". This is about as spurious and petty of a revert/edit summary as I've ever seen on Misplaced Pages.
    Note that all but the first two of these were made AFTER a 1RR notification was issued: (both notifications were removed)
    Diffs of previous relevant sanctions, if any

    blocked as part of Arbitration Enforcement on two previous occasions, both fairly recent, for exactly the same article.

    1. Blocked for violations at the closely related Donald Trump presidential campaign article.
    2. Blocked for 1RR violation at Donald Trump presidential campaign article article.

    In regard to the second diff, in case Doc tries to argue that the above listed edit were not reverts, please note the discussion that followed his May 2016 block where the blocking admin, User:Coffee explains to him precisely what a revert is. So he knew he was doing bad.

    If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)

    See above. The user has been sanctioned on these articles under DS previously and also received a recent notification (I was not aware he had previous blocks in this area until I started writing this report)

    Additional comments by editor filing complaint

    Personally I can't tell if this is some kind of personal grudge (the nature of Doc's comments come off that way) or it's just the topic involved. Either way, it's clear that the user has decided unilaterally that I should not be allowed to edit the article for some reason, and has proceeded to edit war, breaking not just 1RR (which the article is subject to) but even 3RR, making very petty reverts. My edits didn't even change the text, just improved the sourcing so this is clearly a WP:POINT violation, where Doc is basically saying "I will not allow you to make a single edit to this article". Even putting aside the edit warring and the personal attacks, this is disruptive and unacceptable.

    In light of the previous blocks the user received on this very article on a very closely related article ("Donald Trump presidential campaign" vs "Donald Trump) I request a two week block from editing as well as a topic ban from anything related to Donald Trump and the ongoing presidential election, broadly construed.Volunteer Marek (talk) 09:06, 1 August 2016 (UTC)

    See also these two previous AN/I threads which document exactly the same problematic behavior in other areas. This means previous warnings have been issued. Repeatedly. a dispute with User:SMcCandlish, closed by User:John, and initiated by User:John (don't know how that ended up).Volunteer Marek (talk) 10:21, 1 August 2016 (UTC)

    Notification of the user against whom enforcement is requested


    Statement by (Doc9871)

    • Point #7 illustrates the extremely misguided nature of this complaint. "A very explicit personal attack". Yeah, right. This is a complete waste of time. Doc talk 09:48, 1 August 2016 (UTC)
    • On the AN/I's - I don't recall having any further issues with that editor, almost a year ago. I didn't get blocked or topic-banned in either case. So it's really a stretch to even bring it up. Doc talk 10:30, 1 August 2016 (UTC)
    • Bishonen definitely has an axe to grind here. For the record: I've never socked, never lied about socking, and never supported socking. Doc talk 10:56, 1 August 2016 (UTC)
    • You are not an uninvolved admin. You are inarguably involved and have an axe to grind with me. I do not trust your decision to be neutral at all. Please note that the thread was not even open more than a few hours before this decision was handed down. This is grounds for immediate appeal. Seriously not in line with due process. Doc talk 11:58, 1 August 2016 (UTC)
    • SMcCandlish, thanks for another thorough breakdown of my behavior and how it should be effectively addressed. I think it's a little beyond the scope of the Trump stuff though, maybe? Thanks fer stoppin' by. Doc talk 12:39, 1 August 2016 (UTC)

    Statement by Johnuniq

    Would admins please explain to Doc9871 that whacking people with a wet trout is not a substitute for a calm exchange of views, and this diff at User talk:Bishonen#August 2016 is entirely inappropriate. I see several aspersions being cast above, and no evidence. Johnuniq (talk) 12:05, 1 August 2016 (UTC)

    Statement by SMcCandlish

    I'm reluctant to get into any dispute involving Doc9871, but this is the same problem as last year. Volunteer Marek diffed my previous ANI complaint, but there were two; the second also closed without action, despite being about immediate resumption of the same behavior after a warning. No consequences = no impetus for adjustment.

    There's no excuse for comments like "You really have no business editing this article", and others diffed by Marek (there is no requirement that editors be neutral, only content must be; are any editors neutral about Trump?). The "Don't challenge me ... You have no chance getting me on a "personal attack'" battlegrounding mirrors the stuff last year (e.g.: "Open an AN/I on me if you want." and several other such 'I'm invincible' challenges, "Ask around if I am one to quarrel with. I will 'Wikilawyer' you, and really good. You don't have to like me: you have to reckon with me.", "You're playing with fire. You better know when to recognize this.", "I will fight this PC nonsense until the bitter end."). (Actually, I just realized this previous matter really is American-political, an anti-progressivism stance.)

    Doc9871 uses others' block logs as weapons, and struts that he is immune to repercussions just because his own block log is clean , , , (samples from his months-long, bad-faith-assuming and veiled-threat abuse of a single editor, Ihardlythinkso, in a pattern repeated later with me). WP does not need a gangland kingpin. This behavior has to stop.

    I suggest prohibiting Doc9871 from:

    • Namecalling or questioning the good faith of other editors
    • Menacing other editors on the basis of their administrative enforcement history regarding matters unrelated to the topic
    • Trying to hound other editors out of a topic
    • Threatening any editor with harassment, battleground, or editwar tactics, or issuing 'you can't do anything about me'-type challenges.

    Give escalating blocks for recurrent transgressions. This would nip this battlegrounding problem in the bud. All four of these behaviors are consistently exhibited in Doc's aggressive soapboxing against Ihardlythinkso, myself, and Volunteer Marek in series, over a long time; it's not a fluke or coincidence. AE should put out Doc's "fire", since ANI never results in action due to Doc having a bit of a fan club.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅ᴥⱷ≼  12:29, 1 August 2016 (UTC)

    @Bishonen: I honestly think the approach I outline above, without any initial block or a particular topic ban, would be more effective, because the behavior is not actually localized. I was once subject to a "not questioning good faith" sanction myself, and it markedly changed my approach to other editors, away from my habitual Usenet-style "verbal combat" tactics. (To someone habituated to it, it does not seem wrong, and it takes a while to learn why it is in this environment and how to shift). It's a form of teaching contextual manners and distinction-drawing. I have faith that it would work in Doc's case, while a not-that-short topic ban will probably feel unfair and punitive rather than preventative, and may just increase the angry mastodon mode in the long run. I also speak from experience here, having been twice subjected to short-term TBs, in ways that effectively supervoted in favor of the other party and gave them free reign, leading to a major mess that had to be cleaned up after the TBs expired (and one of those parties has been indeffed; I was right, just being a WP:JERK about it). I think the cases are parallel; there's a good chance that the underlying NPoV issues that Doc is trying, intemperately, to address are legitimate. So a TB rather than some behavioral fencing might negatively affect the content. TBs are a hammer that should only be used on the nails of long-term (or suddenly massively disruptive) patterns of localized disruption, in my view (not as a matter of strict rules, but of what works and what does not). Matters like this are screws, not nails, and need a more subtle tool.  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅ᴥⱷ≼  13:04, 1 August 2016 (UTC)
    @Bishonen: It could be a bit fuzzy, but "questioning the good faith of other editors" it not very fuzzy at all, as it directly addresses what the editor writes, in public view, about another editor's motivations. My own restriction of this sort was very fuzzy, reading "prohibited from assuming bad faith about other editors", a matter of mind-reading thoughtcrime, and people did attempt to game it (unsuccessfully).  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅ᴥⱷ≼  13:36, 1 August 2016 (UTC)

    Evidence that we already know the TB will not be effective: "You really think this is going to teach me a lesson?", from Doc's response to the TB . TBs can also lead to cases of myopic "fight the injustice" WP:NOTHERE + WP:GREATWRONGS behavior (which is how and why the aforementioned party got indeffed). I would have concerns in this regard given Doc's followup comment, "What it teaches me is that there is no due process here. I was absolutely railroaded on this issue." The "issue" for him is "censorship" from a particular topic, and he believes the motivation for it is political (see same diff). This would not be happening if the remedy was directly and only targeted at behavior patterns across topics instead of just at his ranting over Trump articles in particular. That's all I'll say about it; I just don't want to be in an "I told you so" position a few months from now, with Doc blocked repeatedly, and sour on WP, instead of being successfully herded into being less verbally hostile (which for me was a difficult and probably still incomplete, but ultimately rewarding transition, with off-WP benefits).  — SMcCandlish ☺ ☏ ¢ ≽ⱷ҅ᴥⱷ≼  14:10, 1 August 2016 (UTC)

    Statement by USERNAME

    Result concerning Doc9871

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
    • I saw the edits on the article talkpage, and was just writing up a warning to Doc before this AE report; I've posted it now. As I imply there, I'm quite prepared to topic ban Doc from Donald Trump-related pages if he persists in his aggressive personalized talkpage posting. Perhaps we can await the result of my warning, as well as of the DS alert and this report, before taking any action. Noting, however, the nasty tone of even Doc's response right here ("probably because doing research is bothersome"), which doesn't exactly suggest he's currently taking any criticism to heart. Bishonen | talk 10:44, 1 August 2016 (UTC).
    • Adding: Actually, I hadn't realized that some of the worst posts by Doc on Talk:Donald Trump were made after the discretionary sanctions alert, which apparently, just like the warnings (including mine), made no impression at all. I've topic banned him for one month from all Donald Trump-related pages. Bishonen | talk 11:09, 1 August 2016 (UTC).
    • Reply to Doc: Yes, it's supposed to be simple. Discretionary sanctions are actually meant to make it simpler to ban disruptive editors from controversial pages; they're not intended to add a layer of bureaucracy. I'm using my admin discretion, as is the intention of the discretionary sanctions. I would have done it without this AE report — as I said above, I was already writing up a warning to you — and it would be a bit paradoxical to let the report prevent me. On the other hand, I haven't "closed" the report. If other admins disapprove of my sanction, they can decide per consensus right here to void it. (Or to extend it, for that matter.) I'm sure there will be more admin input — America by and large isn't awake yet — so I suggest you may consider defending yourself a bit better before they arrive. For instance, if you're serious about me being "blatantly biased", "looking to settle the score," etc, you may want to offer some evidence. I don't know what you mean by it, for my part. What score? Bishonen | talk 11:37, 1 August 2016 (UTC).
    • Reply to @SMcCandlish: you would address Doc's aggressive behaviour specifically, with a ban from questioning the good faith of others. I hear you, but the problem with that is that it has fuzzy borders. It's harder for the user to comply with, and to feel secure that he is complying with it. It's easier for others to play gotcha. A topic ban is a lot 'cleaner': simple to comply with, simple to oversee. That said, Doc can certainly be blocked if he persists in what you call a "Usenet style". I hope he realizes that he's on notice wrt to that now, especially as far as attacking Volunteer Marek is concerned. Bishonen | talk 13:27, 1 August 2016 (UTC).
    • I concur with the sanction applied based on evidence presented here. If the behavior continues after the month, we can revisit an extended TB. --Laser brain (talk) 13:15, 1 August 2016 (UTC)
    • Their response in accusing Bishonen of "having an axe to grind" is both unhelpful and demonstrates they don't understand the problem with their behavior (and are thus likely to do it again). Also, see this on their talk page. Very much agree with the topic ban imposed. Lord Roem ~ (talk) 03:15, 2 August 2016 (UTC)
    • I fully agree with the decision by Bishonen; this is exactly the type of quick action to curb disruption that discretionary sanctions is designed to facilitate, and there was crystal clear cause for action here. Since SMcCandlish has also provided an indication that disruption has occurred outside the area of Donald Trump, I'll also warn in no uncertain terms that if this type of conduct occurs elsewhere in the area of American politics, the topic ban will be substantially broadened, and will be lengthened or made indefinite. Seraphimblade 04:16, 2 August 2016 (UTC)

    62.0.34.134

    Clear violation after several warnings. Blocked 72 hours. Seraphimblade 16:41, 4 August 2016 (UTC)
    The following discussion has been closed. Please do not modify it.

    This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
    Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

    Request concerning 62.0.34.134

    User who is submitting this request for enforcement
    RolandR (talk · contribs · deleted contribs · logs · filter log · block user · block log) 15:11, 4 August 2016 (UTC)
    User against whom enforcement is requested
    62.0.34.134 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

    Search CT alerts: in user talk history • in system log

    Sanction or remedy to be enforced
    WP:ARBPIA3#500/30
    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
    1. 08:18, 4 August 2016 Editing in the topic area despite repeated notifications that IPs are prohibited
    2. 17:06, 1 August 2016 Editing in the topic area despite repeated notifications that IPs are prohibited
    3. 12:33, 18 July 2016 Editing in the topic area despite notification that IPs are prohibited
    4. 13:36, 19 May 2016 Highly POV edit in the topic area despite notification that IPs are prohibited
    Diffs of previous relevant sanctions, if any
    If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)
    • Alerted about discretionary sanctions in the area of conflict in the last twelve months, see the system log linked to above.


    Additional comments by editor filing complaint

    This editor has been repeatedly warned that IPs are prohibited from editing any article that may be reasonably construed as being related to the Arab-Israeli conflict. Yet the IP continues to make such edits. It would appear from the content that the same editor has been using this IP for several weeks,

    Notification of the user against whom enforcement is requested

    Discussion concerning 62.0.34.134

    Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
    Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

    Statement by (username)

    Result concerning 62.0.34.134

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

    Volunter Marek and My very best wishes

    Sanction or remedy to be enforced
    WP:EE
    WP:ARBAPDS
    User against whom enforcement is requested

    Volunteer Marek (talk · contribs · deleted contribs · logs · filter log · block user · block log)
    My very best wishes (talk · contribs · deleted contribs · logs · filter log · block user · block log)

    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

    Volunteer Marek and My very best wishes have a history of tag-teaming in edit wars. Lately they have been doing this in articles relating to American politics.
    Examples: Since July 24, Volunteer Marek was edit-warring at Debbie Wasserman Schultz, especially regarding material on criticism of how DWS handled the NGP VAN data breach and the fact that she was booed off the stage at the DNC .

    Then on August 2, My very best wishes, who had hitherto never shown any interest in the article, appears out of nowhere to revert on behalf of Volunteer Marek (violating 1RR as well) .

    Same thing at Clinton Foundation on 8-9 July: My very best wishes steps in to revert on behalf of Volunteer Marek over a POV tag . They're tag teaming over other information as well:

    Same thing at Donald Trump on July 4: Volunteer Marek adds some text , and after it is removed, Mvbw shows up a few hours later to re-add it, even though he has never edited the article before .

    If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)
    Additional comments by editor filing complaint

    I had previously made a case request at WP:ARBCOM regarding tag teaming in eastern Europe related articles, but since that area is already under discretionary sanctions, I was told to file at WP:AE instead. There's a long history of tag-teaming, and it is not limited to WP:EE or WP:ARBAPDS.

    Beginning mid-2014 (and possibly earlier), Volunteer Marek and My very best wishes appear to be helping each other out in edit-wars by tag-teaming. VM is the more active of the two, and the tag-teaming typically has the form of VM getting involved in an edit-war in an article that My very best wishes has not previously edited. Once the edit-war is under way, My very best wishes appears out of nowhere and reverts on VM’s behalf. In a minority of instances, it is VM that steps into an edit-war that Mvbw is involved.

    Since mid-2014, the tag teaming has occurred over a large number of articles (at least 40 in 2015 alone, although there are possibly more), some of which are quite obscure (e.g. Philip M. Breedlove, Khan al-Assal chemical attack, The Harvest of Sorrow). Initially the tag-teaming was restricted to Eastern Europe-related articles, particularly the Ukraine crisis, but as of 2015 it has spread to non-EE articles (example), hence I'm inclined to believe that it's not merely mutual interests that guides them. Furthermore, though both these editors have edited for a long time, they edited few articles in common in the period 2012-mid 2014, with the number of articles they edit in common skyrocketing after that. It should be noted that VM edits a far larger variety of articles than Mvbw does; however, most of the articles Mvbw chooses to edit after mid-2014 appear to be articles VM edits, especially of those he is facing contention (i.e. the April contributions of Mvbw and VM are noticeably similar). The disruption this has caused is considerable. Some examples below: I don’t think all this is needed. Just a brief explanation as above and a link to the evidence page is sufficient.

    1. WP:GAME - Tag-teaming so as to circumvent 1RR articles, which appears to be the case at WP:ARBAPDS as well. See: followed by Mvbw's reverts . Then an attempt to have their opponents blocked at 3RRN . An example of this occurred recently at Russian military intervention in the Syrian Civil War, where VM ran out of 1RR reverts, only to have Mvbw revert and ultimately have the user blocked.
    2. Outnumbering lone opponents (sometimes having them blocked; example) ]) Not sure about this. How does one diff prove that?
    3. Article protections (example)
    4. Hampering the consensus building process (most noticeable through NINJA-style reverts with no TP participation; example) Not sure about this. How does one diff prove that?

    In order to see the extent of the tag-teaming, I have provided an extensive list of tag-team edit-war occurrences over the past year here.

    Notification of the user against whom enforcement is requested

    Discussion concerning Volunteer Marek and My very best wishes

    Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
    Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

    Statement by Volunteer Marek and My very best wishes

    Statement by (username)

    Result concerning Volunteer Marek and My very best wishes

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.