Revision as of 04:39, 10 September 2020

• WP:ARCA

• recent changes
• purge this page
• view or discuss this template

Currently, there are no requests for arbitration.

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

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:
   • Click here to file a request for clarification of an arbitration decision or procedure.
   • Click here to file a request for amendment of an arbitration decision or procedure (including an arbitration enforcement action issued by an administrator, such as a contentious topics restriction).
   • Click here to file a referral from AE requesting enforcement of a decision.
   • Click here to file a referral from AE appealing an arbitration enforcement action.
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.

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 Misplaced Pages, 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-llists.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 Misplaced Pages: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 Misplaced Pages:Arbitration/Index/Clarification and Amendment requests. Numerous legacy and current shortcuts can be used to more quickly reach this page:

• WP:ARCA
• WP:ARA
• WP:A/R/C&A
• WP:A/R/CL
• WP:A/R/A
• WP:A/R/CA
• Misplaced Pages:Arbitration/Requests/Clarification and .../Amendment

Clarification request: Pseudoscience

Initiated by RexxS at 21:47, 19 August 2020 (UTC)

Case or decision affected

Pseudoscience 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:

• RexxS (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) (initiator)

Statement by RexxS

I apologise for making what appears to be a content-related request, but the behaviour of editors at Ayurveda and Talk:Ayurveda needs to be restrained, and a simple confirmation should be all that's needed to clarify the underlying issues.

Following a contentious edit war at Ayurveda and a WP:AE discussion, El C created an RfC at resolve the question of whether the phrase "pseudoscience" should be in the lead. The debate involved over 60 editors, was closed as no-consensus, reviewed, and re-opened for closure by an admin.

Many proponents of Ayurveda have taken the opportunity in that debate to argue that Ayurveda is not pseudoscientific and are attempting to have the phrase removed entirely. I believe that the position on Misplaced Pages is that Ayurveda is a pseudoscience as a matter of fact. I am therefore seeking a clear confirmation from ArbCom that the article is subject to discretionary sanctions as a pseudoscience (as even that fact has been contested). Having a clear statement of the position will enable a closer to accurately weigh the strengths of the arguments and to reject entirely arguments that clearly contradict Misplaced Pages policy on pseudoscience.

In the decision at WP:ARBPS#Generally considered pseudoscience, ArbCom asserted the principle

Theories which have a following, such as astrology, but which are generally considered pseudoscience by the scientific community may properly contain that information and may be categorized as pseudoscience.

I would like a clarification that the principle includes Ayurveda in the same way as astrology, and consequently that Ayurveda can be considered in the same light.

Thank you in advance for your assistance in this matter. --RexxS (talk) 21:47, 19 August 2020 (UTC)

@MrX: It is a truism that as far a WiIkipedia is concerned, Ayurveda is either a pseudoscience or it is not. If it is, then editors who breach WP:AC/DS requirements for behaviour can be sanctioned as an AE action. If it is not, then they cannot. You have earlier disputed that ArbCom has designated Ayurveda as a pseudoscience in Misplaced Pages's view, but that leads to an unsustainable situation. If your logic holds, any other editor can use your ipse dixit argument to claim that they cannot be sanctioned – simply by stating that Ayurveda is not a pseudoscience on the grounds that ArbCom has not explicitly said so. Any admin can take AE action against any editor breaching the expected standards of behaviour at Astrology; however the consequence, if your reasoning is accepted, is that anyone editing articles such as Ayurveda has a get-out-of-jail-free card by the simple expedient of denying that the topic is a pseudoscience.

We already have prior debate: RfC July 2015 and Talk:Ayurveda/Archive 13 #Pseudoscience concluding that Ayurveda is a pseudoscience, but that is insufficient, it appears, as editors are free to deny the fact as if it were not so.

Who then should be the authority that decides that question? At the very least, ArbCom needs to clarify that position. --RexxS (talk) 22:42, 20 August 2020 (UTC)

@Xeno: I'm not sure that ArbCom would be comfortable in addressing the second part of my request for clarification, although you were happy enough to do exactly that for Astrology, which is completely analogous to Ayurveda. The first part is naturally more important, particularly as we are currently under attack at the Talk:Ayurveda page from a concerted campaign, organised through Twitter to distort the consensus away from the recognised scientific viewpoint. An admin has felt it necessary to take the extraordinary step of semi-protecting the talk page temporarily, and I've been playing Whack-a-mole with about 30 newly registered meat/sock-puppets who have repeated the same disruptive edit requests. We need a lot more eyes on the disruption to that page, and it's possible that it is going to require another ArbCom case if the DS prove insufficient. Having a clear statement that Ayurveda is pseudoscience in the same way that Astrology is would go a long way to settling down the disruption there and establishing that Misplaced Pages's content cannot be held hostage by special interest groups. --RexxS (talk) 17:20, 26 August 2020 (UTC)

@Newyorkbrad and Katie: we already have had two RfCs confirming that the community regards Ayurveda as pseudoscience, as well as a catalogue of reliable sources stating the same. See  Talk:Ayurveda/Archive 12 #Category:Pseudoscience and Talk:Ayurveda/Archive 13 #Pseudoscience. This does not stop the talk page being flooded with SPAs to distort consensus and oppose the appellation. The serious discussions have been made and the consensus is long-standing, but that doesn't stop the disruption.

@DGG: see Misplaced Pages:Sockpuppet investigations/Anuram567. Your idea and mine of "a very small number of editors" differ quite dramatically. --RexxS (talk) 17:35, 26 August 2020 (UTC)

@Thryduulf: there is a community consensus that the topic is pseudoscience, but that hasn't stopped the disruption. What is needed is some backbone from ArbCom to make sure that there is not a shadow of doubt about the position of Ayurveda. I'm up to my armpits in alligators over at that article and its talk page and you and a few more admins need to get their backsides over there by the time that the semi-protection wears off the talk page (!) and the disruption starts up again. I'm sick of boatloads of editors with no more than half-a-dozen edits turning up and arguing black is white time and again. --RexxS (talk) 21:30, 26 August 2020 (UTC)

@DGG: The Ayurveda article has indeed recently been EC-protected. However, we're in the process of trying to decide issues by discussion on the talk page, but the recent disruption to the talk page has resulted in the talk page being semi-protected for two days. It is not a tenable situation to have talk pages protected, and I don't think you appreciate the degree of disruption we're having to deal with.

If the 2020 committee feels unable to affirm that Ayurveda is included in the principle "Theories which have a following, such as astrology, but which are generally considered pseudoscience by the scientific community may properly contain that information and may be categorized as pseudoscience." that the 2006 committee passed 8-0, then so be it: I won't take up any more of your time. --RexxS (talk) 17:16, 27 August 2020 (UTC)

Statement by Thryduulf (re Pseudoscience)

If the arbitrators feel that explicitly declaring this (or any) topic as pseudoscience would be a content decision, an alternative option would be to allow the discretionary sanctions to be applied to topics that are described as pseudoscience in independent reliable sources even if that status is disputed. In other words saying that the DS applies to subject areas that are or are called pseudoscience so that the application of DS itself does not require a determination of whether it is or is not pseudoscience and the application of DS does not mean that Misplaced Pages is necessarily calling something pseudoscience. Thryduulf (talk) 11:14, 20 August 2020 (UTC)

Re Shashank5988 I'd forgotten about that case, but discretionary sanctions are indeed authorised for "Complimentary and alternative medicine" and would seem to be a good fit. The Ayurveda article describes it as "an alternative medicine system" and a look at the current talk page suggests that this characterisation is not disputed. Thryduulf (talk) 13:09, 20 August 2020 (UTC)

@RexxS: If there is or was a community consensus that the topic is pseudoscience then the pseudoscience DS applies. If there is active debate about whether the topic is pseudoscience then the pseudoscience DS applies. The alternative medicine DS also applies. If the DS isn't working then I don't understand what arbcom saying that the pseudoscience DS applies will change? In terms of content the most the committee could say is that there is a community consensus that the topic is pseudoscience (anything else would be a pronouncement on content that is outside their remit) - what would such a statement change? Thryduulf (talk) 18:57, 26 August 2020 (UTC)

Statement by Shashank5988

Arbcom created Misplaced Pages:Arbitration/Requests/Case/Acupuncture for subjects like this, to avoid the conflict between "pseudoscience" and "alternative medicines". Shashank5988 (talk) 11:46, 20 August 2020 (UTC)

Statement by MrX

