Jump to content

Wikipedia:Arbitration/Requests/Clarification and Amendment

Add links
From Wikipedia, the free encyclopedia
< Wikipedia:Arbitration | Requests

This is an old revision of this page, as edited by L235 (talk | contribs) at 00:16, 19 April 2019 (→Motion: Amendment to the standard provision for appeals and modifications: enact). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Shortcut
Arbitration Committee proceedings
Request name Motions Initiated Votes
Covert canvassing and proxying in the Israel-Arab conflict topic area   6 November 2024 0/3/0
[edit]
Open cases
Case name Links Evidence due Prop. Dec. due
Backlash to diversity and inclusion (t) (ev / t) (ws / t) (pd / t) 10 Oct 2024 24 Oct 2024
[edit]
Recently closed cases (Past cases)

No cases have recently been closed (view all closed cases).

Request name Motions  Case Posted
Clarification request: Gun control Motion (orig. case) 25 February 2019
Amendment request: Eastern Europe none (orig. case) 16 April 2019

No arbitrator motions are currently open.

Requests for clarification and amendment

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

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

Submitting a request: (you must use this format!)

  1. Choose one of the following options and open the page in a new tab or window:
  2. Save your request and check that it looks how you think it should and says what you intended.
  3. If your request will affect or involve other users (including any users you have named as parties), you must notify these editors of your submission; you can use {{subst:Arbitration CA notice|SECTIONTITLE}} to do this.
  4. Add the diffs of the talk page notifications under the applicable header of the request.
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129

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

Guidance on participation and word limits

Unlike many venues on Wikipedia, ArbCom imposes word limits. Please observe the below notes on complying with word limits.

  • Motivation. Word limits are imposed to promote clarity and focus on the issues at hand and to ensure that arbitrators are able to fully take in submissions. Arbitrators must read a large volume of information across many matters in the course of their service on the Committee, so submissions that exceed word limits may be disregarded. For the sake of fairness and to discourage gamesmanship (i.e., to disincentivize "asking forgiveness rather than permission"), word limits are actively enforced.
  • In general. Most submissions to the Arbitration Committee (including statements in arbitration case requests and ARCAs and evidence submissions in arbitration cases) are limited to 500 words, plus 50 diffs. During the evidence phase of an accepted case, named parties are granted an automatic extension to 1000 words plus 100 diffs.
  • Sectioned discussion. To facilitate review by arbitrators, you should edit only in your own section. Address your submission to arbitrators, not to other participants. If you wish to rebut, clarify, or otherwise refer to another submission for the benefit of arbitrators, you may do so within your own section. (More information.)
  • Requesting an extension. You may request a word limit extension in your submission itself (using the {{@ArbComClerks}} template) or by emailing clerks-l@lists.wikimedia.org. In your request, you should briefly (in 1-2 sentences) include (a) why you need additional words and (b) a broad outline of what you hope to discuss in your extended submission. The Committee endeavors to act upon extension requests promptly and aims to offer flexibility where warranted.
    • Members of the Committee may also grant extensions when they ask direct questions to facilitate answers to those questions.
  • Refactoring statements. You should write carefully and concisely from the start. It is impermissible to rewrite a statement to shorten it after a significant amount of time has passed or after anyone has responded to it (see Wikipedia:Talk page guidelines § Editing own comments), so it is often advisable to submit a brief initial statement to leave room to respond to other users if the need arises.
  • Sign submissions. In order for arbitrators and other participants to understand the order of submissions, sign your submission and each addition (using ~~~~).
  • Word limit violations. Submissions that exceed the word limit will generally be "hatted" (collapsed), and arbitrators may opt not to consider them.
  • Counting words. Words are counted on the rendered text (not wikitext) of the statement (i.e., the number of words that you would see by copy-pasting the page section containing your statement into a text editor or word count tool). This internal gadget may also be helpful.
  • Sanctions. Please note that members and clerks of the Committee may impose appropriate sanctions when necessary to promote the effective functioning of the arbitration process.

General guidance

  • Arbitrators and clerks may summarily remove or refactor discussion without comment.
  • Requests from blocked or banned users should be made by e-mail directly to the Arbitration Committee.
  • Only arbitrators and clerks may remove requests from this page. Do not remove a request or any statements or comments unless you are in either of these groups.
  • Archived clarification and amendment requests are logged at Wikipedia:Arbitration/Index/Clarification and Amendment requests. Numerous legacy and current shortcuts can be used to more quickly reach this page:
Shortcuts:
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129

Clarification request: Gun control

Initiated by GoldenRing at 15:38, 25 February 2019 (UTC)[reply]

Case or decision affected
Gun control arbitration case (t) (ev / t) (w / t) (pd / t)

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

Confirmation that all parties are aware of the request

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:

  1. Is deletion of a page an enforcement action that is authorised under discretionary sanctions?
  2. If the answer to 1 is "yes", was Bishonen's undeletion a violation of WP:AC/DS#sanctions.modify?
  3. If the answer to 1 is "yes", is DRV a valid venue to review deletions carried out under discretionary sanctions?
  4. 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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @BU Rob13: That is a good point and I will strike my fourth question. GoldenRing (talk) 17:07, 26 February 2019 (UTC)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]
  • @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)[reply]

Statement by Dlthewave

I've abstained from comment here because I don't feel that I have any strong insight or opinion regarding the intricacies of Arbcom procedures, and I'm not going to push for an outcome that affects the entire community just so that I can keep my userpage. However, I feel that the Committee would be remiss if they did not answer the first of Goldenring's questions, "Is deletion of a page an enforcement action that is authorised under discretionary sanctions?" –dlthewave ☎ 18:46, 15 April 2019 (UTC)[reply]

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).[reply]

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)[reply]

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)[reply]

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)[reply]
  • 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)[reply]
@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)[reply]
  • 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)[reply]
