• Assume good faith
• Use etiquette
• Be civil
• Be open to compromise
• Discuss on talk pages
• Failure to discuss
• Help desk (Request)

• Third opinion (Request)
• Mediation
• Noticeboards
• Request comments (Request)
• Resolution noticeboard (Request)

• Administrator assistance (Request)
• Arbitration (Request)

• v
• t
• e

• About arbitrationTalk
• Arbitration policy (CU/OS)
• Guide to arbitration
• Noticeboard + Talk
• Search archived proceedings
• Ban appealsReport

• All open requests
• Case requests
• Clarification and Amendment requests
• Arbitrator motion requests
• Enforcement requests

• Contentious topics (Log)
• General sanctions
• Editor sanctions

• Discuss+
• Contact
• Members
• Procedures
• ElectionsTalk
• History
• Clerks+ Talk
• Clerk procedures
• Conflict of interest reports

• Talk
• StatisticsTalk
• Reports (pre-2016)

• v
• t
• e

• WP:ARC
• WP:A/R/C

About this page

Use this section to request the committee open an arbitration case. To be accepted, an arbitration request needs 4 net votes to "accept" (or a majority).

Arbitration is a last resort. WP:DR lists the other, escalating processes that should be used before arbitration. The committee will decline premature requests.

Requests may be referred to as "case requests" or "RFARs"; once opened, they become "cases". Before requesting arbitration, read the arbitration guide to case requests. Then click the button below. Complete the instructions quickly; requests incomplete for over an hour may be removed. Consider preparing the request in your userspace.

To request enforcement of an existing arbitration ruling, see Misplaced Pages:Arbitration/Requests/Enforcement. To clarify or change an existing arbitration ruling, see Misplaced Pages:Arbitration/Requests/Clarification and Amendment.

File an arbitration request

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

• This page is for statements, not discussion.
• Arbitrators or clerks may refactor or delete statements, e.g. off-topic or unproductive remarks, without warning.
• Banned users may request arbitration via the committee contact page; don't try to edit this page.
• Under no circumstances should you remove requests from this page, or open a case (even for accepted requests), unless you are an arbitrator or clerk.
• After a request is filed, the arbitrators will vote on accepting or declining the case. The <0/0/0> tally counts the arbitrators voting accept/decline/recuse.
• Declined case requests are logged at Misplaced Pages:Arbitration/Index/Declined requests. Accepted case requests are opened as cases, and logged at Misplaced Pages:Arbitration/Index/Cases once closed.

• WP:ARM
• WP:ARBM

This section can be used by arbitrators to propose motions not related to any existing case or request. Motions are archived at Misplaced Pages:Arbitration/Index/Motions.

Only arbitrators may propose or vote on motions on this page. You may visit WP:ARC or WP:ARCA for potential alternatives.

Make a motion (Arbitrators only)

Workflow motions: Arbitrator discussion

• I am proposing these three motions for discussion, community input, and a vote. Each seeks to improve ArbCom's functioning by providing for the performance of basic administrative responsibilities that sometimes go neglected, which, in my opinion, if successful, would significantly improve ArbCom's overall capacity. Motivation: We've known about the need for improvements to our workflow and capacity for some years now – I wrote about some of these suggestions in my 2022 ACE statement. It's a regular occurrence that someone will email in with a request or information and, because of the press of other work and because nobody is responsible for tracking and following up on the thread, we will let the thread drop without even realizing it and without deciding that no action is needed. We can each probably name a number of times this has happened, but one recent public example of adverse consequences from such a blunder was highlighted in the Covert canvassing and proxying in the Israel-Arab conflict topic area case request, which was partially caused by our failure to address a private request that had been submitted to us months earlier. Previous efforts: We've experimented with a number of technological solutions to this problem during my four years on the Committee, including: (a) tracking matters on a Trello board or on a private Phabricator space; (b) tracking threads in Google Groups with tags; (c) requesting the development of custom technical tools; (d) reducing the appeals we hear; and (e) tracking appeals more carefully on arbwiki. Some of these attempts have been moderately successful, or showed promise for a time before stalling, but none of them have fully and fundamentally addressed this dropping-balls issue, which has persisted, and which in my opinion requires a human solution rather than just a technological solution. Rationale: The work we need done as framed below (e.g. bumping email threads) isn't fundamentally difficult or sensitive, but it's essential, and it's structurally hard for an active arbitrator to be responsible for doing it. For example, I could never bring myself to bump/nag others to opine on matters that I hadn't done my best to resolve yet myself. But actually doing the research to substantively opine on an old thread (especially as the first arb) can take hours of work, and I'm more likely to forget about it before I have the time to resolve it, and then it'll get lost in the shuffle. So it's best to somewhat decouple the tracking/clerical function from the substantive arb-ing work. Other efforts: There is one more technological solution for which there was interest among arbitrators, which was to get a CRM/ticketing system – basically, VRTS but hopefully better. I think this could help and would layer well with any of the other options, but there are some open questions (e.g., which one to get, how to pay for it, whether we can get all arbs to adopt it), and I don't think that that alone would address this problem (see similar attempts discussed above), so I think we should move ahead with one of these three motions now and adopt a ticketing system with whichever of the other motions we end up going with. These three motions are the result of substantial internal workshopping, and have been variously discussed (as relevant) with the functionaries, the clerks, and the Wikimedia Foundation (on a call in November). Before that, we held an ideation session on workflow improvements with the Foundation in July and have had informal discussions for a number of years. I deeply appreciate the effort and input that has gone into these motions from the entire committee and from the clerks and functionaries, and hope we can now pass one of them. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)
  • One other thing I forgot to suggest—I'd be glad to write motions 1 or 2 up as a trial if any arb prefers, perhaps for 6-12 months, after which the motion could be automatically repealed unless the committee takes further action by motion to permanently continue the motion. Best, KevinL (aka L235 · t · c) 23:39, 1 December 2024 (UTC)

Workflow motions: Clerk notes

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

• I've excluded from the vote counts the votes of arbitrators whose terms expired on 1 January. See WP:ARBPOL#Participation and WP:AC/CP#Tasks at the beginning of each year. SilverLocust 💬 00:46, 3 January 2025 (UTC)

Workflow motions: Implementation notes

Clerks and Arbitrators should use this section to clarify their understanding of which motions are passing. These notes were last updated by SilverLocust 💬 at 05:39, 10 January 2025 (UTC)

Motion name	Support	Oppose	Abstain	Passing	Support needed	Notes
Motion 1: Correspondence clerks	4	7	0		Cannot pass	One support vote contingent on 1.4 passing
Motion 1.2a: name the role "scrivener"	2	6	2		Cannot pass
Motion 1.2b: name the role "coordination assistant"	1	5	4		Cannot pass
Motion 1.3: make permanent (not trial)	0	9	0		Cannot pass
Motion 1.4: expanding arbcom-en directly	3	5	2		Cannot pass	Cannot pass because motion 1 is not passing
Motion 2: WMF staff support	1	9	0		Cannot pass
Motion 3: Coordinating arbitrators	8	0	2		·	Two support votes are second choice to motion 1
Motion 4: Grants for correspondence clerks	0	8	0		Cannot pass

Motion 1: Correspondence clerks

Nine-month trial

The Arbitration Committee's procedures are amended by adding the following section for a trial period of nine months from the date of enactment, after which time the section shall be automatically repealed unless the Committee takes action to make it permanent or otherwise extend it:

Correspondence clerks

The Arbitration Committee may appoint one or more former elected members of the Arbitration Committee to be correspondence clerks for the Arbitration Committee. Correspondence clerks must meet the Wikimedia Foundation's criteria for access to non-public personal data and sign the Foundation's non-public information confidentiality agreement.

Correspondence clerks shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work.

The specific responsibilities of correspondence clerks shall include:

• Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
• Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
• Reminding members of the Committee to vote or otherwise take action in pending matters;
• Organizing related correspondence into case files; and
• Providing similar routine administrative and clerical assistance to the Arbitration Committee.

The remit of correspondence clerks shall not include:

• Participating in the substantive consideration or decision of any matters before the Committee; or
• Taking non-routine actions requiring the exercise of arbitrator discretion.

To that end, upon the first appointment of correspondence clerks, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and correspondence clerks.

The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by correspondence clerks.

All correspondence clerks shall hold concurrent appointments as arbitration clerks and shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.

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

Support

• (former arbitrator) This is my first choice and falls within ArbCom's community-granted authority to approve and remove access to mailing lists maintained by the Arbitration Committee and to designate individuals for particular tasks or roles and maintain a panel of clerks to assist with the smooth running of its functions. Currently, we have arbitration clerks to help with on-wiki work, but most of ArbCom's workload is private (on arbcom-en), and our clerks have no ability to help with that because they can't access any of ArbCom's non-public work. It has always seemed strange to me to have clerks for on-wiki work, but not for the bulk of the work which is off-wiki (and which has always needed more coordination help). When consulting the functionaries, I was pleasantly surprised to learn that four functionaries (including three former arbitrators) expressed interest in volunteering for this role. This would be lower-intensity than serving as an arbitrator, but still essential to the functioning of the committee. We already have a number of ex-arbs on the clerks-l mailing list to advise and assist, and this seems like a natural extension of that function. The Stewards have a somewhat similar "Steward clerk" role, although ArbCom correspondence clerks would be a higher-trust position (functionary-level appointments only). I see this as the strongest option because the structure is familiar (analogous to our existing clerks, but for off-wiki business), because we have trusted functionaries and former arbs interested who could well discharge these responsibilities, and because I think we would benefit from separating the administrative responsibility from the substantive responsibility. The cons I see are that volunteer correspondence clerks might be less reliable than paid staff and that we'd be adding one or two (ish) people to the arbcom-en list. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)

  I continue to urge my colleagues to support this motion to establish the trial of correspondence clerks. I hear the concern that this will add one or two more people to the mailing list, bringing it from 15 to 16-17, but I would suggest that the additional risk is quite small relative to the other considerations, which should predominate.
  Every new arbitrator elected in the future has access to every email sent to the committee now. One might estimate that over the next ten years, perhaps on average eight arbs will be elected per year of which four will be new to the committee. So, in addition to 15 current arbitrators, 40 future arbitrators will also be able to see the mailing list. (And let's be honest – it's not that hard to be elected to the committee.)
  By contrast, this proposal draws solely on former arbitrators (who have already had mailing list access), and doesn't increase the set much at all. And I trust that the committee will appoint only those former arbs who in its view retain its trust to access highly confidential information.
  In 2019, the community increased the size of the committee from 13 to 15, which reversed the 2018 change from 15 to 13. In neither discussion did the additional security risk of 15 mailing list subscribers (over 13), or the marginal security benefit of 13 subscribers instead of 15, even come up. The community was far more concerned with the effect of the committee's size on its ability to fulfill its functions.
  Similarly, here, I believe the committee should focus on whether this change could help the committee execute on its responsibilities. If yes, I urge the committee to give it a try; this nine-month trial isn't all that risky in the grand scheme of things.
  As for Cabayi's point that some material should be seen only by arbitrators, that's why this proposal explicitly provides that The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by correspondence clerks.
  Best, KevinL (aka L235 · t · c) 08:53, 30 December 2024 (UTC)

1. Contingent on 1.4 passing. This option was not my first choice, and I'm inclined to try having a coordinating Arb first, if we can get a volunteer/set of volunteers. Given that the new term should infuse the Committee with more life and vigor, we may find a coordinating Arb, or another solution. But I think we should put this in our toolbox for the moment. This doesn't force us to appoint someone, just gives us the ability and outlines the position. CaptainEek ⚓ 05:29, 7 December 2024 (UTC)
   • (former arbitrator) Slight support for this, mostly on the condition that it only be former Arbs that have consistent activity. One point I do wonder on is how the email clerks can ensure that Arbs actually get around to resolving the raised issues. Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
2. Per below – the community wants us to solve problems, and this is what best helps us solve problems. I don't think we severely damage people's privacy by increasing the number of ANPDP-signed and trusted functionaries who view the emails from 15 to 16, and to the extent it's bad for the opacity of ArbCom as an institution, that's just not my highest priority. theleekycauldron (talk • she/her) 01:28, 1 January 2025 (UTC)
3. I think this idea would allow someone to nudge us to ensure votes would take place. In the past, this was done by individual arbs, and if that worked we wouldn't need this motion. However, it hasn't and thus outside assistance would probably be more likely to solve the workflow problems we experience. Z1720 (talk) 17:34, 1 January 2025 (UTC)
4. Per Eek. Former arbs know what this is like, they know how to push the buttons, they understand the privacy implications, and of the myriad imperfect solutions that have been suggested, it's imho the best one. Katie 23:12, 6 January 2025 (UTC)

Oppose

