Misplaced Pages

Revision as of 11:21, 29 June 2016

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 WP:AE WP:ARE 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: ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and 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: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action was not reasonably necessary to prevent damage or disruption when first imposed, or 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: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action represents an unreasonable exercise of administrative enforcement discretion, or compelling circumstances warrant the full Committee's action. The administrator may indicate consent at any time before, during, or after imposition of the restriction. 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: ask the enforcing administrator to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and 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-enwikimedia.org). Modifications by administrators No administrator may modify or remove a sanction placed by another administrator without: the explicit prior affirmative consent of the enforcing administrator; or 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: 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. 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. 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. 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.

Debresser

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 Debresser

User who is submitting this request for enforcement

Nableezy (talk · contribs · deleted contribs · logs · filter log · block user · block log) 22:16, 7 June 2016 (UTC)

User against whom enforcement is requested

Debresser (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:Requests for comment/Jerusalem (I understand Im linking to an RFC here, however that RFC was mandated by ArbCom and is binding through July 9, 2016, and this topic area is covered by discretionary sanctions

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

1. 7 June 2016 Revert in violation of binding RFC

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

• Participated in an arbitration request or enforcement procedure about the area of conflict in the last twelve months, on 15 March 2016.

Additional comments by editor filing complaint

There was a binding RFC on claims to Jerusalem being capital of Israel and Palestine and its location that was mandated by the Arbitration Committee (Misplaced Pages:Requests for comment/Jerusalem). That RFC resulted in the material currently in the lead of the Jerusalem article and per the Arbitration Committee is binding for three years. A user added material to the lead that violated that RFC, was reverted, which was also reverted. This was prior to any talk page discussion. I reverted that final revert and opened a talk page section detailing why (here, with the user I had reverted agreeing that the material shouldnt be included. Debresser then ignores the binding RFC and re-reverts, writing in the talk page Sourced, relevant, neutrally worded. The Rfc is expiring. The Rfc avoided the issue. All in all, ample reason to keep this addition. By the way, is there anything you think is wrong with the text, apart from bureaucratic arguments? When Debresser was reverted he or she posted to that users talkpage that their revert was "hothead revert" (here). Im not quite sure why this user thinks that binding means something other than all users have to follow this, but a reminder is surely in order.

Re the idea that this is a personal issue, no, not at all. Debresser is the only one to have reverted following the explanation that the material violated a binding RFC. And when asked to revert declined to do so. And then complained when somebody reverted him or her. Debresser's comment on the talk page of that article implied that he or she felt that a binding RFC did not apply to him or her. That is what brought me here. nableezy - 00:09, 8 June 2016 (UTC)

Sorry Debresser, I guess an edit summary that says the RFC is expiring in a month, a comment on the talk page saying the edit should stand, a comment on the talk page of the person that reverted you calling their revert hotheaded, those things dont lead to the reasonable conclusion that a. you knew that you were prohibited from making said edit due to a binding revert, b. didnt care, and c. wouldnt self-revert. Silly me, where could I have possibly gotten that idea. You know what I find disruptive? Editors thinking the rules that apply to everybody else dont apply to them. Editors who knowingly revert against a consensus (thats what an RFC determines fyi). Basically, you. nableezy - 21:11, 8 June 2016 (UTC)

@OID, I object to that edit on a number of grounds. However, the rule breaking is what is relevant on this board for a topic area that is covered under discretionary sanctions. Bright line rules only work if when somebody breaks them there isnt hand waving about well its only a technicality.

Notification of the user against whom enforcement is requested

Notified

Discussion concerning Debresser

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 Debresser

Nableezy seems to have a personal issue with me, because of the three editors who made this same edit, I am the only one he is reporting. Nableezy has a huge POV in the I/P-conflict area, and we have conflicted on many articles already. He is now trying to fight his personal vendetta against me through the editors at WP:AE. I think that is fair reason to dismiss this report. Recently he engaged in an edit wat at Ancient synagogues in Palestine, for which I decided not to report him. I am disappointed that he should repay me in this way.

As to the actual matter at hand, I think Talk:Jerusalem#addition_to_the_lead is where the discussion is taking place, and where I have made my arguments, and have already stated, that I will not challenge the Rfc, which stands till July 9. At the same time, I think the issue will have to be re-visited in the near future, if only to avoid edit wars, blocks and a lot of bad blood, and the proposed edit is a very good NPOV candidate, summing up the issue well and along the same lines as the Rfc.

In short, I think this report should boomerang back on Nableezy for the blatant personal motives behind this report, as well as his own recent WP:ARBPIA violations on "Ancient synagogues in Palestine".Debresser (talk) 23:36, 7 June 2016 (UTC)

@EdJohnson The 9 July date comes from counting 3 years after the Rfc reached a conclusion. Debresser (talk) 09:51, 8 June 2016 (UTC)

@Nableezy No need to say things you can't possibly know. I didn't refuse to revert. Somebody else reverted my edit even before I read your post on my talkpage. You continue with your bad faith assumptions, viewing Misplaced Pages as a battlefield, and me as the enemy. I find this attitude of yours disruptive. Debresser (talk) 21:01, 8 June 2016 (UTC)

@GoldenRing I know it is not advised to antagonize editors here, but I don't understand what further "backing down" is needed, after I have already stated both here and on the talkpage that I will not challenge the status quo? You did read my posts here and on the talkpage, didn't you? Debresser (talk) 10:56, 10 June 2016 (UTC) @GoldenRing In view of the above, neither do I understand what you claim I am "doubling down on". Debresser (talk) 19:06, 12 June 2016 (UTC)

@GoldenRing The Rfc specifically states that the consensus reached in it is binding only for a 3-year period. There is no rule on Misplaced Pages that an Rfc is needed to establish consensus, including to establish if there has been a change of consensus. A simple talkpage discussion, or even a bold edit that is accepted by the community, per definition can establish a new consensus. Debresser (talk) 11:35, 10 June 2016 (UTC)

@User:Newyorkbrad Ha, ha. That's a good one. Debresser (talk) 04:35, 24 June 2016 (UTC)

@Seraphimblade I don't think you are correct. See my comment above to GoldenRing, that there is no rule that an Rfc must be followed by an Rfc. Any way of establishing consensus is valid. The only exception could perhaps be, if such a stipulation were made specifically in the first Rfc, as in the current example provided by The Wordsmith below. Debresser (talk) 14:28, 28 June 2016 (UTC)

Statement by OID

Ed, dates from RFC's are always taken from the closure of an RFC as that is the point at which consensus has been determined by the closer. There would be no point in a fixed for 3 years consensus being valid until the actual consensus was determined. Saying that, it would still be up in a month anyway, so suggest close with trouts for everyone. Nableezy, if you have to rely on technical rule-breaking to revert an edit, rather than addressing the substance of the edit, it tends to get peoples backs up. 'Would this edit be controversial in a months time?' should be the question you ask yourself. Only in death does duty end (talk) 10:28, 8 June 2016 (UTC)

Comment by GoldenRing

I think Timoetheus has the right of it here; RfCs do not expire as such. Consensus can change, but the right way to go about changing consensus established in an RfC is a new RfC, not gung-ho edits to the article before the time limit established by the RfC has even expired and especially not in an article as contentious as this one. I suggest User:Debresser backs down and apologises and we let this lie; if not, sanctions are probably appropriate. GoldenRing (talk) 10:21, 10 June 2016 (UTC)

@Debresser: Consensus is always binding. It doesn't expire. I read the three-year limit in that RfC as essentially the same as a moratorium on further discussion. But however you read it, the essential point is that it hasn't expired. Of course it doesn't take an RfC to establish consensus - but when one has been held, a change made without any discussion whatsoever doesn't cut it. Since you're doubling down on this, I can't see what else to recommend but sanctions. GoldenRing (talk) 21:35, 10 June 2016 (UTC)

Statement by ZScarpia

Consensus-wise, where things will probably now turn ugly is that there are perceptions among some editors that consensus is established by carrying out a show of hands and that personal opinions, rather than the contents of reliable sources, establish what is factual and what is neutral.     ←   ZScarpia   17:35, 11 June 2016 (UTC)

Statement by Sir Joseph

An RFC is not consensus. Simple as that. It is a ruling that must be followed but when that ruling is sunsetted, then there is no obligation to follow that ruling. General Wiki rules and policies apply but you can't say that once there is a temporary RFC, or injunction, then any change requires a consensus or new RFC. Sir Joseph 15:46, 23 June 2016 (UTC)

Statement by (username)

Result concerning Debresser

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

• The original Arbcom motion was passed on December 27, 2012. It provided that the ban on changing the lead of Jerusalem 'will be binding for three years from the adoption of this motion'. To me, that implies December 27, 2015, so the freeze on changing the lead has already expired. The RfC closers stated that 'this decision is binding for three years' on 9 July, 2013 but I don't see that the closers were given authority to change the date specified in Arbcom's own motion. EdJohnston (talk) 05:05, 8 June 2016 (UTC)
• Ed makes an interesting point. I do not recall any discussion about it, but then when we passed the appointments motion I don't think any of us expected the process to take half a year to conclude.

  That said, in my view, even after the three-year period ends, the conclusions reached in the RFC remain consensus until and unless the existence of a different consensus is demonstrated, and until then edits that are substantially contrary to those conclusions remain sanctionable under DS for failure to "comply with all applicable policies and guidelines" and "follow editorial and behavioural best practice" (see WP:AC/DS#guide.expect). T. Canens (talk) 05:22, 8 June 2016 (UTC)

• If we accept T. Canens' view, we should place a new banner on the talk page of Jerusalem. We should tell editors they are risking a block if they change the lead away from the 2013 RfC version before such time as a different consensus is demonstrated. EdJohnston (talk) 03:15, 12 June 2016 (UTC)
• It appears that extending the freeze at Jerusalem is an option that is within our power, under discretionary sanctions. See WP:Arbitration/Requests/Clarification and Amendment#Clarification request: Genetically modified organisms where the committee is still considering a parallel issue regarding GMO. See the comments by User:Salvio giuliano and User:Drmies in that ARCA, though not everyone agrees with them. Why not keep this Jerusalem-related AE open until the ARCA finishes, and see if we want to propose something for Jerusalem. We could make a DS stating that the wording of the Jerusalem lead is still frozen until a new RfC is held. EdJohnston (talk) 14:33, 15 June 2016 (UTC)
  • I have reopened the thread, because that request for clarification has been dealt with. As I said there, as far as I'm concerned, a restriction along the lines of that one would be a cromulent use of DS. Tarapia tapioco (aka Salvio) (talk) 08:24, 21 June 2016 (UTC)
• Unless there is an admin who wants to give us wording for a new discretionary sanction reinstating the freeze, I suggest this be closed with warnings to User:Debresser and User:Plot Spoiler. They changed wording that was agreed upon in a large RfC in 2013 without providing evidence of a new general consensus in favor of their version. I doubt that anyone is looking forward to a new edit war on the lead of Jerusalem. Given data we currently have, it appears that Debresser and Plot Spoiler are risking admin action if they continue, which might consist of blocks or a page ban. EdJohnston (talk) 15:26, 23 June 2016 (UTC)

• I don't think we need to reinstate or extend the freeze, which is best read as a moratorium on new discussions; I do not currently see a need to prevent new RFCs on this topic. However, it is elementary that a consensus reached after an extensive and well-attended discussion requires a discussion of similar caliber to undo. Editors who ignore the existing consensus do so at their own peril. T. Canens (talk) 20:26, 23 June 2016 (UTC)

• I perceive nothing sanctionable here, but I also would remind editors that "next year in Jerusalem" does not mean "next year more arguing about Jerusalem". Newyorkbrad (talk) 00:20, 24 June 2016 (UTC)
• I agree broadly with T. Canens. If the wording was agreed upon after a broad and well-attended RfC, a new RfC of similar scope would be needed to propose changes to it, other than minor edits that do not substantially change its meaning or content. I'd suggest closing with a warning that seeking new consensus would be required prior to any such change. I don't, however, want to see an extension of any moratorium on such discussions, as it is an evolving situation, and it's entirely possible that events have necessitated changes or additions, or rendered some of the current information obsolete or inaccurate. Seraphimblade 16:21, 27 June 2016 (UTC)
• If it interests anyone, we're currently holding an RFC on GMOs based on the Jerusalem model, and the DS I logged to enforce it is as follows: "A moderated RfC is being held at Misplaced Pages:Requests for comment/Genetically modified organisms to determine how to phrase the safety of GM foods across all relevant articles. Whatever consensus is decided shall not be modified or overturned without an equivalent RfC. Additionally, the RFC is under further restrictions listed on that page and in the editnotice, including WP:0RR." The Wordsmith 14:34, 28 June 2016 (UTC)

Rms125a@hotmail.com

Wuerzele

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 Wuerzele

User who is submitting this request for enforcement

Kingofaces43 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 12:23, 22 June 2016 (UTC)

User against whom enforcement is requested

Wuerzele (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/Genetically_modified_organisms#Wuerzele_topic_banned

Misplaced Pages:Arbitration/Requests/Case/Genetically_modified_organisms#Casting_aspersions

Misplaced Pages:Arbitration/Requests/Case/Genetically_modified_organisms#Discretionary_Sanctions

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

1. Violates topic ban editing at Monsanto legal cases and returning to battleground behavior.
2. Casting asperisions

Diffs of previous relevant sanctions, if any

1. Topic banned by ArbCom: "Wuerzele is indefinitely topic-banned from all pages relating to genetically modified organisms and agricultural chemicals, broadly construed; appeals of this ban may be requested no earlier than twelve months since the date the case closed."
2. Previously blocked for edit warring and general combativeness towards editors.

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

• Mentioned by name in the Arbitration Committee's Final Decision linked to above.

Additional comments by editor filing complaint

Wuerzele was previously topic banned for extremely combative behavior, constantly sniping at editors, etc. while edit warring The discretionary sanctions and the topic bans handed out by ArbCom specifically say all pages relating to genetically modified organisms, agricultural chemicals, etc. broadly construed including the companies that produce them. The discretionary sanctions were specifically reworded by ArbCom to include the companies themselves to prevent prevent a case like this where topic banned editors still try to hang around related pages and continue additional behavior problems.

In addition to the diff itself being in the topic ban page, the edit summary shows a return to the very sniping behavior that resulted in their ArbCom topic ban, "Undid revision 726362373 by Kingofaces43 (talk) who appears not to read the newspaper? common knowledge, decent coverage". It's that kind of sniping directly at editors that Wuerzele has shown they are incapable of stopping that resulted in their ban, so I would like an admin to weigh in on how to further deal with their behavior. This response was to me removing the content from a previous editor for poor sourcing. The lawsuit in particular involved a branch of Monsanto that's using climate modeling, etc. to recommend pesticide, fertilizer, etc. applications for farmers, which puts this content squarely in the realm of the topic ban without even needing to consider broadly construed.

Wuerzele has also now engaged in apsersions: "No, I consider this retaliatory, because I exposed your relentlessly controlling, always pro-industry and negative editing behavior." This was the exact attitude this ArbCom principle was meant to put a stop to and why Wuerzele was topic banned. That this is still continuing after their sanctions is a problem, especially since my edit removed content that actually favored the company (they were the one filing the complaint this time), which runs completely contrary to the hounding narrative Wuerzele is still trying to pursue against me.

At this point, a one-way interaction ban from me seems logical to diffuse this continued behavior. The only times I ever interact with Wuerzele now is responding to when they engage in this behavior when they still pursue my edits. There shouldn't be a need for a two-way interaction ban since I generally try to avoid Wuerzele and haven't had anything with respect to Wuerzele that would warrant the two-way ban since the ArbCom case. Kingofaces43 (talk) 15:27, 22 June 2016 (UTC)

EdJohnston, the WSJ source doesn't cover much detail, but other sources regularly discuss things like seed choice, pesticide application, etc. as the core products of the decision making platform this company markets. There's really no way to say this doesn't relate to the topic ban in a broadly construed manner.

The larger problem though is the continuation of sniping on multiple counts I mentioned above. Arbs specifically expanded the DS to company pages saying that they didn't need to expand the topic bans as DS would take care of editors that immediately jump into behavior that resulted in their bans again while testing the edge of their ban. (read the arb opinions on topic bans) That's exactly what's happening here. Kingofaces43 (talk) 15:48, 23 June 2016 (UTC)

Notification of the user against whom enforcement is requested

Discussion concerning Wuerzele

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 Wuerzele

Statement by Tryptofish

Just before I found this AE, I had seen the edit in question and reverted it. This is really a no-brainer: the page is about Monsanto, and it absolutely is within the scope of the topic ban. It's a pity, because Wuerzele has been doing a good job of obeying the sanctions until now. --Tryptofish (talk) 21:39, 22 June 2016 (UTC)

About being within scope, Misplaced Pages:Arbitration/Requests/Case/Genetically_modified_organisms#Discretionary_Sanctions specifically includes "the companies that produce them". --Tryptofish (talk) 22:43, 22 June 2016 (UTC)

@EdJohnston: Yeah, I see what you mean and you are technically correct. (At this point, Tryptofish mumbles under breath about ArbCom dropping the ball about GMOs yet again.) The way I see it, I really do not care whether there is a block or a warning. As I said above, until this flare-up, I've been impressed with Wuerzele's adherence to the rules while remaining otherwise a good contributor. Looking back at the Arbs' statements in their vote not to expand the topic bans even while they were expanding the DS, I note that a couple of them said explicitly that it would be reasonable to apply DS to companies if the need arises for topic-banned editors, so that would justify a firm and final warning here, instead of a block. I also note with a bit of irony that the justification they gave was that the topic-banned editors hadn't tested this boundary yet. And, as someone who watched the whole case very closely, I feel that I am correct in saying that the change in the DS language was never meant as an expansion of the scope, but rather, as a clarification. Thus, companies really were included all along in the "broadly construed" part of the topic ban language, and maybe that should not allow for a get-out-of-jail free card. So that is an argument for an AE block. I guess it comes down to what Wuerzele could reasonably be expected to have understood from what the Committee articulated. --Tryptofish (talk) 19:11, 23 June 2016 (UTC)

Newyorkbrad, you make some very good points about civility and decorum. But I hope that the result of this AE will not take the form of saying "go ahead and edit through the loophole, but you are warned to be civil when you do so". If there is a warning, as opposed to a block based on "broadly construed" (and "broadly construed" really does need to mean something), I hope that it will be a warning that, in addition to civility, there should be no "company" edits going forward. Going forward, the inclusion of companies in the scope is clearly the Committee's intent. --Tryptofish (talk) 23:00, 24 June 2016 (UTC)

Statement by (username)

Result concerning Wuerzele

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

• Though Wuerzele is not banned by the Committee from making edits about Monsanto, if the change he has made at Monsanto legal cases cocerns genetically-modified seed then it is a violation. Not seeing any words to the contrary in the WSJ article, it's reasonable to assume that the scheme for stealing Monsanto's data would be part of a plan to use the information to grow genetically-modified seed elsewhere. This is a narrow enough issue that this request might need only a warning. EdJohnston (talk) 15:14, 23 June 2016 (UTC)

@Tryptofish: Please see the linked page. In January 2016 the committee broadened the DS to include the companies but decided not to change the topic bans of those already sanctioned in the decision, including Wuerzele. They are still allowed to edit about the companies. EdJohnston (talk) 15:56, 23 June 2016 (UTC)

• Even assuming there was no violation of the topic-ban, an edit summary like this one is uncivil and inappropriate. (The edit summary also reflects a misunderstanding of the edit Wuerzele was reverting; Kingofaces43 had questioned the notability or importance of Monsanto v. Chen, not whether the case exists or has been reported anywhere.) If Wuerzele plans to continue editing these articles to the extent permitted by (depending on one's viewpoint) either a limitation of or a loophole in the remedies, he should do so with civility and decorum. Subject to any explanation Wuerzele may provide, I would support a warning on this basis. Newyorkbrad (talk) 00:16, 24 June 2016 (UTC)
  • @Wuerzele: Please post a response to this request, addressing both the scope and civility issues, the next time you edit. Thank you. Newyorkbrad (talk) 14:57, 27 June 2016 (UTC)

HughD

Aaabbb11

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 Aaabbb11

User who is submitting this request for enforcement

PCPP (talk · contribs · deleted contribs · logs · filter log · block user · block log) 17:22, 28 June 2016 (UTC)

User against whom enforcement is requested

Aaabbb11 (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/Falun_Gong_2 :

(Disclaimer: I am current under a topic ban from 2011 over the FLG articles as documented here . I have not edited WP in the years since, and currently I have no intention to edit the FLG articles or appeal the ban. I am writing this per WP:BANEX, where it refers to another user's conduct. I would be happy if an admin can clarify or notify me otherwise.)

Aaabb11 is a single purpose account, whose sole major edits relates to editing the Falun Gong series of articles, often pushing a pro-FLG POV. As indicated by his edit counter, his most edited articles include Persecution of Falun Gong, Epoch Times, Kilgour-Matas report etc. .

Aaabbb11's edit patterns are counterproductive, disruptive, and indicated has a serious problem with WP:COMPETENCE and WP:NPOV, often pushing blatant POVs which even other non-involved editors question. His basic habits is to push the views of Gutmann, Kilgour/Matas et al on organ harvesting into basic China or communism related articles.

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

1) POV pushing on the China page: . In spite of others questioning the amount of undue weight, Aaabbb11 has continued to edit war on the page, pushing Kilgour-Matas, and "genocide" allegations, and push personal attacks against users who reverted him.

• Problematic article edits - pushing a distinct POV:

• Personal attacks, called two editors, including one long term editor on the China articles, as Chinese trolls, and called for them to investigated

2) Soapboxing with the Gao Rongrong page . The page, as noted by three different editors at AFC, has questionable notability . Nevertheless, the article was created by Aaabbb11 on June 16, yet even per the article itself, the sources mostly date from 2005, and even the Daily Mail article from 2012 only gave a two pictures and sentences. Note his rationale for creation of the article, which has little to do with WP policies and guidelines, but to "embarrass the PRC government", "highlight the stupidity of the torturers", promote the FLG mouthpiece Epoch Times as "having strong focus on human rights", and interestingly, directly admitting that there is a lack of coverage of of Gao Rongrong's case, all highlighting an issue of competence.

Aaabbb11 also previously inserted the the disputed image of the deceased woman, plus FLG soapboxing, onto the page about the electroshock weapon and cattle prod, and not to mention scrolling down his own talk page.

3) POV pushing on the Anti-communism page: .

• Problematic article edits - continued attempts to push WP:UNDUE, plus misusing an image of a deceased FLG practitioner

• Note that his last edit on the article against is littered with WP:UNDUE, adding images that has little to do with anti-communism, more with FLG itself.

4) Deletion of sourced material on the Epoch Times page:

• Problematic article edits - deletion of sourced material referring to the paper as anti-CCP, pro-FLG

5) Attempts to change the article Persecution of Falun Gong to genocide, a position which is not supported by reliable sources. . He also resorts to further soapboxing .

6) Personal attacks, soapboxing etc.

• Referred to STSC as "denying the Chinese people from accessing true information"
• Later he called STSC a "propaganda victim" and WP would be better off without him.
• Referred to Zanhe and 小梨花 as single purpose accounts who should be investigated

7) Notifications from other editors over behavior:

• Notified by Benlisquare over disrputive editing
• Notified by Benlisquare and Simonm223 over disruptive behavior at the China article
• Notified by STSC over disruptive editing and the improper use of dead woman's image

Diffs of previous relevant sanctions, if any

1. Previous block for edit-warring at the FLG main article space, over a wililink to the term "cult".

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

• Notified by JimRenge over discretionary sanctions on FLG.

Additional comments by editor filing complaint

Overall, Aaabbb11's edits are are littered with promotion and POV pushing for FLG, and his edits on the FLG related articles and Gutmann, Kilgour, Matas, et al. are filled with clear advocacy. Content disputes aside, Aaabbb11's editing patterns and behavior indicates that he's a clear single purpose account who is here to push views not consistent with scholarly studies on the subject. I request

Notification of the user against whom enforcement is requested

Discussion concerning Aaabbb11

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 Aaabbb11

Current editors such as Zujine and TheBlueCanoe should be asked for their opinion. None of the 3 people making statements against me is a current editor of Falun Gong pages, so I don't think their opinion counts as much as current editors such as Zujine and TheBlueCanoe who are extremely knowledgeable, experienced and respected in my opinion.

I'd also like to point out that I gave up editing the China page some time ago. I change what I'm doing as I learn more and get bored with what I'm doing. I made mistakes in the past but I learn from them. I don't enjoy the conflict that happens on some[REDACTED] articles. Some people find the truth very hard to accept but it should be on[REDACTED] as much as possible. The truth is shocking sometimes. I'd like to forget about some of the things I know.

Statement by simonm223

For what it's worth, tendentious and probably paid full-time editors with substantial and persistent biases, like Aaabbb11 are the reason I don't edit[REDACTED] anymore. And frankly, I'm not likely to come back to Misplaced Pages if Aaabbb11 is gone, because the problem is systemic and persistent. But if any of you care about Misplaced Pages being anything other than a propaganda vehicle for whichever person has the most time and energy to burn fighting pointless battles you'll ban this user from ever editing anything even peripherally related to the Falun Gong or China. Simonm223 (talk) 17:42, 28 June 2016 (UTC)

Statement by STSC

Aaabbb11's had indiscriminately inserted the image of Gao Rongrong in many articles (610 Office, Cattle prod, Electroshock weapon, Freedom of religion in China, Human rights in China, Anti-communism). When I complained about the inappropriate image inclusion , Aaabbb11 then deliberately posted 19 pieces of that image all over his/her talk page. Just this disgraceful and disrespectful behaviour alone deserves a complete site ban. STSC (talk) 18:50, 28 June 2016 (UTC)

Statement by Rhoark

I've looked at the diffs and see no basis for complaint. The filer is topic banned from this area and has no connection to the issue at hand that would activate BANEX. STSC needs to stop dropping people hostile templates like he owns the place. Simonm223 should tell us more about how he was canvassed, since he doesn't edit anymore. Close this with no action. Rhoark (talk) 22:05, 28 June 2016 (UTC)

Result concerning Aaabbb11

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

• I'm certainly seeing an aggressive pattern in the edits and actions undertaken by Aaabbb11, which is cause for concern. I think a topic ban from Falun Gong might be in order, but will hear what Aaabbb11 has to say if they'd like to explain what's going on here. Seraphimblade 20:31, 28 June 2016 (UTC)