@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)[reply]

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)[reply]

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)[reply]

  • @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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]
  • @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)[reply]
  • Arbitrators, you're in the process of reaching a bad decision here, and it's worrying that you're reaching it with such glacial slowness. I think you're already overworked and you don't have the attention to spare on reviewing AE decisions in a timely way. Nobody has ever produced an example of a deletion that should properly be reviewed at AE; and we already have a prompt, effective, low-drama and trouble-free way of reviewing deletions at DRV; so it would be appropriate for you to make a decision explicitly pointing all deletions to DRV. You can do so with every confidence that DRV will call on you if you're needed.—S Marshall T/C 18:14, 15 April 2019 (UTC)[reply]

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)[reply]
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)[reply]
"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)[reply]
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)[reply]
(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)[reply]
(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)[reply]
(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)[reply]
--SmokeyJoe (talk) 07:26, 15 March 2019 (UTC)[reply]
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)[reply]
Arbs creating a motion creating a gag order on *discussing* a problem with ArbCom overreach in a process created by arbs? —SmokeyJoe (talk) 21:52, 13 April 2019 (UTC)[reply]
--SmokeyJoe (talk) 04:59, 17 April 2019 (UTC)[reply]
I would suggest:

All queries or appeals regarding arbitration enforcement, including those felt alleged to be out of process or against existing policy, must first follow arbitration enforcement procedures to establish if such enforcement is inappropriate before being reversed or discussed at another venue.

* This isn't about feelings.
* There is no need to address nonexisting policy.
* At the DRV, the alleged against policy deletion has been thoroughly discussed by the community. Has anything been wrong with that. The DRV closer is waiting for the ArbCom procedure (here) before reversing. That is consistent with your motion.
* Gagging project-relevant discussion anywhere, whether User_talk, or a formal DRV discussion, is not acceptable.
* There is an interesting pretense that the temp-undelete is not really a reversal. I think that should be considered acceptable. Temp-undeleted blanked pages are not allowed to be edited or copied. Denial of longstanding temp-undeletion practice will me DRV goes back to the practice of referring to off-site cache copies, which is not desirable.
* The venue of reversal is unimportant redundant wordiness and is not concise.
--SmokeyJoe (talk) 06:34, 17 April 2019 (UTC)[reply]

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)[reply]

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)[reply]
@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)[reply]

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)[reply]

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)[reply]
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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

@RoySmith: re Special:Diff/891855139: Agree that resolution would be nice. The rest is a nonissue: you should be looking at the content and logs of pages you restore anyway, even temporarily. If it contains blatant attacks or copyvios, or it's labeled as a copyvio or an "arbitration enforcement" variant ("AE" or "discretionary sanctions" or "DS" or "AC/DS"), you don't just restore it on your own initiative even if you think the labeling's incorrect, you consult with the deleting admin. If the deletion isn't labeled as arbitration enforcement, then it's not a valid enforcement action, per WP:AC/DS#sanctions.log. —Cryptic 16:13, 11 April 2019 (UTC)[reply]

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)[reply]

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)[reply]

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)[reply]
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)[reply]
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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]
alas, my autocorrect was right and you are going to give super Mario precedence. Bearing in mind that a higher level of consensus is required to overturn an ae action than a normal deletion you really are giving outlier admins carte blanch to do what the hell they like and stick two fingers up to consensus. Can you clarify if deletion decisions can be appealed here if AE choses not to overturn super mario? Spartaz Humbug! 20:38, 17 April 2019 (UTC)[reply]

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)[reply]


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)[reply]

@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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

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)[reply]

@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)[reply]

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)[reply]

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)[reply]

Unclosed, following objections from Goldenring--Ymblanter (talk) 10:54, 15 April 2019 (UTC)[reply]

Statement by Nosebagbear

@SilkTork: - I was hoping you (as the tweaking arb) could clarify how this is going to avoid looping round to the same problem - if it goes to AE, which would probably rule to adopt the broader interpretation of its own authority, then we seem set to end right back up again here as the "losing" side appeals the decision. The "appropriate forum" is only a symptomatic consideration since it would never be considered for DRV if arbitrary sanctions didn't/doesn't include deleting pages. Nosebagbear (talk) 20:29, 16 April 2019 (UTC)[reply]

Statement by Mojoworker

If the final motion passes (as it appears it will), you may also want to clarify WP:Arbitration Committee/Procedures#Standard provision: appeals and modifications. Will an undeletion request be considered to be the same as a request for modification of page restrictions and so may be made by any editor? Otherwise, "(a)ppeals may be made only by the editor under sanction", and for a page deletion, the deletion could affect many editors (an ESSAY for example). Perhaps explicitly change it to something like "Requests to undelete pages or for modification of page restrictions may be made by any editor." But does that really belong in a section titled "Appeals by sanctioned editors", when that's not necessarily who will be appealing? Mojoworker (talk) 19:12, 17 April 2019 (UTC)[reply]

I note that Premeditated Chaos may be concerned (and rightly concerned in my view) that this wording would make explicit that deletion is a valid AE action, which it appears is what you're trying to avoid with your final motion. And perhaps it's making policy on content as well. But I'm glad i don't have to figure it out – I guess that's why y'all get paid the big bucks. Mojoworker (talk) 19:36, 17 April 2019 (UTC)[reply]

Statement by 2A0C:E300:0:0:0:0:0:23

Most editors are loathe to read anything related to guns on Wikipedia, let alone comment. This issue is much broader than any disputed area. If this request were entitled for example "Authorize page deletion as a discretionary sanction" or some such, the feedback our arbiters would be receiving from our community would be very different. 2A0C:E300:0:0:0:0:0:23 (talk) 20:22, 17 April 2019 (UTC)[reply]

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).

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)[reply]
  • @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)[reply]
  • @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)[reply]
  • 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)[reply]
  • 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)[reply]
  • 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)[reply]
  • 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)[reply]
  • 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)[reply]
    • 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)[reply]
    • @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)[reply]
      • @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)[reply]
    • @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)[reply]
  • 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)[reply]
  • 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)[reply]
  • 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)[reply]
    • @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)[reply]
  • 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)[reply]

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

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)[reply]
I think that would be useful. Would you be able to do that Rob? SilkTork (talk) 11:41, 12 March 2019 (UTC)[reply]
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)[reply]
  • 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)[reply]
    • @Joe Roe: I view acceptable DS deletions as falling into the category of "removal of content pages 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)[reply]
      • 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)[reply]
    • 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.
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)[reply]
  • @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)[reply]
    • @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)[reply]
      • @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)[reply]
  • 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)[reply]
  • 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)[reply]