1. I don't think we should extend access to the mailing list and the private information it contains beyond what is absolutely necessary. I understand the reasoning behind former arbitrators in such a role as they previously had such access, but people emailing the Arbitration Committee should have confidence that private information is kept need to know and that only the current arbitrators evaluating and making decisions based on that private information have ongoing access to it. - Aoidh (talk) 23:36, 9 December 2024 (UTC)
2. Might as well make it formal per my opinions elsewhere on the page. Primefac (talk) 13:24, 10 December 2024 (UTC)
3. This is limited to former arbitrators for good reasons, most of them privacy-related. But the same concerns that led to this proposal being limited to former arbitrators are also arguments against doing this at all. ~ ToBeFree (talk) 19:16, 14 December 2024 (UTC)
4. I don't find it hard to think of correspondence that the committee has received recently that absolutely should not have a wider circulation. I find myself in agreement with Aoidh - need to know. Cabayi (talk) 11:32, 27 December 2024 (UTC)
5. As I've made clear in private, I prefer having staff help (see that vote). I think that having non-professionals in this role mean that this proposal barely fails in balancing an acceptable level of "intrusion" on the list (ie the reduced privacy) against the probability of success and benefits. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)
6. Roughly per Aoidh, with additional concerns about creating additional overhead such as another mailing list and creating a bottleneck that could become a problem if the clerk were to become inactive for any reason. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
7. Coordinating arbitrators appears to be passing, and that's my preference on trying to keep workflow moving behind-the-scenes. I am not necessarily opposed to this in principle, but my preference would be to try coordinating arbitrators (including one coordinating this portfolio) first, and if for any reason we get a portion of the way through the year and that still isn't working, very happy to look at this again. I was considering supporting for the same reasons as Eek (put it in our toolkit for a rainy day), but instead I'm voting oppose on the basis that, should we wish to try it in the future, it's a very easy vote to quickly run through at that point (and, even if this passed, we'd probably need to have an internal vote to implement it at that time anyways). Daniel (talk) 20:08, 1 January 2025 (UTC)

Abstain

Motion 1: Arbitrator views and discussions

• I'd be glad changing this to only appoint former arbs, if that would tip anyone's votes. Currently, it's written as "from among the English Misplaced Pages functionary corps (and preferably from among former members of the Arbitration Committee)" for flexibility if needed, but I imagine we would only really appoint former arbs if available, except under unusual circumstances, because they understand how the mailing list discussions go and have previously been elected to handle the same private info. I am also open to calling it something other than "correspondence clerk"; that just seemed like a descriptive title. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)

  I do like the idea of using our Arbs emeritus for this position (and perhaps only Arbs emeritus); it ensures that they have experience in our byzantine process, and at least at some point held community trust. CaptainEek ⚓ 01:31, 3 December 2024 (UTC)

  @CaptainEek: I have changed the motion to make only former arbs eligible. If anyone preferred broader (all funct) eligibility, I've added an alternative motion 1.1 below, which if any arb does prefer it, they should uncollapse and vote for it. Best, KevinL (aka L235 · t · c) 02:07, 3 December 2024 (UTC)

• I also think that if we adopt this we should choose a better name. I know Barkeep49 meant this suggestion as a bit of a joke, but I actually think he was on the money when he suggested "scrivener." I like "adjutant" even more, which I believe he also suggested. They capture the sort of whimsical Misplaced Pages charm evoked by titles like Most Pluperfect Labutnum while still being descriptive, and not easily confused for a traditional clerk. CaptainEek ⚓ 03:21, 4 December 2024 (UTC)

  Whimsy is important -- Guerillero 08:55, 4 December 2024 (UTC)

• @CaptainEek and Guerillero: Per the above discussion points, I have (a) proposed two alternative names below that were workshopped among some arbs ("scrivener" on the more whimsical side and "coordination assistant" on the less whimsical side; see motions 1.2a and 1.2b), and (b) made this motion a nine-month trial, after which time the section is automatically repealed unless the Committee takes action to extend it. Best, KevinL (aka L235 · t · c) 03:10, 7 December 2024 (UTC)
• I plan on supporting motion 1 over anything else. I've spent a week just getting onto all the platforms, and I'm already kind of shocked that this is how we do things. Not only is there a lot to keep track of, all of the information moves unintuitively between different places in a way that makes it very difficult to keep up unless you're actively plugged in enough to be on top of the ball – which I don't think anyone can be all the time. I just don't think a coordinating arb is sufficient: we need someone who can keep us on track without having to handle all of the standard work of reviewing evidence, deliberating, and making an informed decision. (Better-organized tech would also be great, but I'd need to spend a lot more time thinking about how it could be redone.) I understand the privacy concerns, but I don't think this represents a significant breach of confidentiality: people care more whether their report gets handled properly than whether it goes before 15 trusted people or 16. So, I'll be voting in favor of motion 1, and maybe motion 3 will be a distant second. theleekycauldron (talk • she/her) 21:40, 17 December 2024 (UTC)
• I just want to briefly address @Moneytrees's question. In my view, nothing a c-clerk (or anyone else) can do can make arbs fulfill their functions. What the c-clerks can do is help reduce the needless duplicated time and effort arbs spend on trying to figure out what matters are outstanding, what balls they might be dropping, where their time can be effectively spent. But if an arb truly is checked out, yeah, regular emailed reminders aren't going to help. Best, KevinL (aka L235 · t · c) 08:59, 30 December 2024 (UTC)

References

1. Misplaced Pages:Arbitration/Policy § Scope and responsibilities
2. Misplaced Pages:Arbitration/Policy § Procedures and roles

Motion 1.1: expand eligible set to functionaries

Motion 1.2a: name the role "scrivener"

If motion 1 passes, replace the term "correspondence clerks" wherever it appears with the term "scriveners".

For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.

Support

1. Nicely whimsical, and not as likely to be confusing as correspondence clerk. CaptainEek ⚓ 04:11, 7 December 2024 (UTC)
2. per Eek :) theleekycauldron (talk • she/her) 01:28, 1 January 2025 (UTC)

Oppose

1. I think correspondence clerk is fine if role is something we're going with, it's less ambiguous as to what it entails than scrivener. - Aoidh (talk) 04:12, 11 December 2024 (UTC)
2. I have never heard that word before; at least "correspondence" and "clerk" are somewhat common in the English Misplaced Pages world. When possible, I think we should use words people don't have to look up in dictionaries. ~ ToBeFree (talk) 19:07, 14 December 2024 (UTC)
3. Follows on from my vote on Motion 1. Cabayi (talk) 11:38, 27 December 2024 (UTC)
4. As I've said in private, I think that this name would be unnecessarily opaque and complicated. Most people would need to search in a dictionary to understand what this means. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)
5. This sounds too much like we are appointing pirates, IMO. Too obscure of a word. Z1720 (talk) 17:35, 1 January 2025 (UTC)
6. I might be in the minority but I have no issue with 'correspondence clerks'. Daniel (talk) 20:08, 1 January 2025 (UTC)

Abstain

• (former arbitrator) I think that because it's more archaic and possibly less serious, I disprefer this to either "coordination assistant" or "correspondence clerk", but would ultimately be perfectly happy with it. Best, KevinL (aka L235 · t · c) 03:11, 7 December 2024 (UTC)
• (former arbitrator) Agree with Kevin. Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)

1. I don't think the name matters overmuch, although I think even if this passed they'd probably still be called a clerk in practice because who wants to type out scrivener every time? ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
2. I do. not. care. what it's called. Katie 23:12, 6 January 2025 (UTC)

Arbitrator discussion

Motion 1.2b: name the role "coordination assistant"

If motion 1 passes, replace the term "correspondence clerks" wherever it appears with the term "coordination assistants".

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

Support

1. Slightly better, I guess, in that the role (whatever it is called) is more about coordination (keeping track of business) than actual correspondence (replying to people who contact us). Not exactly an issue of paramount importance. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)

Oppose

1. bleh. CaptainEek ⚓ 04:12, 7 December 2024 (UTC)
2. Follows on from my vote on Motion 1. Cabayi (talk) 11:38, 27 December 2024 (UTC)
3. mm, not my favorite. theleekycauldron (talk • she/her) 01:28, 1 January 2025 (UTC)
4. Prefer correspondence clerks. Z1720 (talk) 17:36, 1 January 2025 (UTC)
5. Per 1.2a. Daniel (talk) 20:08, 1 January 2025 (UTC)

Abstain

• (former arbitrator) I am indifferent between this and "correspondence clerk". Best, KevinL (aka L235 · t · c) 03:11, 7 December 2024 (UTC)

1. If we're going to use a role like this, either this or correspondence clerk is fine. - Aoidh (talk) 04:13, 11 December 2024 (UTC)
2. That would be okay. ~ ToBeFree (talk) 19:08, 14 December 2024 (UTC)
   • (former arbitrator) 🤷‍♂️ Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
3. I'm not fussed about what color we paint the bike shed. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
4. Per above. Katie 23:12, 6 January 2025 (UTC)

Arbitrator discussion

Motion 1.3: make permanent (not trial)

If motion 1 passes, omit the text for a trial period of nine months from the date of enactment, after which time the section shall be automatically repealed unless the Committee takes action to make it permanent or otherwise extend it.

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

Support

Oppose

1. I recently experimented with sunset clauses and think that frankly a lot more of what we do should have such time limits that require us to stop and critically evaluate if a thing is working. CaptainEek ⚓ 04:19, 7 December 2024 (UTC)
2. If this change is necessary, there should be a review of it after a reasonable trial period to see what does and does not work. - Aoidh (talk) 01:34, 8 December 2024 (UTC)
3. ~ ToBeFree (talk) 19:10, 14 December 2024 (UTC)
4. Follows on from my vote on Motion 1. Cabayi (talk) 11:38, 27 December 2024 (UTC)
   • (former arbitrator) Agree with Eek. Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
5. This is a big change and so I'd rather that we forced a review. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)
6. If this passed it should require affirmative consensus to continue past the trial period. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
7. A trial first would be better. Z1720 (talk) 17:37, 1 January 2025 (UTC)
8. Daniel (talk) 20:08, 1 January 2025 (UTC)
9. Katie 23:12, 6 January 2025 (UTC)

Abstain

• (former arbitrator) I have no preference as to whether this is permanent or a trial. I do think that nine months is a good length for the trial if we choose to have one: not too long to lock in a year's committee; not too short to make it unworthwhile. Best, KevinL (aka L235 · t · c) 03:13, 7 December 2024 (UTC)

Arbitrator discussion

Motion 1.4: expanding arbcom-en directly

If motion 1 passes, strike the following text:

To that end, upon the first appointment of correspondence clerks, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and correspondence clerks.

And replace it with the following:

To that end, correspondence clerks shall be added to the arbcom-en mailing list. The Committee shall continue to maintain at least one mailing list accessible only by arbitrators.

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

Support

1. Much less trouble to have them on the main list than to split the lists. CaptainEek ⚓ 04:13, 7 December 2024 (UTC)
2. Especially if it's former arbs who've already had access to most of the list at one point or another, I think the trade-off of scriveners being able to properly do their jobs is worth it. theleekycauldron (talk • she/her) 01:28, 1 January 2025 (UTC)
3. Per my vote above. Katie 23:12, 6 January 2025 (UTC)

Oppose

1. Access to private information should be as limited as possible to only what is strictly necessary to perform such a task, and I don't see allowing full access to the contents of the current list necessary for this. I'd rather not split the list, but between that and giving full access then if we're going to have a correspondence clerk, then it needs to be split. - Aoidh (talk) 04:21, 11 December 2024 (UTC)
2. Motion 1 is already problematic for privacy reasons; this would make it worse. ~ ToBeFree (talk) 19:14, 14 December 2024 (UTC)
3. Follows on from my vote on Motion 1. Cabayi (talk) 11:38, 27 December 2024 (UTC)
   • (former arbitrator) I think the lists should be split. Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
4. If the clerk/skrivienenrener (see, I can't even spell it!) motion passes I would prefer to split the lists. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
5. I'd like to split the lists, in case there is a topic that arbs want to discuss as arb-only. The new role doesn't need to be observers in many discussions we have amongst arbs. Z1720 (talk) 17:39, 1 January 2025 (UTC)

Abstain

• (former arbitrator) I would not really object to this. C-clerks (or whatever we call them) are former arbs and have previously been on arbcom-en in any event, so it doesn't seem that like a big deal to do this. On the other hand, I would understand if folks prefer the split. Best, KevinL (aka L235 · t · c) 03:24, 7 December 2024 (UTC)

1. I am really torn on the competing arguments between decreased effectiveness and privacy of the lists. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)
2. Per Kevin & Sdrqaz. Daniel (talk) 20:08, 1 January 2025 (UTC)

Arbitrator discussion

• Proposed per Guerillero's comment below. KevinL (aka L235 · t · c) 03:24, 7 December 2024 (UTC)

Motion 2: WMF staff support

The Arbitration Committee requests that the Wikimedia Foundation Committee Support Team provide staff support for the routine administration and organization of the Committee's mailing list and non-public work.

The selected staff assistants shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work. Staff assistants shall perform their functions under the direction of the Arbitration Committee and shall not represent the Wikimedia Foundation in the course of their support work with the Arbitration Committee or disclose the Committee's internal deliberations except as directed by the Committee.

The specific responsibilities of the staff assistants shall include, as directed by the Committee:

• Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
• Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
• Reminding members of the Committee to vote or otherwise take action in pending matters;
• Organizing related correspondence into case files; and
• Providing similar routine administrative and clerical assistance to the Arbitration Committee.

The remit of staff assistants shall not include:

• Participating in the substantive consideration or decision of any matters before the Committee; or
• Taking non-routine actions requiring the exercise of arbitrator discretion.

To that end, upon the selection of staff assistants, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and staff assistants.

The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by staff assistants.

Staff assistants shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.

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

Support

1. I will come out here and support this, given my many comments in private, though it seems unlikely to pass now. Pragmatically speaking, I think that having staff on-list would have a greater likelihood of effectiveness due to being professionals who do this in their day job and having a greater obligation to help us because they're, well, staff (have a clearer subordinate–superior relationship in the WMF structure compared to a clerk, who is ultimately a volunteer that cannot be forced to work). Moreover, while I think that the separation between Community and Foundation is important, I feel that active Community members would have greater chances of having conflicts of interest due to pre-existing relationships; we have had very few petitions to us on Foundation actions in the last few years. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)

Oppose

1. I appreciate that Kevin put this together, and I think this would be very helpful, maybe even the most helpful, way to ensure that we stayed on top of the ball. But just because it would achieve one goal doesn't make it a good idea. A full version of my rationale is on the ArbList, for other Arbs. The short, WP:BEANS version is that this would destroy the line between us and the Foundation, which undoes much of our utility. CaptainEek ⚓ 01:22, 3 December 2024 (UTC)
2. Per my comment on motion 4. - Aoidh (talk) 01:31, 7 December 2024 (UTC)
3. Might as well make it formal per my opinions elsewhere on the page. Primefac (talk) 13:24, 10 December 2024 (UTC)
4. I like the general idea of the WMF using its donated resources to support the community that made the donations possible. I am uncomfortable with putting WMF staff in front of ArbCom's e-mail queue, however, as this would come with unavoidable conflicts of interest and a loss of independence. ~ ToBeFree (talk) 19:05, 14 December 2024 (UTC)
5. The help would be useful, but the consequences would be detrimental to both ArbCom & WMF. Some space between us is necessary for ArbCom's impartiality & for the WMF's section 230 position. Cabayi (talk) 12:56, 24 December 2024 (UTC)
   • (former arbitrator) Not a bad idea, but I believe the various conflicts of interest between us and the foundation, both major and minor, make this unworkable. Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
6. This would likely be the most effective way to go for keeping things moving, but I'm too concerned about the separation of Arbcom and WMF. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
7. I think other options need to be tried first before considering getting resources from WMF. Z1720 (talk) 17:40, 1 January 2025 (UTC)
8. Daniel (talk) 20:08, 1 January 2025 (UTC)
9. Under no circumstances do I want the WMF inserted into the arb list. Katie 23:02, 6 January 2025 (UTC)