I agree that clarification is needed, inasmuch as a principle from a nearly 14 year old Arbcom case has been leveraged to assert that various subjects are pseudoscience based on ipse dixit declarations by involved editors. If my recollection serves me, previous Arbcoms have opined about this before (someone could perhaps check so that this Arbcom doesn't have to reinvent the wheel). Perhaps it's addressed in this FOF: WP:Requests for arbitration/Pseudoscience#Pseudoscience_2.

RexxS has expressed an understanding that, by my interpretation, would cast a broad net over a range of subjects making them automatically classified as pseudoscience based on (I guess) it being "pointed out in a discussion". I think it's self-evident why such an approach to dispute resolution would be problematic. If not, please let me know and I will explain further.

There are proponents with strong views on both side of the dispute at Ayurveda (note: I'm uninvolved). I would aver that simply because members of one side declare that "the position on Misplaced Pages is that Ayurveda is a pseudoscience as a matter of fact" does not make it so. Nor does it obviate the question in dispute: should the subject be described as pseudoscience in the first sentence of the article? Arbcom either needs to distance themselves from this reasoning or embrace it, because the ambiguity left by a nearly 14 year old Arbcom case has to potential to be weaponized in these disputes. This is not the first article where such a dispute has broken out. - MrX 🖋 19:51, 20 August 2020 (UTC)

@RexxS: I'm not aware that there is a serious dispute that Ayurveda is subject to discretionary sanctions. WP:Requests_for_arbitration/Pseudoscience#Discretionary_sanctions says "Standard discretionary sanctions are authorised for all articles pages relating to pseudoscience and fringe science, broadly interpreted.". Does anyone disagree that Aruyveda is at least related to pseudoscience and fringe science?

However, that's an entirely different issue than your request which says "clarification that the principle includes Ayurveda in the same way as astrology, and consequently that Ayurveda can be considered in the same light." In other words, I don't think you are asking if editors on the article are subject to DS, but whether the article can describe the subject as pseudoscience on the basis of the a principle written in a 2006 Arbcom case. - MrX 🖋 14:09, 21 August 2020 (UTC)

Statement by My very best wishes

Subjects like Ayurveda are clearly covered by the decision on Complementary and Alternative Medicine . As about pseudoscience, it was another decision , with good wording: "Theories which have a following, but which are generally considered pseudoscience by the scientific community".

In my view, no action is required here because the specific area of Complementary and Alternative Medicine is already covered by your decision. However, what qualify as pseudoscience in general is a good question. I think it is not enough just to say "if there is any plausible dispute over whether DS applies in a specific case". One must have at least one solid RS saying that subject X belongs to pseudoscience. Yes, there are such sources in the case of Ayurveda, although the consensus of RS seems to be this is just a traditional medicine. Should we label all projects in the field of traditional medicine funded by the National Center for Complementary and Integrative Health (a part of National Institutes of Health) as pseudoscience? I doubt. My very best wishes (talk) 15:49, 21 August 2020 (UTC)

@Newyorkbrad. OK. So, if an admin thinks that certain edits (for example, about a book) might belong to pseudoscience, than it is covered by pseudoscience DS, even if there are zero sources claiming the subject belongs to pseudoscience (and in fact it may belong to mainstream science)? That seems too much, given that admins may not be experts in the corresponding area of science. My very best wishes (talk) 02:27, 22 August 2020 (UTC)

@Newyorkbrad. Thank you! Understood and agree. My very best wishes (talk) 04:36, 22 August 2020 (UTC)

• As a side note, this is actually about content. I think too many subjects in WP are labeled "pseudoscience". This is a very serious label, and it must be exceptionally well sourced. Some of these subjects are simply not science, but a traditional medicine or something else, like Aurveda. Others, like Osteopathy aka Osteopathic medicine, implement at least some science-based procedures (one can follow this subsection of page Osteopathy to linked page Osteopathic medicine in the United States to realize this), and even completely mainstream Allopathic medicine was included to template "Alternative medicine". My very best wishes (talk) 21:59, 24 August 2020 (UTC)

Statement by Sunrise

As far as I'm aware, the answer is that the pseudoscience DS apply regardless, but the scope of DS cannot itself affect how the topic is described in an article. This is because the scope follows the concept of broadly construed - the DS will apply because the question "does this qualify as X?" is itself an X-related topic (otherwise topic-banned editors could wikilawyer endlessly around the edges of their sanction). However, for the same reason, simply being within the scope of X-related DS doesn't actually tell us whether or not the topic is or is not an X. Quoting from WP:BROADLY (I'm the original author of this text, but it's never been challenged in the more than two years since it was written): "Broadly construed" is also used when defining the topic areas affected by discretionary sanctions. In particular, if there is any plausible dispute over whether DS applies in a specific case (for example, definitional disputes: whether a particular issue counts as a type of American political issue, whether a particular practice counts as a type of alternative medicine, etc), that is normally taken to mean that it does. For this particular case, while the article does indeed state that Ayurveda or parts thereof are pseudoscience as a matter of fact (and has done so for a long time), that is because of the strength of the sourcing as determined by previous consensus, rather than being directly determined by ArbCom. The specific statement at WP:ARBPS#Generally considered pseudoscience does apply, but I think of it as mostly being a confirmation that using the term "pseudoscience" is in fact permissible under these circumstances. Sunrise (talk) 10:48, 21 August 2020 (UTC)

@MVBW: Traditional medicine and similar practices become pseudoscience when their effectiveness is disproven and they continue to be promoted regardless. Except in the most restrictive definitions, promotion with a disregard for evidence or on the basis of an unscientific belief system will also constitute pseudoscience (non-scientific reasoning is being presented as supporting a scientific claim). With regards to the allopathic medicine article, the template itself may or may not be warranted, but the relationship comes from the origins of the term as a derogatory label used by homeopaths. Sunrise (talk) 15:55, 26 August 2020 (UTC)

Statement by Aquillion

I I think the only answer is that all discussions of whether a topic is pseudoscience fall under the pseudoscience DS (that is the entire point of the restrictions, since that is the whole debate that requires DS in that topic area), and that, once the issue has been raised, the entire topic falls under the pseudoscience DS restrictions until there is an affirmative consensus that it is not pseudoscience. As long as there is reasonable doubt that it might be pseudoscience, basically, there is going to be debate of the sort that the DS were specifically created to govern. Obviously the applicability of the DS restrictions in that situation should not itself be taken as an absolute statement that the topic is pseudoscience, merely that it is at least under dispute. --Aquillion (talk) 19:01, 25 August 2020 (UTC)

Statement by Vanamonde

The determination of whether or not something is pseudoscience is a content decision that needs to be made by the community, but the determination of whether or not something falls under the scope of an AC/DS is very much a decision that is ultimately ARBCOM's responsibility. Making that decision does not require a ruling on content as such; it just requires ARBCOM to determine whether the problematic behavior that led to the authorization of DS is present in the topic under consideration. As such, this is a decision ARBCOM needs to be willing to make, regardless of whether another DS regime applies. By refusing to decide whether the pseudoscience DS regime covers Ayurveda, ARBCOM creates the possibility of endless wikilawyering with respect to the scope of such regimes, specifically, the argument that because there is not consensus among reliable sources that a topic is related to the name of a DS regime, that the relevant sanctions do not apply. Vanamonde (Talk) 16:21, 26 August 2020 (UTC)

@Xeno: I'll leave it to RexxS to articulate what he wants from this request; but my statement was more in response to the many people arguing here that this would constitute an expansion of the DS regime, or that ARBCOM needn't bother answering whether Ayurveda is within scope here because Ayurveda is covered by the alternative medicine DS regime. I think both of those are dangerous lines of argument for the reasons I've given above. I think you (ARBCOM) need to make explicit that Ayurveda is within the scope of these sanctions, and moreover, clarify why you've made that determination. Vanamonde (Talk) 16:55, 26 August 2020 (UTC)

@DGG: To be clear, are you arguing that pseudoscience DS do not apply to Ayurveda, contrary to what Xeno and others have said? Vanamonde (Talk) 18:36, 27 August 2020 (UTC)

@DGG: With respect, that's not the question I asked. I'm asking whether Ayurveda falls within the scope of an ARBCOM authorized discretionary sanctions regime, namely, the pseudoscience DS. The scope of those sanctions is within your purview and no-one else's; refusing to take a position on that is a cop-out. Vanamonde (Talk) 03:15, 28 August 2020 (UTC)

Statement by Guy Macon

I am not sure that this is a problem that Arbcom should try to fix, but I am sure that we have a problem, most of which is the direct result of OpIndia declaring war on Misplaced Pages and sending an army of twitter followers to the Ayurveda (edit | talk | history | links | watch | logs) page.

An incomplete history of Misplaced Pages's previous attempts to solve this problem:

• Misplaced Pages:Administrators' noticeboard/Incidents#Talk:Ayurveda
• Talk:Ayurveda#RFC: pseudoscience in the opening sentence
• Misplaced Pages:Administrators' noticeboard/Archive310#Ayurveda
• Misplaced Pages:Administrators' noticeboard/Archive272#RFC Review at Talk:Ayurveda/Archive 9
• Misplaced Pages:Administrators' noticeboard/Archive266#Ayurveda
• Misplaced Pages:Fringe theories/Noticeboard/Archive 69#Quacks who poison patients with mercury compounds and the Misplaced Pages editors who think this is OK
• Misplaced Pages:Fringe theories/Noticeboard/Archive 44#Ayurveda
• Misplaced Pages:Fringe theories/Noticeboard/Archive 43#Ayurveda and modern medical terminology
• Misplaced Pages:Fringe theories/Noticeboard/Archive 28#Ayurveda#Safety
• Misplaced Pages:Fringe theories/Noticeboard/Archive 28#Ayurveda and Talk:Ayurveda again
• Misplaced Pages:Fringe theories/Noticeboard/Archive 27#Ophthalmology in Ayurveda
• Misplaced Pages:Reliable sources/Noticeboard/Archive 301#Journal of Natural Science Biology and Medicine
• Misplaced Pages:Reliable sources/Noticeboard/Archive 244#Ayurveda

--Guy Macon (talk) 14:55, 31 August 2020 (UTC)

• DGG, Re: "It already has Extended confirmed protection, and why is that not enough?" We are still seeing a large amount of disruption. The protection stopped the flood of new accounts posting the same thing over and over, but OpIndia's twitter feed continues to attack Misplaced Pages and is encouraging posts to the Ayurveda talk page by twitter followers who have existing Misplaced Pages accounts and are already extended confirmed. --Guy Macon (talk) 15:03, 31 August 2020 (UTC)

• DGG, I am going to expand on what I wrote above ("I am not sure that this is a problem that Arbcom should try to fix"): I have yet to see a good argument showing that this is a problem that Arbcom should try to fix. We need multiple administrators watching over not just Ayurveda but whatever page OpInda attacks next (there is a list at User:PaleoNeonate/Watchlist Ayurveda). We need them to aggressively pageblock editors who were obviously sent by OpInda. I fail to see how any of this needs Arcom intervention.

Here is what I think Arbcom can do:

Proposal:

In my opinion, all that is needed is a simple statement that the 2020 version of Arbcom agrees with the decision by the 2006 version of arbcom (WP:ARBPS#Generally considered pseudoscience) that...

"Theories which have a following, such as astrology, but which are generally considered pseudoscience by the scientific community may properly contain that information and may be categorized as pseudoscience.

...and that Arbcom is not in the business of playing Whac-A-Mole by deciding what is and is not pseudoscience. You might want to drive the latter point home by re-issuing the 2006 decision without "such as astrology". If you do that, please add a note saying that you are not declaring Astrology to not be pseudoscience. --Guy Macon (talk) 20:08, 31 August 2020 (UTC)

Statement by Beyond My Ken

If the community has determined that Ayurveda is pseudoscience, then ArbCom - which does not make content determinations -- must treat it as pseudoscience and enforce against it any sanctions which are routinely used against pseudoscience. ArbCom has absolutely no remit to overturn a community determination about content. ArbCom's personal or collective opinions on the matter are completely irrelevant, since its hands are tied by the community decision.

That being said, ArbCom could exclude Ayurveda from any specific DS simply by changing the wording of the text and excluding Ayurveda from the definition of "pseudoscience" for the purposes of that sanction.

Beyond My Ken (talk) 23:32, 31 August 2020 (UTC)

Statement by jps

This strikes me as a tempest in a teapot. I am certain that Pseudoscience DS apply. I also think that that job of arbcom is not to adjudicate content. I asked you all some years ago to vacate the nonsense demarcation that a now-disgraced arbitrator penned oh-these-many years ago. The time is now to vacate that. An arbitration decision that says what is or is not pseudoscience is just not a good idea.

If there is a reasonable conflict/discussion about whether arguments about pseudoscience is relevant to a page, the pseudoscience DS are relevant. Obviously, it is relevant to ayurveda. That is as far as arbcom should be moving. I recommend vacating all the attempted demarcation and letting the community get back to business. Yes, that means that DS could be applied to pages relating to psychoanalysis (this is eminently reasonable). After all, WP:FRINGE works pretty well now in comparison to when this case (to which I was a party) was decided.

Love, etc.

jps (talk) 00:50, 1 September 2020 (UTC)

To clarify, it may be that there are enough interested parties to warrant a full case for arbitration. I am not yet convinced of that, but in principle if we get a lot of BJP activists coming in and arguing for more kid-gloved treatment of ayurveda or vedic astrology or hindu creationism, well maybe a case. But right now I think we have things under control as long as y'all are willing to say that Psuedoscience DS apply where the people here are claiming they apply. jps (talk) 00:52, 1 September 2020 (UTC)

Oh, and in case you need a clearer exhortation, it's this: REMOVE SPECIFIC MENTION OF BOTH ASTROLOGY AND PSYCHOANALYSIS FROM THIS ARBCOM CASE'S RULINGS. This isn't because I disagree with those rulings (though, in the case of psychoanalysis, it is something with which I disagree), it is simply because arbcom doesn't make these kinds of determinations any more. jps (talk) 00:57, 1 September 2020 (UTC)

Statement by Jehochman

It is troubling that discretionary sanctions are still in force for a case that is 14 years old. Shouldn't these sanctions have an automatic sunset? The point of sanctions is to solve a problem. Once the problem is solved we should default to our usual rules, which should be sufficient. If a set of sanctions is in force for (to pick an arbitrary term) three years, and the problem still isn't solved, then it's probably time to have a another case to figure out why the problem hasn't been solved, and maybe change the sanctions to something stronger. If an area like American politics is a source of perpetual problems, then we should write that into our community rules and make whatever measures are needed permanent. Jehochman 10:24, 4 September 2020 (UTC)

Statement by Atsme

My views align closer to KrakatoaKatie relative to not knowing what vitamins I should take, if any. As for the content and conduct issues, there appears to be some agreement that ArbCom does not exist to adjudicate article content; count me as a +1. On the other hand, my perspective about DS is that, in practice for the most part, they are neither resolutions nor binding solutions to resolve conduct issues because you cannot bind what is malleable or what was left unresolved. Isn't that why we're here now? DS obliquely, if not directly in some instances, regulate content because they create unintentional hurdles in an environment that is ripe for WP:POV creep, perceived or otherwise. AE grants admins super-authority by allowing them to impose irreversible sanctions against editors in a unilateral action at their sole discretion. In essence, ArbCom is throwing the ball back into the court of irreconcilable differences allowing a single admin to grab the ball and run to the goalpost of their choice (which creates an in the eyes of the beholder decision-making process) and they can do so with no concern of an interception or penalty flag. Most of us try to AGF but as a realist, I'm not quite convinced that decisions based on sole discretion are completely void of prejudice or bias - especially when it involves issues that already failed other DR processes. Give me a choice between sole discretion vs a panel of independent thinkers, and I'll choose the latter. Bottomline, my perception of ArbCom's responsibility is to impose binding solutions to Misplaced Pages conduct disputes that neither community discussion nor administrators have successfully resolved.. Editors who are elected to serve on ArbCom possess certain qualities that have garnered the community's trust, in part because they have demonstrated sound judgment, fairness and neutrality. There is also the thought that several heads are better than one because it adds an element of diversity. Some of the issues that are perceived to be disruption in highly controversial topic areas are "ended" (not always resolved) by a single admin making a judgment call, and in those cases, the potential for such decisions to be unknowingly influenced by POV or prejudice against an editor is highly plausible. The latter is why the community elected a panel - ArbCom - to handle the difficult cases. Somewhere beyond that is the reason we have so many essays. _Talk 📧 22:36, 7 September 2020 (UTC)

• Guy - not trying to be contrare, but I am curious...isn't John Hopkins Medicine a RS? They make no reference to ayurveda as a pseudoscience, rather they refer to it as "a complementary therapy in combination with standard, conventional medical care." Also, EPMA Journal, which has an 4.9 IF and a Scopus CiteScore of 7.7 in 2019, states: "This review article concludes that traditional knowledge systems like Ayurveda and modern scientific evidence-based medicine should be integrated." And there's also Science Direct (Elsevier) which lists multiple books and chapters about "ayuverdic medicine", and this article, (https://doi.org/10.1016/B978-0-12-816347-4.00009-X), Chapter 9 - Potential Treatment Strategies of Dementia With Ayurvedic Medicines, and on and on. I know Science Direct is a RS, and they don't exactly support the POV that it's "pseudoscience". _Talk 📧 15:20, 8 September 2020 (UTC)

  Adding Who Global Report On Traditional and Complementary Medicine 2019, pg 189, which states: Traditional Medicine (TM) and Complementary and Alternative Medicine (CAM):“Traditional medicine” is a comprehensive term used to refer to both various forms of indigenous medicine and to TM systems such as traditional Chinese medicine, Indian ayurveda, and Arabic unani medicine. _Talk 📧 15:31, 8 September 2020 (UTC)

Statement by ProcrastinatingReader

• The community can't really decide if a topic fits under a DS. They can make content decisions, but not this determination. That's made by uninvolved admins by an authority that descends from ArbCom.
• If an abuse of admin discretion was suggested at ARCA, some criteria to determine whether the article was in scope would probably apply (even if only implicit; obviously it would be inappropriate to apply PSDS to Banana). That would be as much of a content decision as deciding whether Ayurveda fits the bill under the psuedoscience DS.
• This particular case is probably resolved by Misplaced Pages:Arbitration/Requests/Case/Acupuncture. It does not necessarily fix the underlying issue. Arbs have suggested the Acupuncture case as being relevant to Ayurveda and thus resolving this issue, which means they consider Ayurveda as "Complementary and Alternative Medicine". According to our articles, "Alternative Medicine" is a subtype of pseudoscience (indeed, it is by definition). In other words, that determination effectively states that Ayurveda is a psuedoscience in a roundabout way, which is apparently what the Committee wants to avoid in this case.

It's not a content decision to decide whether something fits the scope. Ayurveda obviously fits the scope, we all know that here, so that part isn't exceptional. What is exceptional is that nobody wants to say it.

Thus, I think the real lesson here is to create non-inflammatory scopes for a DS. Calling something a "psuedoscience", even under the language of WP:BROADLY, is perceived as inflammatory I guess, which is probably why Arbs don't want to say it. But nobody would hesitate clarifying NRA falls under "organizations associated with ". PSDS is probably the only active DS with a perceived inflammatory scope. But, as above, AC ultimately still has to decide if an article fits within the scope of a DS, because it's the only body that can, and it has to make this decision (even implicitly) every time it reviews an ARCA for scope overreach. Shying away from that for PSDS doesn't seem like a good idea. Easy way out seems to be a comment along the lines of NYB. ProcrastinatingReader (talk) 02:55, 8 September 2020 (UTC)

Statement by JzG (Pseudoscience)

There appears to be consensus that the term pseudoscience can be included in the lead, as it is well sourced and in line with our approach to other pseudomedical modalities. The main problem is an endless succession of new single-purpose accounts following a thread on Twitter. These users typically assert that ayurveda is not pseudoscience because it enjoys a degree of official endorsement in India. This, of course, misses the point: so does homeopathy, after all. Guy (help! - typo?) 12:03, 8 September 2020 (UTC)

Statement by {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.

Pseudoscience: Clerk notes

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

Pseudoscience: Arbitrator views and discussion

• I don't think the committee has to take the position that any particular subject is pseudoscience for DS from that case to be applied (that the status is disputed is rather the point). RexxS: others have noted that the Acupuncture DS could also be applied: would that solve the immediate issue? –xeno 16:23, 21 August 2020 (UTC)
  • Vanamonde93: Any article where there is significant dispute as to whether it is pseudoscience is covered under the Pseudoscience discretionary sanctions: the article already carries the PS DS heading, and I don't think that loophole would carry very far. It seems the clarification request goes further in asking the committee to declare that not only does the DS apply, but also to classify the article subject "as a pseudoscience" (making a content determination) so that certain principles of the Pseudoscience case can be applied more directly - am I reading that right RexxS? –xeno 16:46, 26 August 2020 (UTC)
  • Vanamonde93: The existence of significant editorial disputes as to whether the topic is pseudoscience is sufficient for that topic to be covered by the Pseudoscience discretionary sanctions. In this context, I've withdrawn my question as to whether the Acupuncture DS could be substituted. –xeno 17:04, 26 August 2020 (UTC)
  • RexxS: I don't think you'll get a pronouncement from the 2020 committee that the topic is pseudoscience, despite what the 2006 committee might have said about astrology. The committee might be able to certify that there is community consensus that a preponderance of reliable sources indicate the topic to be pseudoscience and accordingly there is a consensus for it to be be described as such in the article, but I don't really think that kind of thing requires the committee, it can be done at a noticeboard or the article talk page. –xeno 15:22, 27 August 2020 (UTC)
  • RexxS the topic would be covered by that principle to the extent that it "is generally considered pseudoscience by the scientific community". It's not the committee that needs to make that determination, it's the editing community through inclusion of sources and community discussions (and from what you've outlined here, that determination has already been made). In any case: any statement made here by the committee is unlikely to affect the behaviour of the inexperienced editors which have been coming to the article/talk page. –xeno 17:43, 27 August 2020 (UTC)
  • Guy Macon: Thank you for the additional context. The article talk page is semi-protected until 12 Sept 2020, and a page was created for non-confirmed users to post. Discretionary sanctions are in place and enforcement paths are available. If the belief is that the community is unable to handle the issue administratively, it is probably better to file a full case that would allow for more and wider viewpoints (however my above comment re: efficacy applies). Since the edits of concern are mainly from new and newer editors, the wider issue (including the more recent developments covered in the ANI thread) could be heard at WP:AN so other interventions (general sanctions, higher levels of protection, etc.) may be considered by the community before asking the committee to intervene. –xeno 15:41, 31 August 2020 (UTC)
• A discussion of whether or not a given field or phenomenon is a pseudoscience should fall within the discretionary sanctions. Newyorkbrad (talk) 00:39, 22 August 2020 (UTC)
  • @My very best wishes: I'm speaking of a serious discussion that's overtly focused on whether something is a pseudoscience or not, not of a mental reservation that might be present in one admin's head. We just need to avoid the circularity of needing to know the outcome of a discussion of how we categorize something before we can define the rules of the discussion. Newyorkbrad (talk) 04:24, 22 August 2020 (UTC)
• I am unwilling to expand the scope of pseudoscience especially in a situation where there seems to be some cultural bias--it his treated in some geographies as a science with long historical roots and academic underpinnings. Arb com had no business declaring what fields are pseudoscience, or restricting or prescribing the content edited in these or any other fields. (with the exception of such things as blp) Nor does it have any need to deal with ordinary disruptive editing--ordinary admin remedies are sufficient for that. What arbcom does have the right and responsibility of doing is declaring that some fields are so exceptionally disruptive that arb enforcement sticky remedies are needed. The original basis for DS remedies was that in some such fields admins would revert each other, creating untenable situations unless the abbility to do so were restrained. The introduction of DS was successful, and did pretty much put a stop to that sort of privileged disruption. There may be some fields where this is still necessary--I might for example agree thaat American Politics is one of them, at least for the next few months, and some ethnic conflicts, perhaps even indefinitely. It could conceivably be argued that some forms of pseudoscience such as homeopathy are also. though I have doubts here--it has been so thoughly refuted. . I think the addition of any specific pseudoscience or other field to the list should should be discouraged unless it is proven that ordinary admin methhods have failed to deal with disruption. Ordinary arb methods have lately been dealing quite effectively with disruption, as can be seen by the many fewer cases that need to come to arb com. In my view, adding this field to the list unnecessary; its advocates are a very small number of editors who can be dealt with by the ordinary admin remedies. DGG ( talk ) 08:18, 22 August 2020 (UTC)

RexxS: I see a very large number of probable puppets, and ordinary sanctions, not DS, are quite enough to deal with that. DS had a possible role when there are persistent editorss getting repeatedly blocked; it adds nothing to the ordinary admin remedies in cases such as you mention. It does not show a need to arb com. DGG ( talk ) 19:55, 26 August 2020 (UTC)

RexxS: I did now look at the talk page. What do you propose to do under DS that you would be unable to do now.? DGG ( talk ) 17:52, 27 August 2020 (UTC)

Thinking further since I wrote my original comment, I have strenthened my view on DS--I would never support using them even in AP, where they have served to discourage open discussion and influence POV,. DGG ( talk ) 19:55, 26 August 2020 (UTC)

Vanamonde My personal view of whether ayurveda is a pseudoscience is irrelevant here. I'm responding as an arb, and as an arb I have no opinion about content. To the extent the original pseudoscience RFA was an attempt by arb com to give an opinion on content it was a erroneous decision, and we should not repeat their error. To the extent it dealt with conduct of various editors, it was a good decision. DGG ( talk ) 22:20, 27 August 2020 (UTC)

I thank you, Vanamonde, for your repeated question, because is has helped me make my positions clearer. it is not within the scope of any arbitrator to decide the nature of a medical procedure. It is not for us to decide this, and it was not correctly within our scope to make any similar decision we made in the past. If the previous cases implied it was, or required us to decide, they were wrong--it is outside our area. Based on the discussion here, a few other arbs seem to also refuse to take a stand on the matter. In particular your questions have helped me settle my position on the more general question of DS: I would abolish them, and then there would be no more such questions. among other merits of terminating the procedure, is that it leads to inappropriate requests for us to involve ourself in deciding content. What is within the scope of arb com is to end the concept of DS, and the only reason I do not now propose it by motion is that I do not think it would have a majority yet. DGG ( talk ) 04:38, 28 August 2020 (UTC)

• I can't decide what vitamins to take, so I'm in absolutely no position to decide if something is or isn't pseudoscience. Those are discussions that need to take place in a community process per NYB. Katie 13:27, 22 August 2020 (UTC)
• I would prefer to leave the decisions of whether something is pseudoscience up to the editing community when possible. However, it seems like the discretionary sanctions on alternative medicine are applicable here, so is this now a solved problem? GorillaWarfare (talk) 16:23, 22 August 2020 (UTC)

GW--what makes it impossible for the editing community to deal with the question? It already has Extended confirmed protection, and why is that not enough? DGG ( talk ) 20:09, 26 August 2020 (UTC)

Guy, I thought that might be the problem, but wouldn't it be solved by blocking people making disruptive repetitive postings, especially by using the new facility for blocking from a particular page. Any admin can do that as a normal admin action--it doesn't take DS. The only advantage of DS would be if these blocks were being reversed by other admins. Is that the case? What else do you suggest that needs DS? Or is it just meant to be a way of giving a very strong warning? DGG ( talk ) 17:48, 31 August 2020 (UTC)

I'm a little confused which of these comments are directed at me—please feel free to move this reply if I've incorrectly placed it. I don't personally believe that the editing community is unable to determine whether this subject is pseudoscience. GorillaWarfare (talk) 03:57, 1 September 2020 (UTC)

so, looking at your last note, you do not expect any practical effect from this? They why bother? The decision to call is pseudoscience is an editorial decision and can be done regardless of what arbcom thinks about it.. (fwiw, as I thought I had made clear, I disagree with labelling topics as pseudoscience at least in the overly heavy-handed way it is currently used for this topic, and if the arb com decision is used as an excuse to justify it, we need to revise most of the 2006 decision. DGG ( talk ) 20:38, 31 August 2020 (UTC)

I'm not sure what you mean by "why bother". Why bother making a clarification request? Presumably because RexxS didn't know if ArbCom was willing to answer one-off requests as to whether a topic is covered by a specific DS, which is understandable given that there is some general disagreement around whether we should. GorillaWarfare (talk) 00:17, 4 September 2020 (UTC)

• Whether or not the article should refer to Ayurveda as pseudoscience is entirely the decision of the editing community, a decision which should be based entirely upon reliable sources and not past ArbCom statements. Discussions about such language can be moderated under the DS rules, and implemented at the discretion of an uninvolved administrator. Beyond that, we have the "broadly construed" language to cover edge cases, as well as the DS authorized for "Complementary and Alternative Medicine" for when "Pseudoscience" isn't the right description. – bradv🍁 21:14, 31 August 2020 (UTC)

  Beyond My Ken, I don't understand your comment. What specifically are you asserting ArbCom is obliged to do? The only relevant remedies that I know of are listed at Misplaced Pages:Requests for arbitration/Pseudoscience#Remedies and Misplaced Pages:Arbitration/Requests/Case/Acupuncture#Remedies, and none of them mandate anything. They just authorize discretionary sanctions, which still have to be enacted by an uninvolved admin. – bradv🍁 23:52, 31 August 2020 (UTC)

• The "broadly construed" language though originally a good idea, is now in practice used as a device to sweep as much as possible into the same bin where arb com previously decided we need not follow NPOV, but what we think as scientists ought to be the POV. .

As a separate issue, anything that relies on DS will fail. The only way forward is for arb com to directly regulate conduct by removing prejudiced editors and admins, either from an area or from WP, not trying to adopt rules about just how disruptive they can be. DGG ( talk ) 04:39, 10 September 2020 (UTC)

Clarification request: 1RR requirements and enforcement

Initiated by ProcrastinatingReader at 20:23, 2 September 2020 (UTC)

Case or decision affected

Special:Permalink/820600857#Clarification_request:_Discretionary_Sanctions

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

• ProcrastinatingReader (talk · contribs · deleted contribs · logs · filter log · block user · block log) (initiator)

Statement by ProcrastinatingReader

• 2018 ARCA + Motion
• 2020 ARCA

Whilst I still have some time I figured I'd leave this with you for clarification. Over past couple months I've spoken to several admins re. DS procedures, mostly relating to my work on simplifying/cleaning up community sanction templates (speaking of, gentle query on if you've come to a decision re. my July email yet?), as I didn't want to file a dozen clarification requests. This ARCA stems from a discussion I had with El C, here. Would ask if you could read that section (& possibly see the diffs of change on the linked templates) as it provides relevant context for this question. I understand that the 2020 ARCA asked a very similar question to what I ask now, but given the confusion (ref discussion & incorrect template wording for years) I think it's appropriate to ask for a clear judgement.

In the 2018 ARCA, the Committee passed a motion stating that additional page restrictions apply to enforce 1RR. Namely, this meant that enforcing 1RR would require awareness procedures (incl alerting) to be met. The reasoning by the arbs was a strong feeling of it being inherently unfair to enforce 1RR on articles when the editor may not have been aware of this. Thus, a talk and editnotice alone are no longer sufficient.

In the 2020 ARCA, the Committee was going towards the idea of: the 1RR restriction require a formal alert in order to be enforced. After close reading of both, I can only interpret this as 1RR by case remedy doesn't require any awareness, but 1RR by DS does?

Is that a correct understanding? If yes, doesn't it also logically follow that 1RR DS enforcement may use the full, broad range of discretionary sanctions enforcement mechanisms, whilst 1RR case remedy can only use increasing-duration blocks, per ArbCom standard procedures?

My next question is, is this two-tier approach to 1RR even logical? In practice, I don't think many admins see 1RR DS as different from 1RR Case Remedy. Both types of 1RR have the same basic awareness (a large talk notice and editnotice), so it's not really accurate to think editors will be more aware of one than the other. I'd also note that it is purely admin discretion on whether an article is "within the conflict area", so 1RR case remedy is also subject to the same level of "discretion", especially for sanctions like ARBPIA and Abortion which have very broad and discretionary scopes. Thus, it seems quite illogical to treat these two 'types' of 1RR as separate. I'd imagine this two-tier approach is also likely confusing & inaccessible to many editors.

@Bradv: that I follow, which is the assumption I made in para 3. The final two paragraphs of my statement carry on from that assumption and I think those are still relevant questions to ask here, as I think they're the direct consequences of that interpretation. ProcrastinatingReader (talk) 00:28, 4 September 2020 (UTC)

@Bradv: so, per your comments & the first sentence of GW's comment, what is the status of non-ARBPIA4 1RR case remedies (namely GMO & abortion)? Do those require alerting to enforce, or are they the same as ARBPIA4? Also, re para4, is it correct to assume 1RR case remedies (w/o alert) can only be enforced by blocks? Would non-block enforcement actions relating to 1RR (eg topic bans, other restrictions) require an alert + DS action instead? ProcrastinatingReader (talk) 01:09, 4 September 2020 (UTC)

Statement by Atsme

DS...🤯 - also see above. _Talk 📧 23:17, 7 September 2020 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

1RR requirements and enforcement: Clerk notes

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

1RR requirements and enforcement: Arbitrator views and discussion

• The 2020 ARCA was specifically in reference to the 1RR restriction in effect for the WP:ARBPIA4 topic area. In this case it is not a discretionary sanction, but a general prohibition directly authorized by ArbCom, and therefore does not require a formal alert. The 2018 ARCA, on the other hand, was about 1RR as one of the restrictions commonly enacted by administrators as part of the discretionary sanctions system. I know this is confusing, but these two discussions are about two different things. – bradv🍁 23:58, 3 September 2020 (UTC)
  • To expound on this a bit further: the 1RR prohibition in effect for the ARBPIA is accompanied by a 500/30 restriction. This means that editors who do not have 500 edits and 30 days' tenure can't edit these articles at all, much less edit war on them. This makes the bar for entry to these articles high enough that we can expect people to be familiar with the restrictions in this area, and when disruption occurs it can be dealt with quickly. However, as I said at that ARCA, this rule doesn't necessitate a heavy-handed or punitive approach. A simple note that 1RR applies in this area should be all it takes to prevent a good-faith editor from inadvertently igniting an edit war, and applying 1RR to everybody, without requiring extra formalities for some, helps to keep the collaborative editing process fair and balanced. – bradv🍁 00:10, 4 September 2020 (UTC)
    • ProcrastinatingReader, regarding the last part of your question and your last comment, the reasons for enacting 1RR as a general prohibition for this topic area are complex, and would require a thorough reading of the related cases and amendment requests to fully understand. The simplest answer I can give is that this system is felt to be simpler and more consistent than discretionary sanctions. As I wrote above, a blanket 1RR and 500/300 restriction, together, provide a level playing field for the entire topic area, without the rules of engagement changing from article to article (as they do in, say, American Politics). While I certainly wouldn't advocate taking this same approach on every contentious topic area, there is considerable value in keeping things simple, and without evidence that this remedy is failing to work as intended I have to assume it is accomplishing its goals. It's also worth noting that the "discretion" involved here in applying these general restrictions is different from discretionary sanctions – in the case of ARBPIA articles the templates and edit notices can be applied by any editor, not just by uninvolved administrators. And the only consideration in adding the templates is that it be part of the topic area, not whether disruption has occurred or is likely to occur. – bradv🍁 00:44, 4 September 2020 (UTC)
      • ProcrastinatingReader, ARBGMO does not require an alert for 1RR to apply, but the abortion restriction is a little more complicated (see the ARCA below). As for enforcement, blocks can technically be issued even on a first offense, but as I said previously, this is not and should not be common. Topic bans and restrictions are not enforcement actions, but are additional sanctions (a.k.a. bans), and can only be enacted under DS or as a result of a community discussion, per Misplaced Pages:Banning policy#Authority to ban. – bradv🍁 01:16, 4 September 2020 (UTC)
• I would agree with bradv that the 2020 ARCA was intended to address specifically the ARBPIA4 1RR, not all 1RR imposed as a result of a case. While I do think it can be reasonable to enforce the 1RR even without an explicit warning in that topic area (particularly because of the additional 500/30 restriction), I also think admins should be sure to apply common sense. As NYB and others said at the ARCA, The bottom line is that an editor should never be blocked for making an edit that would normally be acceptable but violates a discretionary sanctions restriction, if there's a reasonable doubt as to whether the editor was aware of the restriction. GorillaWarfare (talk) 00:23, 4 September 2020 (UTC)

  Echoing what Bradv said. The topic-wide 1RR remedies imposed as a result of a case do not require the alerts that AC/DS require, but I'd expect it to be fairly rare that people are sanctioned via those 1RR without at least a quick heads up that 1RR applies. GorillaWarfare (talk) 01:19, 4 September 2020 (UTC)

• As others have noted above, it remains my strong position that an editor must never be sanctioned for violating a special rule that he or she was not aware of. Beyond that, the lack of clarity being discussed in this thread supports another strong position of mine, which is that the rules surrounding discretionary sanctions have become too complicated and confusing. Newyorkbrad (talk) 17:15, 7 September 2020 (UTC)
• There is no way of avoiding a first or second advantage in all RR rules.. and DS makes the unfairness all the harder to adjust, and all the easier to perpetuate. We need a new approach altogether. My idea is that the committee, which is electing to regulate conduct that ordinary admin procedures cannot handle, should do the necessary regulation of conduct rather than instruct the admins to do it a more complicated way. --It will be less work than the repeated dealing with issues such as ddressed by this request and the others requests here at the moment . Since the problems have not been solved, we are presumably doing something wrong--either we as arb com, or we at WP more generally DGG ( talk ) 04:33, 10 September 2020 (UTC)

Clarification request: Abortion

Initiated by ProcrastinatingReader at 21:12, 2 September 2020 (UTC)

Case or decision affected

Abortion 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:

• ProcrastinatingReader (talk · contribs · deleted contribs · logs · filter log · block user · block log) (initiator)
• Callanecc (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Confirmation that all parties are aware of the request

Statement by ProcrastinatingReader

It appears in 2011, the community added sanctions for the entire abortion topic area. This included a topic-wide 1RR.

ArbCom later took over the Abortion sanctions in WP:ARBAB. They authorised DS for the topic area.

In 2015, a clarification request was made asking whether 1RR was to be made a case remedy, as it was enacted by the community. 5 arbs agreed to this. I don't believe that was a majority at the time, and there was no motion made, and there remains no amendment to the original WP:ARBAB case to specify 1RR exists for the topic area, and if so, what the scope of 1RR should be. Thus I don't believe that ARCA duly resulted in any change to the status quo. At the time, a clerk (Callanecc) noted that ArbCom did not take over the 1RR.

I have brought this to ARCA following advice from clerks at their noticeboard. The talk notice, {{ArbCom sanctions - abortion}}, and the editnotice {{AbortionGSEN}} indicates the 1RR is a ArbCom remedy. However, Misplaced Pages:General sanctions/Abortion/Log says it has been superseded, whilst Misplaced Pages:General_sanctions#Arbitration_Committee-authorised_sanctions says "See this November–December 2015 clarification request, whereby the previous community 1RR was incorporated into the ArbCom DS". A topic-wide 1RR can't really be part of a DS?

Can the Committee please clarify:

• Has the Committee terminated the 1RR remedy from the community's 2011 abortion sanctions?
  • If yes, has it been replaced by an ArbCom topic-wide 1RR remedy?
    • If yes, should a motion be passed to amend WP:ARBAB, adding such a remedy and deciding on its scope?
    • If no, (but the 1RR from the community is still terminated), then I presume 1RR should be applied on an article-by-article basis? And in such a case, what's to happen to any 1RR enforcement blocks/sanctions prior to this ARCA?

Just a note that split logs overlapping with an ArbCom DS aren't completely abnormal, e.g. WP:GS/IPAK. ProcrastinatingReader (talk) 01:26, 4 September 2020 (UTC)

• Worm That Turned indeed, but what about any 1RRs after the case?I don't believe it's possible for that topic-wide 1RR to be a DS, as I think Thryduulf's statement implies, since (as the ARCA above is suggesting) 1RR case remedy and 1RR DS have totally different requirements. Even if that difference is desired here, it would not be compatible with the community authorisation. DS is somewhat the opposite of NOTBURO in general, such a decision needlessly complicates the system even more and creates inconsistencies with eg IPAK imv. I don't feel like this question should be overcomplicated: do we need a topic-wide 1RR for abortion or not? If so, please just amend the case and make it a normal 1RR like every other case, for consistency and clarity, rather than make abortion a special case. If we don't need one, then some kind of collective statement clarifying that ArbCom doesn't have a 1RR in place would seem helpful to put the matter to rest. Personally, considering WP:AELOG (zero topic 1RR sanctions in 5 years; two DS 1RR sanctions in 2019), I feel the 2nd option is better.While I'm here, and @Newyorkbrad: on this, curious if ArbCom has plans to simplify the DS system in some ways? There's a decade of AELOG history with some of these sanctions; surely enough evidence to codify many of the persistent issues into concrete, clear policies rather than promote the overuse of DS, which is indeed becoming a more and more opaque and somewhat poorly maintained system. Surely this isn't the best/only system that can exist to fix issues in affected topic areas. When there's multiple admins with differing interpretations of different 'rules', there's probably a problem with the system itself imo. ProcrastinatingReader (talk) 02:30, 8 September 2020 (UTC)

Statement by Callanecc

This is hazy in my memory but my thinking is something like this. In the case, ArbCom didn't mention the community-imposed 1RR restriction but did take over the community-authorised discretionary sanctions (number 2 in the ANI proposal). The Committee needs to take affirmative action to override the community and they didn't in this case. Additionally, they also imposed 1RR on individual editors which wouldn't have been necessary if they took over the 1RR restriction. The clarification request from 2015 asked where community-imposed 1RR violation be logged and the agreement amongst the arbs was that only 1 log should be used (for simplicity and NOTBURO). I see three options for the Committee here: (1) take over the community-imposed 1RR restriction (effectively as a drafting slip from the original case), (2) vacate the community-imposed 1RR restriction (effectively taking it over as a drafting slip in the original case, then vacating it as no longer needed), or (3) leaving the status quo (1RR stays as a community-imposed restriction but is logged at WP:AELOG for simplicity (and NOTBURO)). Callanecc (talk • contribs • logs) 09:29, 4 September 2020 (UTC)

Statement by Nosebagbear

Personally I find it amazing that the ARBCOM at the time felt they had the authority to make retroactive decisions with regard to general sanctions, but that's neither here nor there.

The question might be worth asking, but I would note, that if ARBCOM has not implemented a 1RR remedy, then I'm not sure they have the authority merely to terminate a community one as a sanction. There is of course a question against this that they could have implemented one in 2015, and removed it now, which would have had the same effect. However, they missed that boat: just doing it at once is akin to ARBCOM just deciding they felt a community sanction was a bad idea and canning it, rather than as part of a conduct method. Nosebagbear (talk) 08:35, 3 September 2020 (UTC)

Statement by Thryduulf

The 2015 clarification request asked a very specific question - where should violations of the 1RR be logged. The five arbs who answered (I was one of them) said in the central DS log. This, and the other comments in the discussion, imply that everyone was, and should continue to, treat it as a discretionary sanction under the provisions of the arbcom-authorised discretionary sanctions. Thryduulf (talk) 23:39, 3 September 2020 (UTC)

• It might be worth making explicit that any existing specific remedies placed under the DS authorisations, including 1RR restrictions applied to specific articles are not affected and that it also does not preclude the placing of any new 1RR restrictions in this topic area. Thryduulf (talk) 21:52, 8 September 2020 (UTC)

Statement by {other editor}

Abortion: Clerk notes

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

Abortion: Arbitrator views and discussion

• Is the community-authorized 1RR restriction still necessary? A look through WP:AELOG for the past number of years shows 1RR applied to certain articles as a discretionary sanction (such as Talk:Abortion in the United States), but it doesn't show anyone being sanctioned for violating the general 1RR restriction. I suspect that this blanket remedy is no longer being used, and if my assumption is correct, perhaps we should vacate it for simplicity and consistency. – bradv🍁 23:50, 3 September 2020 (UTC)
• Hm, this is a bit of complex question. The way it reads to me is that the ArbCom replaced the general sanctions with discretionary sanctions, but did not address the 1RR. Therefore I would say community-imposed 1RR in the topic area remains in place. The clarification request was about where sanctions should be logged, and it seemed to be agreed that the DS log made sense so there weren't two separate logs for the same topic area, but I wouldn't say that as a result of that clarification request the ArbCom took over the 1RR—that would have to be done more formally, I think. As for what to do now, the ArbCom could either decide to formally take on the 1RR restriction as an amendment to the abortion case, or we could leave it as is. Given the general disuse, I'm leaning towards the latter. However I would oppose us vacating the community-imposed 1RR, as I think that's a decision that should be left to the community. GorillaWarfare (talk) 00:30, 4 September 2020 (UTC)
• To my eyes, The discretionary sanction remedy states All sanctions enacted prior to this case under the terms of the community authorization shall be logged under this case as though they had been enacted under the new authorization. I would therefore have thought that the 1RR application should be considered under the Arbcom banner. What's more, as DS are in place, I would prefer a blanket 1RR is removed, and applied where needed. Worm(talk) 08:54, 7 September 2020 (UTC)
• I don't have a strong view on the specific clarification that is being requested, other than to suggest we not do anything that makes the rules governing discretionary and general sanctions any more complicated than they already are. Newyorkbrad (talk) 17:17, 7 September 2020 (UTC)

Motion: Abortion

The one-revert restriction on all articles related to abortion, authorized by the community here and modified by the Arbitration Committee in the Abortion arbitration case, is formally taken over by the committee and vacated. Discretionary sanctions remain authorized for all pages related to abortion, broadly construed.

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

Support

1. Proposed, in the absence of any evidence that this is still required or commonly used. – bradv🍁 15:47, 8 September 2020 (UTC)
2. Per bradv. No indication that DS is not sufficient. Regards SoWhy 18:40, 8 September 2020 (UTC)
3. we seem to be the right place for determinng conflicts between procedures like this one. DGG ( talk ) 04:25, 10 September 2020 (UTC)

Oppose

1. Per my above comment, since this was imposed by the community I think the decision whether to vacate it should be left to the community as well. GorillaWarfare (talk) 21:54, 8 September 2020 (UTC)

Discussion

Amendment request: Civility in infobox discussions

Initiated by Barkeep49 at 22:26, 6 September 2020 (UTC)

Case or decision affected

Civility in infobox discussions arbitration case (t) (ev / t) (w / t) (pd / t)

Clauses to which an amendment is requested

2. Role of consensus in arbitration enforcement

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

• Barkeep49 (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) (initiator)
• HAL333 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
• Cassianto (talk · contribs · deleted contribs · logs · filter log · block user · block log)
• Mclay1 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
• SchroCat (talk · contribs · deleted contribs · logs · filter log · block user · block log)
• JzG (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• Vanamonde93 (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
• Guerillero (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Confirmation that all parties are aware of the request

• HAL333
• Cassianto
• Mclay1
• SchroCat
• JzG
• Vanamonde93
• Guerillero

Information about amendment request

• Standard discretionary sanctions are authorized for all discussions about infoboxes and to edits adding, deleting, collapsing, or removing verifiable information from infoboxes.

• Whether discrestionary sanctions should be enacted against editors other than I-82

• Role of consensus in arbitration enforcement

• Whether discretionary sanctions were correctly utilized based on the consensus of uninvolved administrators when the AE request was closed (clause from Misplaced Pages:Arbitration/Requests/Case/Arbitration enforcement)

Statement by Barkeep49

On September 1, Ritchie filed an AE request for I-82-I about an Infobox RfC at Frank Sinatra. In subsequent discussion, diffs were brought forward concerning the actions of HAL333, Mclay1, Cassianto, and SchroCat. On September 4 TonyBallioni issued a Checkuser block against I-82-I for disruptive editing while logged out. On September 5, Cassianto opened a thread at ANI accusing Hal of harassment. Approximately four hours later, JzG closed the AE thread with an infobox Topic Ban on I-82-I. Prior to that close, 9 uninvolved administrators (including myself and JzG but not counting Tony) had participated in the discussion. At least three administrators, myself, Vanamonde, and Guerillero had supported sanctions against some of the other editors. A fourth, Ealdgyth, indicated that she saw incivility but did not wish to deal with the people involved . The other uninvolved administrators had not commented on these sanctions pro or con - one administrator feeling that sanctions should not only be applied to one side and two of the uninvolved administrators were participating in a discussion about whether Guerillero's use of "Ok boomer" towards Cassianto was a slur and not Infobox Civility itself. Subsequent discussion with JzG clarified that he had indeed closed the thread as no sanction against any other editors. As this seems to fly in the face of the considered consensus of multiple uninvolved administrators, with ArbCom being the only place to apply an AE decision, and given the sprawling nature of this conflict (which also includes, at minimum, and ), I am filing this appeal in regards to both Infobox editor conduct and JzG's close of the AE thread. Barkeep49 (talk) 22:26, 6 September 2020 (UTC)

• @Kingofaces43: according to a previous ArbCom case, the decision to close at AE with no sanction is is a decision that can only be appealed to ArbCom. See Misplaced Pages:Arbitration/Requests/Case/Arbitration_enforcement#Dismissing_an_enforcement_request_(alternate). As such those of us who felt other sanctions shouldbe levied cannot apply those sanctions.Best, Barkeep49 (talk) 00:34, 7 September 2020 (UTC)
• @Newyorkbrad: I am glad Vanamonde replied first because they said my feelings better than I would have. Pinging you to formalize what I am looking for from ArbCom here and why I think in the name of comity we don't just move on. I think this gets at what you were asking also Kingofaces43. Best, Barkeep49 (talk) 22:46, 8 September 2020 (UTC)

  Newyorkbrad, the people I had mentioned were Mclay1, HAL, Cassianto, and Schrocat (who I know is gone but I have hope might return one day even if under a slightly different account name owing to a password scramble). HAL, Cassianto, and Schrocat have all been a part of Infobox disputes before. So their promise to "stay away" from Sinatra is good - I mean that sincerely - but the sanctions in my mind were more about whatever the next Infobox skirmish is going to be as it is Sinatra. So the only one I would be willing to reconsider in light of a kept promise to stay away is Mclay1. Best, Barkeep49 (talk) 22:55, 9 September 2020 (UTC)

• As to bradv's suggestion that a full case could be beneficial, maybe? I mean we have two different administrators whose actions have been criticized by a range of editors. We also have Cassianto feeling that the ANI thread did not offer him from the harassment he was perceiving from HAL and which wasn't really being discussed at AE. However, I'm not sure, as evidenced by the desire of many people here for this to go away (I mean I got more than one good laugh when I explained to some people close to me what DS is and that we have DS for things like American Politics, Palestine/Israel, Race & Intellegence, and Infoboxes) that a full case is going to bring things forward that an ARCA would not. Now if the structure of a case would be helpful in dealing with these desperate parts then sure go for a case. Just don't expect it to turn into too much more than what has already been presented here. Best, Barkeep49 (talk) 22:46, 8 September 2020 (UTC)

Statement by HAL333

I am so thoroughly tired of this. The original ArbCom request was against I-82 and no one else. That editor retired, abused IP accounts, and was then CU blocked. Case closed. Additionally, SchroCat retired due to this whole ordeal. Can we please just stop here and not lose anymore editors.

Since being warned of the sanctions, I have not responded to a single opposing editor on that thread. I only asked an editor who supported the proposal to clarify his statement. Beyond that, I reverted edits by 73.193.59.165, who was repeatedly closing the RFC and claiming that there was a consensus to uncollapse the infobox (which they did and I reverted). I reported them for vandalism, and they were banned. A diehard pro-infoboxer (Which I'm not - I've gotten several of my works up to featured status without an IB) would have sat back and watched gleefully. I have agreed with SchroCat and Cassianto before, siding with them at Dispute Resolution and have even opposed the addition of an infobox with them.

Regarding the ANI discussion opened against me, here was my defense:

Earlier today, Cassianto referred to me, LEPRICAVARK, and two administrators as "messers". I was not familiar with this term: Cassianto often uses British slang. Oxford's Lexico defines it as "A person who makes a mess, or who messes about; a muddler, a bungler." According to Urban Dict, it is "Irish slang for a sloppy or messy person; someone who fails to take things seriously; a hopeless amateur, a gobdaw." Wiktionary defines it as "someone who messes". Accordingly, I respectfully asked Cassianto to strike through this personal attack. Cassianto was annoyed by my pinging him (which plenty of other people were doing at arbcom) and left a message claiming that I was harassing him. I responded courteously, without a ping. Cassianto then corrects the personal attack to "messrs", which, according to Google, is "used as a title to refer formally to more than one man simultaneously, or in names of companies." I found this a clever solution and it actually made me laugh. The barnstar of good humor was an expression of good faith. I was being genuine and met no ill will. I figured it would ease up tensions, but here we are....

• Note I have previously given Cassianto a barnstar after a disagreement, and it seemed to have improved our relations. I was trying to do the same thing again and assumed he would respond similarly to last time.

Everyone has moved on. I have not revisited any infobox discussions. There is no reason that we can't just let sleeping dogs lie. ~ HAL333 22:53, 6 September 2020 (UTC)

• Genuine confusion This enforcement request was brought because people were edit warring over collapsing a section of the RFC (I was not involved in that). That has been resolved. Why is this continuing? Also, why is SchroCat included in this? He has scrambled his password and no longer edits on Misplaced Pages. Any sanctions or penalties directed to him would be ineffectual and for image only. Sysops have expressed that they would want to penalize the supposed pro- and anti-infoboxers equally. Cassianto has already been placed under sanctions. How can this be impartial if sanctions would just be applied to two "pro"-infoboxers? Furthermore, other editors commented just as much (and perhaps were much more uncivil) as I did in the RFC: just look at the discussion. (I should note that my colorful signature doesn't help lol) Why am I being singled out? ~ HAL333 02:20, 7 September 2020 (UTC)

Statement by Cassianto

Statement by Mclay1

This whole thing seems pointless. The issue is over. I was not aware at the time of any specific rules about infobox discussions (which I'm still not clear on) and only made a few comments. I got into a very short and very mild disagreement with SchroCat, who was being quite rude to a number of people, but that conversation is long over and he's retired, so it's no longer an issue. My involvement in the discussion was not in any way unusual for a discussion on Misplaced Pages. As soon as I was informed of the infobox discussion rules (long before the ArbCom in question), I stopped commenting. I don't care about it anymore and have no need for sanctions. I have no intention of continuing the argument. I agree with HAL333. MClay1 (talk) 02:27, 7 September 2020 (UTC)

Statement by SchroCat

Statement by JzG

An AE was opened against I-82-I. That user subsequently used logged-out editing to evade scrutiny and was indefinitely blocked. Others used the AE filing as a vehicle for discussing long-standing issues with other editors who were not, I think, originally notified of the AE filing.

It seems to me that the subject of the original filing is effectively complete with the indefinite block of I-82-I. I have no strong view of what dispute resolution processes should be undertaken in respect of other editors discussed in the thread, other than that there should be some, but it seems to me that an AE on an obvious bad actor should not morph into sanctions discussions on long-standing good-faith editors without at least some effort to de-escalate or resolve the dispute. This would be my view regardless of the personalities involved.

As I said at the time and subsequently, if anyone wants to undo the close or spin out the separate discussions they are welcome to do so. I have no beef with any of the other parties here, admin or otherwise. I closed the AE in good faith because the outcome in respect of the original subject was clear, and it seems to me that AE discussions should be narrowly focused (because enforcement). I could be wrong. I am happy to leave this to others to decide because my views on the secondary parties are not strong, and because of a sudden worsening of C7 radiculopathy which means I am as of yesterday in too much pain to deal with this any further. Guy (help! - typo?) 07:25, 7 September 2020 (UTC)

Statement by Vanamonde93

I will not rehash the summary Barkeep49 has provided, but just add the following points. First, editors who are parties to a dispute brought to AE are explicitly also subject to sanctions, assuming they have been appropriately notified, which isn't in question here. Second, in this AE report, there was agreement among at least three administrators as to sanctions against editors other than the one being reported. Third, JzG's closure, while made in good faith, clearly does not represent the consensus of administrators at AE. Fourth, the issue has been discussed with JzG, and he has stated that he has no objections to further discussions about the other editors, but not that he was willing to reconsider the closure of this discussion. ARBCOM has previously rules that a single admin may overrule a consensus of other admins recommending no action to take an action at AE; does this now mean that a single admin can overrule a consensus of other admins recomending action, to prevent any action from being taken? In other words, if I (or Barkeep49, or Guerillero) wish to implement the actions we agreed upon, are we prevented from doing so by the minutiae of procedure? Vanamonde (Talk) 01:04, 7 September 2020 (UTC)

• As a general principle, I'd agree with JzG that a report against someone editing in bad faith shouldn't result in widespread sanctions. In this case, most of the problematic behavior I found occurred before the bad-faith editor even appeared on the scene, and so the subsequent block of I-82-I does not affect my assessment of anything; and I don't see why it should affect anyone else's. Vanamonde (Talk) 14:21, 7 September 2020 (UTC)
• @Newyorkbrad: I don't think anyone wants the AE opened again, but if that would be the only was for sanctions to be applied against the other editors involved, then what you are in effect saying is that any administrator can overrule a consensus of their colleagues to prevent discretionary sanctions from being placed on any problematic editor. If that's not what you mean, then any administrator still has the ability to impose sanctions for the behavior discussed at AE; which is the clarity I am looking for. Vanamonde (Talk) 23:04, 7 September 2020 (UTC)

  @Newyorkbrad: At this moment, I would not impose a sanction, because the principle participants have walked away from the conflict. I am firmly of the opinion that at the time the AE discussion was closed, the proposed sanctions were necessary, and that any willingness to step back on the part of the participants was because of the unfavorable attention they received here and at ANI. This feud went on for months, despite several attempts by uninvolved participants to calm things down. I would be very unsurprised to see further disruption, and if that occurs, any sanctions would need to take the episode discussed at AE into account to be useful. As things stand, it seems as though any sanctions cannot be levied on the basis of the behavior examined at AE already. There is also the issue of precendent; going forward, I would be much less inclined to engage with a contentious AE report, knowing that even a consensus among me and my colleagues could be overruled by a single admin. Vanamonde (Talk) 00:06, 10 September 2020 (UTC)

• Rather to my own surprise, I think a full case may not be the worst idea. A situation like this shouldn't need a full case. There's no substantively new behavioral issue here; AE can deal with it, but only if the discretionary sanctions are allowed to operate as they should. Unfortunately, as with many of our previous civility-related cases (GGTF; TRM) this has just exposed the deep-running rift among administrators with respect to how interactions between editors are perceived and responded to, and that has led to the enforcement of ARBCOM sanctions being hamstrung. If, in dealing with this sort of dispute, individual administrators face difficulties not only with the editors whose behavior is being investigated but also their fellow administrators, it's unsurprising that the dispute seems intractable, and is going to end up in ARBCOM's lap. Vanamonde (Talk) 16:06, 8 September 2020 (UTC)

Statement by Guerillero

My only thought is that JzG's close ran in the face of the consensus of the admins there. --Guerillero | Parlez Moi 22:57, 6 September 2020 (UTC)

• @Bradv: I don't think this rises to the level of a whole case --Guerillero | Parlez Moi 15:46, 8 September 2020 (UTC)

Statement by Sluzzelin

In my opinion (as a mere observer of info-box disagreements for more than a decade), any debate on info-boxes should be ignored by the entire community of editors. In most cases, the relevance of including or omitting an info-box is low. Good editors are wasting time and energy on something insignificant, but that doesn't mean they need to be punished for their exasperation. ---Sluzzelin talk 22:53, 6 September 2020 (UTC)

Statement by Moneytrees

I'll wait for other statements before I get into deeper specifics, but this has been a rather aggressive, tense dispute with many noticeboard visits over the past few months. I highly encourage arbcom to look into it. Moneytrees🏝️ 23:03, 6 September 2020 (UTC)

• @Bradv: I think this does rise to the level of a full case. This has been an issue that the community has not been able to resolve through discussion and AE, and I think these disputes will continue even if this one had died down a bit. Moneytrees🏝️ 15:51, 8 September 2020 (UTC)

Statement by Kingofaces43

Barkeep49, it's not really clear from your initial comments, but what is the issue being presented here that needs ArbCom? JzG closed the AE because the main subject was blocked and made no other sanctions that would have to be "overridden". If any admin felt someone else involved needed to be sanctioned through DS, they simply just need to do so and do not need AE consensus to do that. If anyone felt more discussion was needed to fine-tune a specific sanction on another editor, there's nothing stopping you or anyone else from opening another AE focused on the editor(s), and that's probably a better more focused option anyways to piece apart multi-editor issues. Kingofaces43 (talk) 00:24, 7 September 2020 (UTC)

Barkeep49, to be more clear, I'm wondering why you feel that principle applies here (and hopefully give arbs something even more pointed to address)? That might apply if the close dealt with more than the named subject of the AE or if I-82-I wasn't sanctioned and you thought they should be. Right now, only I-82-I sanctions would fall under the dismissing principle if that had happened. No one else's behavior was the subject of the close. At least from my read of the comments, it looks like you inadvertently set yourself down a slippery slope thinking you couldn't act. JzG's close looked pretty standard in the sense of the named editor has been sanctioned, other issues in the subject can be dealt with separately if warranted. That's how AE has always worked when multi-party issues come up that don't get a sanction all at the same time, which is why I'm finding some logic presented here at odds with how AE normally works.

Simply because the behavior of others was mentioned (and how often is it not?) in an AE request, that does not mean a request being closed against the primary named editor gives immunity to those other potential problem editors in the subject that were not addressed in the close. Editors just need to a bring a separate case focused on the specific editor if they feel DS enforcement is warranted. The infobox drama is foreign to me, but I agree it looks like there are problems outside of I-82-I. If that is dismissed, then the principle applies there for reopening. Otherwise, this approach is setting up problem editors to say their behavior was already "dismissed" at AE citing an early tangential request not focused on them where they were discussed.

Also, none of the above matters if you personally feel as an admin DS should be enacted as AE isn't needed to do that. Even if a request was closed as no action, you can later look at the (assumedly) partial evidence on the other editor(s) there while taking in other background information to place a sanction. "No action" is the default of every admin the moment they are made aware of a potential issue, so there's nothing to really override there (kind of a null hypothesis problem). The dismissing principle seems to be focused on reopening requests rather than making a no action decision on periphery editors (relative to the AE request) prevent future placing of sanctions. If arbs really do intend the latter, especially when it's not the main subject of a request, then it would be good to clarify. Kingofaces43 (talk) 16:22, 7 September 2020 (UTC)

Comment by GoodDay

The AE report-in-question had morphed into something it wasn't suppose to be. The individual who was the topic of that report, was blocked. PS - Can't we get back to the ongoing RFC at old Blue Eyes? GoodDay (talk) 14:30, 7 September 2020 (UTC)

Statement by Thryduulf (re Infoboxes/AE)

With regards to the general issue of consensus at AE would be to establish a principle that while a consensus is not required to act, administrators may not unilaterally act contrary to a consensus if one does exist, nor close a discussion in a manner that prevents other administrators from acting in accordance with that consensus (e.g. closing as "no action" if there is a consensus for action, or closing as "action" when there is consensus that no action is required). This would not compel admins to act - if they disagree with a consensus they may express their view in the discussion or simply leave it for some other admin. (I am explicitly not opining here on how this relates to the specific discussion in question). Thryduulf (talk) 01:00, 10 September 2020 (UTC)

Statement by {other-editor}

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.

Civility in infobox discussions: Clerk notes

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

• Recuse Moneytrees🏝️ 22:34, 6 September 2020 (UTC)
• Recuse --Guerillero | Parlez Moi 22:54, 6 September 2020 (UTC)

Civility in infobox discussions: Arbitrator views and discussion

• *sigh* I'll do my best to refresh myself with the situation and respond presently, but I will just note that one thing does stand out to me and that is Guerillero's "Ok, Boomer" comment. That was not Ok, especially for an admin who is dealing with a case as uninvolved, in an area that has a specific Arbcom case titled "Civility in ". Worm(talk) 09:19, 7 September 2020 (UTC)
• I understand why this request has been filed, and I suppose that in possible it is principle to appeal from an AE closure that didn't sanction one or more editors. That being said, I can't recall any time when we've granted that type of appeal, and I'm not sure this is a sensible place to start. I followed the discussion on the collapsed Sinatra infobox, and one thing that seems to have collapsed there, hopefully temporarily, is the level of civility. However, the logical remedy if this appeal were to be granted would be to direct that the AE thread be reopened. With the temperature on Talk:Frank Sinatra having cooled, and several of the disputants having stepped away, I think that could be counterproductive. If problematic infobox-discussion-related behavior resumes, on that page or elsewhere, a new AE request can be filed and the past behavior can be considered in the context of any ongoing issues. I hope this will not be necessary—and I hope that this hope is not ... hopeless. Newyorkbrad (talk) 17:31, 7 September 2020 (UTC)
  • @Barkeep49 and Vanamonde93: I note JzG's comment above, which I read to mean that he wouldn't object to someone imposing sanctions against one or more of the other editors who were being discussed before the AE thread was closed. But, if you felt authorized to do so, what sanctions would you seek to impose at this point and against whom? In considering this with respect to any specific editor, you might wish to consider, among other things, whether the editor promised to step away from the dispute several days ago, and whether the editor has kept that promise. Newyorkbrad (talk) 22:41, 9 September 2020 (UTC)
• AE is intended as a place to request intervention from an uninvolved administrator. While consensus discussions certainly happen on that page, it is not a forum designed to settle disputes between administrators, and so it is appropriate that this matter has been brought here. With regards to the underlying dispute, I am considering whether to propose a new case to investigate the conduct which led to the AE request, the conduct at the AE thread, as well as this related ANI thread, or whether we can solve this with a couple of motions. Given the level of disagreement that exists between enforcing administrators on how best to handle this, I am leaning toward the former. – bradv🍁 15:26, 8 September 2020 (UTC)

• Misplaced Pages arbitration
• Misplaced Pages requests