Motion: Discretionary sanctions procedure

For this motion there are 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

(1) Proposed:

The Discretionary sanctions Procedure § Sanctions is amended at sanctions.caveats to read as follows:

For the avoidance of doubt, enforcing administrators are not authorised to issue site bans; to require the removal of user rights that cannot be granted by an administrator or to restrict their usage; to delete pages; nor to enforce discretionary sanctions beyond their reasonable scope.

where the text underlined is to be inserted.

Support
  1. 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)[reply]
  2. 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)[reply]
  3. Support as written. ♠PMC♠ (talk) 15:04, 24 March 2019 (UTC)][reply]
  4. Support, with Joe's amendment. RickinBaltimore (talk) 18:43, 24 March 2019 (UTC)[reply]
Oppose
  1. 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) Moved back to oppose in favour of new motion regarding challenging enforcement actions. SilkTork (talk) 02:44, 13 April 2019 (UTC)[reply]
  2. Moving here, in favor of the second version. ~ Rob13Talk 13:31, 25 March 2019 (UTC)[reply]
  3. 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)[reply]
  4. Per OR. Katietalk 15:42, 3 April 2019 (UTC)[reply]
  5. Per Opabinia. I don't see this as needing a hard-line rule to forbid all deletions under AE ever, although I agree that in this case it was not necessary. GorillaWarfare (talk) 03:26, 12 April 2019 (UTC)[reply]
  6. Per OR WormTT(talk) 09:12, 15 April 2019 (UTC)[reply]
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)[reply]
SilkTork (talk) 14:40, 9 April 2019 (UTC) Moved back to oppose. SilkTork (talk) 02:44, 13 April 2019 (UTC)[reply]
Comments by arbitrators

Motion: Discretionary sanctions procedure (2)

For this motion there are 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

(1) Proposed:

The Discretionary sanctions Procedure § Sanctions is amended at sanctions.caveats to read as follows:

For the avoidance of doubt, enforcing administrators are not authorised to issue site bans; to require the removal of user rights that cannot be granted by an administrator or to restrict their usage; to delete pages outside of the deletion policy; nor to enforce discretionary sanctions beyond their reasonable scope.

where the text underlined is to be inserted.

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) Moving to abstain to move this forward. SilkTork (talk) 01:58, 13 April 2019 (UTC)[reply]
  1. Support as first choice, as this is the amendment Joe mentioned above. RickinBaltimore (talk) 12:19, 25 March 2019 (UTC)[reply]
  2. ~ Rob13Talk 13:30, 25 March 2019 (UTC)[reply]
  3. Support as second choice. – Joe (talk) 06:18, 31 March 2019 (UTC)[reply]
Oppose
  1. 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)[reply]
  2. 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)[reply]
  3. See my comment above. Opabinia regalis (talk) 06:52, 1 April 2019 (UTC)[reply]
  4. Per OR. I can't get behind making policy like this based on one instance of hundreds. Katietalk 15:44, 3 April 2019 (UTC)[reply]
  5. Per my comment above, but also because I don't see why it couldn't go through the standard deletion process. Page deletions are not normally something that are useful when discretionary sanctions are involved. GorillaWarfare (talk) 03:27, 12 April 2019 (UTC)[reply]
  6. Moved to oppose in favour of new motion on challenging enforcement actions. SilkTork (talk) 02:45, 13 April 2019 (UTC)[reply]
Abstain
  1. SilkTork (talk) 01:58, 13 April 2019 (UTC)[reply]
Comments by arbitrators

Motion: Amendment to the standard provision for appeals and modifications

For this motion there are 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

The following text is added to the "Important notes" section of the standard provision on appeals and modifications, replacing the current text of the fourth note:

All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.
Enacted: Kevin (aka L235 · t · c) 00:16, 19 April 2019 (UTC)[reply]
Support
  1. I think this is the essential point of concern, and would cover any future actions where people are unsure if an enforcement action is appropriate or not. Querying an action, such as deleting a page, is entirely appropriate, but to avoid confusion and internal conflict, we need to establish exactly where such a query should take place, and that the action should not be undone until it is established that it was in fact out of process. SilkTork (talk) 02:39, 13 April 2019 (UTC)[reply]
  2. This is what important note 4 is intended to say, but your text is much clearer, SilkTork. Do you mind if we rework this to just replace important note 4 with this text? ~ Rob13Talk 14:36, 13 April 2019 (UTC)[reply]
  3. We always can revisit this issue if there are still practical problems where deletion and arb enforcement meet. AGK ■ 14:42, 13 April 2019 (UTC)[reply]
  4. I've deleted "such as DRV" because it could be taken as implying that deletion is a valid AE action (which we couldn't agree on above); I don't think the example is essential to the meaning. Otherwise, I agree this is a sensible procedure and, had it been followed in this case, we might not have ended up with such a lengthy dispute. – Joe (talk) 16:15, 13 April 2019 (UTC)[reply]
  5. RickinBaltimore (talk) 20:04, 14 April 2019 (UTC)[reply]
  6. GorillaWarfare (talk) 20:42, 14 April 2019 (UTC)[reply]
  7. Looks good to me WormTT(talk) 09:14, 15 April 2019 (UTC)[reply]
  8. I don't disagree with this, but for the record I don't like that we haven't come to a conclusion on AE deletion, and I suspect the issue will return. ♠PMC♠ (talk) 14:49, 17 April 2019 (UTC)[reply]
  9. Katietalk 15:38, 17 April 2019 (UTC)[reply]