Abstain

Motion 2: Arbitrator views and discussions

• I am quite open to this idea. A professional staff member assisting the committee might be the most reliable and consistent way to achieve this goal. ArbCom doesn't need the higher-intensity support that the WMF Committee Support Team provides other committees like AffCom and the grant committees, but having somebody to track threads and bump stalled discussions would be quite helpful. I'm going to wait to see if there's any community input on this motion before voting on it, though. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)

Motion 3: Coordinating arbitrators

The Arbitration Committee's procedures are amended by adding the following section:

Coordinating arbitrators

The Arbitration Committee shall, from time to time, designate one or more arbitrators to serve as the Committee's coordinating arbitrators.

Coordinating arbitrators shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work.

The specific responsibilities of coordinating arbitrators shall include:

• Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
• Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
• Reminding members of the Committee to vote or otherwise take action in pending matters;
• Organizing related correspondence into case files; and
• Performing similar routine administrative and clerical functions.

A coordinating arbitrator may, but is not required to, state an intention to abstain on some or all matters before the Committee without being listed as an "inactive" arbitrator.

For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.

Enacted. SilverLocust 💬 23:30, 10 January 2025 (UTC)

Support

1. This is currently my first-choice option; we have unofficially in the past had arbitrators take on specific roles (e.g. tracking unblock requests, responding to emails, etc) and it seemed to work fairly well. Having those rules be more "official" seems like the best way to make sure someone is responsible for these things, without needing to expand the committee or the pool of people with access to private information. Primefac (talk) 18:53, 1 December 2024 (UTC)
2. I may still vote for the clerks option, but I think this is probably the minimum of what we need. Will it be suffucient...aye, there's the rub. CaptainEek ⚓ 01:14, 5 December 2024 (UTC)
3. Of the motions proposed, this one is the one I'd most support. It doesn't expand the number of people who can view the ArbCom mailing list beyond those on ArbCom, and creates a structure that may improve how the mailing list is handled. - Aoidh (talk) 23:21, 9 December 2024 (UTC)
4. Per Primefac. ~ ToBeFree (talk) 19:19, 14 December 2024 (UTC)
   • (former arbitrator) Sure; this has been an informal position shared by many Arbs over the years (Barkeep, Maxim, Izno, L235, myself etc.) Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
5. Second choice to motion 1. theleekycauldron (talk • she/her) 01:29, 1 January 2025 (UTC)
6. I've mentioned that I don't think that having a titled role will make it more likely that the work gets done, but I accept that Kevin's arguments have some merit so here I am. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
7. Second choice to motion 1: I would prefer that the correspondence clerks be implemented instead: if this option worked, I think it would already be implemented (and has been implemented informally in the past in various forms). However, if motion 1 doesn't pass, this is probably the next best thing. Z1720 (talk) 17:42, 1 January 2025 (UTC)
8. First preference, per Primefac. Daniel (talk) 20:08, 1 January 2025 (UTC)

Oppose

Abstain

1. I don't think that this needs to be in our public procedures and feel like this could have been carried out without needing a formal vote on the subject (see comments by Izno and leek/SFR). I do have some reservations over whether having a specific person to do x will mean that the rest of us won't do x, but we'll see. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)
2. My first thought was "as long as I'm not the one who has to do it," and if that's how I'm thinking, I should sit this one out. Katie 23:01, 6 January 2025 (UTC)

Motion 3: Arbitrator views and discussions

• I am also open to this idea, though I am worried that it will be insufficient and haven't made up my mind on my vote yet. This idea was floated by a former arbitrator from back when the committee did have a coordinating arbitrator, though that role kind of quietly faded away. The benefits of this approach include that there's no need to bring anyone else onto the list. This motion also allows (but does not require) arbs to take a step back from active arb business to focus on the coordination role, which could help with the bifurcation I mention above. Cons include that this could be the least reliable option; that it's possible no arb is interested, or has the capacity to do this well; and that it's hard to be both a coordinator on top of the existing difficult role of serving as an active arb. I personally think this is better than nothing, but probably prefer one of the other two motions to actually add some capacity. Other ideas that have been floated include establishing a subcommittee of arbitrators responsible for these functions. My same concerns would apply there, but if there's interest, I'm glad to draft and propose a motion to do that; any other arb should also feel free to propose such a motion of their own. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)
• I was partial to this idea, though it was not my first choice. I proposed that we might make it a rotating position, à la the presidency of the UN security council. Alternatively, a three person subcommittee might also be the way to go, so that the position isn't dependent on one person's activity. I like this solution in general because we already basically had it, with the coordinating arbitrator role. CaptainEek ⚓ 01:35, 3 December 2024 (UTC)
  • @CaptainEek: I think your last sentence actually kind of nails why I don't love this solution? From a new person on the scene, it doesn't seem to me like trying old strategies and things we've already been doing is really going to solve a chronic problem. If there are arbs who really are willing to be the coordinators, that's better than nothing, but I haven't seen any step up yet and I'm not convinced that relying on at least one arb having the extra time and trust in every committee to do this work is sustainable. I am leaning towards voting for the scriveners motion, though, because I do love a good whimsical name theleekycauldron (talk • she/her) 21:51, 17 December 2024 (UTC)

    My concern with this is that if an arb already has the time and inclination you'd expect them to be filling the role, as has happened in the past. Simply formalizing the role doesn't help if no one has the motivation to do it. It's still the option I support the most out of those listed, though. ScottishFinnishRadish (talk) 22:07, 17 December 2024 (UTC)

    I think formalizing it does move the needle on someone doing it. Two possible benefits of the formalization:

    • It makes clear that this is a valuable role, one that an arb should feel is a sufficient and beneficial way to spend their time. It also communicates this to the community, which might otherwise ask an arb running for reelection why they spent their time coordinating (rather than on other arb work).
    • It gives "permission" for coordinating arbs to go inactive on other business if they wish.

    These two benefits make this motion more than symbolic in my view. My hesitation on it remains that it may be quite insufficient relative to motion 1. Best, KevinL (aka L235 · t · c) 22:18, 17 December 2024 (UTC)

• I could get behind this idea, not as a permanent single coordinating arb but as a "hat" that gets passed on, with each of us taking a turn. That would allow the flexibility for periods of inactivity and balancing workload when the coordinating arb wants/needs to act as a drafter on a complex case. It would also ensure that a wide-view of our workload was held by a wide-range of arbs. 3.5 weeks each and the year is covered. Cabayi (talk) 08:35, 27 December 2024 (UTC)

Motion 4: Grants for correspondence clerks

In the event that "Motion 1: Correspondence clerks" passes, the Arbitration Committee shall request that the Wikimedia Foundation provide grants payable to correspondence clerks in recognition of their assistance to the Committee.

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

Support

Oppose

1. Misplaced Pages should remain a volunteer activity. If we cannot find volunteers to do the task, then perhaps it ought not be done in the first place. CaptainEek ⚓ 01:09, 3 December 2024 (UTC)
2. We should not have a clerk paid by the WMF handling English Misplaced Pages matters in this capacity. - Aoidh (talk) 01:48, 6 December 2024 (UTC)
3. ~ ToBeFree (talk) 19:18, 14 December 2024 (UTC)
4. I feel bound by my RFA promise - "I have never edited for pay, or any other consideration, and never will." Cabayi (talk) 08:41, 27 December 2024 (UTC)
   • (former arbitrator) Would be cool, but no. “To whom much is given, much will be required”… Moneytrees🏝️(Talk) 23:20, 28 December 2024 (UTC)
5. Per the others. Primefac (talk) 07:23, 30 December 2024 (UTC)
6. Not against having a paid clerk in general, given my support of a WMF staff liaison, but would rather devote that money to a WMF professional, whom I believe would provide a greater likelihood of effectiveness. Sdrqaz (talk) 23:46, 30 December 2024 (UTC)
7. I might support something like this if it were to to hire a clerk independent of the WMF and volunteer functionaries, but I don't support paying a volunteer to tell other volunteers they need to respond to emails. ScottishFinnishRadish (talk) 16:58, 1 January 2025 (UTC)
8. Daniel (talk) 20:08, 1 January 2025 (UTC)

Abstain

Motion 4: Arbitrator views and discussions

• Proposing for discussion; thanks to voorts for the idea. Best, KevinL (aka L235 · t · c) 19:00, 1 December 2024 (UTC)

  I am leaning no on this motion. The potential downsides of this plan do seem to outweigh the benefit of being able to compensate a correspondence clerk for what will ultimately likely be something like 5 hours a week at most. Best, KevinL (aka L235 · t · c) 02:13, 3 December 2024 (UTC)

Community discussion

Will correspondence clerks be required to sign an NDA? Currently clerks aren't. Regardless of what decision is made this should probably be in the motion. * Pppery * _{it has begun...} 18:29, 1 December 2024 (UTC)

Good catch. I thought it was implied by "from among the English Misplaced Pages functionary corps" – who all sign NDAs as a condition to access functionaries-en and the CUOS tools; see Misplaced Pages:Functionaries (Functionary access requires that the user sign the confidentiality agreement for nonpublic information.)  – but I've made it explicit now. KevinL (aka L235 · t · c) 18:31, 1 December 2024 (UTC)

You're right that that was there, but I missed it on my first readthrough of the rules (thinking correspondence clerks would be appointed from the clerk team instead). * Pppery * _{it has begun...} 18:37, 1 December 2024 (UTC)

Why does "coordinating arbitrators" need a (public) procedures change? Izno (talk) 18:34, 1 December 2024 (UTC)

As Primefac mentioned above, it seems reasonable to assume that having something written down "officially" might help make sure that the coordinating arbitrator knows what they are responsible for. In any event, it probably can't hurt. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)

It is a pain in the ass to get formal procedures changed. There is an internal procedures page: I see 0 reason not to use it if you want to clarify what the role of this arbitrator is. Izno (talk) 19:13, 1 December 2024 (UTC)

On top of that, this doesn't actually change the status quo much if at all. It is almost entirely a role definition for an internal matter, given "we can make an arb a CA, but we don't have to have one" in it's "from time to time" clause. This just looks like noise to anyone reading ARBPRO who isn't on ArbCom: the public doesn't need to know this arb even exists, though they might commonly be the one responding to emails so they might get a sense there is such an arb. Izno (talk) 19:21, 1 December 2024 (UTC)

While I appreciate that some functionaries are open to volunteering for this role, this borders on is a part-time secretarial job and ought to be compensated as such. The correspondence clerks option combined with WMF throwing some grant money towards compensation would be my ideal. voorts (talk/contributions) 18:35, 1 December 2024 (UTC)

Thanks for this suggestion – I've added motion 4 to address this suggestion. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)

In the first motion the word "users" in "The Committee shall establish a process to allow users to, in unusual circumstances" is confusing, it should probably be "editors". In the first and second motions, it should probably be explicit whether correspondence clerks/support staff are required, permitted or prohibited to:

• Share statistical information publicly
• Share status information (publicly or privately) with correspondents who wish to know the status of their request.
• Share status information (publicly or privately) about the status of a specific request with someone other than the correspondent.

  For this I'm thinking of scenarios like where e.g. an editor publicly says they emailed the Committee about something a while ago, and one or more other editors asks what is happening with it.

I think my preference would be for 1 or 2, as these seem likely to be the more reliable. Neither option precludes there also being a coordinating arbitrator doing some of the tasks as well. Thryduulf (talk) 18:49, 1 December 2024 (UTC)

Thanks for these suggestions. I've changed "users" to "editors". The way I'm intending these motions to be read, correspondence clerks or staff assistants should only disclose information as directed by the committee. I think the details of which information should be shared upon whose request in routine cases could be decided later by the committee, with the default being "ask ArbCom before disclosing until the committee decides to approve routine disclosures in certain cases", because it's probably hard to know in advance which categories will be important to allow. I'm open to including more detail if you think that's important to include at this stage, though, and I'd welcome hearing why if so. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)

I see your point, but I think it worth clarifying certain things in advance before they become an issue to avoid unrealistic or mistaken expectations of the c-clerks by the community. Point 1 doesn't need to be specified in advance, maybe something like "communicating information publicly as directed by the Committee" would be useful to say in terms of expectation management or maybe it's still to specific? I can see both sides of that.

Point 2 I think is worth establishing quickly and while it is on people's minds. Waiting for the committee to make up its mind before knowing whether they can give a full response to a correspondent about this would be unfair to both the correspondent and clerk I think. This doesn't necessarily have to be before adoption, but if not it needs to be very soon afterwards.

Point 3 is similar, but c-clerks and community members knowing exactly what can and cannot be shared, and especially being able to point to something in writing about what cannot be said publicly, has the potential to reduce drama e.g. if there is another situation similar to Billed Mammal's recent case request. Thryduulf (talk) 19:30, 1 December 2024 (UTC)

What justification is there for the WMF to spend a single additional dollar on the workload of a project-specific committee whose workload is now demonstrably smaller than at any time in its history? (Noting here that there is a real dollar-cost to the support already being given by WMF, such as the monthly Arbcom/T&S calls that often result in the WMF accepting requests for certain activities.) And anyone who is being paid by the WMF is responsible to the WMF as the employer, not to English Misplaced Pages Arbcom.

I think Arbcom is perhaps not telling the community some very basic facts that are leading to their efforts to find someone to take responsibility for its organization, which might include "we have too many members who aren't pulling their weight" or "we have too many members who, for various reasons that don't have to do with Misplaced Pages, are inactive", or "we have some tasks that nobody really wants to do". There's no indication that any of these solutions would solve these kinds of problems, and I think that all of these issues are factors that are clearly visible to those who follow Arbcom on even an occasional basis. Arbitrators who are inactive for their own reasons aren't going to become more active because someone's organizing their mail. Arbitrators who don't care enough to vote on certain things aren't any more likely to vote if someone is reminding them to vote in a non-public forum; there's no additional peer pressure or public guilt-tripping. And if Arbcom continues to have tasks that nobody really wants to do, divest those tasks. Arbcom has successfully done that with a large number of tasks that were once its responsibility.

I think you can do a much better job of making your case. Risker (talk) 20:05, 1 December 2024 (UTC)

