Dispute resolution (Requests) |
---|
Tips |
Content disputes |
Conduct disputes |
Wikipedia Arbitration |
---|
|
Track related changes |
A request for arbitration is the last step of dispute resolution for conduct disputes on Wikipedia. The Arbitration Committee considers requests to open new cases and review previous decisions. The entire process is governed by the arbitration policy. For information about requesting arbitration, and how cases are accepted and dealt with, please see guide to arbitration.
To request enforcement of previous Arbitration decisions or discretionary sanctions, please do not open a new Arbitration case. Instead, please submit your request to /Requests/Enforcement.
This page transcludes from /Case, /Clarification and Amendment, /Motions, and /Enforcement.
Please make your request in the appropriate section:
|
Contents
- 1 Requests for arbitration
- 2 Requests for clarification and amendment
- 2.1 Clarification request: Gun control
- 2.1.1 Statement by GoldenRing (Gun Control)
- 2.1.2 Statement by Dlthewave
- 2.1.3 Statement by Bishonen
- 2.1.4 Statement by Simonm223
- 2.1.5 Statement by Ivanvector
- 2.1.6 Statement by Doug Weller
- 2.1.7 Statement by Black Kite
- 2.1.8 Statement by Levivich
- 2.1.9 Statement by RexxS
- 2.1.10 Statement by S Marshall
- 2.1.11 Statement by User:SmokeyJoe
- 2.1.12 Statement by Hobit
- 2.1.13 Statement by RoySmith
- 2.1.14 Statement by Sandstein
- 2.1.15 Statement by Cryptic
- 2.1.16 Statement by GMG
- 2.1.17 Statement by DGG
- 2.1.18 Statement by Drmies
- 2.1.19 Statement by Xymmax
- 2.1.20 Statement by Wnt
- 2.1.21 Statement by Spartaz
- 2.1.22 Statement by Fish and karate
- 2.1.23 Statement by Alanscottwalker
- 2.1.24 Statement by Deryck
- 2.1.25 Statement by Atsme
- 2.1.26 Statement by SMcCandlish
- 2.1.27 Statement by EdChem
- 2.1.28 Statement by Aquillion
- 2.1.29 Statement by Ymblanter
- 2.1.30 Statement by {other-editor}
- 2.1.31 Gun control: Clerk notes
- 2.1.32 Gun control: Arbitrator views and discussion
- 2.1 Clarification request: Gun control
- 3 Motions
- 4 Requests for enforcement
Requests for arbitration
Requests for clarification and amendment
Clarification request: Gun control
Initiated by GoldenRing at 15:38, 25 February 2019 (UTC)
List of any users involved or directly affected, and confirmation that all are aware of the request:
- GoldenRing (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) (initiator)
- Dlthewave (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)
- Bishonen (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Confirmation that all parties are aware of the request
- Notification of Dlthewave
- Notification of Bishonen
Statement by GoldenRing (Gun Control)
In the course of a request at the arbitration enforcement noticeboard, I deleted User:Dlthewave/Whitewashing of firearms articles as an arbitration enforcement action. My reason for doing so is that WP:UP states that "Users should generally not maintain in public view negative information related to others without very good reason. Negative evidence, laundry lists of wrongs, perceived flaws, collations of diffs and criticisms related to problems, etc., should be removed, blanked, or kept privately (i.e., not on the wiki) if they will not be imminently used, and the same once no longer needed. The compilation of factual evidence (diffs) in user subpages, for purposes such as preparing for a dispute resolution process, is permitted provided it will be used in a timely manner.
In my view, this page is obviously the sort of "collation of diffs and criticisms related to problems" that the policy forbids. Dlthewave has repeatedly stated (eg diff) that the purpose of the page is as background to an opinion piece in The Signpost; since I have repeatedly asked and they have given no other explanation, I have taken this as an admission that the material is not intended for dispute resolution. My justification for doing the deletion as an arbitration enforcement action is the "other reasonable measures that the enforcing administrator believes are necessary and proportionate for the smooth running of the project
" provision of WP:AC/DS#sanctions.user. I'm aware that deletion is unusual as an enforcement action, but didn't expect it to be as controversial as it has proved.
Dlthewave appealed this at AE and in the course of the appeal, Bishonen advised them to start a request at WP:DRV, which they did. Bishonen undeleted the page so that those participating in the DRV request could see the content. I have objected to the undeletion as a unilateral overturning of an enforcement action but Bishonen has declined to self-revert this. I have no interest in wheel-warring over it.
A number of editors at DRV have objected to the deletion, for two main reasons: Firstly, that the content doesn't violate policy, and secondly that deletion is not a valid enforcement action (ie is not authorised under discretionary sanctions). Additionally, I and a couple of other editors have pointed out that DRV can't review enforcement actions, but a number of editors have objected this, too. These objections include some very experienced editors who I respect and I'm not so sure of myself as I was 24 hours ago. So I would like the committee please to answer these questions:
- Is deletion of a page an enforcement action that is authorised under discretionary sanctions?
- If the answer to 1 is "yes", was Bishonen's undeletion a violation of WP:AC/DS#sanctions.modify?
- If the answer to 1 is "yes", is DRV a valid venue to review deletions carried out under discretionary sanctions?
If the answer to 1 is "yes", while we're here, we may as well consider the substance as well: Was deleting this page in line with policy and a reasonable exercise of administrator discretion in an area subject to DS?
I would like to be very clear that I am asking these questions for clarification and am not looking for action against anyone; in particular, I am not requesting any action against Dlthewave for starting the DRV (they were, after all, advised to do so) nor against Bishoen for giving that advice or for undeleting the page (Bishonen is an admin I hold in high regard and while we disagree on this point of DS procedures, any action against her would be a great loss to the project; I would much rather concede the point and let the undeletion stand than see action here).
- @SilkTork: I don't know how much clearer I can make my rationale, but I will try: The policy says, "Negative evidence, laundry lists of wrongs, perceived flaws, collations of diffs and criticisms related to problems, etc., should be removed." The deleted page is a long list of quotes of edits made by other editors which Dlthewave himself thinks is "important to highlight the long-term pattern" of which their AE complaint is "a continuation" (diff). This is plainly a collection of negative evidence, and the attempt to lawyer around the language by not giving diffs by quoting the content of the diff and giving a link to where it can be found is, in my view, entirely specious. Dlthewave themselves said in the diff I have just quoted, "It is understandable that this may be viewed as polemical, howeveri feel that it is important to highlight the long-term pattern" - or, in about as many words, they know it violates policy but think their cause is more important. GoldenRing (talk) 22:59, 25 February 2019 (UTC)
- @SilkTork: I see what you're getting at. As far as I know, this page was not the subject of any substantive discussion prior to the deletion. Dlthewave brought an action at AE and another editor pointed out this page; I asked Dlthewave to explain how it was not a violation of POLEMIC (diff). Two and a half days later I had received no response (diff), despite Dlthewave having edited the AE complaint in that time (diff), so I went ahead and deleted it. I do not claim any of the speedy deletion criteria as justification for the deletion, but rather the authorisation of discretionary sanctions.
- Regarding your question about blanking v deletion, I took the word "remove" in WP:UP to include deletion and it is routinely interpreted this way at MfD, where POLEMIC is generally accepted as grounds for deletion, not blanking. Although there is some controversy about where the line between keep and delete outcomes is, no-one argues that POLEMIC is not grounds for deletion. Pages with similar content are deleted at MfD, see eg 1 2 3, especially the last one which likewise claims to document whitewashing of an article; there are many others in the archives of MfD.
- My reasoning for doing this as an arbitration enforcement action rather than through community processes was (and is) that maintaining such a page is not conducive to collaborative editing in the topic of gun control; that gun control is an area where discretionary sanctions have been authorised; and that administrators are expected to use DS "to create an acceptable collaborative editing environment for even our most contentious articles" (WP:AC/DS#admin.expect). If administrators working AE are suddenly expected to use community processes to resolve disputes, then what was the point of authorising DS?
- To answer a couple of procedural queries I missed in my last reply, Dlthewave met the awareness requirements at the time of the enforcement action because they had started a request at the arbitration enforcement noticeboard (the deletion happened in the context of this request) and I don't see how an editnotice is relevant to this particular action as it doesn't involve a page-level editing restriction. GoldenRing (talk) 10:18, 26 February 2019 (UTC)
- @SilkTork: I am seriously considering other ways out of this and have been for some time. Nonetheless, I think the committee needs to clarify whether deletion is a valid enforcement action; it is clear (most particularly from the comments at DRV and also those here) that a significant portion of the community think it is not, while I can't see how deletion is different to any other administrative action done under DS and authorised by the "other reasonable measures" provision of DS. In the meantime, I am a little unsure what you mean when you say, "such a deletion should meet with policy." There are a great many administrative actions taken routinely that are not authorised by policy but are authorised by discretionary sanctions: administrators cannot normally place topic bans, interaction bans, 1RR restrictions on users or pages, consensus-required restrictions, civility restrictions or BRD restrictions and yet these have all been applied unilaterally by administrators since the beginning of this year. Ordinarily, any of these would require a community consensus process (eg a discussion at AN for a topic ban) but are valid as unilateral actions because they are authorised by discretionary sanctions. How is deletion any different? Ordinarily it requires a community consensus process at XfD (ignoring for the moment speedy deletion criteria) but here it is a valid unilateral action because discretionary sanctions are authorised. And, in the end, what is more serious? Deleting a user page? Or banning a user? If you trust admins with the latter, you should trust them with the former. GoldenRing (talk) 16:22, 26 February 2019 (UTC)
- @SilkTork: I appreciate your point about arbcom needing the consent of the community to function and to be a positive force in the community. At the same time (and I know this is itself somewhat controversial in the community) my understanding is that all of the powers granted to administrators in discretionary sanctions are available because the community has ratified the arbitration policy which makes arbcom the final, binding decision-maker in disputes, not because of explicit policy changes. As GMG points out, the usual forms of DS are subject to a "boiling frog" effect; and this action is likely to be controversial not because it is invalid but because it is unusual. Posting it at DRV has involved a lot of users who are not accustomed to dealing with DS.If I had deleted a featured article on the main page without a very good reason, I would expect the action to be overturned at AN sharpish. That is the outlet the community has for controlling unilateral enforcement action with consensus.The committee still need to decide whether "other reasonable measures" means what it plainly says or rather "other reasonable measures except deletion," which some here are advocating. The committee still need to decide whether "All enforcement actions are presumed valid and proper, so the provisions relating to modifying or overturning sanctions apply, until an appeal is successful" means what it plainly says or rather "All enforcement actions are presumed valid and proper unless another admin unilaterally decides the action was obviously outside the scope of DS," which some here are advocating. GoldenRing (talk) 11:45, 27 February 2019 (UTC)
- @BU Rob13: That is a good point and I will strike my fourth question. GoldenRing (talk) 17:07, 26 February 2019 (UTC)
- @RexxS: I would like to correct a few things you have said:
- It is absolutely prohibited to unilaterally modify arbitration enforcement actions; seee WP:AC/DS#sanctions.modify. BLP and COPYVIO are not the only absolute prohibitions.
- All enforcement actions have what you describe as "the usual immunity to reversion", whether they are valid or not because all enforcement actions are presumed valid and proper until an appeal in one of AE, AN or ARCA succeeds; see point 4 of WP:AC/DS#appeals.notes.
- We do not prohibit collections of negative information about other editors "for reasons of BLP" (if that were so, they would never be allowed) but because it's not a civil, collegial thing to do, though sometimes necessary for use in legitimate dispute resolution processes.
- And lastly, the elephant in the room: no careful reading is necessary, the whole page consists almost entirely of quotes of other editors statements at talk page. By what sophistry is this material not related to the editors who made those statements??? GoldenRing (talk) 23:24, 25 February 2019 (UTC)
- @RexxS: I hope no admins follow your interpretation of policy; it is a recipe for desysopping. The simple reality is that the community has accepted the arbitration committee as the final, binding decision-maker in conduct disputes and, short of changing the arbitration policy, the community cannot override its decisions. Some of its decisions are to authorise discretionary sanctions; to make administrator actions under DS appealable only to AE, AN and ARCA; and to give such actions a presumption of validity until they are overturned in a proper appeal. If you doubt this, you might find the level 2 desysop of Yngvadottir for a single instance of overturning a controversial AE action instructive (in fact an AE action which was only confirmed by the committee in a 6-5 vote). GoldenRing (talk) 11:36, 26 February 2019 (UTC)
- @BU Rob13: I struggle to articulate what such a motion would even mean in practice. Essentially, I guess it means admins can delete pages as an enforcement measure so long as the page meets one of the criteria for speedy deletion or a consensus to delete exists at the relevant XfD venue. The only difference making deletion available under DS would make is that review would be reserved to AE, AN and ARCA rather than the usual deletion review process - yet PMC has argued for option B with review carried out at DRV! If "deletion done under DS" is going to be "deletion in line with deletion policy and reviewed at DRV" then it's indistinguishable from ordinary deletion and there's no point including it in DS - just propose a motion to exclude it.I do still feel strongly is that the existing DS wording allows deletion as it allows any other measure, and reserves review of such deletions to the arbitration appeal venues. The only argument I can see being made to the contrary is AGK's, which essentially says that a sanction placed on a page reading "This page is subject to 1RR" is not a sanction placed on a page. I don't understand it. Unless someone can propose another construction of the DS wording that excludes deletion, the now-closed DRV was out of process.Whether deletion should be allowed under DS is another question and not one I feel strongly about either way. As an enforcing administrator, I would probably prefer that the committee exclude deletion altogether from DS than to add further complexity to the scope and review processes for DS. GoldenRing (talk) 11:54, 12 March 2019 (UTC)
- @Opabinia regalis: To some extent I agree with you, and had I known what the outcome would be, I would have sent this to MfD. I saw AE deletion as a way to do this without drama, and clearly that was a mis-judgement; however, I would contend that much of the drama was not because of the AE action itself, but because it was sent to DRV out-of-process. And leaving the answer to the question "is deletion a valid AE action?" as "maybe" is not useful to AE admins who would like to know what the scope of sanctions possible under DS is. GoldenRing (talk) 10:22, 15 March 2019 (UTC)
- @BU Rob13: Are you sure that only deletions outside mainspace should be valid AE actions? What about actions that are also valid under one of the CSD, but which is marked as an AE action? I can easily think of cases in American politics, for instance, or indeed gun control, that should be deleted under CSD but which an admin might want to mark as an AE action to avoid a highly dramatised DRV. I do struggle to think of a valid mainspace deletion outside of the CSD, but I don't want to say it couldn't happen. GoldenRing (talk) 10:21, 15 March 2019 (UTC)
- @BU Rob13: I take your point about the optics of using DS to avoid scrutiny, but you also need to bear in mind that DS are authorised in areas where community processes have already broken down and are already ineffective, usually because there are large groups of otherwise-productive editors on either side of the dispute. Picking up your AP2 example, I think the likely outcome at MfD for such a page would be deletion. But I would choose to delete as an AE action every time because I know that if I send it to MfD, a crowd of fringe-supporters will emerge from the woodwork to argue against deletion; the same crowd will turn up at the inevitable DRV; and they will kick off at least three complaints at ANI in the course of proceedings and likely another two afterwards trying to contest the outcome. DS are indeed supposed to circumvent these highly-controversial community processes in highly-controversial topics. GoldenRing (talk) 11:37, 18 March 2019 (UTC)
- @Premeditated Chaos: So why don't all TBAN requests go via AN? Why do we allow AE to circumvent the usual community process of placing bans? GoldenRing (talk) 13:38, 18 March 2019 (UTC)
- @SilkTork: A some at WT:DRV have noted, your proposal leaves it unclear whether a deletion within existing deletion policy can be marked as an AE action to make it only reviewable at arbitration venues. GoldenRing (talk) 10:45, 25 March 2019 (UTC)
Statement by Dlthewave
Statement by Bishonen
@SilkTork: You have perhaps forgotten part of the process, then. Unless pages at DRV are temporarily undeleted, only admins will be able to read them, i. e. only admins will be able to discuss them in a meaningful way. It's not supposed to work like that. I followed these instructions for how to do it. Bishonen | talk 18:27, 25 February 2019 (UTC).
Statement by Simonm223
Is deletion of a page an enforcement action that is authorised under discretionary sanctions? Based on the argument by Ivanvector at DRV I would say no. It is not. Furthermore I think the argument that it constituted WP:POLEMIC in the first place is flawed. Simonm223 (talk) 16:21, 25 February 2019 (UTC)
Statement by Ivanvector
This response is directed to GoldenRing's bullet point #1 only, as the subsequent bullets assume a view with which I disagree.
As I stated at DRV, my view is that page deletion is not authorized by discretionary sanctions, certainly not explicitly, and neither in spirit. While the standard provisions authorize administrators to act in arbitration enforcement through the use of editing sanctions and page restrictions, and we grant significant latitude to administrators to create restrictions within the bounds of these categories and to block users who violate those restrictions in the name of arbitration enforcement, these powers do not extend to editorial and/or political control, nor wholesale removal of content. Furthermore, nothing in the gun control case appears to specifically enact these powers. And generally, it is common practice that the Arbitration Committee does not weigh in on matters of encyclopedia or userspace content, and as such it is an improper assumption that the Committee would wish to empower admins with unilateral deletion powers. But noting the disagreement at DRV, I would also like this to be explicitly clarified.
As for Bishonen's action and DRV itself in this incident: if Arbcom has explicitly declared that deleting a page is a sanction available for arbitration enforcement, then I would agree that AE would be the correct venue to review an Arbitration-enforcement deletion. However, the community's venue for deletions out-of-process is DRV, thus DRV is a logical venue for this incident. It is standard and widely-accepted practice to undelete content while its deletion is under review, and Bishonen's restoration ought to be viewed in that light unless and until someone can point to already-established Arbitration procedure in which the Committee has explicitly authorized userpage deletion as a discretionary sanction, and if and only if that process is already established, then owing to the present disagreement Bishonen should be given an acting in good faith pass on this one, or a "to satisfy the pedants" admonishment at the most severe.
Stating for the record that I believe that everyone carrying a mop has acted in good faith with respect to this incident. I also hold both GoldenRing and Bishonen in very high regard, and I appreciate GoldenRing seeking clarification on this point. Ivanvector (Talk/Edits) 16:35, 25 February 2019 (UTC)
- I would think that the situation described by Black Kite, in which an editor subject to an AE restriction creates a page in violation of that restriction, would be dealt with under WP:G5, and as a result the deletion itself would not be AE enforcement and the venue to review deletion would remain DRV. But maybe we are over-generalizing. Ivanvector (Talk/Edits) 17:35, 25 February 2019 (UTC)
- Again, as others have tried to point out but are apparently falling on deaf Committee members' ears, the policy which directs the deletion of English Wikipedia content is the deletion policy; to the best of my knowledge it is the only policy which does now or has ever had community consensus for deletion of an entire page (as opposed to revision deletion, suppression/oversight, or other actions which maintain a visible history). Observant editors will note that deletions directed by the Arbitration Committee are not mentioned in that document.
- Quoting from the deletion policy's companion guideline, Wikipedia:Deletion process: "The speedy deletion process applies to pages which meet at least one of the criteria for speedy deletion, which specify the only cases in which administrators have broad consensus support to, at their discretion, bypass deletion discussion and immediately delete Wikipedia pages or media." (bold in original, underline added) It's been said by several others here and elsewhere already: arbitration enforcement is not one of the criteria for speedy deletion. The deletion process document also specifies in no uncertain terms that deletions may only be performed outside the scope of the policy when ordered by the Wikimedia Foundation.
- Now quoting from the arbitration policy, which under the heading "policy and precedent", reads: "The arbitration process is not a vehicle for creating new policy by fiat. The Committee's decisions may interpret existing policy and guidelines, recognise and call attention to standards of user conduct, or create procedures through which policy and guidelines may be enforced. The Committee does not rule on content, but may propose means by which community resolution of a content dispute can be facilitated." (emphasis added)
- The Committee members now arguing that content deletion is in fact within the scope of arbitration enforcement are engaging in modifying the deletion policy by fiat. While GoldenRing and the members of the Committee may have very good reasons for wanting to allow content deletion as an arbitration power, the deletion policy does not currently permit this and the arbitration policy explicitly forbids it. If the Committee wishes to reserve these powers for itself, a community discussion is required to modify both policies. Unless and until those discussions happen, the Arbitration Committee is not authorized to delete pages, and likewise has no power to authorize administrators to unilaterally delete pages in the name of Arbitration enforcement.
- Following on that argument, GoldenRing's deletion must be considered to have been performed under the auspices of speedy deletion, since arbitration enforcement cannot authorize that action, and there was no discussion. It is very clearly stated in the community's policies that the venue to dispute a deletion, speedy or otherwise, is WP:DRV. The Committee insisting that this deletion can only be appealed to the Committee is, again, modifying policy by fiat. Ivanvector (Talk/Edits) 18:16, 26 February 2019 (UTC)
- @Premeditated Chaos: you're inventing policy again with your latest comment. As it stands, deletion under discretionary sanctions is forbidden because it is not expressly permitted, not the other way around, because the deletion policy (the only policy directing deletions) sets out when deletion is allowed, and expressly forbids all other deletions.
- @All the arbitrators: your straw poll is invalid. If you want to modify the community's deletion policy to permit deletions as arbitration enforcement, then do the work to modify that policy. That means putting it to the community in an RfC, not pretending that you can decide that that's how things are without any community input. The way this discussion is going is an alarming endorsement of admins doing any damn thing they please under a veil of arbitration enforcement, and of the Committee retroactively altering its own procedures to suit any such action. In this case, the Committee retroactively endorsed an out-of-process deletion, retroactively forbade discussion of the out-of-process deletion in the usual community forum for discussing improper deletions, retroactively endorsed (by omission) threatening with desysopping the administrator who restored the deleted page per the normal community expectation for discussing deletion challenges, and is attempting to retroactively modify the scope of standard discretionary sanctions to justify the entire affair. This entire discussion is an embarassment. Ivanvector (Talk/Edits) 21:57, 13 March 2019 (UTC)
- Just noting that the deletion review was closed five days ago now as "clear consensus is that this deletion should be overturned per the deletion policy", but the page remains blanked with the DRV notice. Presumably this discussion has had a chilling effect by which administrators are not carrying out the community's desired action out of fear of Arbcom reprisal, and for that matter, this is not only not an issue that the community cannot resolve, but it has already been resolved, other than this thread sitting open blocking anyone from doing anything. This request is close to entering its third week; to quote The Colonel, "get on with it!" Ivanvector (Talk/Edits) 17:20, 14 March 2019 (UTC)
- @SilkTork: the distinction between "to delete pages" and "to delete pages outside of the deletion policy" is moot, as deletions outside of the deletion policy are already not permitted; any deletion that is carried out with a rationale of arbitration enforcement is inherently outside of the deletion policy. None of this is putting an "AE admin" at a disadvantage over a non-"AE admin", (and when did we invent that distinction?) it simply means that if they wish to delete a page, they can do so under one of the methods and criteria already approved by the community, which is already a very broad scope. For example, in the situation you described, a page created in violation of an Arbcom restriction can be deleted under the community's criterion WP:CSD#G5. There's no need for an Arbcom back door here. Ivanvector (Talk/Edits) 13:56, 25 March 2019 (UTC)
Statement by Doug Weller
I agree with Ivanvector. Such a deletion is not within the scope of discretionary sanctions. Perhaps an Arbitrator with a longer memory than I have may find such a procedure but I'd be surprised. Certainly it was not authorised by us during the four years I was on the committee. I think everyone has acted in good faith with this but I believe that GoldenRing was wrong and that the page should not have been deleted. I've looked at the page and agree with those who say that the content does not violate policy. I'll also note that no editors have been named although obviously they can be identified via the links. I'll add that even if it hasn't been used it is information that has the potential to be useful. Doug Weller talk 17:10, 25 February 2019 (UTC)
Statement by Black Kite
I can think of situations whereby deletion would be in the purview of an AE action (for example, if a topic-banned editor was violating their TBan on a userspace page) but I agree with the two editors above that I can't see that this falls into this category. It is probably something that ArbCom could do with clarifying for future reference. Black Kite (talk) 17:28, 25 February 2019 (UTC)
- @SilkTork: It is SOP to undelete pages whilst they are at DRV so that non-admins can assess whether the close was correct - for example, whether a CSD deletion actually met the CSD criteria, or in the case of AfD whether the discussion comments were actually valid. In this case, with no AFD or standard CSD, then assuming the DRV is valid the page would have to be visible as otherwise no non-admins could make any judgement about the deletion. Black Kite (talk) 18:24, 25 February 2019 (UTC)
Statement by Levivich
If no harm would arise from having this page discussed at MfD, then it should be discussed at MfD, rather than deleted by any one person's unilateral action. Obviously both admin acted in good faith in a situation that is unclear and possibly unprecedented; any suggestion of sanctions would be over the top. Leviv ich 18:01, 25 February 2019 (UTC)
Statement by RexxS
If an administrator erroneously deletes a page as an Arbitration Enforcement, when the page is not eligible for deletion under that criterion, they cannot claim the usual immunity to reversion of the action that we reserve for justified AE actions. From GoldenRing's own statement, the relevant criterion upon which they are relying is:
Users should generally not maintain in public view negative information related to others without very good reason. Negative evidence, laundry lists of wrongs, perceived flaws, collations of diffs and criticisms related to problems, etc., should be removed, blanked, or kept privately ... (my emphasis)
But nobody reading Special:Permalink/881981663 carefully would conclude that information on that page is "related to others
". All of the information therein is related to articles, and there is no Arbitration Enforcement available to prevent editors from gathering quotes or diffs from articles or from article talk. We prevent users from gathering negative information about others, for reasons of BLP, but that is not licence to extend the prevention to collating article text. 'Shonen's restoration of the deleted page to allow scrutiny does not breach WP:BLP or WP:COPYVIO (the only absolute prohibitions on restoration), and meets the test of COMMONSENSE.--RexxS (talk) 19:28, 25 February 2019 (UTC)
- Response to GoldenRing. Contrary to what you think, BLP and COPVIO are the only absolute prohibitions to undeletion of content for obvious reason, see Wikipedia:Deletion review #Temporary undeletion where this is documented. Any other prohibition is subject to IAR and 'sanctions.modify' is no exception. It is merely a procedure of the Arbitration Committee and has no status greater than WP:policies and guidelines (which actually don't even recognise 'procedure of the Arbitration Committee' as policy or guideline). ArbCom must not confer on itself greater powers than the community is pleased to grant. It is free to create its own procedures, but does not have authority to create policy: that is the prerogative of the community. In the case of a conflict between a guideline like Wikipedia:Deletion process and an ArbCom procedure, then I suggest common sense needs to be the tie-breaker. The damage done to the encyclopedia by denying undeletion of a page when requested at DRV need to be balanced against the damage done to the encyclopedia by a temporary undeletion. In this case, the balance is obviously in favour of allowing undeletion.
"All enforcement actions have what you describe as "the usual immunity to reversion", whether they are valid or not."
I refute that. To misquote Jimbo, the presumption of validity is not a suicide pact. If a claimed AE action is obviously invalid , as yours was, then a reversion of that action in order to comply with a conflicting policy or guideline is perfectly reasonable. Even you recognise that 'Shonen's actions were reasonable.- I concede your point that BLP concerns are not the only reasons to disallow collections of negative information about other users; although that would be the rationale behind collections of negative information about living persons who were not editors.
- I completely deny your last point. All content in the encyclopedia is provided by editors: that is undeniably not what was intended by
Users should generally not maintain in public view negative information related to others
, otherwise no quotes would ever be allowed. The sophistry is in trying to stretch those words to justify deleting a page that quotes hundreds of different editors, and cannot sensibly be construed to contain negative information about those editors. Any such connotation is purely in the mind of the observer, and you've made the mistake of construing talk page comments critical of an article or of statements in that article as "negative information" about the editors who made the comments. - The elephant in the room is actually your error in attempting to convert a possibly justifiable deletion of a page (by normal process) into an AE action. AE actions were granted the privilege of immunity from reversion for a particular reason (the problems of second-mover advantage), in order to solve intractable problems of civility enforcement. Admins must be careful not to abuse that privilege by claiming AE action in borderline or invalid cases, otherwise the community may lose faith in the necessity for having such an exemption to normal admin procedures (WP:WHEEL). --RexxS (talk) 00:18, 26 February 2019 (UTC)
Statement by S Marshall
- I think this matter raises novel issues about procedure. Wikipedian culture takes deleting pages very seriously, and deleting a page out of someone's userspace feels quite violative to me. I was appalled to learn that a page that purports to describe the rules says that AE deletions can be reviewed at the AN but not at DRV. I feel that in the (probably relatively rare) situation where it's appropriate to review an AE deletion without direct scrutiny from Arbcom, then the most correct venue would be DRV. But I also feel that deleting a page as an AE action is the kind of thing that Arbcom should normally supervise directly, because an AE action should normally be about an editor's behaviour rather than a matter of content. Therefore the scrutiny should normally happen here.—S Marshall T/C 21:01, 25 February 2019 (UTC)
- @SilkTork: --- The deleter's position is that this could not be justified as an in-process speedy deletion and was done purely as AE (diff). I also don't fully agree with my friends RoySmith, Hobit, SmokeyJoe et. al. when they say DRV is mainly about content. I feel that what DRV is mainly about is the analysis and critique of sysop judgement calls and use of discretion. Interestingly, in the decade or so since I became heavily involved in DRV, we've never reached a consensus to ask Arbcom to desysop anyone -- which is why there's never really been any overlap between the two venues. We've found wrong calls, because sysops are only human, but we've never found serious misuse of the mop.—S Marshall T/C 12:17, 26 February 2019 (UTC)
Statement by User:SmokeyJoe
- This clarification is not about Gun control, but is about whether, in general, page deletion is a reasonable measure of arbitration enforcement
- Page deletion is not a reasonable measure of arbitration enforcement. Certainly not if the page is not directly subject to an ArbCom ruling. Exceptions would be considered extraordinary.
- If page deletions were subject to AE admin arbitrary unilateral deletion, this would amount to a secret punishment. The user involved can't read the page deleted. The wider community can't read what was deleted.
- What is going on here is a turf war over the powers and scope of ArbCom. Not by ArbCom directly, but by their delegates, which is worse.
- ArbCom is supposed to stay out of content decisions. Deleting a page containing content is most definitely a content action. This page in question, while not content per se, is a page directed at content decisions. That's pretty close to content.
- This issue is the same as the deletion of Universa Blockchain Protocol, discussed at Wikipedia:Deletion review/Log/2018 July 9. That one was overtly a content page issue. I think this is resolved with agreement that deletions like this should additionally cite WP:CSD#G11, which was agreed in hindsight to have applied.
- WP:Deletion policy is written in clear cut language. WP:CSD is even clearer: "The criteria for speedy deletion (CSD) specify the only cases in which administrators have broad consensus to bypass deletion discussion, at their discretion, and immediately delete Wikipedia pages or media. They cover only the cases specified in the rules here." If ArbCom AE admins also have deletion discretion, add it to CSD, for the record, and to ensure that the community is on the page. ArbCom should not be responsible for undermining the validity or respect afforded to WP:Deletion policy.
- WP:DRV is a long standing very successful forum and process. It is not an enforcement process, but a continuing education exercise. A measure of its success is that lack of repeat culprits being dragged through it. DRV is the highest court for content decisions. There is no cause for carving out deletions that are not reviewable by DRV. {{Temporarily undeleted}} is an essential part of DRV if you consider nonadmins to important in the management of the project. There is already a sufficiently conservative culture at DRV for being responsible with copyright, attacks, and BLP issues.
- --SmokeyJoe (talk) 01:03, 26 February 2019 (UTC)
- AE action to blank the page, protect the page, and block every user associated with the page, would not have been offensive to WP:Deletion policy. —SmokeyJoe (talk) 12:33, 26 February 2019 (UTC)
- "Such deletions do not need to meet our deletion policy". AE deletions do not need to meet policy? Policy does not need to read at face value? What is the policy on AE deletions? ArbCom has broad monarchical reserve powers, but to use them to authorize delegated policy-exempt CSD? That's a characteristic of a police state. --SmokeyJoe (talk) 00:56, 27 February 2019 (UTC)
- Agree with Cryptic and RoySmith that policy clarity would be a good thing. Documentation at WP:CSD#G9 pointing to WP:AC/DS would be a good thing. It would mean that Twinkle could easily link to it. --SmokeyJoe (talk) 03:00, 27 February 2019 (UTC)
- In Wikipedia:Arbitration_enforcement_log, there are three instances of deletion:
- (1) User:Dlthewave/Whitewashing of firearms articles deleted for violating POLEMIC. GoldenRing (talk) 12:28, 20 February 2019 (UTC)
- (2) Sergio Urias deleted for reasons explained here. T. Canens (talk) 04:23, 20 September 2012 (UTC)
- (3) OYCH1961 (talk · contribs) blocked one month for disruptive editing, as described at this link. He recreated a POV-fork draft of the Senkaku Islands article that had just been deleted at WP:MFD. Editor was previously notified by Qwyrxian. EdJohnston (talk) 04:29, 31 August 2012 (UTC)
- (1) explicitly reviewed here. (2) and (3) explained within deletion policy.
- A bigger concern are the DSGS deletions that ArbCom seems to have delegate and does not supervise or review.
- Wikipedia:General_sanctions/Blockchain_and_cryptocurrencies#Log_of_notifications includes 15 mainspace deletions.
- Wikipedia:General sanctions/Syrian Civil War and Islamic State of Iraq and the Levant lists others, including Chemical weapon conjecture in the aftermath of the 2017 Shayrat missile strike, by User:NeilN and User:BU Rob13
- With User:BU Rob13 here having personal involvement of the overreach of ArbCom in overriding deletion policy, I think he should recuse himself. --SmokeyJoe (talk) 07:26, 15 March 2019 (UTC)
- --SmokeyJoe (talk) 07:26, 15 March 2019 (UTC)
- User:BU Rob13, I accept that that deletion was part of a history merge, not a real deletion. However, there may be some problem that your log summary giving implied approval to the previous DS deletion, of a mainspace page. Have you personally ever done a DS deletion not within Deletion Policy or CSD? Have you ever explicitly encouraged or approved of another to do DS deletion not within Deletion policy or CSD? —SmokeyJoe (talk) 22:21, 15 March 2019 (UTC)
Statement by Hobit
The basis for deletion comes from WP:UP. That same page says "In general other users' user pages are managed by that user. Except for blatant or serious matters, it is preferable to try contacting the user before deletion (see above). However, unambiguous copyright violations, attack pages, promotional text, and privacy or BLP violations can be speedy deleted using a suitable template, such as {{db-attack}}, {{db-copyvio}} or {{db-spamuser}}; other pages likely to require deletion (or where remedial action is not taken) may be submitted to deletion discussion.
Justifying a deletion by citing policy and then not following the policy for how to go about deletion seems problematic at best.
The reason for deletion is not a speedy criteria. And standard DS do not allow for deletion of a page as near as I can tell. I only see one other deletion in WP:AEL and that was justified on A7/BLP grounds. As S Marshall has indicated, AE enforcing admins very much deserve our support and I'm personally grateful to those that take on such a demanding and stressful job. But here there is overreach outside of the scope of either a single admin or AE. There was no rush and no reason WP:MfD couldn't have been used (where I suspect it would have been kept).
In any case, I agree with Roy (below)--this is about content not behavior. The discussion belongs at DRV. edited Hobit (talk) 04:45, 26 February 2019 (UTC) Hobit (talk) 01:55, 26 February 2019 (UTC)
- A heavy reliance on WP:CONTENT (an essay with about 30 edits) to argue that ARBCOM has utter control of anything not in mainspace is quite the power grab. I'd urge members of the committee to be very very careful making the claim that ARBCOM can do whatever it wants outside of mainspace because it "isn't content". Hobit (talk) 14:43, 17 March 2019 (UTC)
- @BU Rob13: I am not making a claim about what is and isn't content. I am instead saying that claiming ARBCOM has complete jurisdiction over everything not in mainspace is a large power grab. Are you claiming ARBCOM has been empowered by the community to delete any content that isn't in mainspace? And you are using an essay to justify that? I'd rather go with something more clearly on-point "The arbitration process is not a vehicle for creating new policy by fiat. The Committee's decisions may interpret existing policy and guidelines, recognise and call attention to standards of user conduct, or create procedures through which policy and guidelines may be enforced." Taking deletion policy and moving it from the community to ARBCOM doesn't make sense in that context. The policy for how to deal with deletion is clear. And "The Committee does not rule on content, but may propose means by which community resolution of a content dispute can be facilitated." is making it clear that ARBCOM doesn't get involved in content. But that doesn't mean it has jurisdiction over everything that isn't content. Hobit (talk) 04:34, 18 March 2019 (UTC)
- A heavy reliance on WP:CONTENT (an essay with about 30 edits) to argue that ARBCOM has utter control of anything not in mainspace is quite the power grab. I'd urge members of the committee to be very very careful making the claim that ARBCOM can do whatever it wants outside of mainspace because it "isn't content". Hobit (talk) 14:43, 17 March 2019 (UTC)
Statement by RoySmith
I don't often get involved in ArbCom business, so forgive me if I'm not up on the nuances of policy and procedure here. But, reading what User:SmokeyJoe said above: ArbCom is supposed to stay out of content decisions, I find myself very much in agreement. The converse is certainly true; DRV deals with content, and stays out of behavioral issues. It's common in DRV debates for somebody to write, We're only here to talk about the page deletion; if you want to pursue a user's conduct, there's other fora for that. This seems like a natural and useful division of responsibilities, and why it seems odd to be talking about ArbCom getting involved in reviewing a page deletion.
I don't think it was appropriate to delete the user page. I also think it was perfectly reasonable (and SOP at DRV) to temp-undelete the page for review. I also want to echo what others have said; while there's clearly a disagreement about what the proper course of action should have been, it's also clear that everybody has acted in good faith here. There should be no thought of sanctions for anybody. -- RoySmith (talk) 03:03, 26 February 2019 (UTC)
- I've done a lot more reading of the full history of this. My earlier comments notwithstanding, I agree with User:SilkTork that having two parallel discussions in different forums is a bad idea. At this point, I suggest that DRV defer to ArbCom on this one. -- RoySmith (talk) 15:29, 26 February 2019 (UTC)
- User:Cryptic is exactly right. If the end result of this is to confirm that AE can include speedy deletion, then WP:CSD needs to add a category for it. My big fear (as somebody who also does a lot of temp-undeleting at DRV) is that given the current discussion, I could very easily see myself having undeleted this and then finding that I'd accidentally run afoul of a policy I didn't really understand, and put my mop at risk. If this fell under WP:G9, or a new G-whatever specifically for AE, it would have been clear that this was out of bounds. Clarity is a good thing. -- RoySmith (talk) 02:48, 27 February 2019 (UTC)
I don't know if I have standing here, but can I request that this get resolved sometime soon? Surely, six weeks is long enough to make a decision. I, as an admin, are left not knowing if temp-undeleting a page at WP:DRV could lead to my being desysoped. What we've got now is arbcom saying, "We reserve the right to desysop you if you break the rules, but we won't tell you what the rules are". That's not useful. -- RoySmith (talk) 15:40, 10 April 2019 (UTC)
Statement by Sandstein
While I disagree with GoldenRing on the merits of the deletion, I agree with their submission of 16:22, 26 February 2019 in that the Committee should clarify whether deletions (other than those already allowed by ordinary deletion policy) are in principle allowed as discretionary sanctions, and whether any review of deletions labeled as discretionary sanctions must take place by way of the procedures for the appeal of AE actions. In my reading of applicable policy, the answer to both questions is clearly yes, but the opinions to the contrary that have been voiced at DRV show that this question needs clarification. Sandstein 16:36, 26 February 2019 (UTC)
Statement by Cryptic
I've performed I'd guess around a quarter of the temporary undeletions at DRV over the past few years. Contra what's been stated both above and below, it's neither an absolute right (even barring copyvio and blp - there's been a number of cases where no admin's been willing to tempundelete in the cases of egregious spam, for example; I can dig out some example DRVs if it'd be helpful) nor, in particular, automatic: in practice we almost always wait until an uninvolved user requests it. I don't recall ever seeing the author of a page requesting temp undeletion for the purposes of DRV before; even had this deletion not been labeled an AE action, I'd certainly have declined, though I might have offered to email it. —Cryptic 20:57, 26 February 2019 (UTC)
Dialing my wonk-o-meter up to 11, I'm not seeing anywhere in WP:Protection policy that authorizes arbcom to authorize admins to protect pages, either. (It does mention arbcom with respect to unprotections, and very indirectly for extended-confirmed protections.) So the idea that arbcom can't authorize deletions just because it's not explicitly stated in WP:Deletion policy or WP:Criteria for speedy deletion doesn't get a whole lot of sympathy from me. That said, if the committee ends up deciding this deletion was correct, I'll go through the hassle at WT:CSD to try to get this properly documented, probably as a variant of WP:G9. —Cryptic 22:07, 26 February 2019 (UTC)
Statement by GMG
If we're going to allow that ACDS is legitimate grounds for out-of-process deletion, then we're probably approaching the point where we've abandoned the pretense that ArbCom does not make policy. GMGtalk 01:18, 27 February 2019 (UTC)
- To be fair, I've been saying for a while now that ACDS is also wholesale rewriting of our blocking and banning policy, but I think most people have just gotten used to it. So I don't expect most people will take this comment seriously, and if they do, it's just because the water got a little hotter than they're accustomed to yet. But them's the breaks when you allow ArbCom to rewrite policy while claiming they don't write policy. GMGtalk 01:50, 27 February 2019 (UTC)
Statement by DGG
- I too frequently make undeletions for review at Del Rev. I approach it a little differently,so I would not suggest that either their approach or mine is authoritative, nor do I presume to say what other admins do. . I have never refused to undelete for DR, except for copyvio, or if the request is disruptive or unnecessary. I interpret the rule as not requiring it, as merely making the necessary provision to not do so as a special situation. (And if it would apparently help the discussion, I do not wait for a request-sometimes the person bringing it to DR does not know its possible--and the person bringing it often is the author of the content) Since Arb Com authority does not extend to content, neither does AE. Though community consensus cannot override AE, neither can AE override the basic principles of community editing. If I rewrote an article summary to conform to my idea of what the true meaning of an arb com decision required, I could not call it AE to prevent others from reverting my change. Just as I cannot rewrite under AE, I cannot remove it under AE. AE is dangerously inflexible even if used in the ordinary way--giving individual admins sticky discretion over content in such a direct way as to permit them to delete by AE, is not within a reasonable scope. AE is not a free pass to anarchy; because of the stickiness, it requires even more careful judgement than other admin actions. If anything, we need how to restrict the scope rather than add to it. If the scope of AE is to increase, it can only do so by a change in arbitration policy by the community. DGG ( talk ) 06:04, 4 March 2019 (UTC)
- I am quite confused by the reasoning in the arb section. The basic rule of arb policy is that arb com has no direct authority over content. (its jurisdiction with respect to conduct can and sometimes does affect content, which is inevitable because the two are related, & because many conduct disputes are derived from content disputes). Since arb com has no direct authority over content, no remedy it enacts can give anyone authority over content, and no DS it enacts can allow for authority over content. Therefore, any admin acting under AE may not do so in such a way as to directly edit content. Editing content includes redirecting, or deleting, or undeleting. Arb com cannot do such actions as arbs, or authorize them as AE. They do have jurisdiction over any admin pretending to do them as AE. DGG ( talk ) 01:39, 17 March 2019 (UTC)
- BU Rob13, In addition to the pages strictly speaking in content space, I really cannot see the rationale for giving arb com or AE any direct control of anything except their own pages. People employ user space for many purposes, most having to do with the preparation and discussion of content. What is on those pages is not any direct business of arbcom--or AE. They already have all the power they need by the ability to sanction editors. Unlike possible speculations for what harm might be caused that is out of reach of speedy/MfD/office, this discussion was started by a use of AE to do an action that may or may not have had consensus; there is no way in which removal of that page could be considered an emergency, so it could have been discussed in the usual way at MfD followed by DR. (or speedy followed by DR, if is was really abusive or advocacy) . If people have power, there is a temptation to use it. There are some pages in user space that I regard as harmful to the proper purpose of WP--some deal with AP or other areas where AE is available. If I nominated them under MfD, most would probably not be deleted, but if I deleted them as AE, most of them probably would not get the necessary clear consensus to restore. Most active admins I know probably have some pages in mind similarly. If there's precedent for using this power, it will be used again. Arbitrary unilateral power is dangerous; some is necessary, but we should only have what is actually necessary, not everything that might conceivably be necessary under circumstances we cannot presently specify. (Getting back to AP, there a current RW analogy). DGG ( talk ) 04:24, 19 March 2019 (UTC)
Statement by Drmies
If the standard operating procedure of undeletion for DRV can be called a violation of an enforcement action authorised under discretionary sanctions, I think we've reached sort of an end point grammatically and in terms of Arb Power. Sorry, but I think this is silly and pushing the point of authoritay too far. Drmies (talk) 15:19, 5 March 2019 (UTC)
Statement by Xymmax
I came upon this when I went to close the DRV. The committee's discussion thus far, in my opinion, has yet to fully grapple with the core concern that I see from those critical of permitting DS deletion, and one that I share: permitting out of process deletion under the authority of enforcement of DS is taking DS enforcement away from being a tool to enable administrators to deal with disruptive conduct, and instead making admins arbiters of disfavored content. The dichotomy is real, as several committee members appear to feel that under appropriate circumstances an administrator acting under DS enforcement authority could delete a page (or I suppose an article) and be subject to review only at ARCA. The tools ordinarily used - topic bans, blocks, and page protections - are designed to reduce disruption by modifying user conduct. Deletion, uniquely, hides the information from ordinary readers, and that is why the comprehensive deletion process governs when there is consensus that such removal is acceptable. The committee should recognize that just as the AN community has special expertise in dealing with user conduct issues, Afd/Mfd/DRV and their ilk are where editors have particular insight these content issues. It would be concerning if the community's expertise were to be deprecated in favor of an enforcement mechanism made for user conduct issues. My personal preference here would be to see the committee take deletion off the table of DS enforcement options. Functionally equivalent would be to say the deletion process must be followed - a speedy deletion criterion cited, with review at DRV. Less satisfactory would be to limit such reviews to ARCA. Xymmax So let it be written So let it be done 04:52, 6 March 2019 (UTC)
- I have to confess that I'm finding this conversation to be a bit frustrating. It would be helpful to me if each of the committee members would address the core issue here: under what circumstances may the committee delete (or I suppose, order deleted) a page. I'm not talking about the individual members of the committee, all of whom are trusted oversighters and admins, and have enormous discretion to act under that authority, rather I mean the committee as a group. DS are simply delegated powers, and the committee can only delegate powers that it has. So I ask, when, committee members, are you empowered to order deletion? Xymmax So let it be written So let it be done 18:11, 17 March 2019 (UTC)
Statement by Wnt
I happened to see mention of this discussion and am alarmed by the way it is going. Reading this user page, it is clearly a complaint about the bias of articles, which is to say, it is directly applicable to Wikipedia editing. It is not addressed at any editor (indeed, has timidly omitted usernames). It does, of course, favor a certain point of view, but editors should be allowed to favor a point of view they agree with when it is being excluded from articles. I say this even though I am pro-gun rights and suspect many of the individual edits were correct.
The consequence of (literally) arbitrarily excluding such content is to propagate the idea that Wikipedia is biased and to encourage editors to share information like this off-site. The consequence of that is that Wikipedia loses any ability to suppress deliberate cyberbullying, while the editors lured to partisan sanctuaries are more likely to fall under the influence of actual lobbyist money. In every way, the quality of discourse is degraded by deletions like this. And unless the arbitration decision specifically prohibited making any new pages about a topic, such deletions cannot possibly be valid arbitration enforcement. Wnt (talk) 20:47, 8 March 2019 (UTC)
Statement by Spartaz
I just closed the DRV as overturn as the clear consensus of the discussion. Once you have completed your august deliberations could someone let me know if I can enact the clear consensus of the discussion or whether super Mario has won. Incidentally my autocorrect hates arbcom it keeps changing it to random or wrecked. Spartaz Humbug! 19:03, 9 March 2019 (UTC)
- Can we have an update on this please or are you going to prove my autocorrect right? Spartaz Humbug! 06:40, 9 April 2019 (UTC)
Statement by Fish and karate
The arbitration process exists to impose binding solutions to Wikipedia conduct disputes (i.e., not content disputes requiring mediation) that neither community discussion nor administrators have successfully resolved. The arbitration process is not a vehicle for creating new policy by fiat. The Committee's decisions may interpret existing policy and guidelines, recognise and call attention to standards of user conduct, or create procedures through which policy and guidelines may be enforced. The Committee does not rule on content, but may propose means by which community resolution of a content dispute can be facilitated. (My bolding). Fish+Karate 11:16, 12 March 2019 (UTC)
Statement by Alanscottwalker
In my view "removal" in Arb/DS policy is meant in the sense it is used at WP:TALK or WP:BLP, that is an action that removes an edit or comment, it is not meant in the sense it is used in deletion policy or oversight policy. As we see from this case, it is not prudent to have the expansive construction of "removal" in Arb/DS to include deletion and oversight, which both have extensive articulated process, separate and apart. -- Alanscottwalker (talk) 10:43, 14 March 2019 (UTC)
- @SilkTork:, @Joe Roe:, @RickinBaltimore:, and the rest of the arbs: Part of the sticking point is when you write "outside of the deletion policy" do you mean all of WP:Deletion policy? Deletion policy includes, "Deletion review" [1], and WP:UDP. So, it seems you are not making things much clearer and are setting up further confusion, of the kind we see on this page with Bishonen's un-deletion.
- Is the community sanctioned, "Deletion Review" the process of review for these, so rare, almost unheard of, discretionary deletions? In particular, the un-deletion aspects (WP:UDP) that make for an informed community decision? Alanscottwalker (talk) 17:15, 26 March 2019 (UTC)
Statement by Deryck
Wherever we draw the boundaries of arbitration enforcement, there will be fringe cases where admins may disagree on whether AE applies. ArbCom needs to decide whether it retains (or wants to retain) exclusive jurisdiction over the policing of AE boundaries. Today we're talking about page deletion, next time we may talk about the applicability of AE over protection in certain circumstances or some other admin action.
If ArbCom decides it retains exclusive jurisdiction over the boundaries, which I disagree with, then it needs to be prepared that any action that is declared by any admin as an act of arbitration enforcement will automatically escalate to ArbCom if someone disagrees with it. This seems to go against ArbCom's mantra that lower venues of dispute resolution ought to be tried first if possible (as is DRV in this case) before escalating to ArbCom in general.
As for the case at hand, I agree with RexxS and Ivanvector here. We ought to be narrow and cautious in the interpretation of AE provisions. While the ArbCom is allowed to make an (clarifying) amendment that DS covers page deletion, I don't think "removal" in the current wording includes page deletion, because as many other have pointed out, page deletion redacts the contents of the page history from public view. Deryck C. 14:40, 18 March 2019 (UTC)
- P.S. I would like to echo others in this discussion in their praise of GoldenRing and Bishonen for their collegiality throughout this debate, and of the fact that this was brought to ARCA as a debate on principles rather than specifics. Deryck C. 17:58, 26 March 2019 (UTC)
Statement by Atsme
Maybe, just maybe my comment will help motivate a close. Countless hours are spent/wasted trying to decipher ambiguous PAGs. The obvious solution would be to clarify the ones that create the problems. As editors are so often advised, it is not about who is right or wrong, it's about the disruption, and admins & ArbCom need to apply this to their own actions. It appears ArbCom invests a measurable amount of time and energy looking for reasons to not take a case...thus, the creation of AE...which sometimes leads to more confusion under the guise of saving time and energy. What we're doing in essence is substituting input from several admins for discretionary action and passing it over to a single admin, and if they execute the action improperly, off with their heads. Fix the ambiguities. I can't see that either admin is at fault here; therefore, trying to afix blame is not resolving the problem. Atsme Talk 📧 14:28, 20 March 2019 (UTC)
Statement by SMcCandlish
Option C in the survey below seems to be the only valid option. Because WP:AC/DS is simply delegation of ArbCom authority to admins, and ArbCom does not make content decisions, general decisions to delete content as such are outside the remit of AC/DS, absent some other deletion rationale. However, if admins are already empowered to delete something under other policy, then doing so, within those policy limits, and as part of AC/DS action would be legitimate. For example, AC/DS is most specifically about blocks and topic bans, but admins can do other things, like impose a "move-ban" on someone mis-using manual page moves, and require them to use RM process. I don't think anyone would argue that if someone were disruptively moving pages in an AC/DS topic area that DS could not involve a move ban, despite not being mentioned at the AC/DS page. The difference here is that the deleting admin is making what amounts to an WP:IDONTLIKEIT content decision about the material in the page (I have no opinion on the allegation that this was politically motivated). That's not a rationale for DS action, and not a rationale for deletion, so no combination of DS + DP/CSD results in "I can delete this because I feel like it". In this particular case, the motivation seems genuinely WP:POLEMIC-enforcement-motivated (though I don't think I agree with the assessment that the material necessarily qualified under POLEMIC). We cannot predict the future with certainty, but can make educated guesses. Since AC/DS is applied to controversial topics, and disruption correlates strongly with controversy, it seems virtually guaranteed that unrestrained deletion under AC/DS will result in suppression by admins of material they disagree with, by translating "is opposite my or the majority view in a dispute" into "is disruptive". Content by itself is not disruptive (outside some narrowly defined classes like vandalism with butthole pictures, or OUTING with personally identifiable information); editorial actions are.
On the follow-up questions: DRV is and should remain an obvious venue for review of any deletion. It's not "WP:Deletion review except for some people". WP:NOT#BUREAUCRACY and WP:GAMING are important. We don't want a decision under which any admin who seeks to avoid DRV and general community scrutiny for questionable deletions can simply claim some vague AC/DS rationale and thereby close all avenues of appeal other than AE (which is a star chamber that leans toward presumption of guilt of anyone accused by an AE admin, and is generally hostile to editors who challenge an AE admin's decision), or ArbCom (which is even scarier to most editors, though actually fairer). In both processes, there is a strong bias in favor of the admin who acted, both in the minds of those reviewing the action and usually in the admin party's knowledge of the excessively legalistic procedures surrounding ArbCom and its AE board. ArbCom is not bound by precedent, so the fact that it has historically treated all AC/DS actions as appealable only to AE or ArbCom is irrelevant. Explicitly allowing deletion as a DS action is dangerous, and removing DRV as an examination venue would be a disenfranchisement of the community without any real discussion or notice. ArbCom deciding that its clan of AE "enforcers" how has deletion impunity and near-immunity (option B in the survey, or even option C with DRV excluded) would be a poor and controversial move. — SMcCandlish ☏ ¢ 😼 21:09, 20 March 2019 (UTC)
Statement by EdChem
I think that the approach proposed by AGK – to make it clear that deletions are not possible as an AE action – is the best way forward. I recognise the concern that SilkTork raises, but the alternative proposal is not the way to address that, in my view. As I understand it, SilkTork wants it to be clear that an admin may make a deletion under their ordinary authority under the deletion policy while also addressing an AE situation. However, by adding the extra mention of the deletion policy implies that the use of ordinary authority in relation to deletions is an exception. It admits the interpretation that the existing practice of an indefinite block with only the first year as an AE action is not permitted.
I suggest that AGK's approach / addition be preferred, and a relevant addition to the DS procedures state that:
- nothing in the DS policy restricts an admin from acting under their ordinary authority as part of addressing an AE issue – this would make clear that a deletion under the CSD guidelines, for example, or extending a block from a 1 year under AE to indefinite beyond that under ordinary authority remain available.
- any and all admin actions that are not explicitly available under the DS policy as AE-protected actions that may be undertaken are limited by the ordinary discretion and authority available to admins and subject to the usual procedures with which those actions are associated.
- any action taken relating to an AE issue under ordinary authority is not protected by the DS appeals restrictions and are addressed under standard procedures relating to admin actions – this makes clear that DRV and REFUND remain as they are and that appeals from a block beyond the 12 months of AE protection can be actioned in the usual ways.
The advantage of this approach, in my view, is that it covers not simply this deletion issue but any and all questions that could arise where ordinary admin authority is used. It makes the treatment uniform and avoids any claim that the deletions are treated differently. The second point would also cover any other area that might be questioned in the future. I don't know how much of this is already covered in the DS policy, but I think it is worth codifying. I looked at the policy quickly but didn't see any clear statement that makes this clear, and I don't know exactly where it would be added or how it would be worded. EdChem (talk) 00:44, 26 March 2019 (UTC)
- @SilkTork: You said
I'm not comfortable with the notion that a AE admin should have less authority than a non AE admin, and so create a situation where someone creates a page in direct violation of an ArbCom sanction, yet an AE admin could only delete such a page outside of ArbCom protection, and so there is uncertainty (again) over where the matter should be discussed.
- Firstly, I don't think it's a good idea to suggest that there are "AE admins" and "non-AE admins." I think a wiser approach is to consider that there are admins and that they can take actions under their ordinary authority and/or actions taken under DS / AE authority. The former actions are subject to ordinary procedures, the latter have special procedures and protections.
- Under what I am suggesting, an action in violation of an ArbCom sanction is eligible for any (appropriate) response authorised under DS and attracts additional protections. Any other action is taken under ordinary authority and subject to ordinary protections. The difference lies in what action is taken (DS authorised or not) rather than in by whom it is taken (AE admin or not).
- There is no uncertainty about where things are discussed / appealed. Either the action is authorised in DS and entitled to additional protections, or it is an action under ordinary authority and subject to standard procedures.
- In the specific case, it would be clear that GoldenRing's action was not authorised by DS and so was an ordinary deletion action, reviewable at DRV at (correctly) reversed as unjustified under policy. This is not to suggest that GR should face a sanction, though a general reminder that DS authorises specific actions and not any action that an admin might feel is desirable might be appropriate.
- If a page is created in direct violation of an ArbCom sanction, it is likely to be a candidate for deletion under CSD or AfD / MfD / TfD etc procedures. If a case of a page that is truly a direct violation of an ArbCom sanction but not eligible for deletion under existing policy is ever found, it should be subject to a discussion. Such a case would either demonstrate a gap in deletion policy, which the community should discuss and address, or an ArbCom sanction that is questionable in its basis, which is also something that should lead to a wider discussion. If it was something so bad that immediate action was needed and yet no policy justification was available, we have IAR or appealing to the WMF for an OFFICE action as potential solutions.
- Finally, I fear that your form of words risks unintended consequences. As AGK notes, it is vague which invites wikilawyering – what if the deletion policy is uncertain over a controversial change with an RfC underway and it is that area that may or may not be policy that relates to the page? Adding potential DS appeal / modification protections just adds unnecessary controversy, as the present deletion situation demonstrates. Also, as I noted above, if deletion is a special case under DS, what else that is mentioned in DS is not similarly special? What about things not mentioned in the DS procedures? I agree with you on the desirability of clarity but don't want to create uncertainty in other areas in the process. EdChem (talk) 01:11, 26 March 2019 (UTC)
Statement by Aquillion
The purpose of discretionary sanctions is to enable normal editing and consensus-building procedures to function even in situations where there is substantial disruption; their purpose is not to replace such procedures. The idea that an WP:AE deletion is not subject to WP:DRV therefore seems patiently absurd, especially given that DRV is, itself, historically an extremely high bar to pass (ie. the nature of an appeal means that in the absence of a consensus the default is that the article would stay deleted.) More generally, the problem stems from situations where WP:AE matters intrude on content decisions; based on that danger, I would amend WP:AC/DS#Modifications by administrators to state that by default, any content-based changes resulting from an WP:AE action (including deletions) can be reversed provided there is a clear consensus via an established venue like WP:DRV, without requiring that that be a consensus of administrators; and that in cases where there is a disagreement, such consensus is presumed to be sufficient to establish that something is a content issue. While WP:AE isn't supposed to apply to content in the first place, it is inevitable that there will occasionally be overlap, and it's important to establish that in cases where that occurs, an administrator cannot override or ignore consensus on content issues simply by invoking WP:AE (and that the default, in cases of confusion, is to go with a broad consensus when it exists.) --Aquillion (talk) 04:05, 7 April 2019 (UTC)
Statement by Ymblanter
Note that earlier today I closed the AE appeal [2] and consequently restored the page in question. At the time, I was not aware of the existence of this clarification request (I have probably seen it on my watchlist some time ago, decided that it has no relation to my activities, and forgotten about it). I believe that the closure of AE is completely orthogonal to the request, since I believe nobody says the page may not be restored as a result of an AE closure. However, if anybody feels that the existence of this clarification request mandates that the AE request must sty open, feel free to unclose it.--Ymblanter (talk) 10:44, 10 April 2019 (UTC)
Statement by {other-editor}
Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.
Gun control: Clerk notes
- This area is used for notes by the clerks (including clerk recusals).
- Recuse obviously. GoldenRing (talk) 15:43, 25 February 2019 (UTC)
- @SportingFlyer: I've removed your comment in the survey section as that falls under the Gun control: Arbitrator views and discussion section. That section is reserved for members of the Arbitration Committee. --Cameron11598 (Talk) 21:29, 6 March 2019 (UTC)
Gun control: Arbitrator views and discussion
- I'm still looking into the aspects of this, but as a general principle AE does give admins the discretion to " impose on any page or set of pages relating to the area of conflict page oprotection, revert restrictions, prohibitions on the addition or removal of certain content (except when consensus for the edit exists), or any other reasonable measure that the enforcing administrator believes is necessary and proportionate for the smooth running of the project", and if the admin considers that the "other reasonable measure" is deletion of a page, that would for me fall within the admin's discretion, so my response to point 1 is yes. That does not mean I think this current deletion is appropriate or reasonable, but that the principle of page deletion is within an AE admin's discretion. And it is important that the community adheres to ArbCom processes such that any ArbCom sanction can only be reversed by following appropriate procedures. So a) undoing an ArbCom enforcement without authority for doing so is a violation of the process, and b) appealing the enforcement in a venue other than the appropriate one is a violation of the process. As such for point 2 my response is yes in principle, and for point 3, it is no in principle. It is sometimes that an AE admin makes a mistake, and the process do allow for other users to question page restrictions, but they should follow process. As for this particular incident - were all the due processes followed? Was Dlthewave given an appropriate warning that DS applied to the page under question? And was the template Template:Ds/editnotice applied to the page in question? I am still looking at the page in question, and would like some more rationale behind why the page was considered to fall foul of "believes is necessary and proportionate for the smooth running of the project". What was the particular harm you saw in the page GoldenRing? My thinking at this stage, even with a convincing rationale for the page deletion, is that the unusual nature of the page restriction (deletion) and lack of clarity in this matter is such that I am not seeing any sanctionable behaviour for Bishonen's advice to take the matter to DRV. As regards undeleting the page. It's been a while since I got involved in DRV, but I don't recall it being a part of the process that pages were undeleted. And while we do give admins discretion to userfy pages on request, I don't think it should be considered that undoing an AE enforcement without first getting clear consensus at an appropriate venue is something ArbCom would be willing to overlook. That may have been a step too far, even with the confusions about the process. Bishonen, could you give us some of your thinking behind why you undeleted the page? SilkTork (talk) 18:16, 25 February 2019 (UTC)
- @Black Kite:, thanks for that - it's been a while since I had anything to do with DRV.
Are all articles automatically undeleted for DRV, or is it just a selected few? And if it is a selected few what is the criteria for undeleting, and on average what percentage of articles are undeleted?SilkTork (talk) 19:00, 25 February 2019 (UTC) - @Bishonen:, thanks for that - very useful. So articles on DRV which are requested to be undeleted are done so, and in this case you were requested. I strike my questions to Black Kite, as your response has given me the appropriate information. SilkTork (talk) 19:05, 25 February 2019 (UTC)
- Because of the unique nature of this AE action I'm not seeing that Bishonen has done anything sanctionable, though for the avoidance of future doubt, if my colleagues agree with me, I think we need to make it clear that nobody should undo an AE action without first getting clear consensus to do so at an appropriate venue. SilkTork (talk) 19:08, 25 February 2019 (UTC)
- Thanks GoldenRing. I phrased my question awkwardly. I can see why you had concerns about the page, what I'm asking really is why you felt the need to delete the page rather than raise your concerns with Dlthewave, or blank it, or amend it in some other manner. Your deletion, albeit done under AE, was a speedy deletion. The closest justification under speedy is G10. Did you (do you still) feel that G10 was the rationale for deletion? Or was it purely based on the user page policy, which says that negative material should be removed or blanked, but doesn't say deleted. It is the decision to delete rather than use other options that I'd like to hear your thinking on. While I support in principle the notion that an AE admin have within their discretion the option to delete a page, my thinking is this should be done within policy, so I'm looking for the policy that allows deletion in this instance. At the moment I'm seeing a page that can be considered to be of concern, but it appears to me that the appropriate solution would be discussion about the page rather than deletion of the page. I've not looked closely - is there discussion about the page that you can direct us to? SilkTork (talk) 08:42, 26 February 2019 (UTC)
- Thanks GoldenRing, that makes things a lot clearer. My thinking is that everyone here has acted in good faith and with a view that what they were doing was within policy and procedure. While I feel that in principle an AE admin can delete a page as part of DS, that such a deletion should meet with policy, and if the deletion is not to go through a community discussion process (ie, is a Speedy deletion), then such a deletion should meet Speedy criteria. So, as in this case the deletion was not done under Speedy, the page should instead have been blanked. As this deletion was done under AE, albeit - in my opinion - inappropriately, it should be discussed at WP:AE rather than DRV. At the moment we have discussion at both DRV and AE. Rather than create a constitutional crisis, one venue or other should give up the right to discuss it; or perhaps, GoldenRing, you could reflect on if an AE enforced blanking serves the purpose as well as a deletion, and agree on the DRV that it can be undeleted, so we can resolve that discussion there, and you can then blank the page under AE and Dlthewave can appeal the blanking at AE. SilkTork (talk) 12:10, 26 February 2019 (UTC)
- GoldenRing "I am a little unsure what you mean when you say, "such a deletion should meet with policy."" What I mean is that ArbCom is a part of the community and runs with the consent of the community. All the things that we do we do with the consent of the community, and any of the things that we are allowed to do, such as topic bans, etc, have evolved out of consensus. The one big thing that ArbCom has is that any legitimate ArbCom action is binding, and can not be undone by a community discussion at, say DRV, but only be undone by an appropriate ArbCom process. But even that big thing is done by the consent of the community, and if the community don't like what ArbCom are doing they can at any point say, "Fuck this for a game of soldiers", and decide to close ArbCom. Yes, an AE admin can do what they reasonably feel is needed, but only within the consent that the community have already given us, and the community have not given us explicit consent to delete out of process. This particular deletion is actually a minor issue, and everyone here is discussing this as an interesting point of process, but if you'd deleted a featured article on the main page or Jimbo's talkpage, we'd have a serious issue on our hands. There are necessary limits to what ArbCom can do, and we must be aware of them and abide by them, and if in doubt seek consensus. SilkTork (talk) 07:07, 27 February 2019 (UTC)
- @Black Kite:, thanks for that - it's been a while since I had anything to do with DRV.
- My view is that deletion of a page is permitted as an enforcement action under discretionary sanctions. Indeed, there are intentionally very few limits on what sanctions an administrator can impose under discretionary sanctions. As such, I see Bishonen's undeletion as a violation of WP:AC/DS#sanctions.modify, albeit one that was carried out in good faith with the best of intentions while uncertain of whether the arbitration enforcement action was permissible. I will note that WP:AC/DS#appeals.notes (bullet point 4) indicates that any action taken under discretionary sanctions are presumed valid and proper until a successful appeal, so if there were a question over whether deletion is a permissible discretionary sanction, that should have come to ARCA initially. All AE actions can only be appealed at WP:AE or WP:AN, so this cannot be appealed at WP:DRV. Leaving a note at WP:DRV directing interested editors toward such an appeal would be appropriate in this situation. I decline to answer GoldenRing's fourth question for two reasons. Ideally, ArbCom should not be the first point of appeal of a discretionary sanction. Separately, the admin who placed a discretionary sanction may not appeal their own sanction. This is especially important for an appeal that potentially skips AE/AN, since that would deprive other editors of the ability to appeal at those venues under our procedures. ~ Rob13Talk 16:40, 26 February 2019 (UTC)
- Such deletions do not need to meet our deletion policy, as a side note. Discretionary sanctions are intended to allow administrators the discretion to handle cases not covered by our typical policies and guidelines in particularly contentious areas. Administrators should be cautioned that overzealous deletions as AE actions are likely to be overturned. In the case of repeated occurrences, this could result in a restriction from carrying out deletions as AE actions or from carrying out AE actions as a whole. ~ Rob13Talk 16:44, 26 February 2019 (UTC)
- @SmokeyJoe: I will not be recusing myself for multiple reasons. First, simply taking a somewhat similar action in the past does not preclude one from reviewing unrelated administrative actions. If this were not true, truly absurd arguments could emerge (e.g. "Since X arbitrator has previously voted against desysop for an administrator who did Y, they must recuse when a different administrator did Y in a different set of circumstances"). Second, and most importantly, I did not delete any pages as an AE action. After a page was deleted as an AE action, and without making any comment on the validity of the deletion, I undeleted it to perform a necessary history merge and then restored the action. My role was to undo a copy-and-paste move that was non-compliant with the licensing requirements on Wikipedia. That is the only action I took with relation to that page. I had no role in the AE action. Tangentially, I see you saying that deletion of any page must, be necessity, remove content. WP:CONTENT defines content as things in the mainspace and related navigational pages, so this deletion, which affected only a user page unrelated to any mainspace material, was not "content" under that definition. ~ Rob13Talk 17:40, 15 March 2019 (UTC)
- @SmokeyJoe: So I've looked into that deletion more. I didn't remember it very well, since it happened in 2017. First of all, it actually wasn't an AE action. It was a general sanctions action, which is similar, but not identical. The authority there derives from the community, not ArbCom, and whether GS deletions in areas where general sanctions are approved is permitted is entirely a question for the community. This discussion/clarification has no bearing on that. Second, I actually declined to delete that page under CSD prior to NeilN's deletion, looking through the edit history. Lastly, the deletion appears to be because AssadistDEFECTOR, an editor who I recall being an extremely disruptive civil POV pusher who is now indefinitely blocked, forked off a conspiracy theory into its own article which treated the conspiracy as fact after consensus had been to take it out of the main article for that subject. While I would not have done the same action, I see why NeilN did it. The page was very clearly created purely to circumvent the settled consensus and force other editors to re-debate the removal of that content. In that sense, I think the deletion was supported by WP:CONSENSUS and WP:IAR. NeilN's deletion did clearly achieve what editors had already reached a consensus to do - remove a seriously fringe conspiracy theory from mainspace. See here for more detail. Hopefully, that provides more context to NeilN's deletion. Any further discussion on the "general sanctions" tangent should presumably go to a venue where the community can clarify whether deletion is allowed under general sanctions. ~ Rob13Talk 22:51, 15 March 2019 (UTC)
- @GoldenRing: I'm sure this isn't what you intend to say, but your example of a mainspace AE deletion specifically to avoid a DRV discussion comes across as an admin using AE actions to avoid scrutiny. I would not support anything like that. AE actions should never be performed with the sole intent of avoiding scrutiny of a borderline action. I don't think moving the discussion from DRV to AE or AN is likely to decrease drama over a questionable deletion, in any event. See this whole ARCA as evidence of that, honestly. ~ Rob13Talk 17:44, 15 March 2019 (UTC)
- The purpose of discretionary sanctions is to minimize disruption in contentious areas in order to allow Wikipedia's usual processes to proceed smoothly - they are not a replacement for them. Admin.expect backs that up by stating that admins should "allow responsible contributors maximum editing freedom with the need to keep edit-warring, battleground conduct, and disruptive behaviour to a minimum." In other words, enact the minimal necessary sanction to allow editing to proceed as usual, through typical community processes.Sanctions.page permits admins to enact a number of suggested measures, including "other reasonable measures that the enforcing administrator believes are necessary and proportionate for the smooth running of the project." There is nothing explicitly prohibiting deletion as an AE action. However, any AE enforcement must be reasonable, necessary, and proportionate, and I think it would be very rare for deletion to meet that standard. By its very nature, deletion does more to limit the editing freedom of responsible contributors than any other page-level sanction. Even fully-protected pages can be edited via edit request. For that reason, I would argue that use of deletion as an AE action should have a much higher threshold to pass before it can be considered reasonable, necessary, and proportionate.In my opinion, deletion as an AE action should not be used unless it can be demonstrated that there is significant disruption coming as a direct result of the page in question, and that there is no other reasonable way to mitigate or prevent that disruption. I understand that this is a fairly high standard, but that's the point - generally speaking, there are other tools available than an AE deletion, including regular community deletion processes. By analogy, you could cut your steak with a chainsaw, but it's much more sensible to go find a steak knife.With regards to this particular action, I don't think the high threshold I would expect to justify an AE deletion was met. There was nothing in the page that was so egregious that it necessitated immediate removal. There was no edit-warring on or about the page. There was no indication that taking the page to MfD would have caused more disruption than any other controversial XfD. In other words, I'm not convinced this use of deletion was reasonable, necessary, and proportionate. I don't think GoldenRing should be sanctioned for it, but I do think it was unnecessary, and in general, should not set a precedent for wider use of deletion as an AE action.In the same vein, I don't think Bishonen's temporary undeletion for DRV is a violation of sanctions.modify. It is customary to undelete pages at DRV so they can be viewed and judged by non-administrators; her intention there was clearly to allow the DRV process to proceed as normally as possible, not to simply reverse GoldenRing and walk away. I don't see that as sanctionable.I think we should heavily discourage the use of deletion as an AE action, but if we are not going to prohibit it, I don't think it's unreasonable to allow DRV to review AE deletions. The crowd there is going to be familiar with the deletion policy and evaluating administrators' application of it, which I think is relevant. However, the question of where to appeal these actions is not a hill I'll die on compared to the rest of my thoughts on the matter. ♠PMC♠ (talk) 21:17, 27 February 2019 (UTC)
- Feeling obliged to be less brief, but I find this a simple answer. I disagree with my colleagues. Deleting is not a valid action under discretionary sanctions, GoldenRing's action did not enjoy protection under WP:AC/DS, and we can consequently dispose of the other procedural questions.In the procedure for Discretionary Sanctions, placing sanctions is authorised for contentious areas. The nature of a sanction is left to the judgment and discretion of administrators, though it is loosely defined as "any sanction, restriction, or other remedy". However, I find it axiomatic that sanctions are actions that apply to a person. Discretionary Sanctions are a method of regulating conduct, not content. Blocking, warning, or topic-banning Dlthewave for conduct that disrupts the area of conflict would have been a discretionary sanction. Deleting the page on which Dlthewave performed that disruptive conduct was not a discretionary sanction. Even broad, page-level actions taken by administrators (eg "all these pages are subject to 1RR") apply to users, not pages. The Discretionary Sanctions system started out of a recognition that an area of conflict can be improved if the dramatis personae can be made to behave. Deleting pages is not within that scope. AGK ■ 11:43, 2 March 2019 (UTC)
- OK, I know I'm being annoying by dropping in on this waaaaaay late, but.... reading most of the comments here is sort of like reading a discussion about whether or not angels need a public performance permit before dancing on the head of a pin. Forgetting all the "paragraph 4 of subsection 2b of policy G" stuff, was this action useful? It seems like, on balance, it wasn't - the net effect was to attract a lot more attention to an otherwise-obscure page and occupy a lot of community time without seeming to have much effect on the person hosting this potentially-problematic material. (Am I missing something, or have they not commented on this topic?) For this specific instance, it seems like the easier route would have been the boring one - just take it to MfD. For any future hypothetical instance, the most useful answer to "can I delete stuff using DS?" is "maybe, but you're almost certainly better off doing something else". Opabinia regalis (talk) 07:23, 15 March 2019 (UTC)
- @GoldenRing: Yeah, but "maybe" is the answer to just about every question of the form "is XYZ against the rules?" :) I mean, within reason - obviously copyvio and poop vandalism are out. But if it's all just internal back-office stuff, "you can try, but it might not work" is IMO a better answer than having us all look at this particular set of circumstances and reach a decision that turns out not to be a good fit for the next time. Opabinia regalis (talk) 09:44, 18 March 2019 (UTC)
- For the purposes of clarity, I am inactive on this request despite having returned to active status as most of it has taken place while I was away. Mkdw talk 21:17, 28 March 2019 (UTC)
Survey
To see if we need to take this discussion further, it may be helpful to take a quick survey:
- Can AE admins delete pages under "other reasonable measures" as part of the enforcement process?
- A) No
- B) Yes
- C) Yes, but only per deletion policy
- C SilkTork (talk) 16:16, 4 March 2019 (UTC)
- B, with a strong note that deletions well outside the deletion policy will almost certainly be overturned at AE (or ARCA). ~ Rob13Talk 19:37, 4 March 2019 (UTC)
- B, as per Rob. RickinBaltimore (talk) 19:43, 4 March 2019 (UTC)
- B, in the sense that it's not explicitly prohibited. However as I've stated above it should be avoided unless there is absolutely no other way to mitigate some kind of serious disruption. ♠PMC♠ (talk) 20:15, 4 March 2019 (UTC)
- A. AGK ■ 23:08, 4 March 2019 (UTC)
- C Katietalk 15:13, 5 March 2019 (UTC)
- A/sorta C. The fundamental principle of arbitration is that it deals with conduct, not content. Deletion falls firmly in the "content" category. So even if the DS could be read as including deletion, ArbCom doesn't have the remit to authorise it. Of course as an admin GR is free to delete pages within the deletion policy as he wishes, but calling it an AE action doesn't make a difference, except to muddy the waters as to whether the community can overturn it (they can). – Joe (talk) 16:30, 7 March 2019 (UTC)
Post-survey discussion
- Assuming that everyone who supports B would support C if B would not pass, the rough consensus here appears to be for C. Should we propose a motion to that effect? ~ Rob13Talk 14:55, 11 March 2019 (UTC)
- I think that would be useful. Would you be able to do that Rob? SilkTork (talk) 11:41, 12 March 2019 (UTC)
- My choice of "B" was based on the wording of DS as it is currently written - ie, deletion is currently permitted because it is not explicitly forbidden - not because I think it is a good idea to include. I would oppose any motion which codified deletion as an acceptable use of DS (even option C, which is a meaningless distinction in my opinion) and would much rather we explicitly forbid DS deletion. ♠PMC♠ (talk) 20:33, 13 March 2019 (UTC)
- I have to say, I'm having trouble understanding other's views on this, because like AGK I think the answer is very obviously A. Could someone please explain how a motion along the lines of B or C would be compatible with WP:ARBPOL, "the Committee does not rule on content"? – Joe (talk) 22:35, 13 March 2019 (UTC)
- @Joe Roe: I view acceptable DS deletions as falling into the category of "removal of
contentpages outside the mainspace that is the product of a user conduct issue". For instance, if an editor in the American politics topic area kept a user page in their userspace that compiled "coverage" of conspiracy theories surrounding some modern politicians (e.g. Murder of Seth Rich, Pizzagate conspiracy theory) from fringe sources that could never be integrated into an article, I would consider a deletion of that userpage under DS to be proper. Such a user page would serve no encyclopedic purpose and would clearly represent the product of a user conduct issue (WP:NOTHERE) while not falling within the traditional CSD criteria. (U5 could apply, but not if the editor also had substantial edits in the mainspace.) Taking such a page to MfD would clearly result in deletion, but would be undesirable because it would bring attention to the fringe sources and potentially attract a disruptive brigade from off-wiki, as such discussions often do in that topic area. I think that type of behavior is exactly what DS is intended to solve: user conduct issues in particularly contentious topic areas. Sometimes, those conduct issues permeate entire pages, in which case deletion would be appropriate. I would be highly skeptical of a DS deletion in the mainspace, to be clear. ~ Rob13Talk 01:09, 14 March 2019 (UTC)- I've altered my above comment, since it was pointed out to me that WP:CONTENT defines content as stuff in the mainspace (and certain navigational pages). In that sense, this user page was quite literally not content. ~ Rob13Talk 02:13, 15 March 2019 (UTC)
- My thinking on this is more with regard to challenging an ArbCom enforcement action. The special aspect of ArbCom is that any decision is binding, and any enforcement of those decisions can only be challenged within prescribed process. If the community wishes to take away that aspect of ArbCom (as effectively has happened here) then that diminishes the special status of ArbCom. Now, if the community decides that ArbCom is no longer needed, and that we have reached a stage where the community can deal effectively with all disputes, then that's not a problem, but if the community wishes to retain ArbCom and its special aspect, then any action by an AE admin in the name of ArbCom can only be challenged and overturned in the appropriate venue. What we have here is an unusual situation in that an AE admin deleted a page under AE, and there is a question as to if this was allowable, and that question was resolved not by appropriate ArbCom process, but within a standard process. That for me is the part we need to clear up. But in order to clear that up we need to see if there is a consensus in the Committee for what is allowable. I can't see how deleting out of process is allowable because ArbCom has not been given that power. And I don't see that an AE admin is restricted in what they can do, so that they have less powers than any other admin. When an AE admin is allowed to do what is "reasonable" I am seeing that as "anything that any admin can do within policy" with the understanding that when an AE admin does that action it can only be challenged within the AE process. The significant difference for me between an action done by an admin under AE and an action done by an admin not under AE, is that the AE action has to be challenged under AE rules, and the non AE action has to be challenged under standard rules. A deletion under policy done by an admin not under AE can be challenged at DRV, and a deletion under policy done by an admin under AE can only be challenged under AE process. If we as a Committee can agree that an AE admin can do reasonable actions within policy then the special aspect of ArbCom and AE enforcement is retained, and any future such actions can be debated with AE process. For me, whichever venue this was discussed in, the outcome would have been the same - that the page should not have been deleted because it was out of process.
- @Joe Roe: I view acceptable DS deletions as falling into the category of "removal of
- Short version: An AE admin shouldn't be restricted in what actions within policy they can do. An AE admin should not do an action not allowed by policy. Questions regarding if an AE action was within policy should only be discussed within AE process.
- If we can get together a motion which says this, there can be a due process discussion at AE regarding the deletion, it can be formally overturned, and if an AE admin feels it appropriate, the page can be blanked (not deleted) under an AE action which can then be challenged at AE. SilkTork (talk) 09:35, 14 March 2019 (UTC)
- @DGG: Not all text on Wikipedia is content. WP:CONTENT defines "content" as things in the mainspace and related navigational pages. Removal of text or deletion of pages do not necessarily affect content if not undertaken in the mainspace (or related namespaces that generate content in the mainspace, like Category, Template, etc.) ~ Rob13Talk 04:54, 17 March 2019 (UTC)
- @Hobit: It's worth noting that all of our core content policies also refer to articles as the content. I'm a bit surprised that editors are making the apparent claim that any writing at all on Wikipedia is "content", which is implicit in the argument that any page deletion in any namespace would necessarily be policing content. Is this discussion right now content, in your view? ~ Rob13Talk 20:43, 17 March 2019 (UTC)
- @Hobit: I'm (of course) not saying ArbCom has jurisdiction over everything not in mainspace, just like I'm not saying ArbCom has jurisdiction over everything in mainspace merely because discretionary sanctions allow page protections there. ArbCom retains jurisdiction over past cases, including the relevant topic areas involved where we have enacted discretionary sanctions. To the extent those areas overlap with things not in the mainspace, I think deletion is one valid tool of many that admins could use when appropriate and warranted by the level of disruption inherent in a particular page. I think it should be used extremely sparingly, and ultimately, the community can determine at AE whether any particular deletion is warranted. ~ Rob13Talk 05:06, 18 March 2019 (UTC)
- @Hobit: It's worth noting that all of our core content policies also refer to articles as the content. I'm a bit surprised that editors are making the apparent claim that any writing at all on Wikipedia is "content", which is implicit in the argument that any page deletion in any namespace would necessarily be policing content. Is this discussion right now content, in your view? ~ Rob13Talk 20:43, 17 March 2019 (UTC)
- GoldenRing, I strongly disagree with that reasoning. AE is a tool for allowing community processes to occur smoothly. It is not a replacement for those processes, no matter how controversial they have the potential to be. If, as you have argued, there's disruption XfD or DRV or ANI, you use targeted sanctions to remove the disruption and allow the community to proceed as normal. You don't just get to decide that something might be problematic and delete it because it might cause too much of a fuss. By your logic, one could justify deleting anything that might be controversial. Too many people arguing about a BLP AfD? Just delete it. Tired of people arguing about an India-related navbox? Delete it. No. No way. I absolutely object to the use of DS as a shortcut around community processes. That is absolutely not their purpose. ♠PMC♠ (talk) 13:10, 18 March 2019 (UTC)
- GoldenRing, sanctions under AE are supposed to be deployed when there is a problem, in order to control the problem so the normal process of editing and consensus-building can resume. You issue a TBAN when someone has demonstrated an inability to edit in an area without causing problems, so that everyone else in that area can get back to editing normally (and, hopefully, so the TBANned editor can go edit constructively elsewhere). You don't issue a TBAN pre-emptively before someone causes a problem on the assumption that they might. In the same vein, I don't think it's reasonable to assume that an XfD/DRV/ANI discussion will be so problematic that preemptively deleting a page is the best solution, especially when there are lesser sanctions available to handle disruption as it comes up. ♠PMC♠ (talk) 23:54, 18 March 2019 (UTC)
Motion: Discretionary sanctions procedure
- For this motion there are 10 active arbitrators, not counting 3 who are inactive and 1 who has abstained or recused, so 6 support or oppose votes are a majority.
(1) Proposed:
- Support
-
- Proposed. I understand that some colleagues have asserted views to the contrary, above, but we need to progress towards a decision. I simply don't think we want page deletion to be used as a means of enforcing user conduct standards. This one edge case (after over a decade) should not be used to expand the scope of DS or the rights of Enforcing Administrators. AGK ■ 14:23, 24 March 2019 (UTC)
- I'm fine with this as is, but perhaps others might be happier with the addition of "to delete pages outside of the deletion policy", in line with the results of our straw poll above? – Joe (talk) 14:42, 24 March 2019 (UTC)
- Support as written. ♠PMC♠ (talk) 15:04, 24 March 2019 (UTC)]
- Support, with Joe's amendment. RickinBaltimore (talk) 18:43, 24 March 2019 (UTC)
- Oppose
Because this does not solve the problem. Alternative proposed. SilkTork (talk) 09:54, 25 March 2019 (UTC)Move to abstain to help move this forward. SilkTork (talk) 14:40, 9 April 2019 (UTC)- Moving here, in favor of the second version. ~ Rob13Talk 13:31, 25 March 2019 (UTC)
- You know, I still agree with myself up above that this is not really a problem that needs a new rule. The answer should be 'maybe', as in, probably not, but if you make a good argument for a specific oddball case then sure. This particular set of circumstances didn't fit, but that doesn't mean it's a terrible idea that must be forbidden forever. I agree with AGK's first point - we probably don't want to make this a habit - but have the opposite feeling on the second, that is, if in over a decade we've come across only this one edge case, then that means we don't need to write any new stuff and choosing not to do so is not "expanding" anything. Sorry to anyone who's been reading this hoping for "clarity" or "bright lines" - I just don't think this is an issue calling out for definitive resolution. If it starts happening five times a month, we should revisit it then. Opabinia regalis (talk) 06:50, 1 April 2019 (UTC)
- Per OR. Katietalk 15:42, 3 April 2019 (UTC)
- Abstain
For now. I may oppose, but my thoughts at the moment are basically that this comes up so infrequently and causes so much drama that an enforcing administrator should just use the other tools available to them in such a situation, even if they aren't quite as good a fit. If an editor is creating whole user pages that contain polemical statements in an area with discretionary sanctions, just block them for disruption. ~ Rob13Talk 15:39, 24 March 2019 (UTC)
- Comments by arbitrators
- @Spartaz: My phone has learned "arbcom" by now, but the top alternative is "a boom". I think our phones are trying to tell us something... :) Opabinia regalis (talk) 07:16, 9 April 2019 (UTC)
Motion: Discretionary sanctions procedure (2)
- For this motion there are 10 active arbitrators, not counting 3 who are inactive, so 6 support or oppose votes are a majority.
(1) Proposed:
- Support
-
- Putting forward an alternative. I'm not comfortable with the notion that a AE admin should have less authority than a non AE admin, and so create a situation where someone creates a page in direct violation of an ArbCom sanction, yet an AE admin could only delete such a page outside of ArbCom protection, and so there is uncertainty (again) over where the matter should be discussed. The above motion does not protect against such a situation, and so does not solve this problem. SilkTork (talk) 09:54, 25 March 2019 (UTC)
- Support as first choice, as this is the amendment Joe mentioned above. RickinBaltimore (talk) 12:19, 25 March 2019 (UTC)
- ~ Rob13Talk 13:30, 25 March 2019 (UTC)
- Support as second choice. – Joe (talk) 06:18, 31 March 2019 (UTC)
- Oppose
-
- No, because if the deletion is within the deletion policy, then there is no need to use DS as a reason for deletion in the first place. If it is that problematic, chances are it will fit under a speedy criteria (such as G10 if it is an attack page or G5 if created in violation of an existing sanction). If not, there is no reason it cannot be taken through the relevant XfD process (which can be controlled with DS sanctions if that causes problems). ♠PMC♠ (talk) 19:16, 25 March 2019 (UTC)
- First, per PMC. We are providing for discretionary sanction to not include deletions. We are not prohibiting an administrator from also deleting a page under their separate powers. We are, in passing, preventing absurd consequences like "Are these deletions subject to DRV?" or "Can deleted text be provided and adapted under WP:REFUND?" I should also oppose because the clause "per the deletion policy" is a vague, catch-all statement lacking the precision that we know administrators expect to be in place before they act. I am not sure I clearly understand what parts of the deletion policy it means now. Finally, I do not see what ambiguity is left behind by removing deletion as a D.S. as in the first motion – I have perhaps misunderstood SilkTork's contribution on this point. Also, I should repeat my earlier vote – deleting pages has not (except for minor cases under ARBBLP) been a form of discretionary sanction. Changing that now would be unnecessary and unwise. AGK ■ 22:06, 25 March 2019 (UTC)
- See my comment above. Opabinia regalis (talk) 06:52, 1 April 2019 (UTC)
- Per OR. I can't get behind making policy like this based on one instance of hundreds. Katietalk 15:44, 3 April 2019 (UTC)
- Abstain
-
- Comments by arbitrators
Motions
Proposed amendment to the arbitration policy
Motion adopted (version 2) Bradv🍁 23:04, 8 April 2019 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Version 1Pursuant to the arbitration policy's section on "Ratification and amendment", the Arbitration Committee resolves that the following change to the arbitration policy will be submitted for formal ratification by community referendum: This amendment to the arbitration policy will enter into force once it receives majority support, with at least one hundred editors voting in favour of adopting it. Until this amendment is ratified, the existing arbitration policy remains in effect.
Version 2Pursuant to the arbitration policy's section on "Ratification and amendment", the Arbitration Committee resolves that the following change to the arbitration policy will be submitted for formal ratification by community referendum: This amendment to the arbitration policy will enter into force once it receives majority support, with at least one hundred editors voting in favour of adopting it. Until this amendment is ratified, the existing arbitration policy remains in effect. Enacted – Bradv🍁 22:58, 8 April 2019 (UTC)
Discussion and comments
|
Restoration of sysop privileges to Necrothesp
Motion adopted (Version 1) – bradv🍁 02:57, 10 April 2019 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Version 1 (Necrothesp)On March 14, 2019, the administrator permissions of Necrothesp (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) were temporarily removed as a suspected compromised account under the Level 1 desysopping procedures. Following discussion concerning account security, and pursuant to the procedures for return of revoked permissions, the Arbitration Committee resolves the following: Enacted – bradv🍁 02:50, 10 April 2019 (UTC)
Version 2 (Necrothesp)
|
Motion adopted (Return of permissions) – bradv🍁 14:53, 10 April 2019 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Motion 3: Return of permissionsEnacted – bradv🍁 14:50, 10 April 2019 (UTC)
Discussion and comments (Necrothesp)I don't wish to beat up on this particualr admin (since that's already been done to the point where I'm sure the message has been received) but I would urge the committee to go with version 2, and to consider it a sort of final warning that admins are expected to secure their accounts and ignorance of the last 5-6 years (at least) of evolving policy on this matter is no excuse as we expect admins to be up to speed on important policies. And reports about this hae been in the monthly admin newsletter how many times now? I've lost count. Kinda a big part of the job, and if you can't be bothered to keep up you should be big enough to hand in the tools. Beeblebrox (talk) 01:18, 8 April 2019 (UTC)
|
Requests for enforcement
Arbitration enforcement action appeal by Dlthewave
Warning retracted, page restored--Ymblanter (talk) 05:50, 10 April 2019 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
To help determine any such consensus, involved editors may make brief statements in separate sections but should not edit the section for discussion among uninvolved editors. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see WP:UNINVOLVED).
Sandstein (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Statement by Dlthewave
Statement by SandsteinAfter rereading User:Dlthewave/Whitewashing of firearms articles, I agree with the appellant that the page was not (quite) a violation of WP:POLEMIC because it did not name editors and did not make allegations of misconduct, except as implied in the title ("whitewashing"), but that alone probably doesn't merit a warning. Because that page was the reason for my warning, I am striking it and recommend that GoldenRing (talk · contribs) undelete the page. A case can perhaps be made for its deletion on grounds of copyright / attribution, but that's a matter for the deletion process. Sandstein 18:37, 23 February 2019 (UTC)
Statement by SpringeeI'm clearly an involved editor. As I said before I think Dlthewave has a very strong POV on this topic and I frequently disagree with them. However, when push comes to shove, I don't think on good faith they viewed the page as a POLMIC. For what it's worth, I would support reverting Dlthewave's warning. Springee (talk) 19:12, 23 February 2019 (UTC) Statement by GoldenRingI disagree with Sandstein above and stand by this action. Dlthewave has stated right here that the purpose of this page is to document long-term problematic editing and policy is clear that such material is allowed only for dispute resolution and when used in a timely manner. I don't see the practical difference between, "so-and-so said this" (which the appellant seems to admit would be disallowed) and "someone said this and here's a link showing who it was" which is what they've actually done. GoldenRing (talk) 21:01, 23 February 2019 (UTC)
Statement by Simonm223Marginally involved. I just found out about the removal of DLThewave's excellent summary of the challenges faced to bring firearms into compliance with WP:N including the way that a wikiproject has tried to present their MOS suggestions as policy. I've said as much at another venue, but this is definitely not a violation of WP:POLEMIC and should be undeleted for the valuable resource it is. Simonm223 (talk) 15:03, 25 February 2019 (UTC) Statement by (involved editor 2)Discussion among uninvolved editors about the appeal by Dlthewave
Result of the appeal by Dlthewave
|
Roscelese
Blocked for a week. Sandstein 17:40, 4 April 2019 (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. Request concerning Roscelese
Roscelese has three restrictions against her that are, as far as I know, currently in place. They include being indefinitely prohibited from:
I offer here a few representative samples. First, reverting without discussing the issue first on the talk page: It is also worth noting that 25 of her last 100 edits have "Reverted" in the edit summary. Some of these are clearly reverting vandals, but many are reversions not discussed on talk first. Next, casting aspersions and personalizing disputes:
For what it's worth, I tried extending an olive branch to Roscelese about a month ago, but it was rejected.
Discussion concerning RosceleseStatements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Roscelese
Statement by PudeoThe diffs that represent "engaging in conduct which, in the opinion of any uninvolved administrator, casts aspersions, or personalises disputes" at Talk:Dissent from Catholic teaching on homosexuality#Condemnation of homosexuality seem very valid. Roscelese wrote: This motion is from 2015, so perhaps it's hard for Roscelese to always keep in her mind, or then she's just being harsh with new editors who aren't aware of these personal sanctions. In any case, this sanction should be either enforced or rescinded, because it's pointless otherwise. --Pudeo (talk) 07:13, 29 March 2019 (UTC)
Statement by Slugger O'TooleIt is true that the restriction does not say that reverts need to be discussed first on the talk page, but they were not discussed by you at all. Additionally, when you call me out by name, and use my former username to boot, that is personalizing a dispute. So is talking about my "personal caviling." I am not saying I am blameless. There are surely times when I could have acted better and for those times I apologize. --Slugger O'Toole (talk) 00:50, 2 April 2019 (UTC) Statement by DebresserI think this request should be rejected since it was made by an editor who has admitted to not having clean hands. In addition, I do not think that mentioning Slugger/Brian by name has "personalized" the conflict, as claimed. Debresser (talk) 17:02, 4 April 2019 (UTC) Statement by (username)Result concerning Roscelese
|
Nishidani
Debresser (talk · contribs) is banned from creating or making comments in WP:AE reports related to the Arab-Israeli conflict, except if they are the editor against whom enforcement is requested. Sandstein 16:57, 7 April 2019 (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. Request concerning Nishidani
I haven't seen Nishidani around in a while after his latest announced retirement ended (admittedly not after a week but after 6 weeks), but he unfortunately has still not mended his bad ways. His inflammatory and insulting language, consciously or not intended to intimidate his opponents, coupled with hounding and harassing me on various pages, including my talkpage, are unacceptable battleground behavior on this project, and especially in the IP-conflict area.
@Huldra
@Black Kite The hounding and general battleground mentality are a result of Nishidani's problem with me, which is rooted on our disagreements in the WP:ARBPIA area. If this forum would, however, decide, IMHO mistakenly so in view of the larger picture, that this is the wrong venue, I will indeed take your advice and report him at WP:ANI. Debresser (talk) 02:00, 7 April 2019 (UTC) @Cullen328
Discussion concerning NishidaniStatements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by NishidaniI don't think I need comment, after Cullen's palmary reflection. If I were to, it would be easy to show Debresser's behavior in my regard has been persistently vexatious. But since on principle I refrain from whingeing, I won't do so even under provocation (unless of course an admin thinks I need to defend myself from the 'evidence' given above).Nishidani (talk) 10:06, 7 April 2019 (UTC)
Statement by Huldra
Pot.Kettle.Black, Huldra (talk) 23:53, 6 April 2019 (UTC) Statement by NableezyDebresser, and I hope you take this as honest advice, but I would suggest that inviting scrutiny to the editing history of Eliezer Berland would likely not be in your own interest. If you do however want to invite that scrutiny then this cannot be the place for it, as this page is very specifically about enforcing arbitration decisions. Neither of the articles here are covered by ARBPIA (or any other arbitration case), making them irrelevant on this page. nableezy - 02:25, 7 April 2019 (UTC) @Cullen328: youve attributed noble pursuits to me that I regretfully cannot take credit for. nableezy - 03:39, 7 April 2019 (UTC) Statement by Cullen328I am involved in discussing the content issues at the talk pages of both articles. Debresser brought the Eliezer Berland dispute to ANI, incorrectly accusing another editor of refusing to discuss the dispute at the article talk page. Debresser was edit warring on that article to include promotional self-published puffery from a website controlled by a convicted, self-admitted rapist. As for Talk:Jewish religious clothing, there was an active RFC underway there, which draws in previously uninvolved editors. Surely Debresser knows that processes such as RFC and venues such as ANI draw previously uninvolved editors such as Nishidani into the discussions. This is not hounding. I do not like use of the f-bomb in conversations among editors, do not use it myself and recommend that other editors refrain from its use. But there is no consensus that this word is banned from spirited debates among editors. Debresser seems to be advocating a stranger standard here: it is OK for him to drop f-bombs every 33,000 edits or so, but not OK for other editors to do so more frequently. As for ARBPIA, these are both topics related to Judaism but neither has any connection to the Israel-Palestinian conflict. If Eliezer Berland was related to that conflict, then Debresser's edit warring there would have been even more egregious. As for Talk:Jewish religious clothing, Nishidani is advocating for genuine improvements to that article, while Debresser is dragging his feet, because he does not like images and content that deviate from his admitted personal ultra-Orthodox Jewish identity. I recommend that Nishidani dial back use of the f-bombs because I consider that counterproductive. Nishidani should also be advised to stay away from Debresser's talk page, with the exception of standard required notifications. In my opinion, the real cause of this report is that Debresser resents the fact that a pro-Palestinian editor is making cogent and incisive observations about articles concerning Jewish topics. That is nothing to be concerned about and instead should be welcomed. No formal action is required here other than mild admonitions to the two parties. Cullen328 Let's discuss it 03:35, 7 April 2019 (UTC)
Statement by IcewhizNote there was a recent RfC at WP:CIVIL regarding Statement by Dan MurphyFor fuck's sake. Debresser was formally warned against filing any more "vexatious" arbitration requests. Less than six months ago. So there is some enforcement to be done here. Here is what the closing admin said of Debresser's ongoing pattern of behavior at the time: "On a number of occasions, Debresser has improperly presented requests for arbitration enforcement. Taken as a pattern, Debresser's actions are an abuse of process that is serving to inflame tensions in topic areas that already are heated. Furthermore, whilst Wikipedia process pages are internal, conduct such as abuse of process itself, indirectly, affects the external topic area that is subject to arbitration enforcement. Conduct such as Debresser's is therefore equivalent in seriousness to tendentious or disruptive editing of content pages. I therefore formally warn Debresser that continuing such conduct will result in enforcement action, such as restrictions from requesting enforcement, blocks, and topic bans." You'd be foolish just to punt on this problem. His dissembling and dishonest presentation of disputes only grows worse when he isn't disciplined.Dan Murphy (talk) 16:26, 7 April 2019 (UTC) Result concerning Nishidani
|
Icewhiz
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 Icewhiz
- User who is submitting this request for enforcement
- Nableezy (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) 17:21, 9 April 2019 (UTC)
- User against whom enforcement is requested
- Icewhiz (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)
Search DS alerts: in user talk history • in system log
- Sanction or remedy to be enforced
- Wikipedia:Arbitration/Index/Palestine-Israel_articles#Standard discretionary sanctions
- Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
Tendentious editing is defined in WP:TE as a manner of editing that is partisan, biased or skewed taken as a whole. It does not conform to the neutral point of view, and fails to do so at a level more general than an isolated comment that was badly thought out. On Wikipedia, the term also carries the connotation of repetitive attempts to insert or delete content or behavior that tends to frustrate proper editorial processes and discussions. WP:ARBPIA3#Tendentious editing further says that Users who disrupt the editing of articles by engaging in sustained aggressive point-of-view editing and edit-warring may be banned from the affected articles. I believe the evidence below demonstrates that Icewhiz is such an editor engaging in sustained tendentious editing.
Icewhiz routinely removes material on spurious grounds when that material is, in his view, negative towards Israel. He will routinely make opposing arguments based solely on the POV presented. He will oppose reliable sources when it suits him and support unreliable sources when it suits him, sometimes making the exact opposite argument nearly simultaneously depending on the POV of the source.
- In this edit (7 June 2018) Icewhiz places in the article material on footage that was doctored by the IDF, footage that was widely denounced as a propaganda ploy
- In this edit (8 June 2018) Icewhiz restores that she was "allegedly shot" by the IDF, when the cited source says flat out as shot dead by Israeli troops the previous day along the Israel-Gaza border. ... Razan Najjar, a 21-year-old volunteer paramedic, was shot as she tried to help evacuate wounded near Israel's perimeter fence with Gaza. Yes, that was a revert of an IP editor. However, the material had likewise been added by an IP, with Icewhiz editing directly after and not enforcing the general prohibition there. And even if the revert is excused by the general prohibition, we all take responsibility for our reverts. When Icewhiz restored the edit he took responsibility for its content. That content being quite different from what the cited source said.
- In this edit (11 June 2018) Icewhiz removes all of the content critical of the IDF's manipulation, changing misleadingly took a prior interview that al-Najjar gave to a Lebanese television station out of context to cut a short segment of a prior interview that al-Najjar gave to a Lebanese television station in which she He also removed the rest of the statement, a statement that every reliable source covering the manipulation included as demonstrating that the IDF manipulation was done to mischaracterize her words.
- When asked about why he removed what every reliable source had said about the doctoring of the video, he responded That is a factual representation of this 10 second clip.
- Restores an op-ed by a political activist (1 January 2019). On the talk page he argues that this should be retained because it was published in an RS. Compare to his removal of an op-ed published in a reliable source which he said was Random opinion of non-politician/expert - UNDUE and on the talk page said of highly fringe political activist, in an op-ed. That is his arguments are diametrically opposed based solely on the POV of the op-ed. Where it supports his POV he argues for inclusion, when it opposes it he argues for exclusion. I dont think there is a better example of tendentious editing than making the opposite argument based solely on POV.
In sum, his efforts at Rouzan al-Najjar consisted of originally pushing propaganda, removing that it was propaganda when covered by numerous reliable sources as such, and pushing in opinion pieces of the sort he rejected when it suited his own POV elsewhere.
- In this (13 December 2018) and this edit Icewhiz removes a source, and all material cited to it, as "propaganda" and claims the source is misrepresented because we included the wrong publisher. The living person who he says was "propaganda minister", which if I am not mistaken is a pretty blatant BLP violation, is in fact the former Information Minister (in charge of election polls and TV and other media licensing) and Foreign Minister. Note that Google Books includes the wrong publisher, which is Kluwer Law International and not Brill. Instead of correcting the error, the entire source is removed. The book is edited by two academics (Moshe Maoz and Sari Nusseibeh) and published by a respected press, but Icewhiz's BLP violation of an edit summary ignores all of that to excise material he dislikes on the most spurious of grounds.
- His other contribution of note (25 January 2019) was to excise about half of the article unilaterally. The removed information was uniformly of material that has garnered criticism of Israel. He completely removed, not condensed or moved to sub-articles or anything else that might be justified by WP:SIZE, reliably sourced material on comparisons to colonialism, on terminology bias, on American media bias, on land seizures, on the history of the settlement enterprise, the entirety of the section on settler violence, most of the material on torture, the impact on children, on fragmentation, the road closure system, censorship, restrictions on Palestinian agriculture, on the use of the territory as a waste zone. What he removed had one common thread. It was reliably sourced material that dealt with topics that have drawn criticism of Israel's methods. No attempt at justifying the removal, not splitting but straight up removal, was ever even attempted besides a vague wave to WP:SIZE. He made no attempt to summarize, no attempt to split. It was purely a tactic to excise material that Icewhiz would rather not be covered on Wikipedia.
- Tendentious editing regarding sources
- Here (25 July 2018) Icewhiz argues that a "part-time historian" (his words) would be perfectly fine for an attributed statement. Compare that to here (15 June 2018), where an actual historian who has been published by academic presses is rejected as definitely a WP:BIASED source, and would require balancing at the very least. The only consistency in Icewhiz's arguments regarding sources is when they are supportive of his POV he encourages their use, and when they are not he opposes them.
- Removes Yael Berda per WP:BLOGS (8 April 2019). Note that this is hosted by Stanford University Press, where the author had just had a book on this topic published which WP:BLOGS says means her self-published work is allowed (established expert whose work in the relevant field has previously been published by reliable third-party publications). Compare that to this (17 March 2019) where Icewhiz argues for the inclusion of material referenced to IDFBlog.com (now defunct) for attributed quotes. However, a blog entry by an author who is academically published and hosted by Stanford University Press is not usable for an attributed quote because the author is a fairly young scholar. The only consistent part of this argument is how it reflects his POV. A blog by an unnamed person at the IDF that has been cited by no-one and has an h-index of 0 that coincides with his own POV is fine to use. One by a published academic that has has over 100 citations to her work but that opposes his POV is not because her h-index is 5 and she is "fairly young".
- Tendentious editing regarding tagging
- Here Icewhiz argues that "removing the tag without consensus is edit warring" (3 December 2018)
- Here he removes a tag as not having consensus (25 July 2018)
Again, the only thing consistent about these actions is how they reflect on his POV. When his POV is presented no tag may be included absent a consensus for it (which is honestly kind of silly, if there were already a consensus then the article content would be adjusted), but when his POV is not given what he feels is its appropriate prominence the tag must remain absent a consensus to remove.
- 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, on 29 March 2019
- Gave an alert about discretionary sanctions in the area of conflict in the last twelve months, on 8 April 2019
- Participated in an arbitration request or enforcement procedure about the area of conflict in the last twelve months, on 7 April 2019.
- Additional comments by editor filing complaint
I understand this is a long complaint. I dont know how to demonstrate tendentious editing without exceeding 500 words as the act is defined by a long term pattern and not just one or two diffs. I also understand it deals with content, but I think the evidence demonstrates continued tendentious editing and not merely a content dispute. One cannot make opposing sides of the same argument and pretend that they are two individual content disputes. Either Icewhiz feels that blogs may not be used or that they may. Either Icewhiz feels that opinion pieces may not be used or they may. Either Icewhiz feels tags may not be removed without a consensus or they may. Icewhiz apparently feels all these things, it just depends on what POV is under discussion. That is, to my understanding, textbook tendentious editing.
- Sir Joseph, I am not complaining that Icewhiz claimed Finkelstein is biased. I am complaining that he has made polar opposite arguments about sources when it suits his POV. This is not about opposing Finkelstein or supporting Tabenkin. It is about making opposing arguments where the only consistency is the POV being pushed. That behavior is, I think, called tendentious editing here, and it is prohibited on Wikipedia, especially so in a topic area covered by discretionary sanctions. As WP:TE says, a single edit is unlikely to be a problem, but a pattern of edits displaying a bias is more likely to be an issue, so yes these diffs stretch back to show that pattern. nableezy - 17:41, 9 April 2019 (UTC)
@Sandstein: I've dated the diffs, however I dont think their age makes them stale. The very nature of WP:TE is that it requires showing a pattern. A pattern is something that occurs over time. How would one show a pattern over time without showing diffs from the past? nableezy - 18:10, 9 April 2019 (UTC)
Yes Icewhiz, I called this claim that this established a consensus a lie. Because it says "no consensus". Calling something that says "no consensus" "a consensus for language in this article" can best be described as what exactly? nableezy - 19:20, 9 April 2019 (UTC)
- The responses below just provide further evidence for tendentious editing. As Zero wrote below, nothing Icewhiz writes can be accepted at face value. I agree, he is a very smart person. He could be a fantastic editor. But he makes bogus arguments on a regular basis. He says Nableezy contrasts an expert in journalism commenting on the NYT imvestigation in Rouzan al-Najjar with a pianist/conductor/activist commenting on Basic Law: Israel as the Nation-State of the Jewish People. No, lets be clear on this. Ira Stoll is not an "expert in journalism". He was managing editor of a failed newspaper and an author of two books, neither on journalism. And the justification of receiving third party coverage was offered only later. When added, Icewhiz was on record opposing the use of op-eds even when published in reliable sources. But with one that supports his POV, Ira Stoll's column was published by a RS, the end. This is a constant issue when discussing issues with Icewhiz, he makes comments that are expected to be taken at face value and they cannot be because they are so often false. nableezy - 05:06, 10 April 2019 (UTC)
I suppose Sandstein may be right and AE is not well suited to such a request. But, Sandstein, it is exactly a person who is not interested in the subject that should be looking at this. Just look at the bullets for tendentious editing regarding sources. Can an editor be acting in good faith when they both support the use of a blog by an unnamed person with an h-index of 0 and then reject the use of a blog by an established expert on the topic because her h-index is 5? Can an editor be acting in good faith when they remove op-eds by non-experts published in reliable sources because they are op-eds by non-experts and then also add op-eds by non-experts and respond that its fine because it was published by a reliable source? Ignore the content entirely. Can an editor in good faith make such opposing arguments? Or is it tendentious editing when their arguments flip depending on POV? nableezy - 14:59, 10 April 2019 (UTC)
- Notification of the user against whom enforcement is requested
Discussion concerning Icewhiz
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 Icewhiz
Due to the extreme length of the complaint, with diffs ranging back almost a year, I can not respond in 500 words and address each accusation here. I will note that in regards to the trim to Israeli occupation of the West Bank (which I discussed prior, after, and initiated Talk:Israeli occupation of the West Bank#RfC: Article size that resulted in the article being trimmed in the end) - I already responded in Wikipedia:Arbitration/Requests/Enforcement/Archive245#Icewhiz - closed "Not actionable; content dispute". I can explain all my actions, though I will note I am not a robot and that my view of Wikipedia policy has evolved over time (e.g. today I am much less of an inclusionist in relation to a year ago). Admins - please point out which diffs I should respond to, if at all.
I do want to raise the immediate background to this complaint: Israeli permit system in the West Bank. Nableezy moved it from "system" to "regime", after 2.5 days of discussion (Talk:Israeli permit system in the West Bank#name), 02:06, 12 March 2019. After his move was challenged, he 14:56, 19 March 2019 move warred. Not only that - he opened an ANI against Wikieditor19920 who challenged him (closed no action, Oshwah moved the article through a few different titles - until it moved back to system). At ANI - Nableezy repeatedly called me "dishonest" (after I challenged his assertion that "regime" was the stable form of the title) - [23][24]. A subsequent Talk:Israeli permit system in the West Bank#Requested move 19 March 2019 closed with "system" remaining. Nableezy then decided, 21:57, 7 April 2019, to add a direct-quote to the lede from one (of the minority) of sources that uses "regime".
When I challenged this quote by Berda in the lede, that resulted in 2 out 3 sentences in the lede being sourced to Berda (sentence 2 already containing her definition - from a published source) - my edit summary wasn't just "BLOGS", it was "WP:BLOGS. No need for direct quote in lead.". I further expanded my argument on talk - diff - that presenting Berda twice in the lede, was UNDUE, and that there was no need to use unpublished work here (as published work is not lacking - including published work by Berda). I did not challenge Berda as a source overall - I challenged the direct quote, from an academic blog (as opposed to her published work), specifically in the lede.
In last few days (7-8 April), in the permit system talk page Nableezy has called me or my edits/arguments: "dishonest"/"deceitful"[25]. I requested him to strike these statements (as a personal attack) [26], which he refused. He continue to use language such as "lying"[27], "dishonest arguments"[28][29], "being dishonest",[30]. He did not strike "being dishonest" even after admitting "you are right".[31] (this in regards to this source,[1] which uses "regimen" in a sub-title and in paragraph2 (further down there is a regime) and which we were quoting in the citation as "regimen").
In less than a span of 3 weeks - Nableezy has filed once in AN/I and once over here in AE against two different users on this article.Icewhiz (talk) 18:57, 9 April 2019 (UTC)
References
- ^ "Israel Has 101 Different Types of Permits Governing Palestinian Movement". Haaretz. 2011-12-23. Retrieved 2019-04-07.
The most common permits are those allowing Palestinians to work in Israel, or in Jewish settlements in the West Bank. Over the decades, however, the permit regimen has grown into a vast, triple-digit bureaucracy.
- @Vanamonde93: - in regards to the first 4 bullets, note that the article was created on 3 June 2018 on a 1 June event. The article was heavily edited in those days, with various new news items added (a general NOTNEWS/RAPID issue). In regards to the 7 June 2018 - when I added this, it was not widely denounced - I summarized the sources I cited. Criticism developed later. In regards to 8 June 2018 - this was a revert per the General Prohobition of an IP (who removed a whole paragraph + allegedly). At the point this was made (7 days from the shooting, no definitive investigation) - while it was highly likely the shots came from the IDF, and some sources said this as fact - others did not. At that point in time, per BLPCRIME and erring in the side of caution, avoiding a definitive stmt in Wikivoice is inline with what we do with other crime/military articles. In regards to 11 June 2018 - contrary to Nableezy's assertion I left criticism in the very next sentence -
"The Israeli military was widely criticized for its efforts in manipulating the video, with commentators drawing parallels to past instances of the IDF manipulating or otherwise faking evidence in the past."
. There was also an issue in that some of the content was sourced to an article title (often edited for sensationalism) and not to its body. I thought that presenting what the IDF presented (in one sentence), followed by a sentence of how this was criticized would separate the exhbit by the IDF and criticism of the exhibit. Regarding 1 Jan 2019 - Stoll's criticism of the NYT piece (which we cover in depth - 4 paragraphs in a level2 header) was covered in a secondary manner by JTA. Nableezy agreed on the TP to use of Stoll via JTA - 8 Jan 2019. Nableezy contrasts an expert in journalism commenting on the NYT imvestigation in Rouzan al-Najjar with a pianist/conductor/activist commenting on Basic Law: Israel as the Nation-State of the Jewish People - for the basic law we have no shortage of critical (even very critical) opinions by experts in law - which we should favor over a non-expert. Inclusion of opinions can of course be debated - there isn't a hard and fast law for DUE/UNDUE - it is article dependent, and in this case the basic law is very different (a topic very well commented and studied - we have no shortage of sources and opinions). In all cases, I participated in the talk page and attempted to form a consensus. I could have done some things better, but I do want to stress that the article was in breaking-news turf in June 2018 - it started with videos and reports from the Palestinian side, followed by Israeli retorts, and only a few months later (e.g. the NYT choosing this incident for an in-depth reconstructive investigation) we had more definitive sources. I am not sure I would have made the same edits today back then (e.g. by avoiding NOTNEWS).Icewhiz (talk) 22:05, 9 April 2019 (UTC)- @Vanamonde93: I'm not saying I was perfect. I was reverting this IP edit with no edit summary, was acting inline with WP:ARBPIA3#500/30 in regards to an IP edit, and I was probably responding to the removal of the paragraph. In retrospect (having re-read NBCNews/AP again now) I should've added a citation that used other language, or used attribution - I admit to sloppy handling of the NBCNews citation - had this been contested on this basis (on the talk-page or in an edit rationale) - I probably would've discussed and/or rectified the citation issue. In terms of lead balance at that point in time - this Washington Post piece in the article at the time was using -
"who witnesses say Israeli soldiers shot dead near the border fence on Friday."
- and didn't directly say Israel in its voice. Our policy - WP:NPOV generally and WP:BLPCRIME specifically - has us being cautious with statements in our own voice. And I stress - this is all me thinking back of what I was thinking in June 2018 - based on sources available then.Icewhiz (talk) 22:44, 9 April 2019 (UTC) - Also - in regards to Nableezy's claim I did not revert per the General Prohibition on - this IP on 7 June - my subsequent edit was my very first edit to this article. I frankly probably did not look at the edit history at all when I made that edit at all. I probably got drawn to the article (4 days after creation) by news or it popping up an alert, and was looking at it for the first time which is not a situation in which I usually look at the editing history too much. After doing my edit - I probably watch-listed it. Icewhiz (talk) 23:05, 9 April 2019 (UTC)
- In regards to "doctoring" vs. "editing" in June 2018 - I was responding directly to Zero himself who advocated (without citing any source) inclusion of
"deliberate doctoring of the video"
- 11:50, 12 June 2018. I opposed this - and what Zero fails to mention is that I described it as possibly"Deceptive editing"
. Unlike Zero - I cited sources for my assertion - namely a dictionary and the New York Times which used "tightly edited".13:06, 12 June 2018 Icewhiz (talk) 10:44, 10 April 2019 (UTC)
- In regards to "doctoring" vs. "editing" in June 2018 - I was responding directly to Zero himself who advocated (without citing any source) inclusion of
- @Vanamonde93: I'm not saying I was perfect. I was reverting this IP edit with no edit summary, was acting inline with WP:ARBPIA3#500/30 in regards to an IP edit, and I was probably responding to the removal of the paragraph. In retrospect (having re-read NBCNews/AP again now) I should've added a citation that used other language, or used attribution - I admit to sloppy handling of the NBCNews citation - had this been contested on this basis (on the talk-page or in an edit rationale) - I probably would've discussed and/or rectified the citation issue. In terms of lead balance at that point in time - this Washington Post piece in the article at the time was using -
Statement by Sir Joseph
There is so much to say here, especially considering that many of the diffs are old, and that this is just a wall of text and trying to blast yet another opponent out of the sphere. I will just note one thing, Nableezy complains that Icewhiz says Finkelstein is biased, of course he's biased, indeed, the very first sentence of his article calls him an activist, "Norman Gary Finkelstein (/ˈfɪŋkəlˌsteɪn/; born December 8, 1953) is an American political scientist, activist, professor, and author." Any serious editor in the IP area would not use Finkelstein as an unbiased source. If you do take this matter seriously, I urge you to take it with a grain of salt. Sir Joseph (talk) 17:35, 9 April 2019 (UTC)
- To Nableezy, regardless, it's irrelevant, those edits were not in mainspace, they were in WP:RS, so I don't get the harm, that is where we do give editor a little leeway to offer why they feel sources are or aren't RS. Sir Joseph (talk) 17:48, 9 April 2019 (UTC)
Statement by GizzyCatBella
I would like to issue a solemn appeal to reviewing administrators to study this report in depth and with special attention. Additionally, please allow some time for other editors to share their comments and opinions.GizzyCatBella (talk) 20:17, 9 April 2019 (UTC)
Statement by Wikieditor19920
Having interacted with both parties, I regard this as a frivolous and vindictive report. Nableezy almost exclusively edits within the ARBPIA area with a distinct edge. If any of Icewhiz's edits, collectively or individually, are considered to show a discernible bias actionable under WP:TE, then an evaluation of Nableezy's contributions by that same standard would have to lead to equivalent or more severe sanctions. Also, the diffs provided could be attributed to errors in judgment or reading sources; in other words, mistakes made in good-faith. Hardly a compelling basis.
I don't want to exceed my limit here, but Zero0000 should have disclosed in his statement below that he consulted with Nableezy about this report prior to its filing. Wikieditor19920 (talk) 14:56, 10 April 2019 (UTC)
Statement by Stefka Bulgaria
I agree that too many diffs going back almost a year isn't helpful. Looking at Icewhiz's more recent edits, he seems to have been actively participating in TP discussions working with other editors in a level-headed manner. If there is a disagreement to the point a RfC/RSN/etc. is needed, then those would be more apt venues to explore. Other than that, I don't see a violation here by Icewhiz. Stefka Bulgaria (talk) 20:37, 9 April 2019 (UTC)
Statement by Zero0000
Icewhiz is an intelligent and knowledgeable person who could easily be one of our best editors. Alas, he doesn't want to be. His transparent purpose in the I/P area is to defend the good name of Israel by means of endless pov-pushing combined with endless tendentious argument. My honest opinion is that Icewhiz is one of the worst editors to have ever appeared in the I/P area of the project.
I don't blame casual observers like Stefka for not seeing the problem at a glance. It takes longer experience to learn that nothing Icewhiz writes can be accepted without checking, and that "discussion" for him means writing anything, anything, that supports his pov.
Nableezy restricted himself to self-contradictions. I won't. Here Icewhiz argues that an anonymous blacklist is a reliable source, and follows up with "McCarthyite" does not mean inaccurate.. He is way too experienced to actually believe that, but the blacklist fits Icewhiz's personal pov. Here he quotes from a Hebrew court ruling without telling us that the very next sentences give contrary context. (Basically, the ruling said that the charges were very serious but the evidence for them was insufficiently compelling; Icewhiz brought just the first part.) These examples are not aberrations but just Icewhiz being Icewhiz.
Many of Icewhiz's talk page contributions can reasonably be called trolling. Nableezy's first case provides an example. Here he brings a dictionary definition of "doctored" to argue that a video which had purposefully been cut in order to change its meaning had not been doctored, even though the dictionary definition fits perfectly. I do not believe this was an argument in good faith; rather, Icewhiz' pov was in danger and he had to write something. Such lack of integrity is why the project would be better off without him. Zerotalk 03:33, 10 April 2019 (UTC)
To Calthinus: "Tendentiously cutting" is a form of doctoring. But that is not the point, since nobody ever tried to put the word "doctored" into the article. Icewhiz didn't want the article to mention the fact that the Israeli army had cut the end off a recording in order to smear (per several reliable sources) a medico they had just killed in cold blood. Since it is impossible to argue for such censorship on a policy basis, Icewhiz chose instead to sideline the discussion by bringing a dictionary definition for a word used only on the talk page. Zerotalk 07:47, 10 April 2019 (UTC)
- And Icewhiz is still at it (above). The real issue was inclusion of the well-sourced fact that the video had been altered to change its impact and thereby smear its subject. Icewhiz didn't like that idea. The precise word to be used for the video manipulation was a side-show that Icewhiz used to deflect attention from the real issue. Even if he had to bring a dictionary definition that proves himself wrong. Zerotalk 14:38, 10 April 2019 (UTC)
It's true that I discussed this case with Nableezy before it was opened, though he didn't (I think) follow any of my suggestions. We discussed it quite openly (not a single email) and if there is any rule against that I'd like to hear about it. This problem has been brewing a long time and I've often wished I had the time and stamina to open such a case myself. Zerotalk 15:14, 10 April 2019 (UTC)
Statement by Calthinus
If I had to sum up a number of things I despise about wiki, this would be a poster case ... alas this hairball could never be condensed to fit on a poster, not least because half of the crap involved is essentially fluff that is likely totally inscrutable to anyone not balls deep in Israel-Palestine wiki bloodletting. Alas, if they were, they couldn't possibly be impartial. Here's one of many points that I think illustrate the issue here - the statement by Zero above. It takes totally out of context an argument about semantics (in this case, the word "doctored" -- indeed something can be "tendentiously cut" and not be doctored -- as the NYTimes perhaps more correctly put it [[32]]) and tries to turn it into some case of "trolling". But most people in good faith would see a simple disagreement... unless they already hated one side's guts. Zero admits Icewhiz "could easily be one of our best editors" -- well the one thing I agree on is that his life on wiki might be more enjoyable if he didn't feel he had to constantly deal with ARBPIA matters, but that is his choice. As much as I hate to say it, what Zero sees as Icewhiz being some sort of manipulative, tendentious editor who the project would be better without (even though he "could be" one of the best if he "wanted to" -- very odd thing to say if you're also saying we should get rid of him), I think most observers would simply see a guy who is trying to stand up for what he believes in, and simply has a disagreement with someone who doesn't seem to be properly differentiating misalignment of opinions with lack of good faith.--Calthinus (talk) 06:33, 10 April 2019 (UTC)
Statement by Levivich
I respectfully request the 500 word limit be enforced, as well as some reasonable measure of staleness (June 2018? Seriously?). Excessively long submissions prevent other editors (including admin) from participating, are unfair to the editor being reported, and to every other editor who has ever worked hard to reduce their AE posting down to 500 words. These standards should be applied equally to all editors. Thank you. Leviv ich 14:11, 10 April 2019 (UTC)
- Is it normal at AE for an editor to help another editor gather diffs in preparation of an AE report, and then comment on the report without disclosing that they helped prepare it? Leviv ich 15:02, 10 April 2019 (UTC)
Result concerning Icewhiz
- This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
- The first diff is from June 2018. I stopped reading there. Please date all diffs as per the template so we can see what's stale and what's not. Sandstein 18:02, 9 April 2019 (UTC)
- In my view, this request is unsuited to AE. If an issue can't be summarized in 500 words, that's an indication that it's more suited to a full case request, not a quick response by an individual admin. And as to the subject matter, AE is fine for dealing with obvious cases of tendentious editing, such as throwing ethnic slurs around. But here, making a determination of tendentious editing would likely require a hour or more of detailed study of numerous complicated content issues and the underlying sources, while distinguishing genuine conduct problems from good-faith content disputes, which is very difficult in this kind of case. Speaking only for myself, particularly as somebody uninterested in this topic area, this is not something I see myself doing in my spare time. This does not preclude others who think that this can be resolved more straightforwardly from taking whatever action they consider appropriate. Sandstein 19:50, 9 April 2019 (UTC)
- I don't think ARBCOM would look kindly on a request at this stage. More generally, new editors keep cropping up in troublesome areas; if we kicked any difficult case to ARBCOM, they would be snowed under very quickly. I haven't looked through all of the diffs here, just the first four bullet points. They are somewhat concerning. While they are quite old, nothing formally prevents us from applying discretionary sanctions for old behavior. The question really is what Icewhiz has to say about those diffs now. Icewhiz, I for one would like to hear a response to Nableezy's first four bullet points. Vanamonde (Talk) 21:12, 9 April 2019 (UTC)
- There's a specific point in your reply I'm none too happy about, Icewhiz. The general prohibition is all very well, but enforcing it to revert the removal of POV language is questionable. I'm not suggesting sanctions in that respect; it's a mistake several people have made, including myself. But it is a mistake. If you think the IP's edits were correct on the substance, the thing to do is to revert it and then perform the same edit yourself (this is also broadly true for dealing with the edits of socks that have made constructive edits). If you still think the IP's edits were wrong, we have a problem. I don't particularly care how that shooting was described, so long as the description was in line with RS. If you want to change it, you need sources supporting the change. Reverting in text that is not explicitly supported by the sources is a problem, especially in a topic such as this; and this is a problem with that edit of yours that you are not acknowledging in its entirety. Vanamonde (Talk) 22:15, 9 April 2019 (UTC)