Oppose
Abstain
Comments by arbitrators
  • User:SmokeyJoe. Yes, I understand the concern regarding slow moving Committee decisions; however, the process for challenging an Arbitration Enforcement, if no satisfaction can be gained from the enforcing admin, is generally to raise the issue at "AE", though "AN" may also be used. And those processes are generally about the same speed as DRV. And the motion does allow for further discussion at a venue such as DRV if the outcome of the initial discussion at AE is that the enforcement was not appropriate, but has not yet been reversed. The idea is to prevent the situation we are currently in, in which there is some doubt as to where an action should first be discussed. Also, in order to preserve the special status of the Arbitration Committee (that decisions are final and binding), this underlines that the principle is to ask questions and wait for a decision before reversing an AE action. SilkTork (talk) 09:21, 13 April 2019 (UTC)[reply]
BU Rob13 - yes, tweak away. I am firmly in favour of collaboration. SilkTork (talk) 15:05, 13 April 2019 (UTC)[reply]
I've added "formally" before "discussed". We don't wish to gag informal discussion, but what we want to avoid is having two formal discussions happening side by side which is both redundant effort and may lead to internal conflict if the venues arrive at different conclusions. SilkTork (talk) 09:54, 17 April 2019 (UTC)[reply]
Fine by me. – Joe (talk) 11:27, 17 April 2019 (UTC)[reply]
That works for me. RickinBaltimore (talk) 11:39, 17 April 2019 (UTC)[reply]
Thanks for the ping, looks fine. GorillaWarfare (talk) 14:19, 17 April 2019 (UTC)[reply]
I'm good with "formally discussed". ~ Rob13Talk 17:22, 17 April 2019 (UTC)[reply]

Amendment request: Eastern Europe

Initiated by Icewhiz at 10:13, 16 April 2019 (UTC)[reply]

Case or decision affected
Eastern Europe arbitration case (t) (ev / t) (w / t) (pd / t)
Clauses to which an amendment is requested
  1. Wikipedia:Requests for arbitration/Eastern Europe#Amendments
  2. Wikipedia:Requests for arbitration/Eastern Europe#Amendments
  3. Wikipedia:Requests for arbitration/Eastern Europe#Amendments
List of any users involved or directly affected, and confirmation that all are aware of the request



Information about amendment request
  • sourcing restriction for non-English sources for Jew-Polish relations.
  • 500/30 protection for Jew-Polish relations.
  • 1RR for Jew-Polish relations.

Statement by Icewhiz

In the past year, editing in the topic of Jewish history in Poland has been difficult. While WP:NOENG is policy - stating a preference for English sources of the same quality when available (generally the case for Holocaust history), and quotation requirements when challenged - NOENG has not been followed in this topic area. Non-English sources of a dubious nature have been inserted into articles, even BLPs, and in some cases, the content has failed verification: not present in the cited sources, contradicted by others. Requests for quotations and a rationale for use have gone unanswered, or dismissed with "the source is reliable" or "WP:AGF and Offline sources".

Admins at AE are reluctant to dive into such issues. This recent case was closed by @Sandstein: with: "Personally, the matter is too complicated and too much tied to content disputes for me to feel comfortable taking action; AE is better suited to relatively straightforward cases of misconduct." [3]. I understand the sentiment here; dealing with users introducing content that fails WP:V when the cited sources aren't online, aren't in English, and/or are very long is difficult. The challenge of tackling source misrepresentations is evident in past AE threads:

List of prior AE actions
  1. GizzyCatBella 26 April 2018 - 1RR violation of page level restriction + claims of fringe sources. Result (purely on the 1RR claim) - "GizzyCatBella blocked 72 hours".
  2. E-960, 8 May 2018 - Complaint alleged violation of 1RR article restriction, coupled with BLP and RS concerns. Closed with a voluntary 72 hour restriction. Note admin discussion on non-English sources without translations.
  3. Icewhiz 9 May 2018 - Complaint alleged removal of Chodakiewicz as a source in a number of articles was inappropriate. Defendant counter-complained about filer's use of WP:SPSes. closed: "Editors directed to WP:RSN to discuss Chodakiewicz....
  4. E-960 12 May 2018 - Complaint alleged violation of 1RR in article with said restriction. Result: "E-960 needs to be more careful when reverting.".
  5. Icewhiz 14 May 2018 - Complaint alleged removal of Anna Poray as a source from over 60 articles was inappropriate as well as alleging Wikipedia:Articles for deletion/Anna Poray was made in bad faith. While admins discuss the misuse of SPS angle, the closing admin remarks "The charge of misusing SPS isn't something I'd act on, because it's close to a content dispute and it's not realistic to expect admins here to check the reliability of this number of sources; that would need an ArbCom case.". Closed due to the reported PAs as "Poeticbent (talk · contribs) is topic-banned from the history of Poland during World War II, including the Holocaust in Poland, for six months.".
  6. François Robere 2 June 2018 - complaint alleged violation of "consensus required provision". Discussion diverged into use of questionable sources. Admins discuss at length possible sourcing restrictions (WP:MEDRS-like, plus suggestion to limit sources only to English, as "To be clear, I don't think that Polish-language sources are inherently unreliable, but they can't be evaluated by most admins here, including me. That impedes arbitration enforcement insofar as source reliability is concerned.". The AE closes with "More editing restrictions on the article applied.". The following restriction is placed on an article level: diff "Only high quality sources may be used, specifically peer-reviewed scholarly journals and academically focused books by reputable publishers. English-language sources are preferred over non-English ones when available and of equal quality and relevance." + "Anyone found to be misrepresenting a source, either in the article or on the talk page, will be subject to escalating topic bans.
  7. 24 June 2018 - Filer alleged misrepresentation of sources. In this particular instance this was seen as beyond a "content dispute". Closed as "GizzyCatBella is topic-banned from the World War II history of Poland".
  8. Icewhiz 3 July 2018 - Filer alleged misrepresentation of sources. Respondent files diffs alleging a misrepresentation in other instances. Closed as "no action" since - "It's quite clear that admins here will not examine the details and nuances of the interpretation of sources in what is, to most, a foreign language and a wholly unfamiliar topic. AE is good at dealing with reasonably obvious misconduct, but not so good at dealing with issues that need an advanced degree in history or some other specialized field to resolve..
  9. Volunteer Marek 5 July 2018 - Filer alleged NPA and V issues, accompanied by counter-allegations. Admins discuss possible sourcing restrictions (e.g. academic, English only) to the topic area based on previous article level restriction to Collaboration in German-occupied Poland. NeilN notes - "That clause was a watered down version of Sandstein's suggestion to limit source-evaluation to English-language academic sources only. He correctly noted that most admins here can't read Polish when the issue of source misrepresentation comes up.". The discussion on sourcing leads to no conclusion. Closed with: "Volunteer Marek and Icewhiz are topic-banned from the history of Poland in World War II (1933-45) for three months for treating Wikipedia as a WP:BATTLEGROUND".

Most of the complaints were on sourcing quality and misrepresentations of sources, while editors were sanctioned for a variety of conduct issues, such as personal attacks and battleground behavior. Admins discussed the possibility of sourcing restrictions (academic and/or English only), or enforcing misrepresentation of sources. A sourcing restriction was applied to Collaboration in German-occupied Poland where the situation did improve following the restriction, but no sourcing restriction was applied elsewhere. Disputes in the topic area have involved numerous other articles (WWII history, geographic locations, BLPs in the field).

I will note that use of sources is further complicated by the legislation which criminalized publication in Polish media of claims of Polish complicity in crimes committed during the Holocaust.[1][2][3]

There are excellent mainstream Polish-language academic sources, referenced by academia outside of Poland. In fact, the Polish Wikipedia often has a balanced representation of the subject matter (see this 2015 oped on a long-running WP:HOAX in Stawiski: "Surprisingly, the Polish Wikipedia articles evidence greater willingness to admit Polish participation in massacres of Jews." corrected in 2018) Unfortunately, sources in Polish introduced to English Wikipedia are often not high-quality mainstream academic writing, but rather right-wing newspaper op-eds, interviews, blog posts, and pulp journals/books.

Please see general examples of misrepresenting sources: (more are available on request)

Diffs of source use failing verification + subsequent reverts / lack of quotations and discussion
  1. Non-EC user added [4] (discussed at AE here, but not subsequent reverts/verification). Challenged as "OR, misrepresentation of sources[5]. Despite the challenge - reverted and reverted by established users. Requests at Talk:History of the Jews in Poland#Recent edits for verifying quotations were not met (over several weeks). I personally accessed many of the cited sources and ascertained the content was not present in the source prior to reverting (a difficult and time-consuming task). The reverting users admitted they did not verify the text - here and here.
  2. diff - removal of Chełmno extermination camp's purpose to exterminate Poles. Sourced to Polish language source - which doesn't contain this claim. This misrepresentation was entered back in 2013. This illustrates how a false citation in non-English can last quite a while.
  3. Editor challenges REDFLAG material in July 2017,rolledback in Feb 2019. Source for "eventually both Poles and Jews were classified as subhuman and targeted for extermination..." is a municipal website in Polish - source which doesn't contain anything of the sort.
  4. challenge of text "systematically exterminated people (primarily Jews and ethnic Poles) they regarded Untermensch.". text returned with a whole bunch of Polish language sources (which do not seem to support the text (they do support persecution of Polish elites - not all Poles). tagged verify source. request on talk 4 March per WP:NOENG for rationale of use of these sources + quotations - no response as of now.

Possibly disruptive edits by non-EC users:

Edit Warring & non-EC edits
  1. Wikipedia:Sockpuppet investigations/Historyk IPN/Archive - editor from IPN (an organization promoting revisionism in Polish-Jewish relations,[4] that was recently involved in the disruption of an academic conference in Paris[5]) - socking and adding WP:SPAM links to a website promoting "the truth".
  2. Edit warring on BLP - despite clear lack of consensus for inclusion (and even possibly consensus to exclude) - [6] (and a number of threads below), multiple re-insertions of challenged text which is based on interviews/op-eds in right-wing Polish media - [7][8], [9], [10], [11], [12], [13], [14], [15], [16] (note the rejection of the Holocaust studies journal (including two pieces by Polish authors) as a source in preference to a right-wing internet portal, a small Polish radio station, Polish League Against Defamation, and biznesistyl.pl), [17], [18], [19], [20], [21].
  3. [22] - adding content sourced to TVNiezaleznaPolonia Canada YouTube channel. Source is an interview in Polish with English subtitles, and the content inserted is a denial (of the generally accepted) Polish role in Jedwabne pogrom.
  4. [23] - IP adds content to Jedwabne claiming this was "instigated by the Soviet-backed Communist security corps" (well after the Red Army retreated in disarray).
  5. [24][25][26] - non-EC adds content to two BLPs + 1 institutions based on media coverage of upcoming Gontarczyk column in wSieci (context on wSieci: [6]). Despite challenges by several users, this is re-inserted.
  6. Jan Grabowski (historian) - conspiracy theories (revdelled) at 21:35, 23 February 2019‎, 11:57, 25 February 2019‎ , 12:24, 25 February 2019‎.
  7. There is also long-term (in one article - over a year), slow-pace edit-warring by an IP on a number of articles - @Ymblanter: and @Drmies: were involved in Naliboki massacre and Polish Center for Holocaust Research recently (see also User talk:Icewhiz#Polish Center for Holocaust Research).
  8. EW report - 6 reverts in a short time span by an IP in the topic area (removing well sourced information), coupled with 3 reverts in the EW noticeboard. Per TU-nor possibly linked to the 64-bit IP described above, which seems plausible.

References

  1. ^ Poland Holocaust law: France criticises 'ill advised' text, BBC, 7 Feb 2018
  2. ^ Gebert, Konstanty. "Projecting Poland and its past: Poland wants you to talk about the “Polocaust”." Index on Censorship 47.1 (2018): 35-37.
  3. ^ Hackmann, Jörg. "Defending the “Good Name” of the Polish Nation: Politics of History as a Battlefield in Poland, 2015–18." Journal of Genocide Research 20.4 (2018): 587-606.
  4. ^ Ambrosewicz-Jacobs, Jolanta. "The uses and the abuses of education about the Holocaust in Poland after 1989." Holocaust Studies (2019): 1-22.
  5. ^ La Pologne minimise les incidents lors d’un colloque sur la Shoah à Paris, Le Monde, 4 March 2019
  6. ^ Polish magazine's 'Islamic rape of Europe' cover sparks outrage, Guardian, 18 Feb 2018

I request that ARCA consider the following:

  1. 500/30 protection for the topic of Polish-Jewish relations.
  2. 1RR for the topic of Polish-Jewish relations.
  3. A sourcing restriction. Some possibilities:
    1. Revert restriction - editors performing reverts of challenged material are responsible for verifying the contents. Failure to verify, and provide supporting quotes, is sanctionable.
    2. consensus for non-English sources: In disputes over foreign-language sources in the subject area of Polish-Jewish relations, disputed sources are removed unless and until there is a consensus to include them. (similar to WP:NOCONSENSUS EL policy).
    3. Only English-language academic sources for historical subjects.
    4. Excluding low-quality non-English sources - Blogs, websites, and media sources that are subject to censorship (e.g. see the WP:HISTRS proposal). High-quality English-language sources can be found in most topics.

Such sourcing restrictions will turn "content disputes" on foreign-language sources that are difficult for enforcing admins to verify themselves into actionable violations of a sourcing restriction. As copious and numerous English language sources are available in Holocaust studies, a restriction won't limit our source pool much; reputable non-English writers get translated to English or analyzed in English language secondary works. Consistent introduction of material that fails WP:V should be taken seriously, however expecting admins at AE to read 50 pages in a foreign language is not reasonable. Our goal should be that Wikipedia conforms to mainstream academic scholarship on the Holocaust, and I believe such measures would be a step forward. A limited measure in ARCA regarding sourcing (in line with AE admin comments over several cases) & non-EC edits might lead to fewer disruptions, an easier time at AE (fewer cases), and can be achieved without a full-fledged case.

Statement by Piotrus

Since 1) I've been quoted by Icewhiz (through not notified, I refer specifically to this diff), and 2) this does concern one of my primary content areas, as I've created dozens articles on Polish-Jewish topics, such as Maria Roszak just few days ago and 3) this contains the most absurd request I've seen in my ~15 years here ("sourcing restriction for non-English sources for Jew-Polish relations."), I feel I should make a statement.

First. Regarding the 1RR restriction request, the "500/30 protection" (what is this, btw? I've never heard such term used on Wikipedia before... it is a form of semi-protection) and others (request to verify sources before reverting, etc.), as someone who has seen various edit conflicts in related topic areas in dozen+ years, including some that ended up at ArbCom, it is my view that there's no significant amount of vandalism, or long term edit warring, or any other malpractices that would raise to the level requiring any special treatment for this topic area or even for any particular articles (one can check history of major articles like Polish Jews or The Holocaust in Poland or such to see they are generally stable). While it would be nice to force editors to use higher quality sources, there's no reason to treat Polish-Jewish topic area any different from the rest of Wikipedia. While there are occasional disagreements, they are not raising above the usual noise level in this area.

Second, it would be absurd to ban or restrict non-English sources. AFAIK this hasn't been done for any topic area, and rightly so, as for each language there are plenty of reliable sources. To say that Foo-language sources (or anything that's not in English) cannot be used for XYZ-topic is a very serious accusation for any scholarship. While there are some particular cases we limit sources, they are very rare - I think there's a general consensus to be careful with Nazi-era sources, for example, but even then, there's no blanket rule saying that no Nazi-era sources are allowed (through perhaps there should be, I can similarly think of issues with ISIS sources, etc. - but those are extreme cases and we are hardly anywhere near this level of seriousness here). Over the years I've cautioned some people to be careful with Soviet-era sources for some topics, or modern Putin-era Russian historiography, and I concur there are some indications some (but certainly not all!) modern Polish historiography works exhibits a worrisome political agenda not unlike that found in Putin's Russia, and it is good for editors to realize this, but overall, WP:RS covers such situations pretty well, and if needed WP:RSN can be brought to bear on specific cases (ex. see this RSN discussion Icehwiz started, which IIRC led to the decision to stop using Paul (an English-language source, btw) as a source in this topic area. It's a proof that current tools and structures work, no special treatment is needed. To ban (and remove?) Polish and other non-English sources from Polish-Jewish topics would do immense damage to the project. Many articles in categories such as Category:Polish Righteous Among the Nations or Category:Jewish ghettos in Nazi-occupied Poland are based on Polish-language sources that simply do not exist in English. To ban sources ranging from Polish Biographical Dictionary to works by scholars from the Jewish Historical Institute or works published by many other Polish-Jewish organizations in Poland would be, IMHO, ridiculous. (As for 'remove low quality sources' plea, of course I support it - but to repeat myself, that's just like saying 'please enforce existing policies like RS'. Doh. Sure. Let's. We all agree. In all content areas. Nothing for ArbCom do look at here).

Nonetheless, the fact that such ridiculous request has been made bears considering in light that Icewhiz has often criticized Polish-language sources (ex. just yesterday here, or few months ago numerous times here - just search for NOENG; it's pretty much all Icewhiz criticizing NOENG/Polish sources; same here). While his criticism has not always been without merit (as sometimes he correctly identified low-quality sources), I don't see any relation between low quality sources he (or others, including myself) identify, and language. Sometimes we find and remove low quality Polish sources, sometimes they are English, occasionally they are in another language altogether. Language is not an issue. The fact that one can seriously make such request (April Fools has come and gone...) makes me wonder about their judgement, since to effectively try to argue that all non-English sources should be treated as if they were Nazi-German era works (i.e. automatically disqualified on the subject matter of Jewish history/culture/etc.) is not a sign of a sound editorial judgement.

Bottom line, if an editor feels that he has lost too many arguments, he should not turn to WP:FORUMSHOPPING. And trying to do so here may result in rather heavy WP:BOOMERANG. Because while there is nothing particularly wrong with Polish-Jewish topics on English Wikipedia (they are reasonably stable and neutral), there is some evidence that some editors are developing WP:BATTLEGROUND-like mentality, evidenced for example by spurious AE and even ArbCom-level requests (see my related wiki-essay). And that may be something that ArbCom may want to investigate, because a number of meritless requests at AE/ArbCom boards is an indicator of a potential problem (one that could warrant for example a ban from submitting spurious requests of such kind in the future). --Piotr Konieczny aka Prokonsul Piotrus| reply here 03:18, 17 April 2019 (UTC)[reply]

Statement by Ealdgyth

Sourcing is bad on all sides in this area... these are just a few small examples I've run across ... I'm sure if I dug deeply, I'd be able to find plenty of others. Note that I've very carefully not pointed out who did these various problems - because that just feeds the battleground mentality.

It's not just the troubling/sloppy sourcing that's occurring (and these are likely the tip of the iceberg), it's the constant battleground mentality that affects most editors in this area. One person adds something that's sloppily sourced, the other side reverts and screams bloody murder on the talk page, but then that second side adds something else that's also sloppily sourced and then the first side starts screaming bloody murder. And everything is accompanied by endless reverts ... there is not any way for third party editors who aren't invested in the conflict to actually contribute for any length of time because it's just so dreadfully draining. 1RR doesn't seem to help, because there are multiple editors on each "side" so ... the reverts just roll in and people who aren't on a side just give up and walk away - I've done it often enough.

I don't know if there are any answers. On days when I'm terribly discouraged, I think banning everyone on both sides might help but...I'm afraid that won't solve the problems, which unfortunately are tied to academic and political debates that have become so contentious that they are spilling over into wikipedia.

Pinging SlimVirgin (talk · contribs) and K.e.coffman (talk · contribs), both of whom I've obliquely mentioned here. Ealdgyth - Talk 15:14, 17 April 2019 (UTC)[reply]

Statement by Nihil novi

The initiator of the present discussion writes that non-Polonophones may have difficulty verifying sources that are not in English. For this reason, where the original Polish texts have been provided, e.g. in the references, I have often translated them into English. I have also suggested that the original Polish texts routinely be so provided, and that I will be happy to render them into English. I stand by my suggestion and offer. Thank you. Nihil novi (talk) 20:53, 17 April 2019 (UTC)[reply]

Statement by Kurtis

@Piotrus: 500/30 (also known as extended-confirmed protection, or 30/500) is a special type of semi-protection that restricts accounts with less than 500 edits or have been registered for less than 30 days from editing certain pages. That is to say, an account that was registered 10 years ago but has only made 404 edits would be unable to edit a page under 500/30 protection, as would an account that has made thousands upon thousands of edits within 24 days of signing up. Both conditions must be met for an account to be granted extended-confirmed status, permitting them to edit a 500/30 protected article. Kurtis (talk) 21:39, 17 April 2019 (UTC)[reply]

Statement by François Robere

If the committee accepts this proposal now, it won't be a moment too soon. Throughout the discussions in this topic area we've seen (in no particular order) book summaries, liturgical press, Geocities-SPS, press releases, Ph.D students on popular websites, censorship based on supposed Communist background, independent authors, potentially antisemitic and pseudonymic authors, and more (other examples here: [27][28]). Piotrus is right in asserting that current policy was enough to resolve all of these problems, but WP:RS alone wasn't enough: we had RfCs on writers you never heard of, and days-long discussions on sources with less than 5 citations globally (which were introduced to the discussion as "notable", "important", or even "preeminant" historians). In several cases editors introduced what would later be deemed a non-RS to dozens of articles at the same time; in another, a plagiarising source was removed 8.5 years after it was discovered. However, he's wrong in suggesting this is "forum shopping" trying to rehash past disagreements - those we mostly managed, with much time and angst; rather, this is an attempt to prevent future ones by raising the bar on sourcing, so that we're left with actual content disputes rather than biography hunts and repeated translation requests.

Nihil novi has indeed made an effort translating and making sources accessible. It removed the language barrier, but did not solve three other problems: out of context quoting (where you'd need the whole page rather than 2-3 sentences); low-quality sources; inaccessible materials (low circulation, out of print etc. - often the result of low quality); and editors refusing to supply quotations or exact citations of their materials - all problems that would be resolved by this proposal.

Which leads me to a fact central to all of this: WWII is a major area of scholarship, and virtually all reputable sourced end up being published in English. Sources that don't are either undiscovered or disreputable; if they're undiscovered (old and forgotten, or new and yet to be translated), then it's not our job to introduce them into the mainstream (in some cases it could even constitute WP:OR); if they're disreputable, we shouldn't use them anyway. And so our choice here is essentially between stability and novelty: do we use the freshest materials, even those that are yet to be translated; or the stablest materials - those that have garnered the broadest attention and acceptance? In topic areas that are this prone to edit warring and disagreement, I'd argue for the stablest.

And one final note on admins: Among the host of... ineffective admins, Ealdgyth has been the only one willing to take this topic seriously and try to make sense of who's who and what's what; the only one to actually go through the sources and try to mediate compromise - or just enforce the rules - instead of waiting for things to repeatedly explode at ANI/AE. Otherwise the boards have been nearly useless, which shouldn't come as a surprise to anyone.[29][30] Whatever other decision you reach, you should pass this stern message to admins: an effective admin is one who gets involved and dives deep into the disagreements, not one who sits on the sidelines and only occasionally and selectively applies policy. An effective admin is not a policy-application machine, but a person who reasons with depth[31] and is willing to make sure things get done. If you're willing to invest yourself in being an effective admin, then by all means do so - you have the backing of the community. But if you don't, then stay away. François Robere (talk) 16:30, 18 April 2019 (UTC)[reply]

Statement by {other editors}

Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information.

Statement by Tatzref

This request is, in my view, misplaced. There is no justification for restricting discussion on historical subjects only to English-language academic sources or imposing a requirement of consensus with regard to non-English, specifically Polish language sources. This would simply erase or block important research by Polish historians that is not available in English or is not mentioned in English texts. A typical case in point is the following. Icewhiz erased the following text in its entirety from the article on History of the Jews in Poland (https://en.wikipedia.org/wiki/History_of_the_Jews_in_Poland), and replaced it with their own:

12:23, 12 March 2019‎ Icewhiz talk contribs‎ 219,143 bytes +1,651‎ →‎Situation of Holocaust survivors and their property: Remove content as it failed verification vs. the cited sources, misused a primary source, and was contradicted by available English RSes. Replace with content cited to academic English-language sources available online.)

A restitution law "On Abandoned Real Estates" of May 6, 1945 allowed property owners who had been dispossessed, or their relatives and heirs, whether residing in Poland or outside the country, to reclaim privately owned property under a simplified inheritance procedure. The law remained in effect until the end of 1948. An expedited court process, entailing minimal costs, was put in place to handle claims. Applications had to be examined within 21 days, and many claims were processed the day they were filed. Poles often served as witnesses to corroborate claims of Jewish neighbors and acquaintances. Jewish law firms and agencies outside Poland specialized in submitting applications on behalf of non-residents. Many properties were also transferred and sold by Jewish owners outside this process.[1] The American Jewish Year Book reported, at the time, “The return of Jewish property, if claimed by the owner or his descendant, and if not subject to state control, proceeded more or less smoothly.”[2] Thousands of properties were successfully reclaimed, for example, more than 520 properties were reclaimed in two county towns of Lublin province alone (281 applications in Zamość, and 240 in Włodawa - some applications involved multiple properties).[3]

All of this information is based on reliable sources produced by reputable, professional Polish historians (Alina Skibinska, Lukasz Krzyzanowski, Krzysztof Urbanski, Adam Kopciowski). Moreover, the information about postwar property restoration is based on primary research into hundreds of Polish court records for each town that is mentioned. Alina Skibinska states, in relation to Szczebrzeszyn, that at least one third of the 210 private properties belonging to Jews before the war were returned to their owners or their heirs by 1950, and that almost all of these properties were very quickly sold to Poles (Klucze o kasa, p. 562). She goes on to assess the workings of the local municipal court: the vast majority of claims were favorably dealt with; the pace at which this was done was very speedy, as many of the claims were allowed the day they were received or very soon after; the judges very often overlooked deficiencies in the applications (Klucze i kasa, p. 568-569).

The text that Icewhiz substituted uses publications of poor quality with no sources cited for the relevant claims (Laurence Weinbaum, The Plunder of Jewish Property during the Holocaust) or publications that do not refer to the research on court records but rather a few anecdotes and then make sweeping generalizations that the primary sources do not support (Cichopek-Gajraj, Beyond Violence; Michael Meng, Shattered Spaces). Moreover, the research into Polish court records fully accords with the monitoring that Jewish organizations were conducting at the time. The American Jewish Year Book, a highly reliable source authored by academics, reported in 1947-1948, that “The return of Jewish property, if claimed by the owner or his descendant, and if not subject to state control, proceeded more or less smoothly.” The postwar decrees in question were introduced for the benefit of the Jews, with a much simplified and cheaper process than the regular court inheritance procedures, which one could always resort to. Icewhiz simply wiped all this out as allegedly “failed verification vs. the cited sources, misused a primary source” because it doesn’t accord with what he thinks the historical record should be. This smacks of censorship and is a disastrous forecast for the state of such articles. Tatzref (talk) 22:34, 18 April 2019 (UTC)[reply]

Eastern Europe: Clerk notes

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

Eastern Europe: Arbitrator views and discussion

  • On the face of it, this seems more like a case request than something for ARCA. If it's too complex for AE, we would need the extended framework of a case to examine the totality of the evidence. I would likely vote to accept this as a case request, but I decline to consider extending 500/30 to an entire topic area in the absence of a case. ~ Rob13Talk 06:27, 17 April 2019 (UTC)[reply]
  • I'm absolutely against placing restrictions on sourcing. That's well into content territory, out of both ArbCom and AE's remit. The other sanctions are possible, but I agree with Rob: we would need a full case to examine this issue properly. – Joe (talk) 09:59, 18 April 2019 (UTC)[reply]
  1. ^ Jan Grabowski and Dariusz Libionka, eds. Klucze i kasa: O mieniu żydowskim w Polsce pod okupacją niemiecką i we wczesnych latach powojennych 1939–1950 (Warsaw: Stowarzyszenie Centrum Badań nad Zagładą 2014), 522–523, 529, 568–569, 575–607. Also Krzysztof Urbański. Kieleccy Żydzi (Kraków: Pracownia Konserwacji Zabytków w Kielcach and Małopolska Oficyna Wydawnicza, n.d. [1993]), 180–190; Marta Pawlina-Meducka, ed. Z kroniki utraconego sąsiedztwa: Kielce, wrzesień 2000/From the Chronicle of the Lost Neighborhood: Kielce, September 2000 (Kielce: Kieleckie Towarzystwo Naukowe, 2001), 202.
  2. ^ American Jewish Year Book, 5708 (1947–1948), vol. 49 (Philadelphia: The Jewish Publication Society of America, 1947), 390.
  3. ^ Adam Kopciowski. Zagłada Żydów w Zamościu (Lublin: Wydawnictwo Uniwersytetu Marii Curie-Skłodowskiej, 2005), 203; Adam Kopciowski, "Anti-Jewish Incidents in the Lublin Region in the Early Years after World War II," ≈Holocaust: Studies and Materials vol. 1 (2008), 188.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Arbitration/Requests/Clarification_and_Amendment&oldid=893098197"