I think there is a need to do something as poor communication and extremely slow replies, if replies are made at all, has been an ongoing issue for the committee for some time. However I agree that asking the foundation to pay someone to do it is going too far. The point that if you are paid by the foundation, you work for them and not en.wp or arbcom is a compelling one. There's also a slippery slope argument to be made in that if we're paying these people, shouldn't we pay the committee? If we're paying the committee, shouldn't we pay the arbitration clerks....and so on. Just Step Sideways 20:26, 1 December 2024 (UTC)

I fully share Risker's concern about a paid WMF staffer who, no matter how well-intentioned, will be answerable to the WMF and not ARBCOM. Vanamonde93 (talk) 21:55, 1 December 2024 (UTC)

The 2023-2024 committee is much more middle aged and has less university students and retirees, who oftentimes have more free time, than the 2016-2017 committee. -- Guerillero 08:56, 2 December 2024 (UTC)

It seems to me that the issue of there often being some Committee members who, for whatever reason, are not "pulling their weight", is at the core of the problem to be addressed here. Because this happens "behind the scenes", the community has no way to hold anyone accountable in elections, and because of human nature and the understandable desire to maintain a collegial atmosphere within the Committee, I don't really expect any members to call out a colleague in public. I suppose there could even be a question of what happens if whoever might be filling the role proposed here nudges a member to act, but the member just disregards that. It's difficult to see how to make it enforceable. I don't have any real solutions, but this strikes me as central to the problem. --Tryptofish (talk) 23:31, 2 December 2024 (UTC)

I think this is largely correct. I was reluctant on the committee to even note this committee's inactivity problem (worst of any 15-member arbcom ever), even though it was based on a metric that is public, when I was still on the committee. And it gets further complicated by the fact that some people not visibly active in public more than pull their weight behind the scenes - the testimonials Maxim received when running for re-election being a prime example. Best, Barkeep49 (talk) 00:00, 3 December 2024 (UTC)

During my first term it was Roger Davies. He was barely a presence on-wiki but he kept the whole committee on point and up-to-date about what was pending. Trypto is right that it isn't enforceable, it is more a matter of applying pressure to either do the job or move oneself to the inactive list.

I also think the committee can and should be more proactive about declaring other arbs inactive even when they are otherwise present on-wiki or on the mailing list" That would probably require a procedures change, but I think it would make sense. If there is a case request, proposed decision, or other matter that requires a vote before the committee and an arb doesn't comment on it for ten days or more, they clearly don't have the time and/or inclination to do so and should be declared inactive on that matter so that their lack of action does not further delay the matter. It would be nice if they would just do so themselves, or just vote "abstain" on everything, which only takes a few minutes, but it seems it has not been happening in practice. Just Step Sideways 00:14, 3 December 2024 (UTC)

And Roger was a pensioner which kinda proves my point -- Guerillero 08:53, 4 December 2024 (UTC)

Roger may have been a pensioner at the end of his time on the committee (7 years), but he certainly wasn't at the beginning of his term. He was co-ordinating arbitrator for a lot of that time, and did a good job without a single bit of extra software. The problem with that software is that people have to already be actively engaged to even contemplate using it. My sense is that the real issue here is the lack of engagement (whether periodic or chronic) on the part of many of the arbitrators. People who are inactive on Arbcom tasks aren't going to be active on any tasks, including reading emails asking them to do things or special software sending alerts. Simply put, if people aren't going to put Arbcom as their primary Misplaced Pages activity for the next two years, keeping in mind other life events that will likely take them away, they should not run in the first place. Yes, unexpected things happen. But I think a lot of the inactivity we've seen in the last few years involved some predictable absences that the arbs knew about when they were candidates. (Examples I've seen myself: Oh, I have a big exam to write that needs months of study; oh, I have a major life event that will require a lot of planning; oh, I'm graduating and will have to find a job.) No, I don't expect people to reveal this kind of information about themselves; yes, I do expect them to refrain from volunteering for roles that they can reasonably foresee they will have difficulty fulfilling. Risker (talk) 04:21, 6 December 2024 (UTC)

I might as well ask a hard question. Is there a way to make public enough information for the community to be able to evaluate ArbCom candidates for (re)election, in terms of behind-the-scenes inactivity? If individual Arbs were to make public comments, that would do it, but it would also potentially be very contentious and could reduce effectiveness instead of improving it. Could ArbCom initiate a new process of posting onsite information about the processing of tasks, without revealing private information (such as: "Ban appeal 1", "Ban appeal 2", instead of "Ban appeal by "), and list those members who voted (perhaps without listing which way they voted)? Maybe do that monthly, and include all tasks that had not yet gotten a quorum. Yes, I know that's difficult. --Tryptofish (talk) 20:48, 6 December 2024 (UTC)

I question an answer to the problem of "we're having trouble finding enough people to do the secretarial work we have already" being "let's create substantially more secretarial work" even accepting the premise that people would then get voted off if they didn't pull their weight. While I think that premise is correct, what this system would also encourage - even more than it already exists - is an incentive to just go along with whatever the first person (or the person who has clearly done the most homework) says. And that defeats the purpose of having a committee made up of individual thinkers. Best, Barkeep49 (talk) 20:55, 6 December 2024 (UTC)

That's a fair point. I'll admit that, even from the outside, I sometimes see members who appear to wait to see which way the wind is blowing before voting on proposed decisions. --Tryptofish (talk) 20:59, 6 December 2024 (UTC)

That's something that's hard to know or verify, even for the other arbs. The arbs only know what the other arbs tell them, and I've never seen anyone admit to that. Just Step Sideways 23:44, 6 December 2024 (UTC)

I think the timing for this is wrong. The committee is about to have between 6 and 9 new members (depending on whether Guerillero, Eek, and Primefac get re-elected). In addition it seems likely that some number of former arbs are about to rejoin the committee. This committee - basically the committee with the worst amount of active membership of any 15 member committee ever - seems like precisely the wrong one to be making large changes to ongoing workflows in December. Izno's idea of an easier to try and easier to change/abandon internal procedure for the coordinating arb feels like something appropriate to try now. The rest feel like it should be the prerogative of the new committee to decide among (or perhaps do a different change altogether). Best, Barkeep49 (talk) 21:44, 1 December 2024 (UTC)

Kevin can correct me if I'm wrong, but I assumed he was doing this now because he will not be on the committee a month from now.

That being said it could be deliberately held over, or conversely, possibly fall victim to the inactivity you mention and still be here for the new committee to decide. Just Step Sideways 23:12, 1 December 2024 (UTC)

Since WP:ACE2024 elections are currently taking place it makes sense to have the incoming arbitrators weigh in on changes like this. They are the ones that will be affected by any of these motions passing rather than the outgoing arbitrators. - Aoidh (talk) 00:27, 2 December 2024 (UTC)

Oh I assumed that's why he was doing it also. I am also assuming he's doing it to try and set up the future committees for success. That doesn't change my point about why this is the wrong time and why a different way of trying the coordinator role (if it has support) would be better. Best, Barkeep49 (talk) 00:28, 2 December 2024 (UTC)

Regarding "timing is wrong": I think you both would agree that these are a long time coming – we have been working on these and related ideas for years (I ran on a related idea in 2022). I do think there's never quite a good time. Very plausibly, the first half of the year is out because the new arbs will need that time to learn how the processes work and think about what kinds of things should be changed vs. kept the same. And then it might be another few months as the new ArbCom experiments with less-consequential changes like the ones laid about at the top: technological solutions, trying new ways of tracking stuff, etc., before being confident in the need for something like set out above. And then things get busy for other reasons; there will be weeks or even occasionally months when the whole committee is overtaken by some urgent situation. I've experienced a broadly similar dynamic a few times now; this is all to say that there's just not much time or space in the agenda for this kind of stuff in a one-year cycle, which would be a shame because I do think this is important to take on.
I do think that it should be the aspiration of every year's committee to leave the succeeding committee some improvements in the functioning of the committee based on lessons learned that year, so it would be nice to leave the next committee with this. That said, if arbitrators do feel that we should hold this over to the new committee, I'm not really in a position to object – as JSS says, this is my last year on the committee, so it's not like this will benefit me. Best, KevinL (aka L235 · t · c) 01:30, 2 December 2024 (UTC)

I think it's entirely possible for the new committee to have a sense of what it wants workload wise by February-April and so it's wrong to just rule out the first half of the year. By the end of the first six months of the year that you and I started (and which JSS was a sitting member on) we'd made a number of changes to how things were done. Off the top of my head I can name the structure of cases and doing quarterly reports of private appeals as two but there were others. Best, Barkeep49 (talk) 01:47, 2 December 2024 (UTC)

Here's what I'll leave you with overall. What you may see as a downside – these proposals being voted on relatively late in the year – I see as a significant possible upside. Members of this committee are able to draw on at least eleven months' experience as arbitrators in deciding what is working well and what might warrant change – experience which is important in determining what kinds of processes and systems lead to effective and ineffective outcomes. That experience is important: Although I have served on ArbCom for four years and before that served as an ArbCom clerk for almost six years, I still learn more every year about what makes this committee click. If what really concerns you is locking in the new committee to a particular path, as I wrote above, I'm very open to structuring this as a trial run that will end of its own accord unless the committee takes action to make it permanent. This would ensure that the new committee retains full control over whether to continue, discontinue, or adapt these changes. But in my book, it does not make sense to wait. Best, KevinL (aka L235 · t · c) 22:58, 2 December 2024 (UTC)

• As a 3-term former arb and a 3-term current ombuds commissioner, I've had experience of about a dozen Wikimedia committee "new intakes". I am quite convinced that these proposals are correctly timed. Process changes are better put in place prior to new appointees joining, so that they are not joining at a moment of upheaval. Doing them late in the day is not objectionable and momentum often comes at the end of term. If the changes end up not working (doubtful), the new committee would just vote to tweak the process or go back. I simply do not understand the benefit of deferring proposals into a new year, adding more work to the next year's committee. That surely affects the enthusiasm and goodwill of new members. As for the point that the '24 committee is understaffed and prone to indecision: argumentum ad hominem. If Kevin's proposals work, they work. If anything, it might be more difficult to agree administrative reforms when the committee is back at full staff. arcticocean ■ 15:49, 10 December 2024 (UTC)

  If these pass now you will have new members join at a moment of upheaval as anything proposed here will still be in its infancy when the new members join (even if we pretend the new members are joining Jan 1 rather than much sooner given that results are in and new members tend to be added to the list once the right boxes are checked). Best, Barkeep49 (talk) 15:55, 10 December 2024 (UTC)

  You're right. And it's important to be realistic: any proposal would be under implementation for several months, so say from December through February. Would that be so bad? Any change will disrupt, in the sense that a few people need to spend time implementing it and everyone else needs to learn the new process. But waiting until later in the year causes even more disruption: members have to first learn an 'old' process and then learn the changes you're making to it… New member enthusiasm is also a keen force that could help to push through the changes. arcticocean ■ 16:28, 10 December 2024 (UTC)

  I think new member enthusiasm is part of why I think this lame duck hobbled committee is the wrong one to do it. I have high hopes for next year's group and think they would be in a better place to come up with the right solution for them. And as I noted to Kevin above this isn't hypothetical - the year we both started as arbs we made a lot of process and procedure changes in the first six months. It was a great thing to funnel that new arb energy into because I was bought into what we were doing rather than trying to make something work that I had no say in and that the existing members had no experience with. Best, Barkeep49 (talk) 16:34, 10 December 2024 (UTC)

  While I think a solution such as adopting ZenDesk is something that could face objections, personally I think the idea of having someone track a list of work items for a committee is a pretty standard way of working (including pushing for timely resolution, something that really needs a person, not just a program). From an outsider's perspective, it's something I'd expect. It doesn't matter to non-arbitrators who does the tracking, so the committee should feel free to change that decision internally as often as it feels is effective. I'd rather there be a coordinating arbitrator in place in the interim until another solution is implemented, than have no one tracking work items in the meantime. isaacl (talk) 19:30, 10 December 2024 (UTC)

Just to double check that I'm reading motion 1 correctly, it would still be possible to email the original list (for arbitrators only) if, for example, you were raising a concern about something the correspondence clerks should not be privy to (ie: misuse of tools by a functionary), correct? Granted, I think motion 3 is probably the simpler option here, but in the event motion 1 passes, is the understanding I wrote out accurate? EggRoll97 02:15, 2 December 2024 (UTC)

@EggRoll97 Yes, but probably only after an additional step. The penultimate paragraph of motions 1 and 2 says The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by correspondence clerks . No details are given about what this process would be, but one possibility would I guess be something like contacting an individual arbitrator outlining clearly why you think the c-clerks should not be privy to whatever it is. If they agree they'll tell you how to submit your evidence (maybe they'll add your email address to a temporary whitelist). Thryduulf (talk) 03:01, 2 December 2024 (UTC)

In my experience working on committees and for non-profits, typically management is much more open to offering money for software solutions that they are told can resolve a problem than agreeing to pay additional compensation for new personnel. Are you sure there isn't some tracking solution that could resolve some of these problems? Liz 07:20, 2 December 2024 (UTC)

In our tentative discussions with WMF, it sounded like it would be much more plausible to get a 0.1-0.2 FTE of staffer time than it would to get us 15 ZenDesk licenses, which was also somewhat surprising to me. That wasn't a firm response – if we went back and said we really need this, I'm guessing it'd be plausible. And we've never asked about compensating c-clerks – that was an idea that came from Voorts's comment above, and I proposed it for discussion, not because I necessarily support it but because I think it's worth discussion, and I certainly don't think it's integral to the c-clerk proposal. Best, KevinL (aka L235 · t · c) 15:00, 2 December 2024 (UTC)

Well, offering compensation for on-wiki tasks would be breaking new ground for the project. I do wonder though about the possibility of securing former arbitrators for these correspondent clerks' positions. It sounds like all of the work of an arbitrator (or more) without any ability to influence the results. I don't know if we'd have many interested and eligible parties. How many clerks would you think would be necessary? One? Or 3 or 4? Liz 21:40, 2 December 2024 (UTC)

Yeah, these are great questions. Responses to your points:

• On volunteers: As I wrote above, four functionaries (including three former arbs) expressed initial-stage interest when this was floated when I consulted functionaries – which is great and was a bit unexpected, and which is why I wrote it up this way. Arbitrators will know that my initial plan from previous months/years did not involve limiting this to functionaries, to have a broader pool of applicants. But since we do have several interested functs, and they are already trusted to hold NDA'd private information (especially the former arbs who have previously been elected to access to this very list), I thought this would be a good way to make this a more uncontroversial proposal.
• How many to appoint? I imagine one or two if it was up to me. One would be ideal (I think it's like 30 minutes of work per day ish, max), but two for redundancy might make a lot of sense. I don't think it's all of the work of an arbitrator (or more) without any ability to influence the results – because the c-clerk would be responsible for tracking matters, not actually attempting to resolve them, that's a lot less work than serving as an arb. It does require more consistency than most arbs have to put in, though.
• On compensating: Yeah, I'm not sure I'll end up supporting the idea, but I don't think it's unprecedented in the sense that you're thinking. Correspondence clerks aren't editing; none of the tasks listed in the motion require on-wiki edits. And there are plenty of WMF grants that have gone to off-wiki work for the benefit of projects; the first example I could think of was m:Grants:Programs/Wikimedia Community Fund/Rapid Fund/UTRS User Experience Development (ID: 22215192) but I know there are many.

Best, KevinL (aka L235 · t · c) 21:59, 2 December 2024 (UTC)

I am quite confused, I often read arbs saying most of ArbCom work is behind-the-scenes work. But is all this behind-the-scenes work essentially just a one-person 30-minute-a-day work? If so, the solution here is that more arbs should simply pull their weight, which Motion 3 helps. I don't think WMF would pay someone to work 30 minutes a day either. Kenneth Kho (talk) 07:19, 3 December 2024 (UTC)

But is all this behind-the-scenes work essentially just a one-person 30-minute-a-day work?. No, the actual work takes a lot more time and effort because each arb has to read, understand and form opinions on many different things, and the committee needs to discuss most of those things, which will often re-reading and re-evaluating based on the points raised. Then in many cases there needs to be a vote. What the "one-person, 30 minutes a day" is referring to is just the meta of what tasks are open, what the current status of it is, who needs to opine on it, etc. Thryduulf (talk) 11:31, 3 December 2024 (UTC)

Thanks, I realized I misunderstood it. I see that this is a relatively lightweight proposal, perhaps it could work but it probably won't help much either.

@L235 I have been thinking of splitting ArbCom into Public ArbCom and Private ArbCom. I see Public ArbCom as being able to function without the tools as @Worm That Turned advocated, focused more on complex dispute resolution. I see Private ArbCom as high-trust roles with NDAs, privy to WMF and overseeing Public ArbCom. Both ArbComs are elected separately as 15-members bodies, and both will be left with about half the current authority and responsibility. Kenneth Kho (talk) 01:54, 4 December 2024 (UTC)

Thryduulf is right; I think Kevin meant that the tracking itself might be a 30 minute a day activity. But it has to happen consistently, and with a high catch rate. It also has to happen on top of our usual Arb work, which for me already averages a good ten hours a week, but can be more than twenty hours in the busy times. And I, like the other arbs, already have a full time job and a life outside Misplaced Pages. I don't like the idea of splitting ArbCom in twain, nor do I think it could be achieved. CaptainEek ⚓ 02:18, 4 December 2024 (UTC)

I agree, having someone managing the work could really help smooth things out. Kenneth Kho (talk) 11:36, 4 December 2024 (UTC)

My first thought is that cleanly splitting arbcom would be very difficult. For example what happens if there is an open public case and two-thirds of the way through the evidence phase someone discovers and wishes to submit private evidence? Thryduulf (talk) 02:31, 4 December 2024 (UTC)

I agree, the split won't be entirely clean. I'm thinking Public ArbCom would narrowly remand part of the case to Private ArbCom if it finds that the private evidence is likely to materially affect the outcome. Kenneth Kho (talk) 11:34, 4 December 2024 (UTC)

How will public know whether the private evidence will materially affect the outcome without seeing the private evidence? Secondly, how will private arbcom determine whether it materially affects the outcome without reviewing all the public evidence and thus duplicating public arbcom's work (and thus also negating the workload benefits of the split)? What happens if public and private arbcom come to different conclusions about the same public evidence? Thryduulf (talk) 11:39, 4 December 2024 (UTC)

You raised good points that I did not address. I think that a way to do this would be to follow how Oversighters have the authority to override Admins that they use sparingly. Private ArbCom could have the right to receive any private evidence regarding an ongoing case on Public ArbCom, and Private ArbCom will have discretions to override Public ArbCom remedies without explanation other than something like "per private evidence". Private ArbCom would need to familiarize themselves with the case a bit, but this is mitigated by the fact that they only concerned with the narrow parts. Private ArbCom could have the authority to take the whole Public ArbCom case private if it deems that private evidence affect many parties. Kenneth Kho (talk) 11:55, 4 December 2024 (UTC)

12 candidates for 9 open seats is sufficient. But it hardly suggests we have so many people that we could support 30 people (even presuming some additional people would run under the split). Further, what happens behind the scenes already strains the trust of the community. But at least the community can see the public actions as a reminder of "well this person hasn't lost it completely while on ArbCom". I think it would be much harder to sustain trust under this split. Best, Barkeep49 (talk) 02:35, 4 December 2024 (UTC)

I honestly like the size of 12-member committee, too many proverbial cooks spoil the proverbial broth. I did think about the trust aspect, as the community has been holding ArbCom under scrutiny, but at the same time I consider that the community has been collegial with Bureaucrats, Checkusers, Oversighters. Private ArbCom would be far less visible, with Public ArbCom likely taking the heat for contentious decisions. Kenneth Kho (talk) 11:40, 4 December 2024 (UTC)

I agree with L235 regarding whether this is all the work and none of the authority: it does not come with all the responsibility that being an Arb comes with either. This role does not need to respond to material questions or concerns about arbitration matters and does not need to read and weigh the voluminous case work to come to a final decision. The c-clerk will need to keep up on emails and will probably need to have an idea of what's going on in public matters, but that was definitely not the bulk of the (stressful?) work of an arbitrator. Izno (talk) 00:26, 3 December 2024 (UTC)

@Liz well that's what I thought. I figured that ZenDesk was the winningest solution, until the Foundation made it seem like ZenDesk licenses were printed on gold bars. We did do some back of the envelope calculations, and it is decidedly expensive. Still...I have a hard time believing those ZenDesk licenses really cost more than all that staff time. I think we'll have to do some more convincing of the Foundation on that front, or implement a different solution. CaptainEek ⚓ 01:29, 3 December 2024 (UTC)

I touched upon the idea of using former arbitrators to do administrative tasks on the arbitration committee talk page, and am also pleasantly surprised to hear there is some interest. I think this approach may be the most expeditious way to put something in place at least for the interim. (On a side note, I urge people not to let the term "c-clerk" catch on. It sounds like stuttering, or someone not good enough to be an A-level clerk. More importantly, it would be quite an obscure jargon term.) isaacl (talk) 23:18, 2 December 2024 (UTC)

To that end, upon the first appointment of correspondence clerks, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and correspondence clerks.

Something I raised in the functionary discussion was that this doesn't make sense to me. What is the basis for this split here? Izno (talk) 00:08, 3 December 2024 (UTC)

I assumed it was so that the clerks would only see the incoming email and not be privy to the entire commitee's comments on the matter. While all functionaries and arbs sign the same NDA, operating on a need to know basis is not at all uncommon in groups that deal with sensitive information. When I worked for the census we had to clear our debriefing room of literally everything because it was being used the next day by higher-ups from Washington who were visiting. They outranked all of us by several orders of mgnitude, but they had no reason to be looking at the non-anonymized personal data we had lying all over the place.

Conversely it would spare the clerks from having their inboxes flooded by every single arb comment, which as you know can be quite voluminous. Just Step Sideways 00:23, 3 December 2024 (UTC)

And it would also prevent them from seeing information related to themselves or something they should actively recuse on. Thryduulf (talk) 01:15, 3 December 2024 (UTC)

This suggested rationale doesn't hold water: someone with an issue with a c-clerk or where they may need to recuse should just follow the normal process for an issue with an arb: to whit, kicking off arbcom-b for a private discussion. Izno (talk) 01:39, 3 December 2024 (UTC)

I was thinking of material from before they were appointed, e.g. if there was a discussion involving the actions of user:Example in November and they become a c-clerk in December, they shouldn't be able to see the discussion even if the only comments were that the allegations against them are obviously ludicrous. I appreciate I didn't make this clear though. Thryduulf (talk) 02:35, 3 December 2024 (UTC)

Making arbcom-en a "firewall" from the arb deliberations would inhibit the c-clerk from performing the duties listed in the motion. I cannot see how it would be workable for them to remind arbs to do the thing the electorate voluntold them to do if the c-clerk cannot see whether they have done those things (e.g. coming to a conclusion on an appeal), and would add to the overhead of introducing this secretarial position (email comes in, c-clerk forwards to -internal, arbs discussion on -internal, come to conclusion, send an email back to -en, which the c-clerk then actions back to the user on arbcom-en). This suggested rationale also does not hold water to me. Izno (talk) 01:43, 3 December 2024 (UTC)

Apologies – if this was the interpretation, that's bad drafting on my part. The sole intention is that the new correspondence clerks won't see the past arbcom-en archives, which were emails sent to the committee on the understanding that only arbitrators would see those emails. C clerks will see everything that's newly sent on arbcom-en, including all deliberations held on arbcom-en, with the exception of anything that is so sensitive that the committee feels the need to restrict discussion to arbitrators (this should be fairly uncommon but covers the recusal concern above in a similar way as discussions about arbs who recuse sometimes get moved to arbcom-en-b). The C clerks will need to be able to see deliberations to be able to track pending matters and ensure that balls aren't being dropped, which could not happen unless they had access to the discussions – this is a reasonable "need to know" because they are fulfilling a function that is hard to combine with serving as an active arbitrator. Best, KevinL (aka L235 · t · c) 01:54, 3 December 2024 (UTC)

Well, I clearly totally misread your intent there. I.... don't think I like the idea that unelected clerks can see everything the committee is doing. Just Step Sideways 03:15, 3 December 2024 (UTC)

FWIW, I oppose splitting arbcom-en a second time -- Guerillero 10:17, 3 December 2024 (UTC)

Regarding 1.4, I think arbcom-en and -c are good ones for a c-clerk to have access to. -b probably doesn't need access ever, as it's used exclusively for work with recusals attached to it, which should be small enough for ArbCom to manage itself in the addition of a c-clerk. (This comment in private elicited the slight rework L235 made to the motion.) Izno (talk) 06:08, 7 December 2024 (UTC)

What does this mean – when was the first time? arcticocean ■ 15:52, 10 December 2024 (UTC)

@Arcticocean: In 2018, arbcom-l became arbcom-en and the archives are in two different places. -- Guerillero 18:54, 10 December 2024 (UTC)

Appointing one of the sitting arbitrators as "Coordinating Arbitrator" (motion 3) would be my recommended first choice of solution. We had a Coordinating Arbitrator—a carefully chosen title, as opposed to something like "Chair"—for a few years some time ago. It worked well, although it was not a panacea, and I frankly don't recollect why the coordinator role was dropped at some point. If there is a concern about over-reliance or over-burden on any one person, the role could rotate periodically (although I would suggest a six-month term to avoid too much time being spent on the mechanics of selecting someone and transitioning from one coordinator to the next). At any given time there should be at least one person on a 15-member Committee with the time and the skill-set to do the necessary record-keeping and nudging in addition to arbitrating, and this solution would avoid the complications associated with bringing another person onto the mailing list. I think there would be little community appetite for involving a WMF staff member (even one who is or was also an active Wikipedian) in the Committee's business; and if we are going to set the precedent of paying someone to handle tasks formerly handled by volunteers, with all due respect to the importance of ArbCom this is not where I would start. Regards, Newyorkbrad (talk) 01:32, 3 December 2024 (UTC)

Thanks for your comments. Regarding little community appetite – that is precisely why we are inviting community input here on this page, as one way to assess how the community feels about the various options. Best, KevinL (aka L235 · t · c) 02:01, 3 December 2024 (UTC)

I also like the idea of an arb or two taking on this role more than another layer of clerks. I'm sure former arbs would be great at it but the committee needs to handle its own internal business. Just Step Sideways 03:37, 3 December 2024 (UTC)

I think it is ideal for the arbitration committee to track its own work items and prompt its members for timely action, and may have written this some time ago on-wiki. However... years have passed now, and the arbitration committee elections aren't well-suited to selecting arbitrators with the requisite skill set (even if recruitment efforts were made, the community can only go by the assurance of the candidate regarding the skills they possess and the time they have available). So I think it's worth looking at the option of keeping an arbitrator involved in an emeritus position if they have shown the aptitude and availability to help with administration. This could be an interim approach, until another solution is in place (maybe there can be more targeted recruiting of specific editors who, by their ongoing Misplaced Pages work, have demonstrated availability and tracking ability). isaacl (talk) 18:01, 3 December 2024 (UTC)

2 and 4 don't seem like very good ideas to me. For 2, I think we need to maintain a firm distinction between community and WMF entities, and not do anything that even looks like blending them together. For 4, every time you involve money in something, you multiply your potential problems by a factor of at least ten (and why should that person get paid, when other people who contribute just as much time doing other things don't, and when, for that matter, even the arbs themselves don't?). For 1, I could see that being a good idea, to take some clerical/"grunt work" load off of ArbCom and give them more time for, well, actually arbitrating, and functionaries will all already have signed the NDA. I don't have any problem with 3, but don't see why ArbCom can't just do it if they want to; all the arbs already have access to the information in question so it's not like someone is being approved to see it who can't already. Seraphimblade 01:49, 3 December 2024 (UTC)

@CaptainEek: Following up on your comments on motion 1, depending on which aspect of the proposed job one wanted to emphasize, you could also consider "amanuensis," "registrar," or "receptionist." (The best on-wiki title in my opinion, though we now are used to it so the irony is lost, will always be "bureaucrat"; I wonder who first came up with that one.) Regards, Newyorkbrad (talk) 03:49, 4 December 2024 (UTC)

Or "cat-herder". --Tryptofish (talk) 00:18, 5 December 2024 (UTC)

Following parliamentary tradition, perhaps "whip". (Less whimsically: "recording secretary".) isaacl (talk) 00:31, 5 December 2024 (UTC)

@Newyorkbrad:, if memory serves @Keegan: knows who came up with it, and as I recall the story was that they wanted to come up with the most boring, unappealing name they could so not too many people would be applying for it all the time. Just Step Sideways 05:03, 10 December 2024 (UTC)

So, just to usher in a topic-specific discussion because it has been alluded to many times without specifics being given, what was the unofficial position of ArbCom coordinator like? Who held this role? How did it function? Were other arbitrators happy with it? Was the Coordinator given time off from other arbitrator responsibilities? I assume this happened when an arbitrator just assumed the role but did it have a more formal origin? Did it end because no one wanted to pick up the responsibility? Questions, questions. Liz 06:56, 6 December 2024 (UTC)

I cannot speak for anything but my term. I performed this role for about 1.5 years of the 2 I was on the committee. To borrow an email I sent not long before I stepped off that touches on the topics in this whole set of motions (yes, this discussion isn't new):

• Daily, ~20 minutes: went into the list software and tagged the day's incoming new email chains with a label (think "upe", "duplicate", etc).
• Daily, ~10 minutes: took care of any filtered emails on the list (spam and not-spam).
• Monthly, 1-2 hours: trawled the specific categories of tags since the beginning of the month to add to an arbwiki page for tracking for "needs to get done". Did the inverse also (removed stuff from tracking that seemed either Done or Stale).
• Monthly, 15 minutes to prep: sent an email with a direct list of the open appeals and a reminder about the "needs doing" stuff (and a few months I highlighted a topic or two that were easy wins). This built off the daily work in a way that would be a long time if it were all done monthly instead of daily.

I was also an appeals focused admin, which had further overhead here that I would probably put in the responsibility of this kind of arb. Other types of arbs probably had similar things they would have wanted to do this direction but I saw very little of such. Daily for this effort, probably another 15 minutes or so:

• I copy-pasted appeal metadata from new appeals email to arbwiki
• Started countdown timers for appeals appearing to be at consensus
• Sent "easy" boilerplate emails e.g. "we got this appeal, we may be in touch" or "no way Jose you already appealed a month ago"
• Sent results for the easy appeals post-countdown timer and filled in relevant metadata (easy appeals here usually translated to "declined" since this was the quick-n-easy daily work frame, not the long-or-hard daily work frame)

(End extract from referenced email.) This second set is now probably a much-much lighter workload with the shedding of most CU appeals this year (which was 70% of the appeals by count during my term), and I can't say how much of this second group would be in the set of duties depending on which motion is decided above (or if even none of the motions are favored by the committee - you can see I've advocated for privately documenting the efforts of coordinating arbs rather than publicly documenting them regarding 3, and it wouldn't take much to get me to advocate against 2 and 4, I just know others can come to the right-ish conclusion on those two already; I'm pretty neutral on 1).

Based on the feedback I got as I was going out the door, it was appreciated. I did see some feedback that this version of the role was insufficiently personal to each arb. The tradeoff for doing something more personalized to each other arb is either time or software (i.e. money). I did sometimes occasionally call out when other members had not yet chimed in on discussions. That was ad hoc and mostly focused on onwiki matters (case votes particularly), but occasionally I had to name names when doing appeals work because the arbs getting to the appeal first were split. In general the rest of the committee didn't name names (which touches on some discussion above). I think some arbs appreciated seeing their name in an email when they were needed.

I was provided no formal relief from other matters. But as I discussed with one arb during one of the stressful cases of the term, I did provide relief informally for the duration of that case to that person for the stuff I was interested in, so I assume that either I in fact had no relief from other matters, or that I had relief but didn't know it (and just didn't ask for anyone else to do it - since I like to think I had it well enough in hand). :-) The committee is a team effort and not everyone on the team has the same skills, desire, or time to see to all other matters. (The probing above about arbs being insufficiently active is a worthwhile probe, to be certain.) To go further though, I definitely volunteered to do this work. Was it necessary work? I think so. I do not know what would have happened if I had not been doing it. (We managed to hit only one public snag related to timeliness during my term, which I count as a win; opinions may differ.)

There is no formal origin to the role that I know of. Someone else with longer committee-memory would have to answer whether all/recent committees have had this type, and who they were, and why if not.

I don't know how much of what I did lines up with what L235 had in mind proposing these motions. I do not think the work I did covers everything listed in the motions laid out. (I don't particularly need clarification on the point - it's a matter that will fall out in post-motion discussion.) Izno (talk) 08:48, 6 December 2024 (UTC)

The original announcement of the Coordinating Arbitrator position was here. Regards, Newyorkbrad (talk) 21:29, 6 December 2024 (UTC)

Archive zero: I love it! --Tryptofish (talk) 21:37, 6 December 2024 (UTC)

Interestingly, that announcement also repeated the announcement at the top of the archive page that a departing arbitrator continued to assist the committee by co-ordinating the mailing list: acknowledging incoming emails and responding to senders with questions about them, and tracking issues to ensure they are resolved. So both a co-ordinator (plus a deputy!) and an arbitrator emeritus. isaacl (talk) 23:23, 6 December 2024 (UTC)

former arbitrator will continue to coordinate the ArbCom mailing list. was probably a statement along the lines of "knows how to deal with Mailman". And I think you're getting that role mixed up with the actual person doing the work management: the Arbitration Committee has decided to appoint one of its sitting arbitrators to act as coordinator (emphasis mine). Izno (talk) 23:46, 6 December 2024 (UTC)

Obviously I have no personal knowledge of what ended up happening. I just listed the responsibilities as described at Misplaced Pages:Arbitration Committee/Noticeboard/Archive 0 § Improving ArbCom co-ordination. I'm not sure what I'm getting mixed up; all I said is that a co-ordinator and deputy were appointed, and that a former arbitrator was said to be co-ordinating the mailing list. It's certainly possible the split of duties changed from the first post in the archive. isaacl (talk) 00:01, 7 December 2024 (UTC)

Oh, I see that now. Izno (talk) 00:04, 7 December 2024 (UTC)

I think I agree with Izno regarding the coordinating arbitrator role. There's no problem letting the community that the role exists, but I don't think it's necessary for the role's responsibilities to be part of the public-facing guarantees being made to the community. If the role needs to expand, shrink, split into multiple roles, or otherwise change, the committee should feel free to just do it as needed. The committee has the flexibility to organize itself as it best sees fit. isaacl (talk) 23:36, 6 December 2024 (UTC)

I think this is the right approach. It doesn't need to be advertised who is coordinating activity on the mailing list, it just needs to get done. If it takes two people, fine, if they do it for six months and say they want out of the role, ask somebody else to do it. And so on. Just Step Sideways 23:50, 6 December 2024 (UTC)

For instance, I don't think it's necessary to codify whether or not the coordinating arbitrator role is permanent. Just put a task on the schedule to review how the role is working out in nine months, and then modify the procedure accordingly as desired. isaacl (talk) 23:32, 9 December 2024 (UTC)

One exception: the first bullet point regarding responding to communications and assigning a tracking identifier does involve the committee's interactions with the community. I feel, though, that for flexibility these guarantees can be made without codifying who does them, from the community's point of view. (It's fine of course to make them part of the coordinating arbitrator's tasks.) isaacl (talk) 23:41, 6 December 2024 (UTC)

Izno, this actually sounds like a helluva lot of work, maybe not minute-wise but mental, keeping track of everything so requests don't fall through the cracks. I think anyone assuming this role should get a break from, say, drafting ARBCOM cases if nothing else. Liz 03:49, 7 December 2024 (UTC)

It might be a lot of work, but it wasn't the bulk of the work, even for the work that I was doing. There was a lot more steps to being the appeal-focused admin above. Izno (talk) 04:02, 7 December 2024 (UTC)

You made me laugh, Liz. That sounds like my normal start-of-day routine, to be accompanied by a cup of tea and, perhaps, a small breakfast. I'd expect most arbitrators to be reading the mail on a daily basis, unless they are inactive for some reason; the difference here is the tagging/flagging of messages and clearing the filters, which probably adds about 10-12 minutes. I'll simply say that any arb who isn't prepared to spend 30-45 minutes/day reading emails probably shouldn't be an arb. That's certainly a key part of the role. Risker (talk) 04:43, 7 December 2024 (UTC)

+1. In my thoughts to potential candidates I said an hour a day for emails but that included far more appeals than the committee gets now. Best, Barkeep49 (talk) 04:47, 7 December 2024 (UTC)

Never mind reading emails, the bulk of my private ArbCom time was spent on processing them: doing checks, reporting results, and otherwise responding to other work. You can get away with just reading internal emails, but it's going to surprise your fellow arbs if you don't pipe up with some rational thought when you see the committee thinking about something personally objectionable and the first time they hear about it is when motions have been posted and are waiting for votes. Izno (talk) 06:17, 7 December 2024 (UTC)

Right now, I check my email account about once a week. I guess that will change if I'm elected to the committee. It would have helped to hear all of these details before the election. Liz 08:41, 7 December 2024 (UTC)

My hour included time to respond to emails, though I also note you're not going particularly deep on anything with that time (at least when ArbCom had more appeals). Best, Barkeep49 (talk) 16:26, 7 December 2024 (UTC)

Now that I'm off the committee and have had a moment to compile some fairly accurate stats, here was the committee's email load over the last four years:

• 2024: 6435 emails in 1040 distinct threads
• 2023: 7826 emails in 1093 distinct threads
• 2022: 7679 emails in 1103 distinct threads
• 2021: 9687 emails in 1271 distinct threads

These are undercounts of the true email load, because this only counts the main arbcom-en list and not the clerks-l, arbcom-en-b, and arbcom-en-c lists, all of which are used for ArbCom-related purposes. But hopefully this gives a general flavor for why, when I was on the committee, I viewed better managing the email workflow as a priority for the committee. My guess would be that these email rates are substantially higher than most, and quite possibly all, other volunteer-driven committees within the Wikimedia movement. Best, KevinL (aka L235 · t · c) 23:51, 3 January 2025 (UTC)

By the way, I just did some counting and clerks-l had 2724 emails in the four-year period between 2021 and 2024 — which is substantially down from the average rate from when I was a clerk. Best, KevinL (aka L235 · t · c) 23:54, 3 January 2025 (UTC)

Currently, motion 3 passes and other motions fail. If there is no more !votes in 3 days, I think this case can be closed. Kenneth Kho (talk) 17:31, 10 January 2025 (UTC)

• WP:AE
• WP:ARE

Please use this page only to:

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

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

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

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

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

Request concerning PerspicazHistorian

User who is submitting this request for enforcement

NXcrypto (talk · contribs · deleted contribs · logs · filter log · block user · block log) 15:53, 19 December 2024 (UTC)

User against whom enforcement is requested

PerspicazHistorian (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced

WP:ARBIPA

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

1. 17:57, 18 December 2024 - removed "discrimination" sidebar from the page of Hindutva (fascist ideology) even though the sidebar was inserted inside a section, not even the lead.
2. 17:59, 18 December 2024 - tag bombed the highly vetted Hindutva article without any discussion or reason
3. 10:15, 18 December 2024 - attributing castes to people withhout any sources
4. 12:11, 18 December 2024 - edit warring to impose the above edits after getting reverted
5. 17:09, 18 December 2024 - just like above, but this time he also added unreliable sources
6. 18:29, 18 December 2024 - still edit warring and using edit summaries instead of talk page for conversation
7. 14:46, 19 December 2024 (UTC) - filed an outrageous report on WP:ANI without notifying any editors. This report was closed by Bbb23 as "This is nothing but a malplaced, frivolous personal attack by the OP."

Diffs of previous relevant sanctions, if any

• Already 2 blocks in last 4 months for edit warring.

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

Additional comments by editor filing complaint

I do not see any positive signs that this editor will ever improve. So far he has only regressed. Nxcrypto Message 15:53, 19 December 2024 (UTC)

While going through this report, PerspicazHistorian has made another highly problematic edit here by edit warring and misrepresenting the sources to label the organisation as "terrorist". This primary source only provides a list of organisations termed by the Indian government as "terrorist" contrary to MOS:TERRORIST. Nxcrypto Message 03:12, 20 December 2024 (UTC)

• PerspicazHistorian is still using unreliable Raj era sources (see WP:RAJ) and wishing to move Shivaji to Chhatrapati Shivaji Maharaj which is a blatant POV. Nxcrypto Message 04:39, 29 December 2024 (UTC)

Notification of the user against whom enforcement is requested

Discussion concerning PerspicazHistorian

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

Statement by PerspicazHistorian

• By far I am also concerned how my edits were forcefully reverted without a proper reason despite providing enough references. Please check how I am getting attacked by them on Chandraseniya_Kayastha_Prabhu Page.

I didn't know about the three-revert-rule before User: Ratnahastin told me about this: User_talk:PerspicazHistorian. Please grant me one more chance, I will make sure not to edit war.

• In the below statement by LukeEmily, As a reply I just want to say that I was just making obvious edit on Chandraseniya_Kayastha_Prabhu by adding a list of notable people with proper references. And according to Edit_warring#What_edit_warring_is it is clearly said: "Edits from a slanted point of view, general insertion or removal of material, or other good-faith changes are not considered vandalism." It was a good faith edit but others reverted it. I accept my mistake of not raising it on talk page as a part of Misplaced Pages:BOLD,_revert,_discuss_cycle.
  
• As a clarification to my edit on Students' Islamic Movement of India, it can be clearly seen that I provided enough reference to prove its a terrorist organisation as seen in this edit. I don't know why is there a discussion to this obvious edit? Admins please correct me if I am wrong.

@Valereee, Yes I read about 1RR and 0RR revert rules in Misplaced Pages:Edit warring#What edit warring is#Other revert rules. I now understand the importance of raising the topic on talk page whenever a consensus is needed. Thank You ! PerspicazHistorian (talk) 07:16, 20 December 2024 (UTC)

Yes, I will commit to that. PerspicazHistorian (talk) 13:10, 20 December 2024 (UTC) Moved comment to own section. Please comment, including replies, only in this section. Seraphimblade 13:19, 20 December 2024 (UTC)

At that time I was new to how AFD discussions worked. Later on when Satish R. Devane was marked for deletion, I respected the consensus by not interfering in it. The article was later deleted. PerspicazHistorian (talk) 11:54, 21 December 2024 (UTC)

• Hi @Doug Weller , I just checked your user page. You have 16 years (I am 19) of experience on wiki, you must be right about me. I agree that my start on Misplaced Pages has been horrible, but I am learning a lot from you all. I promise that I will do better, get more neutral here and contribute to the platform to my best. Please don't block me.

P.S.- I don't know If I will be blocked or what , according to this enforcement rules, I just want to personally wish good luck to you for your ongoing cancer treatments, You will surely win this battle of Life. Regards. PerspicazHistorian (talk) 12:23, 21 December 2024 (UTC)Moved comment to own section. Please comment, including replies, only in this section.Valereee (talk) 15:30, 24 December 2024 (UTC)

• 1) I just asked an user @Fylindfotberserk if the page move is possible. What's wrong with it? I still have not considered putting a move request on talk page of article.

2) Many of other sources are not raj era. Moreover I myself have deleted the content way before you pointing this out. Thank You ! PerspicazHistorian (talk) 06:29, 29 December 2024 (UTC)

even @NXcrypto is seen engaged in edit wars before on contentious Indian topics. see1see2 PerspicazHistorian (talk) 06:37, 29 December 2024 (UTC)

as mentioned by @Valereee before, _{Please discuss at talk, not here; we don't deal with content here}. You can discuss content related topics on talk pages of articles rather than personally targeting a user here in enforcement. PerspicazHistorian (talk) 06:42, 29 December 2024 (UTC)

@Valereee I once filed a complaint to find it @NXcrypto is a sock (out of a misunderstanding, as all were teamed up similarly on various pages). I think he felt it as a personal attack by me and filed this request for enforcement. Please interfere. PerspicazHistorian (talk) 06:47, 29 December 2024 (UTC) moving to correct section Valereee (talk) 13:24, 29 December 2024 (UTC)

• Hi @Toddy1 @Valereee, In my defense I just want to say that

1)Yes I usually edit on RSS related topics, but to ensure a democratic view is maintained as many socks try to disrupt such articles. Even on Rashtriya Swayamsevak Sangh page, I just edited on request of talk page and added a graph. I don't think its a POV push.

2) My main interest in editing is Hinduism and Indian History topics.

3)There have been certain cases in past where I was blocked but if studied carefully they were result of me edit warring with socks(although, through guidance of various experienced editors and admins I learnt a SPI should be filed first). I have learnt a lot in my journey and there have been nearly zero case of me of edit warring this month.

Please do not block me. PerspicazHistorian (talk) 14:09, 29 December 2024 (UTC)

• @Valereee I beg apologies for the inconvenience caused, thanks for correcting me. I will now reply in my own statement section. @Bishonen I am a quick learner and professionally competent to edit in this encyclopedic space. Please consider reviewing this enforcement if its an counter-attack on me as mentioned in my previous replies. You all are experienced editors and I have good faith in your decision-making capability.PerspicazHistorian (talk) 08:27, 30 December 2024 (UTC)
• @Vanamonde93@Bishonen I have edited content marked as "original research" and "mess" by you, I am ready to help removing any content that might be considered "poorly sourced" by the community. Please don't block me.PerspicazHistorian (talk) 08:27, 30 December 2024 (UTC)
• @Valereee This enforcement started for edit-warring and now I feel its more concerned to my edited content(which I agree to cooperate and change wherever needed). After learning about edit wars, there has been no instance of me edit-warring, Please consider my request.--PerspicazHistorian (talk) 08:27, 30 December 2024 (UTC)

  @Valereee I am not a slow learner, I understand the concerns of all admins here. I will try my best to add only reliable sources, and discuss content in all talk pages, as I already mentioned here. PPicazHist (talk) 12:55, 30 December 2024 (UTC)

  @Valereee@UtherSRG I think admins should focus more on encouraging editors when they do good and correct when mistaken. I have made many edits, added many citations and created much articles which use fine citations. The enforcement started out of retaliation by nxcrypto, now moving towards banning me anyways. I started editing out of passion, and doing it here on wiki unlike those who come here just for pov pushes and disrupt article space(talking about socks and vandalizers on contentious Indian topics).

  The article prasada doesn't only has issue on citations, but the whole article is copypasted from the citations I added. I just wanted to point that out. Remaining about Misplaced Pages:CIR, I am currently pursuing Btech in cs from IIT delhi, idt I am a slow learner by any means. Still, happy new year to all ! PPicazHist (talk) 14:01, 31 December 2024 (UTC)

  @UtherSRG You mean to say, "_{The prasada is to be consumed by attendees as a holy offering. The offerings may include cooked food, fruits and confectionery sweets. Vegetarian food is usually offered and later distributed to the devotees who are present in the temple. Sometimes this vegetarian offering will exclude prohibited items such as garlic, onion, mushroom, etc. "} is not copy pasted by this website? Is this also a wiki mirror website? How would you feel if I doubt your competence now? PPicazHist (talk) 14:47, 31 December 2024 (UTC)

  @ UtherSRG I just asked others to share their opinion in the enforcement. With all due respect, I don't think its wrong in any sense. PPicazHist (talk) 15:13, 8 January 2025 (UTC)

  To all the admins involved here,

  • I agree to keep learning and apologize if my previous edits/replies have annoyed the admins.
  • I have not edit warred since a month and please see it as my willingness to keep learning and getting better.
  • Please give me a chance, I understand concern of you all and respect your opinion in the matter. But please don't block me from editing from main article space. I promise that I will abide by all the rules and will learn from other editors.

  PPicazHist (talk) 15:22, 8 January 2025 (UTC)

Statement by LukeEmily

PerspicazHistorian also violated WP:BRD by engaging in an edit war with Ratnahastin who reverted his edits and restored an article to a stable version by admin. Also, I want to assume good faith but it is surprising that PerspicazHistorian claims that he did not know the three revert rule given that he has more than 800 edits.LukeEmily (talk)

Statement by Doug Weller

I'm involved so just commenting. I don't think this editor is competent. I had to give them a community sanction caste warning as they were making a mess of castes. See this earlier version of their talk page.]https://en.wikipedia.org/search/?title=User_talk:PerspicazHistorian&oldid=1262289249] and User:Deb's comment that "It was very unwise of you to keep moving Draft:Satish R. Devane to article space when it has not passed review. As a direct result of your actions, a deletion discussion is taking place, and when this is complete and the article is deleted, you will be prevented from recreating it. Deb (talk) 14:44, 4 December 2024 (UTC)" There have also been copyright issues. I strongly support a topic ban. Doug Weller talk 11:00, 21 December 2024 (UTC)

I won't be involved in the decision. No more treatments for me, just coast until... Doug Weller talk 12:50, 21 December 2024 (UTC)

Statement by Toddy1

This is another editor who appears to have pro-Rashtriya Swayamsevak Sangh (RSS) and pro-Bharatiya Janata Party (BJP) views. I dislike those views, but find it rather alarming that Misplaced Pages should seek to censor those views, but not the views of the political opponents. Imagine the outrage if we sought to topic-ban anyone who expressed pro-Republican views, but allowed Democrat-activists to say whatever they liked.

A lot of pro-RSS/BJP editors turn out to be sock-puppets, so please can we do a checkuser on this account. And to be even-handed, why not checkuser NXcrypto too.

If we want to talk about WP:CIR when editors make mistakes, look at the diff given by NXcrypto for "Notification of the user against whom enforcement is requested" - it is the wrong diff. He/she did notify PerspicazHistorian - but the correct diff is .

A topic ban from Indian topics would be unhelpful, unless given to both parties. Misplaced Pages is meant to be a mainstream encyclopaedia, and BJP and RSS are mainstream in India. Loading the dice against BJP and RSS editors will turn Misplaced Pages into a fringe encyclopaedia on Indian topics.

I can see a good case for restricting PerspicazHistorian to draft articles and talk pages for a month, and suggesting that he/she seeks advice from more experienced editors. Another solution would be a one-revert rule to last six months.-- Toddy1 (talk) 13:55, 29 December 2024 (UTC)

Statement by Capitals00

I find the comment from Toddy1 to be entirely outrageous. What are you trying to tell by saying "Misplaced Pages is meant to be a mainstream encyclopaedia, and BJP and RSS are mainstream in India"? If you want us to entertain those who are in power, then we could never have an article like False or misleading statements by Donald Trump.

You cannot ask topic ban for both editors without having any evidence of misconduct. Same way, you cannot ask CU on either user only for your own mental relief. It is a high time that you should strike your comment, since you are falsely accusing others that they "seek to censor" this editor due to his "pro-Rashtriya Swayamsevak Sangh (RSS) and pro-Bharatiya Janata Party (BJP) views". You should strike your comment. If you cannot do that, then I am sure WP:BOOMERANG is coming for you. Capitals00 (talk) 15:20, 29 December 2024 (UTC)

Statement by Vanamonde93

Toddy1: I, too, am baffled by your comment. We don't ban editors based on their POV; but we do ban editors who fail to follow our PAGs, and we certainly don't make excuses for editors who fail to follow our guidelines based on their POV. You seem to be suggesting we cut PH some slack because of their political position, and I find that deeply inappropriate. Among other things, I don't believe they have publicly stated anywhere that they support the BJP or the RSS, and we cannot make assumptions about them.

That said, the fact that this was still open prompted me to spot-check PH's contributions, and I find a lot to be concerned about. This edit is from 29 December, and appears to be entirely original research; I cannot access all of the sources, but snippet search does not bear out the content added, and the Raj era source for the first sentence certainly does not support the content it was used for. Baji Pasalkar, entirely authored by PH, is full of puffery ("first to sacrifice his life for the cause of Swarajya", and poor sources (like this blog, and this book, whose blurb I leave you to judge), from which most of the article appears to be drawn. Appa (title), also entirely authored by PH, has original research in its very first sentence; the sources that I can access give passing mention to people whose names include the suffix "appa", and thus could perhaps be examples of usage, but the sources most certainly do not bear out the claim.

I will note in fairness that I cannot access all the sources for the content I checked. But after spotchecking a dozen examples I have yet to find content PH wrote that was borne out by a reliable source, so I believe skepticism is justified. We are in territory where other editors may need to spend days cleaning up some of this writing. Bishonen If we're in CIR territory, just a normal indefinite block seems cleanest, surely? Or were you hoping that PH would help clean up their mess, perhaps by providing quotes from sources? That could be a pathway to contributing productively, but I'm not holding my breath. Vanamonde93 (talk) 18:00, 29 December 2024 (UTC)

Thanks Bish: I agree, as my exchanges with PH today, in response to my first post here, have not inspired confidence. . Vanamonde93 (talk) 20:22, 29 December 2024 (UTC)

Statement by UtherSRG

I've mostly dealt with PH around Misplaced Pages:Articles for deletion/Ankur Warikoo (2nd nomination). They do not seem to have the ability to read and understand our policies and processes. As such, a t-ban is too weak. The minimum I would support is a p-block as suggested below, though a full indef is also acceptable. They could then ask for the standard offer when they can demonstrate they no longer have WP:CIR issues. - UtherSRG (talk) 20:05, 30 December 2024 (UTC)

Based on these two edits, I'm more strongly leaning towards indef. - UtherSRG (talk) 12:27, 31 December 2024 (UTC)

They now indicate they believe the article they edited was copied from one of the websites they used as a reference, when in reality the website is a mirror/scrape of the Misplaced Pages article. I believe we are firmly in WP:CIR territory here. - UtherSRG (talk) 14:25, 31 December 2024 (UTC)

This is a mirror of the Misplaced Pages article. - UtherSRG (talk) 16:29, 31 December 2024 (UTC)

Result concerning PerspicazHistorian

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

PerspicazHistorian, can you explain your understanding of WP:edit warring and the WP:3RR rule? I'd like you to read thoroughly enough to also explain wny someone may be edit warring even if they aren't breaking 3RR. Valereee (talk) 21:58, 19 December 2024 (UTC)

@PerspicazHistorian, that explanation of edit warring is a bit wanting. An edit war is when two or more editors revert content additions/removals repeatedly. Even a second reversion by the same editor can be considered edit warring. Best practice -- and what I highly recommend, especially for any inexperienced editor -- is the first time someone reverts an edit of yours, go to the talk page, open a section, ping the editor who reverted you, and discuss. Do you think you can commit to that?

Re: your question on why your "obvious edit" was reverted: we don't deal with content issues here, only with behavior issues, but from a very quick look, the source is 50 years old, and using a list headed "TERRORIST ORGANISATIONS LISTED IN THE FIRST SCHEDULE OF THE UNLAWFUL ACTIVITIES (PREVENTION) ACT, 1967" that includes a certain organization as a source that the organization should be described as a terrorist organization is WP:ORIGINAL RESEARCH; in their revert NXcrypto provided an edit summary of "Not a reliable source for such a contentious label. See WP:LABEL." Please discuss at talk, not here; we don't deal with content here. Valereee (talk) 11:28, 20 December 2024 (UTC)

I'm seeing this as a CIR issue. I'd like input from other admins, if possible. I'm a little concerned that setting a tban from IPA is just setting a trap. Maybe a p-block from article space would be a kinder way to allow them to gain some experience? Valereee (talk) 13:28, 29 December 2024 (UTC)

@PerspicazHistorian, have you seen how many times I or others have had to move your comments to your own section? This is an example of not having enough experience to edit productively. Please do not post in anyone else's section again. Valereee (talk) 16:09, 29 December 2024 (UTC)

I do agree we're in CIR territory, and the concerns expressed are completely valid. I don't think this editor is ill-intentioned. They just don't seem very motivated to learn quickly. Well-intentioned-but-a-slow-learner is something that can only be fixed by actually practicing what you're bad at. I'd prefer an indef from article space which gives them one more chance to learn here before we send them off to mr.wiki or Simple English to try to learn. Not a hill I'm going to die on, though. Valereee (talk) 11:36, 30 December 2024 (UTC)

@PerspicazHistorian, like Uther I have major concerns about the edit you made yesterday, which included replacing a citation needed tag with these sources. The first is a company that markets astrology services. The second is the site for a religious sect. Neither is a reliable source for explaining the concept of prasada in Wikivoice. You made this edit yesterday, after you'd confirmed here and on my talk that you understood sourcing policy.

The reason for an indef from article space is to allow you to learn this policy: You would go into article talk and suggest sources to fix citation needed tags. Another editor would have to agree with you that the sources are reliable before they'd add them. Valereee (talk) 12:51, 31 December 2024 (UTC)

• A tban from IPA for PerspicazHistorian would be a relief to many editors trying to keep this difficult area in reasonable shape. However, Valereee makes a good point about 'setting a trap': it's doubtful that PH would be able to keep to a tban even if they tried in good faith. I would therefore support a p-block from article space. Bishonen | tålk 16:48, 29 December 2024 (UTC).

  Vanamonde93, no, I don't really think PH can usefully help clean up their mess; I was following Valereee, who has been going into this in some depth, in attempting to keep some way of editing Misplaced Pages open for PH. It's a bit of a counsel of desperation, though; there is very little daylight between an indef and a p-block from article space. Yes, we are in CIR territory; just look at PH's recent supposed evidence on this page for NXcrypto being "engaged in edit wars before on contentious Indian topics": one diff of an opponent complaining on NXcrypto's page, and one diff of somebody reverting NXcrypto. What do those actually prove? That NXcrypto has opponents (big surprise). So, yes, as you suggest, I'll support an indef as well. Bishonen | tålk 20:09, 29 December 2024 (UTC).

• Is there a length of time proposed for the p-ban or would it be indefinite? Barkeep49 (talk) 17:06, 3 January 2025 (UTC)

  I would say indefinite; not infinite, but I'd be wary about letting them back into articlespace without some kind of preclearance. theleekycauldron (talk • she/her) 18:39, 3 January 2025 (UTC)

• It looks to me like there is a consensus for an indefinite partial block for PerspicazHistorian from article space. Unless any uninvolved admin objects within a day or so, I will close as such. Seraphimblade 06:31, 7 January 2025 (UTC)

  Given PH's recent slew of requests on multiple admin talk pages, yes, please do. - UtherSRG (talk) 12:58, 8 January 2025 (UTC)

References

1. "Significance of Different Type of Prasad in Hinduism For God". GaneshaSpeaks. Retrieved 2024-12-30.
2. "What Is Prashad". Shree Swaminarayan Mandir Bhuj. Retrieved 2024-12-30.

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

Request concerning AstroGuy0

User who is submitting this request for enforcement

Hemiauchenia (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:41, 4 January 2025 (UTC)

User against whom enforcement is requested

AstroGuy0 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced

Misplaced Pages:Contentious topics/Race and intelligence

(Even though this isn't the usual R&I fare, I consider the intersection of "Race/ethnicity and sex offending", to come under "the intersection of race/ethnicity and human abilities and behaviour")

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

1. 03:19, 4 January 2025 Asserts that "A majority of the perpetrators were Pakistani men" despite the cited source (freely accessible at ) does not mention the word "Pakistani" or any variant once.
2. 01:40, 4 January 2025 Describes the sex offender ring as "Pakistani" in the opening sentence when the cited source in the body says that they were only "mainly Pakistani"

Diffs of previous relevant sanctions, if any

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

Made aware of contentious topics criterion: 01:52, 4 January 2025

Notification of the user against whom enforcement is requested

Additional comments by editor filing complaint:

This new user seems intent on POVPUSHING regarding "Asian/Muslim grooming gangs" and making contentious claims that are not backed up by sources. Hemiauchenia (talk) 03:44, 4 January 2025 (UTC)

Discussion concerning AstroGuy0

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

Statement by AstroGuy0

Statement by Iskandar323

This rather dated "Asian/Muslim grooming gangs" malarkey from the UK has recently been pushed on social media by a certain US tech billionaire and is now recirculating in right-wing social media and the blogosphere, partly in connection with UK politics, so this trend could flare before it dims. Iskandar323 (talk) 03:50, 4 January 2025 (UTC)

Statement by (username)

Result concerning AstroGuy0

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

The second diff was before AG0 received a CTOP alert. I've alerted AG0 to other CTOPs that they've edited in, and I am going to warn them for their conduct in diff #1 without prejudice to other admins determining that further action is warranted. voorts (talk/contributions) 04:33, 4 January 2025 (UTC)

I also looked at the source, and it indeed does not in any way support the claim made; it does not mention "Pakistani" even once. This is a fairly new editor, but I think we need to make it very clear to them that misrepresentation of sources is not something we will tolerate. Seraphimblade 04:59, 5 January 2025 (UTC)

Given that AstroGuy0 has already been issued a warning, I don't think anything further is necessary, and will close as such unless any uninvolved admin shortly objects. Seraphimblade 18:23, 6 January 2025 (UTC)

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

Request concerning Lemabeta

User who is submitting this request for enforcement

EF5 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 20:18, 5 January 2025 (UTC)

User against whom enforcement is requested

Lemabeta (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced

Misplaced Pages:Requests for arbitration/Eastern Europe#Final decision

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

1. 5 Jan 2025 - Made a draft on a European ethnic group, which they are currently barred from doing.
2. 4 Jan 2025 - Started a page on a Georgian ethnologist.

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

• Previously blocked as a discretionary sanction or contentious topic restriction for conduct in the area of conflict, see the block log linked to above.

Additional comments by editor filing complaint

I likely filed this improperly, but to sum it up they continue to make pages in a scope they were banned from. E_F 20:25, 5 January 2025 (UTC)

On the bullet point, I’ve never filed an AE report before, and I wasn’t sure if “block” meant T-ban, p-block, etc., so I just picked whichever one made the most sense. E_F 21:45, 5 January 2025 (UTC)

(Not sure if I’m allowed to reply here) I’ve never filed an AE report before, and I wasn’t sure if “block” meant T-ban, p-block, etc., so I just picked whichever one made the most sense. E_F 21:45, 5 January 2025 (UTC)

Response to Bishonen. Moved from results section. voorts (talk/contributions) 21:58, 5 January 2025 (UTC)

(RES to Bishonen) That's fair. When starting the AE, it only gave me nine options, none of which seemed to fit right. The third bullet ("Previously given a discretionary sanction or contentious topic restriction or warned for conduct in the area of conflict on DIFF by _____") didn't seem to fit, as the sanction wasn't for verbal conduct. E_F 22:05, 5 January 2025 (UTC)

Notification of the user against whom enforcement is requested

Here

Discussion concerning Lemabeta

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

Statement by Lemabeta

Yeah, my bad. Didn't realize translation of a page of ethnographic group would count as a violation of my topic ban about "history of the Caucasus and its cultural heritage, broadly construed" I recognize my mistake. --Lemabeta (talk) 20:30, 5 January 2025 (UTC)

Ethnographic groups and cultural heritage are related but distinct concepts. An ethnographic group refers to a community of people defined by shared ancestry, language, traditions, and cultural identity. In contrast, cultural heritage refers to the *practices, artifacts, knowledge, and traditions preserved or inherited from the past. But cultural heritage is indeed a component of ethnographic groups.

So i don't believe ethnographic group should be considered as either history of the Caucasus or cultural heritage. Lemabeta (talk) 20:56, 5 January 2025 (UTC)

In my opinion, cultural heritage (both tangible and intangible) emerges from ethnographic groups but does not define the group itself. Lemabeta (talk) 20:57, 5 January 2025 (UTC)

I think ethnographic groups fall under the category of Ethnography, or even socio-cultural antropology but for sure not cultural heritage. Lemabeta (talk) 21:09, 5 January 2025 (UTC)

I understand, i already apologized on my talk page for this accident. I will not repeat this mistake again. Lemabeta (talk) 21:13, 5 January 2025 (UTC)

Statement by (username)

Result concerning Lemabeta

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

• I don't see Lemabeta mentioned in the case itself, but they're currently under a topic ban imposed by a consensus of AE admins from "the history of the Caucasus and its cultural heritage, broadly construed". theleekycauldron (talk • she/her) 20:26, 5 January 2025 (UTC)

  To be fair, when you click above to add a new enforcement request, the template states:
  ;Sanction or remedy to be enforced: ]
  <!--- Link to the sanction or remedy that you ask to be enforced ---> voorts (talk/contributions) 20:32, 5 January 2025 (UTC)

• Didn't realize translation of a page of ethnographic group would count as a violation of my topic ban about "history of the Caucasus and its cultural heritage, broadly construed" @Lemabeta: what did you think "the history of the Caucasus and its cultural heritage" meant? I think it's pretty obvious that that an article on an ethnic group from the Caucasus and about an ethnologist who writes about that region is covered by your topic ban. voorts (talk/contributions) 20:37, 5 January 2025 (UTC)

  Note that I've deleted Draft:Rachvelians as a clear G5 violation. I think Mate Albutashvili is a bit more of a questionable G5. voorts (talk/contributions) 20:46, 5 January 2025 (UTC)

  Your definition of "ethnographic group" includes the phrases "shared ancestry" (i.e., history), and "shared ... traditions" and "shared ... cultural identity" (i.e., cultural heritage). Your attempt to exclude "ethnographic group" from either of the two categories in your topic ban is entirely unpersuasive, particularly since your topic ban is to be "broadly construed". voorts (talk/contributions) 21:13, 5 January 2025 (UTC)

  @Tamzin: this doesn't seem like a mistake to me, but I'm okay with a logged warning here. voorts (talk/contributions) 21:29, 5 January 2025 (UTC)

  @Bishonen: This is about violating the TBAN. Per my response to leek, I think the issue is with the AE request template, which is a bit unclear. voorts (talk/contributions) 22:00, 5 January 2025 (UTC)

  @Bishonen: I don't think a block is needed here, but the next violation, definitely. voorts (talk/contributions) 22:06, 5 January 2025 (UTC)

  @EF5: They were "reviously given ... contentious topic restriction", the topic ban at issue. voorts (talk/contributions) 22:09, 5 January 2025 (UTC)

• @Lemabeta: Not every single thing you could write about an ethnic group would fall under cultural history, but that's not really relevant on the Rachvelians page, where the History section was entirely about their cultural history, even containing the words highlighting their ethnographic and cultural identity. There's a reason we use the words "broadly construed" on most TBANs, and a reason we encourage people to act like they're TBANned from a broader area than they are. (Consider: Would you feel safe driving under a bridge where clearance is exactly the same height as your vehicle? Or would you need a few inches' gap to feel safe doing it?)This does seem like a good-faith misunderstanding, so if you will commit to not making it again in the future, I think this can be closed with a clarification/warning. But that's an important "if". If you want to argue semantics, then the message that sends to admins is that you don't intend to comply with the TBAN, in which case the next step would be a siteblock. -- Tamzin (they|xe|🤷) 21:10, 5 January 2025 (UTC)
• EF5, I don't understand your "Previously blocked as a discretionary sanction or contentious topic restriction for conduct in the area of conflict, see the block log linked to above" statement, can you please explain what it refers to? This T-ban? Lemabeta's block log is blank.

That said, I'm unimpressed by Lemabeta's lawyerly distinctions above, and also by their apology for "accidental violations". I'll AGF that they were accidental, but OTOH, they surely ought to have taken enough care to realize they were violations; compare Voorts' examples. I suggest a block, not sure of what length. A couple of weeks? Bishonen | tålk 21:36, 5 January 2025 (UTC).

EF5, OK, I see. Blocks and bans are very different, and the block log only logs blocks. Bishonen | tålk 22:02, 5 January 2025 (UTC).

• It seems that the general consensus here is to treat this as a final warning, and Lemabeta has acknowledged it as such. Unless any uninvolved admin objects within the next day or so, I will close as such. Seraphimblade 01:16, 11 January 2025 (UTC)

I was blocked from Misplaced Pages for ignoring the formatting of a table, I edited an article wrong, Bajii banned me for 2 weeks, but it didn't even take 1 and Hasley changed it to permanent, I tried to make an unban request, they deleted it and blocked my talk page. I asked for help on irc, an admin tried to help me make another unblock request, but the admin jem appeared and told me that I was playing the victim and banned me and expelled me from irc. I just want to contribute to the platform GokuJuan (talk) 20:11, 10 January 2025 (UTC)

@GokuEltit: This is a complaint about Spanish Misplaced Pages - see es:Especial:Contribuciones/GokuJuan, where you have a block history from August 2023 to September 2024 (machine translation). Your block affects Spanish-language Misplaced Pages - it does not affect English-language Misplaced Pages.-- Toddy1 (talk) 20:27, 10 January 2025 (UTC)

You also had some blocks on Commons, but they have expired.-- Toddy1 (talk) 20:30, 10 January 2025 (UTC)

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

Request concerning Boy shekhar

User who is submitting this request for enforcement

Daniel Quinlan (talk · contribs · deleted contribs · logs · filter log · block user · block log) 06:34, 11 January 2025 (UTC)

User against whom enforcement is requested

Boy shekhar (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced

Misplaced Pages:Contentious topics/India, Pakistan, and Afghanistan

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

• This edit violates the topic ban because it is in the topic area. It's also based on an unreliable source and the section header includes a derogatory term.

Diffs of previous relevant sanctions, if any

• Here is the topic ban for persistent insertion of original research, use of unreliable sources or no sources at all, and tendentious editing.

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

• Previously given a discretionary sanction or contentious topic restriction or warned for conduct in the area of conflict on 14 August 2020 by Doug Weller (talk · contribs · blocks · protections · deletions · page moves · rights · RfA).
• Alerted about discretionary sanctions or contentious topics in the area of conflict, on 15 March 2020 (see the system log linked to above).

Additional comments by editor filing complaint

• I've edited the article so I am involved. Daniel Quinlan (talk) 06:34, 11 January 2025 (UTC)

@Vanamonde93: No, I don't think you're being too harsh. I think you're right. My thinking was that if I was uninvolved, I would have blocked them under WP:CT/IPA so I sleepily submitted it here last night instead of ANI, which is what I should have done. Daniel Quinlan (talk)

Notification of the user against whom enforcement is requested

• Diff of the AE notification

Discussion concerning Boy shekhar

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

Statement by Boy shekhar

Statement by Vanamonde

This user hasn't edited for 4.5 years since they were TBANned, and none of their 31 edits show any ability to follow our PAGs. At the risk of sounding harsh, an extended AE discussion is a waste of time; a passing admin should indef them (I cannot, I am INVOLVED on most of the content they have edited). Vanamonde93 (talk) 23:26, 11 January 2025 (UTC)

@Daniel Quinlan: Apologies if that sounded like a criticism of you, it wasn't intended as such: I'm just advocating for the first uninvolved admin who sees this to block and close. Vanamonde93 (talk) 00:14, 12 January 2025 (UTC)

Result concerning Boy shekhar

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

• Vanamonde93's assessment is spot on, the edit in question is the kind of gross violation of WP:NPA we indef people for on the spot even when it's not a TBAN violation. Blocked as a regular admin action. Although I will say, without knowing how exactly Vanamonde93 is involved here, this is so far beyond the pale that they could have gone ahead and blocked on an "any reasonable admin" basis. _signed, Rosguill 04:49, 12 January 2025 (UTC)