Misplaced Pages

:Arbitration/Requests: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 22:30, 12 January 2009 view sourceTennis expert (talk | contribs)24,261 edits Statement from Tennis expert: spelling it out← Previous edit Latest revision as of 03:40, 31 January 2023 view source AmandaNP (talk | contribs)Edit filter managers, Autopatrolled, Bureaucrats, Checkusers, Oversighters, Administrators45,699 edits What the actual fuckTags: Replaced Undo 
Line 1: Line 1:
{{Short description|Wikimedia project page}}
{{pp-semi-protected|small=yes}}{{pp-move-indef}}
<noinclude>{{pp-protected|small=yes}}{{pp-move-indef}}</noinclude>
{{active editnotice}} <!-- See ] -->
{{/Header}}
<!--- the "EditNotice"—text displayed only whilst editing—for this page is located at MediaWiki:Editnotice-4-Requests for arbitration .--->
{{/Case}}
:''WP:RFAR redirects here. You may be looking for ] (]).''
{{/Clarification and Amendment}}
{{/Header}} <!-- front matter of this page-->
{{/Motions}}
{{/Enforcement}}


==Current requests== ]
]
<!-- ''None, currently'' -->
=== Date delinking ===
'''Initiated by ''' —] • ] • ] '''at''' 03:00, 10 January 2009 (UTC)

==== Involved parties ====
<!-- use {{admin|username}} if the party is an administrator -->
*{{userlinks|Locke Cole}}, ''filing party''
*{{userlinks|Tony1}}
*{{userlinks|Greg L}}
*{{userlinks|Lightmouse}}
**{{userlinks|Lightbot}}
*{{userlinks|Dabomb87}}
*{{userlinks|Ohconfucius}}
**{{userlinks|Date delinker}}
*{{userlinks|Guy Peters}}, ''co-filing''
*{{admin|Earle Martin}}, ''co-filing''
*{{userlinks|Colonies Chris}}

;Confirmation that all parties are aware of the request
<!-- All parties must be notified that the request has been filed, immediately after it is posted, and confirmation posted here. -->
*
*
*
*
*
*
*
*Colonies Chris has already made a statement below

;Confirmation that other steps in ] have been tried
This is in chronological order for the most part (where things don't overlap anyways).
<!-- Identify prior attempts at dispute resolution here, with links/diffs to the page where the resolution took place. If prior dispute resolution has not been attempted, the reasons for this should be explained in the request for arbitration -->

*]
*]
*] has hosted numerous discussions on this, the links below span from late August until December of 2008:
**]
***]
***]
***] (discussion supported a stop to date delinking)
**]
**]
**]
**] (Tony disparaging arguments as "I don't like it")
**]
**]
**]
**]
**]
**] (random editor annoyed that such a sweeping change wasn't discussed widely)
**] (perhaps one of the best examples of Tony1's incivility)
**]
**] (an example of Lightmouse's attitude)
**] (when I joined the fray)
**] (another editor who stayed away but noticed the damage being done)
**] (MOSNUM protected because of dispute, still protected to this day)
**]
**]
**] (initial discussion of an RFC on links/formatting)
*(various reports to ] (diffs available upon request))
*(various discussions on ] and ] (archive links available upon request))
*] (Tony1 RFC, late-November)
*] (MOSNUM's RFC, ran concurrently with the Tony1 RFC, also late November)
*] has discussion post-RFC as well, including one attempt at trying to go over the results (which failed):
**]
**]
**]
* ]

==== Statement by ] ====
This has been an ongoing content dispute for the past six months that has repeatedly degenerated into incivility and poor behavior on the part of the proponents of this change. At the moment we have editors using a single script to mass delink dates (collectively over thousands of articles) who have been asked to stop because their changes are disputed and do not have consensus. We've held numerous discussions, conducted a month long RFC (which involved the community and was listed in the watchlist) and have no consensus for these mass automated changes as they're being enacted. In a prior ArbCom decision it was stated:

{{"|Editors who are collectively or individually making large numbers of similar edits, and are apprised that those edits are controversial or disputed, are expected to attempt to resolve the dispute through discussion. It is inappropriate to use repetition or volume in order to present opponents with a fait accompli or to exhaust their ability to contest the change. This applies to many editors making a few edits each, as well as a few editors making many edits.|]}}

All of the editors involved in this dispute are aware of this decision (they were warned about it months ago), but they continue to operate under the assumption that their actions have consensus. I urge the committee to accept this case so the behavior (incivility, edit warring, stalking, personal attacks, and so forth) of those involved can be looked at. I understand the committee doesn't take up content disputes, but I fear this situation will not end without binding arbitration as those involved seem unwilling to consider compromises which don't involve automated date delinking. Thank you for your consideration. —] • ] • ] 03:00, 10 January 2009 (UTC)

; Motion request

If accepted I would request that the committee pass a motion stopping all automated or semi-automated edits of this fashion until the conclusion of arbitration. —] • ] • ] 03:00, 10 January 2009 (UTC)

; Limited response to Dabomb87

I do not believe Mediation or a Third Opinion would help here. We've already solicited the entire community via a watchlist notice, and a slightly uninvolved administrator (Masem) has tried multiple times to try and mediate the issue. To no avail, it seems. The core behavioral issue here is the incivility and the mass unlinking by automated means (the "]") while objections and disputes remain unresolved or unanswered. Further than that, there remains the disparaging behavior of those who simply wish to ignore objections ("this is a waste of time", "don't you have something better to do", "this is only being continued by a 'gang of five'", etc). Remarks which are unhelpful at reaching a consensus, I might add. —] • ] • ] 04:27, 10 January 2009 (UTC)

; Limited response to Tony1

I'm not asking the committee to decide the content dispute, I'm asking the committee to look at the behavior of those ''involved in the content dispute''. Specifically those running automated or semi-automated tools to force their preferred version on the rest of us, but also the uncivil behavior of those participating in the discussions. —] • ] • ] 09:34, 10 January 2009 (UTC)

; Limited response to Arthur Rubin and Masem

The overall goal of this, for me anyways, is to remove the ] from the table. This situation right now makes it impossible (or really difficult) to discuss the issue when a sense of inevitability pervades all discussions ("we're doing this, so talk all you want, but while you were typing that up, I delinked another hundred articles"). This inevitability isn't lost on the proponents of the change either: I get the general impression they feel empowered in these discussions to dismiss compromises and alternatives out of hand (yet another reason for the mass delinkings to stop). Hence my motion request. The community should be able to handle this, but not while editors are pushing their preferred version of things on the rest of us. Worth noting: there are {{NUMBEROFARTICLES}} articles on Misplaced Pages, I really doubt all of them have been delinked already. —] • ] • ] 11:56, 10 January 2009 (UTC)

; Response to Sam Blacketer

The fait accompli is from the sheer magnitude of the edits being performed. As John Vandenberg notes, Date delinker has performed nearly 9,000 edits of this variety. Unless those of us on the other side choose to engage in identical behavior (using a bot or semi-automatic script to relink dates) they effectively present us with a situation that's already to their liking. And the thing to keep in mind is that Date delinker isn't the only one performing these operations. It wouldn't surprise me if there were already 50,000 edits of this type (combined amongst all automated and semi-automated accounts). —] • ] • ] 00:11, 11 January 2009 (UTC)

==== Statement by ] ====
The diversity of the English Misplaced Pages means that disputes are inevitable, and it is unrealistic to believe that 100% support can be garnered for most things. The Date Linking RFCs clearly indicated that there ''is'' consensus against most, if not all, dates being linked (see my comment for a more detailed breakdown). Besides the RFCs, examples of this consensus against delinking dates exist in our ] and ], where the delinking of dates was accepted without any form of resistance, as well as ]. Second, Locke's point of incivility does not seem well-supported. The one instance in which inciviliy was considered a major problem, when a situation culminated in an RFC on ]'s conduct, the survey of attitudes there indicated that not only was Tony1's conduct within policy, but his delinking of dates was not disruptive at all. I would like to impress upon the Arbitrators that ''both sides'' of the debate have remained civil most of the time. Lastly, I do not believe that all other courses of dispute resolution have been used. Other than the Date Linking RFCs, there has been little interaction from editors, admin or not, to give their input. The ANI threads were usually importations of the heated MOSNUM discussions, and most of the admins at MOSNUM were somehow involved in the debate and could not provide a neutral third opinion. I will note that those who have been complaining about the date delinking are largely a small minority group. In most cases, when users have asked questions about the delinking activities, they are given a polite, easy-to-understand answer, which is usually accepted without much complaint. The fact that there has not been a flurry of new complaints demonstrates that there is significant consensus for the date delinkings to occur. Therefore, I ask that the Arbitration Commitee decline this case and allow other forms of dispute resolution, such as ] and ], to take place. ] (]) 03:42, 10 January 2009 (UTC)

==== Statement by ] ====
I really do want to avoid having my activities on one of my hobbies—Misplaced Pages—defined by the whims of others. So I expect (hope) to have a minimum of participation here. I just don’t want to be dragged down in the mud with unproductive bickering over something like how to format a date in an article. I have a practice of my own that is fully in compliance with MOSNUM as well as with the current community consensus according the latest RfCs. Note the beginning ]. As you can see, right at the beginning is a date, 7&nbsp;April 1795, that is unlinked. Further, since the SI’s kilogram is not closely associated with the United States, I elected to consistently use the international-style date format throughout the article. Note also the two date-related links, ] and ], that I added in the ] section of the ''Kilogram'' article. This is but one of ''many'' techniques to let readers know of the availability of these types of history-related articles. Furthermore, this method fully discloses the precise nature of the article a reader would be taken to if they clicked on the link. Since Tony, I, and others found ourselves often repeating the same message on WT:MOSNUM to ‘newcomer’ editors concerned about date de&#x2011;linking after seeing Lightbot activity affect them, I wrote ] to help ease the transition.

I ''do'' think I can be of assistance here by offering this observation: Towards resolving this dispute, arbitrators need a convenient and succinct way to establish '''facts''' regarding the current community consensus on linking and related bot activity. Arbitrators should know that ] has produced a nice summary of the relevant RfCs at ]. It is a convenient portal as it contains links to the RfCs themselves. These RfCs also remind us of a central consideration to resolved here in arbitration: ''is bot activity (or planned bot activity) in accordance with the current community consensus?''

Note that we have editors like ] re&#x2011;linking month/day dates, like today to ]. The end result, of course, is to reestablish links to articles that for the most part have nothing to do with sports. This is contrary to not only the general consensus of the RfCs, but also ], which states that links should be {{xt|relevant connections to the subject of another article that will help readers to understand the current article more fully}}. Said another way, links should be germane and topical to the subject matter of the article.

Clearly, with {{NUMBEROFARTICLES}} articles on en.Misplaced Pages, there are probably over a million date links to be fixed, the vast majority of which take readers to unrelated historical trivia that has little if any relevance to the topic of the article containing the links. This is far too many to manually bring into compliance; human-guided bots are the only way I know of to address such an undertaking. The RfCs show that it should be a rare date indeed that is linked in the form of blued, in&#x2011;line body text. So the very few dates that ''should'' be linked and which are accidentally swept up by bot activity can easily be hand-restored. Furthermore, as I have illustrated above, there are alternative, often superior ways to let readers know about relevant material, such as entries in ''See&nbsp;also'' sections. Hand-restoring a relatively small number of links is a good opportunity for editors to avail themselves of these other techniques.

Another important factor to consider is which camp of editors is best trying to adhere to the community consensus on this matter. How is it that we are all here at ArbCom after a month&#x2011;long series of RfCs that enjoyed wide input? I am not seeing any pattern of behavioral problems with the ''respondents'' to this complaint. Tony and Lightmouse have exemplary block logs ( and , respectively). Both are experienced and influential editors with a long track record on Misplaced Pages. The only block on Tony’s record was quickly withdrawn as being done in error. These sort of track records just don’t happen by accident; they happen only by an editor exhibiting a consistent pattern of being logical and reasonable and by abiding by Misplaced Pages’s rules—even when under duress when acting in a leadership capacity, as Tony often finds himself in. What is '''''not''''' passing my “grin test” here is the for the filing party, Locke Cole, nor the for Aurthur Rubin. There seems to be a pattern here regarding the willingness of notable editors on just one side of the dispute to conform to expected conducted on Misplaced Pages. I think this is germane to the dispute’s origins and believe any reasonable interpretation of the RfCs will bear this out. <span style="white-space:nowrap;">''']''' (])</span> 00:22, 12 January 2009 (UTC)

==== Statement by ] ====
(1) The filing party begins by stating that "This has been an ongoing content dispute". Yet the lead clearly states that:
<blockquote> will not make editorial statements or decisions about how articles should read ("content decisions"). Please do not ask the committee to make these kinds of decisions, as they will not do so.</blockquote>

That the basis of the application is a content dispute is reinforced by this subsequent statement by the filing party: "I understand the committee doesn't take up content disputes, but I fear this situation will not end without binding arbitration as those involved seem unwilling to consider compromises which don't involve automated date delinking."

On this basis, I submit that the application be dismissed.

(2) If there are residual concerns about the claims of "incivility and poor behaviour on the part of the proponents of this change", I believe that a thorough examination of behaviour would conclude that there have been instances of frayed tempers on both sides, but that given the length of the discourse (some six months), this is not out of the ordinary and that other forums have been and could still be used to gain resolution. I do not see incivility as a major ongoing problem, and feel that in this context it has been overstated.

(3) I want to put on record that in the view of many users, the trialling, implementation and refinement of automated and semi-automated means for assisting editors to comply with the style guides WRT the removal of date-autoformatting, and the cleaning up the rather messy state of underlying date formats, have been characterised by politeness, cooperation and sensitivity to critical feedback.

(4) I submit that the filing party's construction of consensus in this context is not a balanced view. In particular, ] in the first RfC cited above provided strong consensus that the use of an automatic or semi-automatic process to bring article text into compliance with any particular guideline in the Manual of Style (dates and numbers) requires no separate or prior consensus. ] ] 08:47, 10 January 2009 (UTC)

'''''Addendum'''''
*(a) '''Colonies Chris says it.''' Much of what I was going to add about the substantive allegations in the statements by the filers and their associates has been clinched in ].
*(b) '''The problem of scope and purpose.''' I believe the Committee may face a difficult task in defining exactly what it should arbitrate on in relation to this application. These comments may be relevant.
:*There appears little that ArbCom would want to do concerning '''incivility''' in this matter, which has not been out of the ordinary—indeed, the matter has been characterised by relative civility, even though the filer has concentrated on making a case that rudeness and chaos abound. Arb. Rlevse's concerns for "more input on behavioral issues related to MOSNUM and attempts to resolve them" (and related concerns by Arb. Vassyana) are laudable, but my experience in that forum suggests that MOSNUM talk will just have to wade through its difficulties as best it can, just as always: MOSNUM, indeed, deals with the most contentious issues of all style guides. I believe that any threat to the "stability to articles" (a concern for Arb. FloNight) has been overstated. Colonies Chris provides statistical and anecdotal evidence of a quite different situation. In summary, I think we're over the worst of it, and things go on despite the tension surrounding the issue (notably, in the past few weeks Locke Cole and Tennis expert have been very supportive of an unrelated initiative of mine).
:*Trying to determine the '''consensus''' for the changes would create a very difficult task for ArbCom. While I can see why Arb. Davies hints at this scope, producing an ''official'' interpretation of the detailed RfCs at MOSNUM, which were not framed in a way that was ever going to produce clear results, is not something I'd wish on the arbitrators; in addition, those RfCs would need to be interpreted in the context of a huge amount of other information—they are only the tip of the iceberg. I note Arb. Blacketer's comment that "the committee cannot issue binding policy on the issues within the RFCs".
:*Several Arbitrators are concerned about '''bot usage'''. Although using this as a test-case for establishing/confirming/changing the rules for bot usage might be possible, the technical complexities needed to underpin a judgement make me quiver. If this is to be part or all of the scope of a case, I submit that the scope be very tightly defined from the start (as suggested by Arb. Vandenberg). Please note that ] produced convincing consensus that special consensus is unnecessary for bots to assist in compliance with styleguides.
:*'''Throwing out the case''' might be an option. While focusing on small intervals of time or collating diffs over a long interval (as above) might give the impression that there are "no visible signs of abating" (Arb. Coren), the noise created by the few is likely to recede, given the strong support in the community for a "smarter" approach to linking and for the removal of date autoformatting. Waiting it out, I suspect, has been on our minds for some time, and is probably the natural and wiki-ish thing to do. ] ] 10:35, 12 January 2009 (UTC)

==== Statement by ] ====
I don't see the point of this. Even if ArbCom were to rule that the date delinking or date delinking bots were inappropriate conduct, the damage has already been done. Perhaps a precedent could be set against the possibility of another family of previously recommended links which became deprecated under questionable circumstances, but ArbCom doesn't really set precedents.

For what it's worth, there appeared to be a weak consensus in favor of ''some'' date autoformatting at Question 2 of ], and a clear consensus that some year links are appropriate at question 4. Given that, bots will clearly have signficant errors. ] has (apparently in a semi-automated process), removed month-day links from year articles in two (short) runs after he specifically agreed it was wrong. (Diffs available on request. I reverted some of the ones today (within 24 hours ago, anyway.))

And in case anyone brings it up, I didn't take any admin action, even though I felt that blocking ] would have been of benefit to Misplaced Pages.

As for what ArbCom can do — I really can't think of a thing. Some otherwise sensible editors are misinterpreting consensus, and some (whether or not they are misinterpreting consensus) have been violating ] and ].

So, I recommend that ArbCom refuse the issue — not because the delinkers have any consensus on their side, but because the damage to Misplaced Pages is mostly done (in large part by bots given authority to make any date linking, delinking, or formatting their authors saw fit), and that there is little that ArbCom can do that would help.

Limited response to ]: I don't see any other venues untried for dispute resolution of the underlying issue, that of date delinking and edit warring over date delinking. (] would be inapproriate unless, say, Tony1 and Greg L were considered identical, and Locke and I were considered identical.) There are still possible venues for the conduct issues. — ] ] 09:05, 10 January 2009 (UTC)

Limited response to ]: Question 3 in your RFC may prove that there would be consensus for a bot to remove '''autoformatting''' if there was a clear consensus that '''autoformatting''' links were '''always''' inappropriate. The hypothesis is disputed, and it would not extend to year or month-day links. — ] ] 09:08, 10 January 2009 (UTC)

Summary: The only thing the ArbCom could do that seems helpful is to determine the consensus. I don't think that's within their charter. (Is that a finding of fact?) — ] ] 17:38, 10 January 2009 (UTC)

Bot followup: Lightbot claims a charter to perform any date linking, delinking, or reformatting that the operator deeps suitable. I don't know whether it was approved for that process, but, even if it were, '''that''' is not a suitable charter for a bot. — ] ] 17:46, 10 January 2009 (UTC)

==== Comment by ] ====

* '''Date linking'''? Solved through content dispute resolution, with community agreement seeming to be "needs to be a good reason to do it". No reason to arbitrate.
* '''Date ''de-linking''''', especially by automated means? <u>Not</u> resolved anywhere I ever saw, rather it seemed to be carried on to put "facts on the ground" as soon as possible, riding over any questions or alternatives. In particular, use of a bot basically means that no editorial discretion is applied. The same goes for an editor who uses a "semi-automated" script to indiscriminately remove ''all'' date and year links. However, it seems that the damage is done, last I checked, LightBot had finished the Z... articles and was chewing into Template: space. It's all over but the crying now.
**Arbitration: an injunction would be helpful to restrict bots (or "semi-bots") from revisiting previously edited articles and again removing ''all'' date and year links. No community consensus exists to remove <u>all</u> links, so bots should not be on constant patrol to defeat good-faith editors making selective decisions. This would not apply to reverts to fully date-linked versions, but the onus is on the bot coder to prove the necessity now. ArbCom has within its remit to require re-certification of the bots/scripts now that their primary task has been completed.
**Arbitration: investigation of the circumstances by which this happened, looking not at content but at procedure. Consensus was widely obtained to restrict date-linking, but I'm aware of no consensus to use automated methods to eliminate ''all'' date-linking. This reflects on the bot-approval and bot-review methods, which are (or should be) within ArbCom's remit.
* '''Behaviour'''? I followed and tried to participate in these debates, but was met in part with, and definitely observed, what I could best describe as an "abrasive" attitude from the pro side of the coin. Pro here being the "we've been trying for two years to get rid of this hideous blot which destroys the entire wikipedia experience, birds sing at midnight, who are you to question this now, it's time to right the ship, you're an ignorant idiot" side (vastly-overblown paraphrase is mine :)
**Arbitration: consider the actions of all involved, with a view to behaviour issues in long-term content disputes. Locke Cole will not fare well, several parties have not behaved in the best light, Tony1 I believe should have some special scrutiny (the "abrasive" thing I mentioned above, on or across the line of civility).
I'm involved only on a very peripheral basis and would likely not present evidence. I believe that my statements above are fairly self-evident and will be supported with factual evidence by parties to this case. If my statements are seen as unduly prejudicial, I will provide evidence if the case is accepted. ] (]) 10:39, 10 January 2009 (UTC)<br />
Addendum on review (re Tony1, item (4)):
:Even granted the consensus Tony posits for Proposal 3,
:* Very clever Tony, you posited a negative hypothesis at the RFC, received a negative consensus, and now seem to construe that as a positive consensus for your positive hypothesis. Masterful, except I don't think it works that way.
:* Even granting your artful dodging, any process which removes <u>all</u> date links from <u>all</u> articles is uncompliant with MOS, unless you can point to where automated processes were imbued with the ability to determine the non-existence of a "reason to do so" per your ]. I take it then that you are also asking for an ArbCom injunction against automated scripts/bots? ] (]) 13:04, 10 January 2009 (UTC)

==== Statement by ] ====
Although there is no consensus '''how many''' dates should be linked (opinions differ from only the most important, which bring huge additional value, to all dates), there is clear consensus that '''some''' dates should be linked always.

Dabomb87, Lightmouse and others '''against''' this consensus '''robotically''' remove '''all''' links to dates. If they were successful, articles from ] to ] would be ] which is against ]. If they wish delete articles from ''499 BC'' to ''2059'', the only proper way for doing so is ].

Dabomb87 additionally wikistalked me, most recently ]. This is quite disrupting in continuation to work for the Misplaced Pages which I started in ]. <span style = "font-family: Old English Text MT">—] <sup>] • ] • </sup></span> 10:47, 10 January 2009 (UTC)

; Limited response to ] & ]

Delinking still continues and despite the effort of Dabomb87, Lightmouse and others, millions of articles cannot be delinked in few months time. <span style = "font-family: Old English Text MT">—] <sup>] • ] • </sup></span> 11:02, 10 January 2009 (UTC)

; Limited response to ]

Years '''are not''' autoformated, only days and months. <span style = "font-family: Old English Text MT">—] <sup>] • ] • </sup></span> 11:06, 10 January 2009 (UTC)

==== Statement by ] ====
All other things being equal, this is not a case that is needed at ArbCom as the usual processes to deal with matters of content and policy are still being worked on. I'd almost consider this a case of forum shopping by Locke Cole.

That said, there are certain questions of how heavy a hand Tony and others that support the removal of dates have been pushing for this. Tony et al must be commended for the effort they have done to recognize the problems with date autoformatting both for how dates are presented to end users that aren't logged in and how they saturate pages with lots of links, as these are problems. However, the effort to completely remove date autoformatting without considering the wide response of the community seem to be a bit heavy handed. While Tony and others have tried to suggest the deprecation of date autoformatting to various wikiprojects and at the Featured Article process, there was really never any formal wide-scale input that one would usually expect for a policy/guideline change that impacts every article, instead relying on the fact that they've received mostly silence from editors when date autoformatting was stripped from articles to imply consensus. At this point, when the actual language of MOSNUM was changed based on their local agreement, this is when all matters started to go south. As one of the comments above noted, some point after this change, I began to get more active, noting that Locke Cole and others that were against the removal of date autoformatting were correct to the extent that there was no obvious visible evidence of a consensus for the change beyond the 5-6 major editors of MOSNUM to that point and suggested an RFC to definitively decide the issue. There was a bit of miscommunication with starting that, but by the end of the date, the RFC was ran, got watchlist-noticed, and garnered around a hundred responses (a good # for an RFC), and clearly showed that date autoformatting was to be removed by strong consensus, justifying Tony et al's deprecation of the tool.

But, that said, the RFC also asked other questions, such as if we should get the devteam to make a working version of date autoformatting that works as we need it to to address the failings of the current method, and without using date autoformatting, when dates should be linked. While the responses were less clear than the DA question, there is certainly support for a new date autoformatting system, something the devteam has stated is possible to correct, and there was certainty in consideration of whe when certain dates should be linked to larger pages. Given that the general response to these questions, to myself at least, I felt that there should be a plan of attack prior to removing the date autoformatting code throughout wikipedia to account for any near-term future improved date autoformatting and to allow editors to markup specific dates that they do want to remain linked (but not autoformatted) to prevent those from being removed (mostly through the use of templates to help mark dates as meta-data). However, Tony and the others cited are insistent about moving forward getting their bots going to strip all date autoformatting from articles and having to manually come back and restore links. Policy has no say about which is the best way but I would think that given the ado over the change in policy that, as there's no deadline to get rid of these, trying to work out the least disruptive means to remove date autoformatting while allowing editors to retain their date links would be the more appropriate route to completing their goal. Already, with Lightbot and the others stripping dates, there have been small edit wars and incident reports at ] on it (though mostly raised by those that were against the removal of date autoformatting in the first place).

But the problem, really, at the end of the day is not so much about any significant behavioral issues but instead about dealing with editors like Tony and the others named that have a strong conviction to achieving certain goals for (as they see it and most of time, correctly) the benefit of Misplaced Pages. As such, their tactics for approaching the implementation of changes to MOSNUM is a bit heavy-handed and at times feels like a cabal, ignoring outside opinion if it runs contrary to what they would like to drive the MOS towards. The rapid push to get rid of date autoformatting without allowance for grandfathering of appropriate link dates or considering any new date autoformatting aspects by the devteam, for example, demonstrate this gung-ho approach that shouldn't necessarily be discouraged (I'm well aware of the molasses that working through a consensus can take) but also should be in check when one considers the general attitude that other editors see and consider the MOSNUM group to be based on these actions. I feel its in their best interest to encourage the participation of the community before taking wide-ranging drastic changes instead of forcing it down, even if it for the best of the community.

Is there anything ArbCom can do about this? Very doubtful (beyond noting if there are any improper bots being run as existing ArbCom response as suggested). Maybe there's some behavioral issues here, I don't see them (some edit wars have broken out with date formatting removal but nothing at a large enough scale to get ArbCom involved). This case is mostly a clash between editors with strong convictions towards a goal, which will make things tense and result in rash decisions that could have negative impacts, but both with WP's best interests in making the work better. Attitudes on both sides are not healthy (I take issue with Tony calling the discussion "polite", particularly in the case of many of Greg L's contributions which seemed condescending to those that did want to keep links to year and date pages; there was also some system-gaming going on when some day-month pages were put up for AFD seemingly to test the waters for their removal during this process), but nothing out of line with ] or other expected behavior from editors. Maybe there's something to be said about what type of actions should be done when a change that likely going to affect nearly every article on WP to prevent edit warring, but even then, there's dozens of other changes that happen to policies and guidelines that go on every day that technically should have the same treatment. There's no punishable behavior here, only that I think all groups involved need to remember they aren't in a vacuum here and to avoid making unilateral decisions, and to consider what other editors may appear to see based on their actions. --] 11:33, 10 January 2009 (UTC)

==== Statement from ] ====
I'll note in passing the tendentious labels put on some of the diffs by <s>]</s> ]<!-- sorry, made a mistake here --> in his collation above. However, I trust that the arbitrators are perceptive enough to recognize this immediately on their own. Lightbot has approval to perform the tasks it does, any complaints should be raised at the ], not here. Automated removal of datelinks has been ] not only by the Bot Approvals Group but is met with overwhelming support from editors. (See the responses to ] launched by ].) The number of complaints from editors watchlisting articles from which datelinks have been removed is minuscule. ] who runs a script that performs a similar task to Lightbot's has statistics. Out of the very small percentage of removals leading to complaints, very nearly all are resolved amicably and swiftly, either by the complainant agreeing that removal of datelinks makes sense, or by the delinker entering an exception for that article. For all practical purposes, there is no community-wide perception of a problem.

Date articles are uniquely privileged in all of Misplaced Pages, in that a permanent spot is reserved for them on the ]. Every single day of the year a large portion of Mainpage screen real estate is reserved to ] which leads to the sort of chronological trivia that some people enjoy; in principle every date article ever created on Misplaced Pages is accessible from there if linked right. There is no risk that they will become linkless orphans in no-man's-land.

I submit that the Arbitration Committee and the community would be best served by a swift dismissal of the request.--] (]) 12:45, 10 January 2009 (UTC)

==== Statement from ] (]) ====
My impression is that the actual ongoing debate is about the date format. The delinking of dates has obtained a good consensus with very little opposition rather quickly long ago, after it was made clear that not logged-in users have never benefited from the autoformating feature connected with the linking. So the bot is acting based on consensus and should be allowed to continue. It would be wise however to define a way by which specific and exceptional date links could be protected from the bot. &minus;] (]) 13:29, 10 January 2009 (UTC)

==== Statement from ] ====
I would respectfully disagree with those who have said this has been largely ], and would ask Arbcom to take this case because it is undoubtedly a behavioural issue stemming from a small group of individuals' inability to accept valid consensus. ] and I have locked horns over the issue almost continually from September 2008 onwards. For the record, said editor is one of approximately five individuals totally opposed to removal of Date-autoformatting, and must be credited for having raised the issue most vocally in a manner akin to ]. This subject/guideline may have the dubious honour of having the record number of attempts to ]. There has been a micron-thin veneer of civility (usually in terse language wrapped in brown paper) but the underlying incivility is undeniable. You may not find extreme civility from me nor from Greg, but our wrapping is transparent film, so what you see is what you get. The plaintiff has had a strong influence on how this debate has taken on a ] over the most trivial issue of a pair of square brackets, using all the bureaucratic means at his disposal. I do confess to having given some best efforts to ], parry and recoil, but find myself no match for the plaintiff's aggressive and unrelenting onslaught. The plaintiff has consistently made it clear that he considers any form of delinking disruptive behaviour. This uncompromising stance makes for uneasy discussion. Things have gone so far and gone on for so long that I simply no longer believe that he takes no pleasure in seeing me blocked.

In addition to creating and expanding articles, I am interested in carrying out ], whereas the plaintiff is on record as not only opposing consensus on the issue (as borne out by the RfCs closed 25 December 2008), but also quoted as saying that ] is "only a guideline" implying that compliance therewith is not mandatory. He has been all over town on his complains in attempts to stymie all efforts to clear the detritus, which a very significant number of users have expressed strongly wanting done away with within the project. I have stripped dates off some 8,600 articles as at today's date, and have received only about ten complaints, most of which have nothing to do with the principle of removing dates. One notable complaint was torrent of abuse. Of course Locke was well within his rights to demand clarification on the matter at RfC, but his adamant refusal to take 'no' for an answer, which ordinarily might do him credit for tenacity, can also be viewed as having a ] dimension. Anyhow, there were few indications that Locke was ever committed to be bound by the outcome of the RfC, so this move hardly comes as a surprise. In fact. Lock has been strategically planning seizing this committee since .

To conclude, The way forward? I have already moved on, and am now concentrating my MOSNUM efforts to unifying date formats within articles. I am glad this ArbCom request is the last resort, because I would dearly like to see an end to this matter, which has been the most gigantesque distraction. ] (]) 04:13, 11 January 2009 (UTC) (reworked from edits 15:43, 10 January 2009 (UTC) and 01:12, 11 January 2009)

=====Addendum=====
Not happy with the state of disruption he and his cohorts have sown in WP, a battle appears to have erupted over the merger of ] into ] by ], and the most ] which the plaintiff is attempting to put through in the latter. While there may be some limited discussion and agreement to merge the two, the timing of that action, together with the nature of amendments which have been made by the plaintiff (thus opening up another front in this dispute) while this WP:MOSNUM arbitration request was being prepared () is under consideration strikes me as being reckless and in contempt of process at worst; at best, I consider it unwise. I contend that this would put Locke's ] into question. ] (]) 02:25, 12 January 2009 (UTC)

===== Important statement regarding ] =====
There seems to be a misconception by a couple of arbitrators that the above account is a bot. I am the operator of this account. I believe it has been made clear that '''the account is not a bot'''. Edits made using the account at present rely predominantly on ] - please refer to the ] on the Userpage. Before AWB approval was gained, reliance was put on multi-windowed functionality of ] to achieve edit speeds of several pages a minute, which triggered WP's spam-guard mechanisms and alerted some admins to block the suspected bot. My arguments that I was not operating a bot was looked at and was accepted by ], ] and ]. ] (]) 14:35, 10 January 2009 (UTC)

===== Limited response to ] =====
With all due respect to the excellent technical efforts of Kotniski, his sage advice and his in my view correct reading of the ], the process he believed was broken is only appears so because a handful of individuals, led by the plaintiff, have demonstrated utter disrespect for the consensus, using all means at their disposal to repeatedly "reinterpret" the declared will of the people. I have full confidence in ArbCom that this subversion not be allowed to pass, for it will surely be a day for the annals of WP as the beginning of the end - one of its fundamental pillars, the consensus model will be irreparably shattered, to be replaced by ]. The only other way I can see of ensuring no disputes on such matters in future would be to replace it with directives from the top. ] (]) 16:01, 12 January 2009 (UTC)

==== Statement from ] ====

I did not participate in ], as at the time I both found the size of the discussion overwhelming, in addition to not having had any stake in the matter from prior experience.

A few days ago I became involved in ] regarding the repeated removal of a single year link from the lede of an article by ]. I ] to suspend the bot's blanket removal of year links until consensus for such an action was demonstrated.

This was immediately after I had taken the time to go through the RfC in search. While there were undeniably a number of voices (roughly 40) agreeing with the proposal that "Year links should never be made", there were ''more'' (roughly 55) agreeing with the proposal that "Year links should be made in certain cases". This is not a consensus for ''either'' point of view.

I was only met with a reply from ] that I shouldn't "be surprised if you see a rash of editors suppressing a discussion that has been brought up many times", and adding that "It is time to move on". In other words, if you raise the issue you'll be told to shut up, so go away. I do not believe that it is appropriate behavior for any editor to make another feel unwelcome in participating in this fashion.

When I took my concerns to ], I was accused of "forum shopping" by ] and greeted with a torrent of aggressive language and swearing by ]: "the puke you expect our articles should be linking to... just because you can prove you can stomach through reading that shit will only prove that ''you'' like reading mindless shit... turning yet more main body text into a giant blue turd". Reading through some of the archive links provided above by Locke Cole shows my experience was far from unique.

It is my concern, both as an editor with an opinion in this debate, and an administrator watching the situation, that the behavior of several individuals in this area equates to no less than an ] issue over the whole site, by using automated or semi-automated tools to forcibly apply ] on style across articles on a vast scale in the absence of any policy requirement for it or even widespread consensus.

Please note that I am not asking the ArbCom to rule on the content issue of whether dates should be linked; I am perfectly aware that that is beyond their remit. Whatever the result is for that in the future, all parties should be expected to abide by it and discuss it in a fair and sanguine manner, as for any other policy issue. No result has yet been found, and therefore it is inappropriate for any editor or group of editors to be acting as if it has. For that reason I have added myself as a co-sponsor of this RfAr. -- ] ]</sup>/<sub>]</sub>] 18:50, 10 January 2009 (UTC)

Additional: I am becoming more and more concerned with the behavior of Greg L. Edits such as are ''totally'' unacceptable behavior. -- ] ]</sup>/<sub></sub>] 21:33, 10 January 2009 (UTC)

==== Statement from uninvolved MickMacNee ====
This whole dispute has been lame beyond belief, but the more important aspect is that it ''is'' damaging Misplaced Pages and therefore it ''is'' behaviour that needs to be examined by the committee. Over the past month I have chopped my watchlist by I would think at least 50%, probably more, dropping at least 1,000 articles that I most likely will never pick up again, directly as a result of the fun and games the involved parties have been having with bots and semi-auto editing. In anticipation of the expected response, I do not as a rule not watchlist minor edits or bot edits, becuase the minor flag is often misunderstood/abused, and bot edits are often marking the flagging of image issues which need attention, rather than trivial things like this. On the actual issue at hand, I have no strong opinion either way, but if it turned out there ''was'' a strong consensus to delink all dates, ''and'' to retrospectively do that, then it should have been done once, as a batch job by one bot account quickly, with anybody edit warring it without cause blocked. But it appears to me to have not been done this way, it has been done over weeks and weeks, by multiple people/accounts, and has been edit warred over without sanctions. If Flagged Revisions is adopted because not enough people are catching vandalism on watchlists, this sort of lame dispute is the reason why. It's maddening. ] (]) 16:46, 10 January 2009 (UTC)

==== Statement from uninvolved ] (]) ====
I agree broadly with MickMacNee. I don't think arbcomm should step in and say "we link dates" or "we do not link dates". I think we need Arbcomm to step in and say "stop this continuous cycle of RfC's, AN/I threads, edit wars and spilling out into ]." It is apparent the community doesn't feel capable of resolving this (and honestly, we tend to resolve these things with an inappropriate level of granularity) and that the content issue doesn't seem to go away though discussion.

=====Response to Sam Blacketer=====
With all due respect, distinguishing between dates delinked during an edit to a page that includes other content changes and dates delinked in a stand-alone edit is asinine. If we require (as the AWB policy does) that dates be delinked along with some change to an article, then a bot will be written or re-written to make a formatting change along with the delinking. If we think that dates ''should'' be delinked then delinking them is part of working on the encyclopedia. It doesn't add anything to argue that delinking is ok, unless it is done all by itself.

==== Statement from semi-involved ] ====
I was debating adding myself to this RfAr or not, but as I have not been in many of the discussions (I've merely implemented delinking and have discussed it on ] and ]), I have decided to stay out of it. I just wanted to note a few things for the Arbitrators.

'''John Vandenberg''' - Lightbot's third RFBA, ], covers its current delinking. I'm not sure if that approval is still active; there were whispers that I heard that it wasn't, but that is something for another user to answer.

The two Requests for Comments showed a clear consensus in most cases for at <s>least</s>most '''very limited linking'''.
*] had a clear consensus to reject date linking and date autoformatting. It had a less clear, but still fairly strong consensus to allow automated and semi-automated edits to help delink dates.
*]
**Deprecating the current date autoformatting - Dates should not be <s>de</s>linked (very clear consensus)
**Is some method of date autoformatting desirable? - About 50/50, but this is not relevant to this RfAr, and is more a Developer issue.
**When to link to Month-Day articles? - 2/49/49 support. Examples:
***"John Fred was born on ] and invented the tricycle on ]."
***American independence was declared on ]
***American independence was declared on July 4.
**When to link Year articles - 10/60/30
***"John Fred was born on ] ] and invented the tricycle on ] ]."
***"In ], Columbus sailed the ocean blue."
***"In 1492, Columbus sailed the ocean blue."
**When to use Year-in-field links - murkier; no real consensus came about there.

Hope this helps. Feel free to alert me if you guys need anything else from me. <font color="navy">]</font>''''' <sub>(<font color="green">]</font>)</sub>''''' 19:23, 10 January 2009 (UTC)

==== Statement from ] ====
I will attempt to dredge up the appropriate diffs and history in a moment but for now, I have this to say:

The issue is not whether or not dates should be linked or not linked, or delinked or whatever. On the list of things that matter, with the main page libeling ] as a child molester at the very top, and whether mono books' default shade of white should be described as "cosmic latte" or "ivory" at the very bottom, ] finds itself somewhere in the bottom 5. This hardly explains why there has been serious incivility, edit warring, abuse of process and otherwise disruptive behavior over the issue although ] might. This would be ] if it wasn't for the genuinely hurt feelings and wasted hours over this issue. In short, there is a major behavior problem here, and if the users involved can't be brought to heel, I would very much like them to be quarantined in ] so the rest of us can get on with our wiki lives in peace.--] (]) 23:39, 10 January 2009 (UTC)

====Statement from ] (Pmanderson)====
On the substantive issue, this is a dispute on this issues discussed in the polls in the ] above.

Is there a consensus that we should always delink dates? If not, should we allow automatic, or semi-automatic delinking of dates? (My own views are that we should link dates rarely, and about half the poll holds that opinion; and that we do not have consensus either to always delink or to handle the matter by bot and accept the cases where the bot delinks a useful link).

Lightbot is presently operating under ]. The request itself was vague; it was disputed at the time; and since then a number of users have requested reconsideration, including Gerry Ashton and myself. Is this sufficient basis for Lightbot to operate?

These questions, unfortunately, only ArbCom can decide; we've tried other methods. It would be nice if Arbcom did.

There is a fundamental underlying issue, which ArbCom may also wish to address. The chief use of MOS and its subpages is to give "authority" to the following procedure: a handful of editors decide that Misplaced Pages ought to do something, and every article must do it (here, the parties to this who did not file think there should ''never'' be a linked date). They write this in as a paragraph on a MoS subpage, and then go around WP insisting on their One True Way because it's consensus. So far they've been bold; fine. But when objections arise, they do not really discuss, or attempt to reach an agreement to disagree; instead, they claim, as here, that it requires consensus to change MOS: ''i.e.'' for these five editors, it would take twenty or thirty editors to object with any effect. ] <small>]</small> 02:22, 11 January 2009 (UTC)

==== Statement from ] ====
I can affirm that although I'm new to the debate on ], I've been treated with remarkable civility by all of the editors there - a little lecturing and a touch of sarcasm, but nothing my delicate constitution couldn't handle, even though I would characterise myself as firmly on one side of the debate. Apart from a brief outburst or two among a huge amount of debate, I suspect the exchanges there have been as polite as most other areas of Misplaced Pages.

Nevertheless, it is conceivable that ArbCom could help. I believe that the disagreement is as I summarised it ] and ]. If it is true that editors are polarised on the question of whether date-links should be an automatic exception to ] or not, then we either need ''another'' RfC (!) or a ruling from ArbCom (?). Otherwise, I fear that we are doomed to recycle arguments like "I can't find a single relevant/useful date link" vs "The date article would be interesting to someone wanting to browse/find out more about that year, etc." --] (]) 04:35, 11 January 2009 (UTC)

; Response to Earle Martin

I should have mentioned that the other factor polarising editors is the interpretation of the recent RfC's. As an example, Earle says ''While there were undeniably a number of voices (roughly 40) agreeing with the proposal that "Year links should never be made", there were more (roughly 55) agreeing with the proposal that "Year links should be made in certain cases". This is not a consensus for either point of view.'' By characterising the RfC as a vote, it misses the point that contributors made comments. Of the 55 (including myself) who '''supported''' "Year links should be made in certain cases", over three-quarters of those '''commented''' along the lines of "Only when it provides useful context/relevance" or echoed Fabrictramp's ''Year links should be made when it truly helps the understanding of the article. This is almost never, but if there ever is a time when it does, I don't want to rule it out''. Several editors take the raw numbers and say "No consensus"; others put together the "Never" and "Rarely" and see a clear consensus that date-links are just as subject to ] as any other link. I remain unsure about whether ArbCom is the place to decide such an issue. --] (]) 05:03, 11 January 2009 (UTC)

==== Statement from ] ====

The various references to "semi-automated" editing includes both scripts and ]. I have previously complained about the use of AWB to make controversial delinking edits at a frantic pace in clear violation of the AWB rules of use, only to have my complaint rejected by an administrator who himself uses AWB at a frantic pace to edit articles, a clear conflict of interest. I refer you to and . Others have complained about the use of AWB to make insignificant or inconsequential delinking edits in clear violation of another AWB rule of use, only to have the complaint rejected. I refer you to , , and . Essentially, AWB, bots, and scripts are being used to make any discussion about the Manual of Style moot, futile, and pointless because all articles will have been changed to conform with one vocal faction's views (who are very proficient in bot and script programming) before the discussion is over. Also, the AWB and script users have converted what were supposed to be semi-automated tools into automated tools that are not bots in name only. Often, when it is brought to the attention of those users that they are making serious errors and asked to correct those errors, the notice is ignored or the reply is "that's the price of progress". See , , and .

The statements by various people that hardly anyone has complained is ridiculous because whenever anyone does complain, they are steam-rolled by edit warring, aggressive posts and edit summaries, canvassing and other conspiratorial behaviors, accusations of mental illness or dyslexia, name calling, and other despicable tactics that clearly violate various Misplaced Pages policies and drive away valuable editors forever. See, for example:<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
.

Aside from all these problems, the Manual of Style has been treated by the date delinkers as if compliance with it were mandatory, regardless of particular article consensus. That is erroneous thinking, as previous ArbCom decisions have shown and as the Manual of Style itself plainly states. ] (]) 05:11, 11 January 2009 (UTC)

=====Reply to ]=====

See and where he admitted his edit warring intentions and activities. See also , where in response he was incivil, confrontational, wikilawyering (esentially claiming that you can't edit war when all you're trying to do is enforce the MOS), and uncooperative. ] (]) 11:38, 12 January 2009 (UTC)

He claims that he has not edit warred about date delinking. But here are a few examples of his doing exactly that:<br>] , <br>] , <br>] , <br>] , <br>] , , <br>] , <br>] , <br>] , <br>] , <br>] , .<br>] , <br>] , <br>] , <br>] , <br>] (]) 21:52, 12 January 2009 (UTC)

====Statement by Woody====

I have been involved in this issue since the beginning of this latest round of delinking. I objected to the mass delinking of FAs and FLs which was made to the talkpages of all featured articles. My initial response can be found at ] that I wouldn't get involved over at MOSNUM because "those pages have their cliques and I have little time for high-school politics." The summary by Septriontrialis is fairly accurate when it comes to the procedure at our MOS pages. Whenever I labour through the talkpages I find that there are editors entrenched on both sides, usually going round in circular arguments with little output.

For too long these pages have become a time-sink where editors debate the merits of the most small, and frankly lame changes to the MOS. They have little time to spend on ''editing'' articles, by that I mean expanding, verifying and reviewing. We need a clear ruling from Arbcom about the behaviour of all those involved on these pages; on the meaning of consensus and its interpretations; and on the use of automated tools to present a ''fait accompli.'' I hope that ARBCOM can finally resolve some of these issues and let us return to the development of articles.

====Statement from ]====
I’ll divide my statement into two parts; my opinion, and some facts about the community reaction to date delinking.

First of all, this whole case is a blatant example of forum shopping. Locke Cole has opposed these changes tooth and nail from the very start – first he lost the argument on the changes to MOSNUM, then he tried to claim that delinking was disruptive even though it was line with MOSNUM; then he tried to get me, Lightmouse and others banned from using AWB to make these edits; then he lost two RFCs, and made spurious complaints at ], then even when he’d lost the RFCs – one of them specifically on the issue of using automated processes to implement the MoS - he’s still trying to say that there’s isn’t consensus to bring the encyclopaedia into line with its own Manual of Style, and also saying that MOSNUM is only a guideline and he doesn’t have to obey it anyway. This is someone who just can’t accepts that things aren’t going his way and is disrupting everyone else to make his point. The claim of incivility is just another spurious attempt to keep the dispute going – as Tony1 said "there have been instances of frayed tempers on both sides" - but none of it has resulted in anything that the ArbCom need be spending its time looking at.

The claim that ‘the bot has unlinked everything already’ is utter nonsense. I’ve just picked a random date (September 12) and checked what links to it – there are about 7000 links, even disregarding links to calendar-related articles. Multiply that up by 365, divide by, say, 5, to allow for multiple date links in articles, and you have about half a million articles still with some form of date linking, at a conservative estimate. What the objectors seem to forget when they object to automated delinking is that those links weren’t made by people carefully considering the merits of whether a particular date should be linked. They were made because that’s what the MoS recommended (in the case of autoformatting) or because the syntax of autoformatting is so unintuitive that the average editor tended to just link all bare years and other date fragments and time periods willy-nilly.

Here are some facts; most of what I do on WP is gnoming. Since the MoS was changed to deprecate autoformatting, I've been routinely unlinking dates in the course of my other edits. I estimate that I've edited about 10,000 articles, and roughly 70% of those edits involved some sort of date delinking – either full dates or bare years or the occasional more exotic combination. That's about 7000 articles delinked. If delinking were seriously disputed – by more than just Locke Cole and a few vocal others - you’d expect me to get a lot of complaints. How many have I had? Seven. In three cases I explained about the MoS and my argument was accepted. In two cases the editors wouldn’t accept that, so I just left them to it. And in two cases editors were so uncivil that no attempt at reasoned argument could have made any difference. This gives the lie to Locke Cole's suggestion that the changes are being steamrollered in. It's just that he doesn’t agree, plain and simple, and he won’t concede that the argument is lost. The community accepts the changes. The evidence is clear.

'''Response to Tennis Expert'''<br>
This claim repeated ''ad nauseum'' that there is a local consensus (on tennis-related articles) that overrides the MoS needs to be exposed for the self-serving nonsense that it is. When various dates in tennis-related articles were being unlinked, in line with the MoS, and Tennis Expert was reverting those changes, in contravention of the MoS, where were the other tennis editors standing up to support this supposed local consensus? There were none - because it existed only in Tennis Expert's mind, as a justification for his insistence that everyone do things his way.
Like it or not, hardly anyone has complained – see the facts in my statement above. And I have not imtimidated anyone, nor steam-rollered, edit warred, nor made aggressive posts and edit summaries. The evidence is open to anyone to examine.

How telling it is that the best Tennis Expert can come up with to support his allegation of edit warring is a complaint that he himself filed, and whose outcome was NOVIO. Strange he didn't mention that.

====Comment from vaguely-involved ]====
My thoughts on this matter, for what they are worth:

'''Where we are now.''' After horrifyingly vast amounts of discussion of this topic, the conclusion of the community seems to be basically thus: dates in WP articles are not to be linked EXCEPT (A) in articles about other dates; (B) possibly in a few other situations where they might be useful. Exception (A) seems pretty clear cut, but all attempts to define any situations to be included under (B) (date of birth, first date mentioned in the article, etc.) have failed to take off. Therefore there is probably no date link, other than those of (A), which the community has any enthusiasm for keeping. On the other hand there ''are'' many thousands of date links (mostly left over from autoformatting) which are now deprecated and are desired to be removed. This is clearly the kind of task that can be usefully done by a bot or by humans using scripts, particularly if combined with other tidying-up. Exception (A) shouldn't be a problem; operators can easily define classes of articles (year articles etc.) where the bots don't delink dates. Exception (B) isn't too significant a problem, since it's far from clear that it ever applies, and in any case the "harm" done by delinking the few (if any) dates in that class is easily outweighed by the "good" done in removing the far greater number of unwanted links. There should simply be some agreed syntax (for example, a comment within the link) which can be used to tell the bots that a particular link is not to be touched (only to be used, of course, when there is good reason – like ] on the ] dab page, yes, there are ''some'' exceptions – and not just because of an editor's personal view on date linking). '''Summary: the bots will benefit the project as long as the described exceptions are provided for.'''

'''How we got here.''' Oh dear. This episode is really not something we can be proud of. Massive unproductive debate over many months, frequently lost tempers, large-scale edit-warring, interpersonal conflicts persisting even now – and all to reach a very simple and clear-cut decision that we could have got to ages ago without a single unkind word being spoken. Something's broken in the way we do decisions, and the wise people of ArbCom may be able to offer some guidance on what lessons are to be learnt from all this. For me, as proposer and writer-into-policy of the original autoformatting deprecation, I take the lesson that proposals directly affecting vast numbers of articles need to be loudly publicized in the community at large before any attempt at implementation. For the community, I suggest that there needs to be a mechanism whereby disputes that are getting hugely out of hand are forcibly brought under control - formally moderated, kept on track, and closed (preferably by a panel, for debates this big) after being allowed to run a reasonable time. We have structured processes for making certain decisions - deletions, renames, RfAs, ArbCom cases - why not have them available to resolve other issues where - exceptionally - the normal consensus-forming process has broken down. '''Summary: something needs to be done to stop this happening again.'''

'''People.''' I believe all those involved in this debate have acted for what they believed to be the best for the encyclopedia. Tempers have been frayed, to say the least, on all sides, but this is largely a consequence of the systemic failure to get the matter properly streamlined until very late in the day. I would hope that everyone can now accept the outcome, and get on with either implementing it or making other positive contributions to Misplaced Pages, which I know that all of them will. And to put aside past conflicts and work together amicably wherever their paths should cross. '''Summary: hey, it's only dates.'''

'''Re the present complaint.''' I agree that actions by various people on all sides in the past might have been imperfectly judged. However there seems to be no reason to complain against the action being taken with the use of bots ''now'', with consensus finally established (at least to the extent that we can see that the use of bots is beneficial, as I've argued above). (I don't understand why some arbitrators seem to be saying that the consensus-building process should still be continuing - it's been as far as it possibly can and a lot further, and I don't believe there's any serious doubt about the principal conclusions as stated above. There will never be unanimity, if that's what they're hoping.) So I would strongly recommend that ArbCom not take any action to obstruct the useful work of these tools being done now, but confine itself to saying what went wrong throughout the whole saga and suggesting what might be done to prevent issues getting so out of hand in the future.

====Comment from completely uninvolved ]====
Looking at this issue, it's apparent that the issue -- content dispute or no -- has not been, and will not be, decided on-project. That makes the issue to accept the case relatively cut-and-dried for the arbitration committee, in my view. As for the underlying facts, it would appear that something at least ''resembling'' consensus was reached at ]. However, per the ''Fait Accompli'' finding in the episodes case, once editors at the individual articles began to dispute this consensus, the automated edits should have stopped immediately. Personally, I don't see any particular value in linking individual dates, unless that date is particularly significant for some reason, but that's beside the point. Once the edits were disputed, they should have stopped. They didn't, and now that is a behavior issue (along with some concerns regarding personal attacks and basic collegiality) that the committee should address. '''SD'''] 17:35, 12 January 2009 (UTC)

==== Clerk notes ====
:''This area is used for notes by non-recused Clerks.''
*Recuse - statement may come later, for now but I was involved very briefly as an administrator, tried to stop an incredibly uncivil discussion, and then was compared to people who trick Black voters in the South so I am definitely not reliably neutral.--] (]) 04:47, 10 January 2009 (UTC)
*Propose renaming to MOSNUM due to larger issues. Date delinking is only the latest incarnation of MOSNUM problems.<span style="font-family:Verdana,sans-serif"> — ] • ] • </span> 13:20, 11 January 2009 (UTC)
**I'm not so sure about the renaming; let's have a little more discussion on that. I don't want the scope of the case expanded in a way that might encourage editors to include in it every disagreement about a style or nomenclature issue across the project. ] (]) 21:17, 11 January 2009 (UTC)

==== Arbitrators' opinion on hearing this matter (8/0/2/0) ====
* edits in two months by ] is a lot when ] is a redlink. Has there been any communal approval of this bot? Very few of ] mentions appear to be venues of broad community approval. ] appears to be the most recent discussion, and problems with the automated edits were raised. Have those problems been fixed? <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 06:17, 10 January 2009 (UTC)
**I also notice that the last 10 edits by ] are outside of the approval given at ], but this "solitary year unlinking" functionality was covered by ]. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 11:11, 10 January 2009 (UTC)
**'''Accept''' with a tight scope of date delinking. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 23:51, 11 January 2009 (UTC)
*Comment. Courtesy archive links for examples of WT:MOSNUM and noticeboard discussions would be appreciated, particularly for discussions leading up to and following the RfCs. ] (]) 06:45, 10 January 2009 (UTC)
** Thank you. ] (]) 08:28, 10 January 2009 (UTC)
** '''Accept''', unless (in the words of FloNight) there is good evidence of a clear ongoing consensus building process that will end with a well-accepted solution. I think there are clear behavioral issues for ArbCom to examine here. The use of the consensus-building process and interpretation of its resolutions seems to be a fundamental issue here, along with related behavioral concerns. There is also a broad range of alleged behavioral issues surrounding these cirucmstances, including but not limited to (semi)automated tool abuse, incivility, OWNership, forum shopping and system gaming. ] (]) 22:35, 10 January 2009 (UTC)
*'''Comment'''. I also can not find anything indicating ] is an approved bot and have asked ] to double check that. While the issue of date delinking is roughly 6 months old, other issues related to ] have been brewing for roughly two years and I keep seeing many of the same users involved in the disputes. The issue of whether to link or not link dates is clearly a content issue outside of arbcom's purview. I'd like to see more input on behavioral issues related to MOSNUM and attempts to resolve them.<span style="font-family:Verdana,sans-serif"> — ] • ] • </span> 13:04, 10 January 2009 (UTC)
::See ], it's using AWB on an alternate account, which is within policy. <span style="font-family:Verdana,sans-serif"> — ] • ] • </span> 14:25, 10 January 2009 (UTC)
:* '''Accept''', largely per Vassyana and suggest renaming to MOSNUM due to larger issues. Date delinking is only the latest incarnation of MOSNUM problems. <span style="font-family:Verdana,sans-serif"> — ] • ] • </span> 13:22, 11 January 2009 (UTC)
*Comment Because of the potential for a dispute on this topic to cause instability to a large amount of articles and the length of the dispute, I'm willing to take this case sooner rather than late, unless there if good evidence of clear ongoing consensus building process that will end with well accepted solution. If the discussion is stalling due to problematic user conduct, then can address it if needed. If issues of unauthorized bot usage need to be addressed then make that clear. Please cite specifics of any problems. ]] 14:43, 10 January 2009 (UTC)
**Now '''Accept'''. Not to make a content ruling but to assist in developing a process that will result in stability to articles and address any user conduct issues that may be causing local article discussion or global topic discussions to stall without forming consensus. ]] 10:48, 11 January 2009 (UTC)
*'''Comment'''; I'm inclined to accept a case when the topic focus causes large, repeated threads on noticeboards with no visible signs of abating. This invariably means there is a behavioral problem, even if the problem is the repeated call to arms rather than the issue itself. &mdash;&nbsp;]&nbsp;<sup>]</sup> 15:28, 10 January 2009 (UTC)
:*'''Accept'''; the issue pivots around large scale implementation of style changes, and the behavior surrounding the propriety of such changes. I don't think the name change is necessary, but it is acceptable. &mdash;&nbsp;]&nbsp;<sup>]</sup> 17:13, 11 January 2009 (UTC)
* '''Question''' Can anyone provide an estimate of: (i) the percentage of articles within the corpus that have so far been de-linked and (ii) the rough proportion of de-linked articles which have been subsequently reverted? --]&nbsp;<sup>]</sup> 15:48, 10 January 2009 (UTC)
** My estimation is very rough and is based on feeling rather than actual data: Perhaps 30 % of all articles with dates were forcibly delinked. Probably in less than 1 % the links were re-introduced. <span style = "font-family: Old English Text MT">—] <sup>] • ] • </sup></span> 21:16, 10 January 2009 (UTC)
:* '''Comment''' I agree that the issue for ArbCom here is behavioural: whether large-scale implementation was premature and whether consensus was sufficiently established for such a profound change. --]&nbsp;<sup>]</sup> 16:50, 10 January 2009 (UTC)
:* '''Accept''' per my comment. --]&nbsp;<sup>]</sup> 02:24, 12 January 2009 (UTC)
*'''Comment'''. In the interests of full disclosure I to ] on this issue, and participated in both the and the proposal. I don't think I have prejudged this case but if seriously asked to recuse on these grounds by a party to an accepted case then I would be bound to accede.
:That being said, I am concerned at the time spent by a small number of editors who have been mass delinking - which cannot truly, I think, be regarded as '''writing''' an encyclopaedia. Removing links while doing other necessary changes on individual articles could not be disruptive, but systematically delinking for aesthetic reasons strikes me as a waste of server time.
:There are two caveats to my opinion. First, the issue of whether to link or delink dates is not, in my mind, entirely on a level with the merging and deleting seen in the Episodes and characters case, and does not create the "''fait accompli''" mentioned in the title of the principle. Second, if we were to accept the case, the committee cannot issue binding policy on the issues within the RFCs. ] (]) 18:44, 10 January 2009 (UTC)
:*Quick reply to two comments (by Locke Cole and Protonk), I certainly agree that making superficial editorial changes along with delinking dates is substantially the same as just delinking them; I was thinking really of manual routine page maintenance rather than automated mass changes. I would '''accept''' a case strictly limited to the use of automated or semiautomated tools to delink dates on articles but nothing wider. The caveat about recusal still stands. ] (]) 21:29, 11 January 2009 (UTC)
*'''Recuse''' I am a good friend of Tony and my ability to be impartial may not be accepted by all. Cheers, ] (] '''·''' ]) 04:39, 11 January 2009 (UTC)
*'''Accept''' pending what the name will be. I support just keeping it to the date delinking conduct issues; if we widen the scope it could be dangerous, so I oppose a rename at this time. ] 16:29, 11 January 2009 (UTC)
*'''Recuse''' - I have participated in date-linking discussions previously, and while I don't hold a very strong opinion on the central issues, and my opinion has shifted over time (to the stage where I support most, but not all, date delinking), I'm involved enough and have discussed this with several of the editors concerned (at least four of the parties), to the extent that I don't feel I could impartially judge the behaviour issues here. I do agree with those who have stated that this case should most emphatically be about the behaviour here, and not the content. Incivility, unnecessarily strong criticism, tendentiousness, inability to compromise or see the other side's arguments, misreading of consensus (possibly in good faith, or being blinded by bias), edit warring, attacks against bot operators, impatient and unhelpful responses by bot operators, misguided application of the manual of style, and other issues, are among those that have taken place here (just a selection of the behaviour on both sides). I also echo the comments by those who point out that date delinking is not really the most urgent matter to be resolved here. ] (]) 00:36, 12 January 2009 (UTC)
----

=<span id="REQ" />Clarifications and other requests=
{{Shortcut|WP:RFAC|WP:RCAM}}
''Place requests related to amendments of prior cases, appeals, and clarifications on this page. If the case is ongoing, please use the relevant talk page. Requests for enforcement of past cases should be made at ]. Requests to clarify general Arbitration matters should be made on the ]. To create a new request for arbitration, please go to ]. '''Place new requests at the top'''.''
{{Misplaced Pages:Requests_for_arbitration/How-to_other_requests}}
{{RfarOpenTasks}}<br style="clear: both;"/>

=== Request for clarification: ] ===

Note: the specific article involved is ]

''List of any users involved or directly affected, and confirmation that all are aware of the request:''
*{{userlinks|Backin72}} (initiator)

(Note: since this case involves an article and not any specific editor(s), neither I nor the parties below are directly affected. However, I've notified all active editors as a courtesy, and have left a note on the article's talk page.)

*{{userlinks|ScienceApologist}}
*{{userlinks|Dematt}}
*{{userlinks|Fyslee}}
*{{userlinks|Hgilbert}}
*{{userlinks|Levine2112}}
*{{userlinks|Verbal}}
*{{userlinks|QuackGuru}}
*{{userlinks|Eldereft}}
*{{userlinks|Enric Naval}}
*{{userlinks|Hans Adler}}
*{{userlinks|Headbomb}}
*{{admin|Elonka}}


<!-- Substitute "admin" for "userlinks" if a user is an administrator. Anyone else affected must be notified that the request has been filed,
immediately after it is posted, and confirmation posted here. The line for username2 can be removed if no-one else is affected. -->

==== Statement by ] ====
We are at an impasse regarding use of the "pseudoscience" label at ]. Certain of the findings of principle in the ] Arb case were incorporated into NPOV (see: ]), and are now being disregarded. Basically, some editors want to characterize as pseudoscience any topic that has received criticism as such, even from self-published sources like Quackwatch and CSICOP. We've had a bunch of RfC's (I stopped counting before 2008: ], ], ], ]), all of which have failed to generate consensus, and lately a lot of edit-warring (see ). We're deadlocked, other attempts at ] have not worked, and each side is convinced they are right, so I believe the time is ripe for ArbCom to clarify.

It wasn't supposed to be this way. ] is quite clear on what to explictly characterize (or label, or categorize) as pseudoscience, and what not to. For convenience (at the expense of the 500-word limit; sorry), here is a cut-and-paste of ]:

{{Quotation|In an ], which can be read in full ], the committee created distinctions among the following:

*''']''': "Theories which, while purporting to be scientific, are obviously bogus, such as ], may be so labeled and categorized as such without more ."

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

The ArbCom ruled that the following should generally not be characterized as pseudoscience:

*''']''': "Theories which have a substantial following, such as ], but which some critics allege to be pseudoscience, may contain information to that effect, but generally should not be so characterized."

*''']''': "Alternative theoretical formulations which have a following within the scientific community are not pseudoscience, but part of the scientific process."}}

It's pretty clear what NPOV is telling us: don't categorize or otherwise characterize a topic as pseudoscience unless it's trivially "obvious pseudoscience" (and requires no reference), or it's "generally considered pseudoscience by the scientific community". Classifying a topic as the latter obviously requires a suitable source, cf. ], and also ]. Such sources usually are scientific academies or other mainstream, official groups (e.g., many of the sources listed in ]). Skeptical advocacy organizations like ] and ], while notable (and perhaps suitable for establishing that a topic is what we call "questionable science"), cannot be taken as representing general agreement in the scientific community. Such sources suffer from self-], and don't even meet ] at all.

However, some editors don't believe that inclusion of "questionable sciences" on the list violates ]. One editor says "a list is not a category", irrespective of the list's title. Some want to populate the list as robustly as possible, and have tended to brush off the objection that we must find the proper sources, i.e., those indicative of what the scientific community generally holds. This is especially problematic given that the list's title is unambiguous: "]" leaves no wiggle room, any more than ] does. When we put a topic on that list, we are saying that the topic ''is'' pseudoscience, no ifs, ands or buts.

My view is that if we keep the list's present title, we should strip out all topics that are not verifiably "generally considered pseudoscience" or "obvious pseudoscience". If we changed the list's title to something like "List of topics referred to as pseudoscience", then I think it would be OK to include "questionable sciences". However, I'm still concerned that we'd have to clearly demarcate the clear-cut pseudosciences from the "questionable" ones. Otherwise, it's like having an alphabetical "List of burglars, and people who might have been burglars according to speculation". It's a violation of ] to have clear-cut pseudosciences alongside grey-area topics.

So, I request that ArbCom clarify that findings 15-18 in ] accordingly:

* '''Proper sources are required to show that a topic is "generally considered pseudoscience".''' (I believe it would also be appropriate to clarify that statements from individual scientists or skeptical bodies do not suffice as sources here.)

* '''These findings apply not only to "category:pseudoscience", but also to lists with unambiguous titles''' such as ], as well as to navigational templates, and any unqualified assertion such as "X topic is pseudoscience". "Questionable sciences" and "alternative theoretical formulations" should not be depicted as pseudoscience, e.g. via inclusion on the list in question, as titled.

* '''Don't hide distinctions in the fine print.''' Obvious or generally-considered pseudosciences should not be conflated with questionable sciences by listing them alongside each other without explanation. ] and other principles require that questionable sciences be clearly demarcated from the former two, either by having their own list, or otherwise by annotation or segregation into a separate section of a broader list (e.g., a "List of topics referred to as pseudosciences").

Thank you for taking the time to consider this matter. --] (]) 13:28, 10 January 2009 (UTC)

:'''Comment''' for Coren and others: Yes, this is a content problem; so were aspects of the original ruling and finding (see ]). In practice, ArbCom does comment on content from time to time, and WP is better for it. Please have a look at those RfC's I linked to before blowing this off to "community resolution". Said community is deadlocked, with some believing that everything on the list, grey-areas included, . But the sourcing situation is a little bit different than Eldereft's humorous renaming example below. There are pseudosciences according to the scientific community, and "pseudosciences" according to lesser sources like advocacy groups or individual critics. There are editors who, like skeptical groups, want to apply this label to as many things as possible, in an ] spirit, because they believe they're right. Others believe ] was correct and should be followed strictly. This has created the present impasse. If the community never resolves it, and there are real NPOV problems, shouldn't ArbCom intervene? --] (]) 21:55, 10 January 2009 (UTC)

::'''Comment''' for Rlevse and Vassyana: I don't think the Fringe Science case will help much; nothing in the ] addresses ] (probably because it's not all that germaine). Please don't be too hasty in blowing this off. If the community could fix it, it would have done so in the past couple years. We have an impasse between editors who take ] seriously and editors who want to IAR because they feel the pseudoscience label is best used liberally. We've tried virtually every part of ], which is why we're at the end of it .... here. So, have another look? Pretty please? It's a fairly narrow issue. --] (]) 08:12, 11 January 2009 (UTC)

==== Statement by ] ====
<!-- Leave this section for others to add additional statements -->

] is currenty a crapola because of so much arguing over that WP:PSCI ruling, but the modifications proposed by Backin would just make it worse. It just deepens the "content ruling" problem by a) expanding its scope and b) enforcing stricter limitations on content.

While that ruling needs modification, this doesn't look the correct way to go.

====Statement by ] ====
This is really more of a content dispute than anything that ArbCom needs to deal with. As background, I have been acting as an administrator for the last few days at ], trying to help stabilize the article via the discretionary sanctions authorized from the ]. There currently appear to be three main points of dispute, though all three appear (to me) to be the topics of constructive discussion on the talkpage. The main three issues are: (1) What should the page be titled; (2) Should ] be included on the list; and (3) Should ] (such as acupuncture) be included on the list. Up until about a week ago, there were pretty systematic back and forth revert wars going on, but since there has been more administrator attention on the article, the revert wars have stopped, and the discussion environment seems to be improving on the talkpage. No direct sanctions have been implemented (at least by me), though I did post a few nudges to the talkpages of a few users: , , , , along with some off-wiki communication with {{user|ScienceApologist}}. All editors have been cooperative and have voluntarily complied with the requests, which is appreciated, and the article appears much more stable as a result, though of course vigorous discussion is continuing on the talkpage. As far as ArbCom is concerned, the existing ArbCom motions and discretionary sanctions seem sufficient for the current situation, so it would probably be best to allow the discussions at ] to continue, with administrators continuing to monitor the page. --]]] 18:32, 10 January 2009 (UTC)

====Statement by ]====
Possibly influenced by the daunting volume of often polite discussion and rapid watchlist-destroying reverts, all listed editors are long-term good faith contributors. There is general consensus that unquestionable science should be excluded from the list - anti-vaccination advocacy groups and others clearly outside the scientific conversation are not sufficient sources.

I prefer to view this as a genuine dispute concerning where the bar of ] falls - if a practice, for instance ], is published in peer-reviewed journals or practiced in some hospitals, can reliably-sourced analysis support an entry in this list? This often boils down to the issue of efficacy vs. rationale - many papers studying the efficacy of ] are published in quality sources, but the original and a continuing rationale asserts the existence and healing powers of a ]. ] applies only to the efficacy side of this question, though assertions made in the absence of evidence may come into play. To further complicate matters, there are three answers to this question: write an entry mentioning nuances and caveats; write an entry discussing solely the pseudoscientific aspects; or write no entry. I favor the first position (adequately sourced) - state that hypnosis exists but Mesmerism and past-life regression are pseudoscience. This issue is treated in the inclusion criteria described in the introduction to the list.

This brings us to the question of sourcing - a few pseudoscientific practices are widespread enough to have attracted the notice of organizations and departments who ordinarily devote themselves to science. Everyone has heard about the 'power lines cause cancer' scare, and the ] felt it worth their time to state that "</nowiki>o plausible biophysical mechanisms for the systematic initiation or promotion of cancer by these power line fields have been identified.]" They have issued no corresponding statement on the misapplication of quantum mechanics in service of mysticism. The test of whether such a body has issued a statement is a much better indicator of how widespread a practice is or how much it impinges on their mission than it is an indicator of "how pseudoscientific" it is. Skeptical bodies are interested in pseudoscience, and may make reliable statements regarding it.

There is also a perennial proposal to rename the list to include ''alleged'', ''purported'', or some similar qualifier in the title. ] gives what I see as the best-articulated formulation of this position ]. My own position is that we should rely on in-line attribution and nuanced explanations to ]. A ridiculous analogy would be a proposed rename to ].

'''Requested clarifications'''
:* How do we treat topics some of whose aspects are reliably described as pseudoscientific?
:* How does ] bear on source segregation, attribution, and pseudoscience?

'''Requested non-clarifications'''
:* Sufficiency of sourcing is a content matter.
:* How do we deal with advocacy, both in ] and in ]?
:* A saintly uninvolved administrator may wish to consider ].

==== Statement by ] ====
<!-- Leave this section for others to add additional statements -->

==== Statement by ] ====
<!-- Leave this section for others to add additional statements -->

==== Clerk notes ====

==== Arbitrator views and discussion ====
*This is a content dispute, and I see no evidence that this could not be solved within the community. &mdash;&nbsp;]&nbsp;<sup>]</sup> 15:35, 10 January 2009 (UTC)
*Content dispute, plus this could be affected by the current RFAR case on Fringe sciences, which is in voting phase. <span style="font-family:Verdana,sans-serif"> — ] • ] • </span> 18:45, 10 January 2009 (UTC)
*'''Decline'''. Normal content disagreement, not requiring the intervention of ArbCom. If discussion isn't getting anywhere, ]. If something ''truly'' is an endemic problem regarding "psuedoscience", and classification as such, there's an ongoing case about the fringe science topic area. ] (]) 21:31, 10 January 2009 (UTC)
** '''Further comment'''. The page has the eyes of one or more experienced editors that seem willing to assist with helping to settle the dispute and resolve the behavioral issues. I would recommend trying to work with them to resolve the situation. If that option fails, there are still other options to explore. ] and ] mediation are options I would recommend exploring. ], ], and ] noticeboards can be used as ''needed'' to request administrator assistance with behavioral issues. Regarding references towards the fringe science case, if this situation is relevant, please add evidence to the case. If ] is an important and relevant principle, please add appropriate workshop proposals to the case. ] (]) 18:26, 11 January 2009 (UTC)
*'''Decline''' ] 02:41, 11 January 2009 (UTC)
*'''Decline''' ] (]) 04:28, 11 January 2009 (UTC)
*'''Decline''' Rlevse sums it up well. ] (] '''·''' ]) 10:32, 11 January 2009 (UTC)
*I am leaning towards declining also as this is a content issue and the proposed decisions of the current fringe science case does have elements that will help. Also, there is still plenty of time to workshop if more are needed. In regards to the requested changes to the pseudoscience case, the principles already indicate to what extent they apply to content as well as "category:pseudoscience", using the terms '''''labeled''''' and '''''categorized'''''. It appears as if the ambiguity is in the word "categorized", which may refer to the ] functionality described in the guideline ], or it may refer to the characterisation of a topic within content of articles. If it is the latter, "labeled" is a term of strong and unambiguous characterisation, while "categorized" is a term of loose characterisation. My reading of principle 15 is that ''only'' obviously bogus science can be "labeled" as such in the content of an article without good sources to support that label. With that in mind, principle 16 indicates that "generally considered pseudoscience by the scientific community" would need still need proper sources. <span style="font-variant:small-caps">] <sup>'''(])'''</sup></span> 10:48, 11 January 2009 (UTC)
*'''Decline''' per Vassyana's comment. -]] 10:53, 11 January 2009 (UTC)
*'''Decline''' - content dispute. My advice, if it will help, would be for those expending time and effort on the very difficult task of finding a stable version of such a list, to work instead on improving ] (and related articles) and all the articles of the potential candidates for this list. Once that is done, then it may be more obvious whether the list in question is possible or even needed. To clarify further, good articles are generally more helpful and informative than controversial lists, and those lists are best done after the groundwork has been done at the articles. ] (]) 00:56, 12 January 2009 (UTC)
----

Latest revision as of 03:40, 31 January 2023

Wikimedia project page

Weighing scales Arbitration​Committee
Dispute resolution
(Requests)
Tips
Content disputes
Conduct disputes
Misplaced Pages Arbitration
Open proceedings
Active sanctions
Arbitration Committee
Audit
Track related changes
Shortcuts

A request for arbitration is the last step of dispute resolution for conduct disputes on Misplaced Pages. The Arbitration Committee considers requests to open new cases and review previous decisions. The entire process is governed by the arbitration policy. For information about requesting arbitration, and how cases are accepted and dealt with, please see guide to arbitration.

To request enforcement of previous Arbitration decisions or discretionary sanctions, please do not open a new Arbitration case. Instead, please submit your request to /Requests/Enforcement.

This page transcludes from /Case, /Clarification and Amendment, /Motions, and /Enforcement.

Please make your request in the appropriate section:

Arbitration Committee proceedings Case requests

Currently, there are no requests for arbitration.

Open cases
Case name Links Evidence due Prop. Dec. due
Palestine-Israel articles 5 (t) (ev / t) (ws / t) (pd / t) 21 Dec 2024 11 Jan 2025
Recently closed cases (Past cases)

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

Clarification and Amendment requests

Currently, no requests for clarification or amendment are open.

Arbitrator motions
Motion name Date posted
Arbitrator workflow motions 1 December 2024

Requests for arbitration

Shortcuts

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-l@lists.wikimedia.org. In your request, you should briefly (in 1-2 sentences) include (a) why you need additional words and (b) a broad outline of what you hope to discuss in your extended submission. The Committee endeavors to act upon extension requests promptly and aims to offer flexibility where warranted.
    • Members of the Committee may also grant extensions when they ask direct questions to facilitate answers to those questions.
  • Refactoring statements. You should write carefully and concisely from the start. It is impermissible to rewrite a statement to shorten it after a significant amount of time has passed or after anyone has responded to it (see 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.


Requests for clarification and amendment

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

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

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

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

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

Guidance on participation and word limits

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

  • Motivation. Word limits are imposed to promote clarity and focus on the issues at hand and to ensure that arbitrators are able to fully take in submissions. Arbitrators must read a large volume of information across many matters in the course of their service on the Committee, so submissions that exceed word limits may be disregarded. For the sake of fairness and to discourage gamesmanship (i.e., to disincentivize "asking forgiveness rather than permission"), word limits are actively enforced.
  • In general. Most submissions to the Arbitration Committee (including statements in arbitration case requests and ARCAs and evidence submissions in arbitration cases) are limited to 500 words, plus 50 diffs. During the evidence phase of an accepted case, named parties are granted an automatic extension to 1000 words plus 100 diffs.
  • Sectioned discussion. To facilitate review by arbitrators, you should edit only in your own section. Address your submission to arbitrators, not to other participants. If you wish to rebut, clarify, or otherwise refer to another submission for the benefit of arbitrators, you may do so within your own section. (More information.)
  • Requesting an extension. You may request a word limit extension in your submission itself (using the {{@ArbComClerks}} template) or by emailing clerks-l@lists.wikimedia.org. In your request, you should briefly (in 1-2 sentences) include (a) why you need additional words and (b) a broad outline of what you hope to discuss in your extended submission. The Committee endeavors to act upon extension requests promptly and aims to offer flexibility where warranted.
    • Members of the Committee may also grant extensions when they ask direct questions to facilitate answers to those questions.
  • Refactoring statements. You should write carefully and concisely from the start. It is impermissible to rewrite a statement to shorten it after a significant amount of time has passed or after anyone has responded to it (see 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

Shortcuts:
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129130131

Motions

Shortcuts

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)

You can make comments in the sections called "community discussion" or in some cases only in your own section. Arbitrators or clerks may summarily remove or refactor any comment.

Arbitrator workflow motions

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

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 an automatic check at 03:40, 31 January 2023 (UTC)

Motion name Support Oppose Abstain Passing Support needed Notes
Motion 1: Correspondence clerks 2 4 0 Currently not passing 4 One support vote contingent on 1.4 passing
Motion 1.2a: name the role "scrivener" 1 3 1 Currently not passing 4
Motion 1.2b: name the role "coordination assistant" 0 2 3 Currently not passing 4
Motion 1.3: make permanent (not trial) 0 4 1 Currently not passing 5
Motion 1.4: expanding arbcom-en directly 1 3 1 Currently not passing 4
Motion 2: WMF staff support 0 5 0 Cannot pass Cannot pass
Motion 3: Coordinating arbitrators 4 0 0 Currently not passing 2
Motion 4: Grants for correspondence clerks 0 4 0 Currently not passing 6
Notes


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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
  1. 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)
  2. 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)
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)
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)

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

If any arbitrator prefers this way, unhat this motion and vote for it.
The following discussion has been closed. Please do not modify it.

If motion 1 passes, replace the text The Arbitration Committee may appoint one or more former elected members of the Arbitration Committee to be correspondence clerks for the Arbitration Committee. with the text The Arbitration Committee may appoint, from among the English Misplaced Pages functionary corps (and preferably from among former members of the Arbitration Committee), one or more users to be correspondence clerks for the Arbitration Committee..

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

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
Oppose
Abstain


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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
  1. Nicely whimsical, and not as likely to be confusing as correspondence clerk. CaptainEek 04:11, 7 December 2024 (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)
Abstain
  1. 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)
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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
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)
Abstain
  1. I am indifferent between this and "correspondence clerk". Best, KevinL (aka L235 · t · c) 03:11, 7 December 2024 (UTC)
  2. 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)
  3. That would be okay. ~ ToBeFree (talk) 19:08, 14 December 2024 (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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
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)
Abstain
  1. 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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
  1. Much less trouble to have them on the main list than to split the lists. CaptainEek 04:13, 7 December 2024 (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)
Abstain
  1. 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)
Arbitrator discussion

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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
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)
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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
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)
Oppose
Abstain

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 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
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)
Abstain

Motion 4: Arbitrator views and discussions

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)

Requests for enforcement

Click here to add a new enforcement request
For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
See also: Logged AE sanctions

Important informationShortcuts

Please use this page only to:

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

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

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

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

Appeals and administrator modifications of contentious topics restrictions

The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following:

All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction.

The appeal process has three possible stages. An editor appealing a restriction may:

  1. ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
  2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
  3. submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email.

Appeals submitted at AE or AN must be submitted using the applicable template.

A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted.

Changing or revoking a contentious topic restriction

An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies:

  • The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change, or is no longer an administrator; or
  • The contentious topic restriction was imposed (or last renewed) more than a year ago and:
    • the restriction was imposed by a single administrator, or
    • the restriction was an indefinite block.

A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction:

  • a clear consensus of uninvolved administrators at AE,
  • a clear consensus of uninvolved editors at AN,
  • a majority of the Arbitration Committee, acting through a motion at ARCA.

Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped.

Standard of review
On community review

Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if:

  1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
  2. the action was not reasonably necessary to prevent damage or disruption when first imposed, or
  3. the action is no longer reasonably necessary to prevent damage or disruption.
On Arbitration Committee review

Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if:

  1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
  2. the action represents an unreasonable exercise of administrative enforcement discretion, or
  3. compelling circumstances warrant the full Committee's action.
  1. The administrator may indicate consent at any time before, during, or after imposition of the restriction.
  2. This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.
Appeals and administrator modifications of non-contentious topics sanctions

The Arbitration Committee procedures relating to modifications and appeals state:

Appeals by sanctioned editors

Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

  1. ask the enforcing administrator to reconsider their original decision;
  2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
  3. submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-en@wikimedia.org).
Modifications by administrators

No administrator may modify or remove a sanction placed by another administrator without:

  1. the explicit prior affirmative consent of the enforcing administrator; or
  2. prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

Important notes:

  1. For a request to succeed, either
(i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or
(ii) a passing motion of arbitrators at ARCA
is required. If consensus at AE or AN is unclear, the status quo prevails.
  1. While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.
  2. These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature.
  3. All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.
Information for administrators processing requests

Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give.

A couple of reminders:

  • Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request.
  • When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X".
  • Enforcement measures in arbitration cases should be construed liberally to protect Misplaced Pages and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Misplaced Pages policies and guidelines; you may use administrative discretion to resolve it.
  • More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated.

Closing a thread:

  • Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days.
  • Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct.
  • You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages.
  • Please log sanctions in the Arbitration enforcement log.

Thanks again for helping. If you have any questions, please post on the talk page.

Arbitration enforcement archives
1234567891011121314151617181920
2122232425262728293031323334353637383940
4142434445464748495051525354555657585960
6162636465666768697071727374757677787980
81828384858687888990919293949596979899100
101102103104105106107108109110111112113114115116117118119120
121122123124125126127128129130131132133134135136137138139140
141142143144145146147148149150151152153154155156157158159160
161162163164165166167168169170171172173174175176177178179180
181182183184185186187188189190191192193194195196197198199200
201202203204205206207208209210211212213214215216217218219220
221222223224225226227228229230231232233234235236237238239240
241242243244245246247248249250251252253254255256257258259260
261262263264265266267268269270271272273274275276277278279280
281282283284285286287288289290291292293294295296297298299300
301302303304305306307308309310311312313314315316317318319320
321322323324325326327328329330331332333334335336337338339340
341342343344345346

Ethiopian Epic

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 Ethiopian Epic

User who is submitting this request for enforcement
Tinynanorobots (talk · contribs · deleted contribs · logs · filter log · block user · block log) 11:23, 12 December 2024 (UTC)
User against whom enforcement is requested
Ethiopian Epic (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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


Sanction or remedy to be enforced
Misplaced Pages:Arbitration/Requests/Case/Yasuke
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. November 14th created during the Yasuke case and went active when it ended. First 11 edits were to Government of Japan. In one case three edits were used to write one sentence.
  2. November 12 Manually reverted the lead back to how it was in September.
  3. November 16 Falsely Claimed cited material was OR. (G
  4. November 24 Falsely Claimed cited material was unsourced
  5. November 24 It took an ANI report to get him to use the article talk page. His defense was accusations and denial.
  6. November 23 He reverted to a version that went against consensus established on the talk page and contained a falsely sourced quote.
  7. November 25 Engages in sealioning
  8. November 29 Removes a well sourced line from Yasuke as well as reverted an edit that was the result of BRD. He has now started disputes with me on all three Yasuke related articles.
  9. November 30 starts disputing a new section of
  10. December 2 Brought again to ANI, he claims that I didn't get consensus for changes, even though I had discussed them on talk prior to making them.
  11. December 4 He keeps mentioning ONUS, and asking me to discuss it, in response to me discussing.
  12. December 9 Used a non-controversial revert to hide his edit warring.
  13. December 11 did the same thing on List of foreign-born samurai in Japan.
  14. December 11 He also repeatedly complains that he doesn't like the definition because it is vague and claims that his preferred version is "status quo"
Diffs of previous relevant sanctions, if any
  1. Date Explanation
  2. Date Explanation
If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)
[
  • Alerted about discretionary sanctions or contentious topics in the area of conflict, on December 1 (see the system log linked to above).


Additional comments by editor filing complaint

I am not sure if this is actually a AE matter, but was told to go here by multiple admins. The biggest issue is the Editing against consensus on accompanied by bludgeoning. However, there are signs of bad faith editing on all three pages where I have interacted with EE. It could also be a CIR issue or it could be some sort of harassment. I don't know. I just know that EE first avoided providing clear reasons for reverting edits and has been trying to engage in Status Quo Stonewalling. He keeps citing Onus or Burden and asks me not to make a change until the discussion is over. Often, this doesn't make sense in context, because the change was in place. He has made false claims about sources and what they say. His editing on Yasuke is not so much a problem as the discussion which comes across as gaslighting.

@User:Red-tailed hawk, I am not an expert on proxies or socks. All the IPs have only posted on the one article and have advocated an odd definition for samurai, that doesn't apply to the article. All except the first one have just reverted. It is possible that this is just laziness, or lack of confidence in writing skills etc. After all, the false citation was added by another user and was just kept. I found the latest one the most suspect, in part because of it first reverting to the incorrect definition, before restoring most of the text and second because of falsely citing policy. I am not sure if they are proxies, but I hoped that someone here would have the expertise to know. I don't think the proxy evidence is the most important. EE is either acting in bad faith or has CIR problems. The later is possible, because he thanked City of Silver during ANI, although City of Silver has been the harshest critic of EE's behaviour towards me.
I think there should be some important context to the quote: "those who serve in close attendance to the nobility". The quote can be found in several books, on Samurai it is sourced to an article published in Black Belt Magazine in the 80s by William Scott Wilson, where he describes the origin of the word samurai. He is describing the early phases of its meaning in that quote, before it became to have martial connotations. It also refers to the time before 900. The earliest foreign samurai on the list was in the late 1500s. It also doesn't apply to most of the persons on the list. Finally, it is not mentioned in Vaporis's book, which EE keeps adding as the source. He hasn't even made the effort to copy the citation from Samurai.
@User:Eronymous

Not only did I have a dispute with Symphony Regalia about samurai being "retainers to lords", but also on Yasuke about "As a samurai" and on List of Foreign-born Samurai in Japan EE made the same reverts as SR. EE had with his first edit in all three articles continued a dispute that I had already had with SR.

@User:Ethiopian Epic I actually don't have a problem with you discussing things. Your talk page posts aren't really discussion though. Your main argument on all three pages has been a shifting of the burden of proof. You don't really discuss content and continually ask me not to make changes without discussing first, and then make changes yourself. I understand that your position is that your preferred version is the status quo. However, my edits regarding the definition on List of Foreign-born samurai in Japan , were discussed and consensus was clearly gotten. Similarly, my edits on Yasuke were discussed, and even though I didn't use the exact same version as Gitz said, Gitz had suggested using warrior instead of bushi, so I used samurai, because I thought it would be less controversial.
Notification of the user against whom enforcement is requested


Discussion concerning Ethiopian Epic

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 Ethiopian Epic

This is clear retaliatory filing because I recently didn't agree with Tinynanorobot's edits against RFC consensus, and because I made talk page sections on some recent edits.

@Eronymous That's not true and you are a very obvious alt account with only 26 edits. No one gave you a notification of this discussion and it's not on the Yasuke talk page. This suggests you are the sock puppet of someone here. Your post is also misleading and incorrect it wasn't an insertion. The line you are talking about in Samurai has been there for over 10 years and is normal. I know because I've read it before. Here is a version from 2017 that still has it. I don't understand why you are misrepresenting edits and using an alt account.

@Red-tailed hawk I think he is just fishing. That's why he removed his IP claims. Even his other diffs are just mislabeled regular behavior. It's amusing because Eronymous is the likely alt of Tinynanorobots or someone posting here. I think the way Tinynanorobots edits against clear consensus, skips discussion, and then files frivolous ANI/AE reports with misleading narrative like above is disruptive. Discussion is an easy solution and benefits everyone. I hope he will respect RFC consensus.

Statement by Relm

I am largely unfamiliar with the account in question, but I do frequently check Yasuke. I believe that EthiopianEpic has displayed a clear slant and battleground mindset in their editing in regards to the topic of Yasuke, but that their conduct on the Yasuke page itself so far has generally been in the ballpark of good faith edits. The revert on December 9th was justified, and their topic on November 29th is well within bounds (though I acknowledge that the background of their prior disputes on other pages with Tinynanorobots shows it may be edit warring) given that the two things being reverted was a change that seemed to skirt the prior RFC with agreement being given in a very non-direct way, and the other portion being an addition which had not been discussed on the talk page prior to its implementation (though previous discussions ered on the side of not including it). I am not accusing Tinynanorobots of any misconduct in any part of that either.

What I will note is that in addition to the sockpuppet IP allegations made by Tinynanorobots, I wanted to lodge that the posting style of EthiopianEpic, as well as their knowledge of much of the previous discussions on the page deep in the archive, led me to suspect that they were an alt of User:Symphony_Regalia. I never found anything conclusive. Relm (talk) 14:48, 12 December 2024 (UTC)

Statement by Simonm223

These two editors have been tangling at WP:AN/I repeatedly. Last time they came there I said that this would likely continue until a third party intervened. And then the thread got archived with no action (see AN/I thread here) so I'm not surprised that the two of them are still tangling. There is evidence that both editors have engaged in a slow-motion edit war. Both have claimed the other is editing against consensus. Here I will say that it appears TinyNanoRobots is more correct than Ethiopian Epic. Furthermore, while neither editors' comportment has been stellar, as other editors have pointed out, it appears more that EE is following TNR about and giving them a hard time than the alternate. . In the linked AN/I case (above) you'll note EE attempted a boomerang on TNR and was not well-received for the effort.

Frankly my view is that both editors are not editing to the best standards of Misplaced Pages but there is definitely a more disruptive member of this duo and that is Ethiopian Epic. I think it would probably cut down on the noise considerably if they were encouraged to find somewhere to edit which was not a CTOP subject and if they were encouraged to leave TNR alone. Simonm223 (talk) 18:05, 12 December 2024 (UTC)

Statement by Eronymous

Similar to Relm I check on the Yasuke page every so often, and it seems very likely given the evidence that User:Ethiopian Epic is an alt of User:Symphony_Regalia created to evade his recent ArbCom sanctions, having started editing the day prior to the Yasuke case closure. Of note to this is the last edit of Symphony_Regalia on Samurai was him attempting to insert the line "who served as retainers to lords (including daimyo)" - curiously enough, Ethiopian Epic's first edit on Samurai (and first large edit, having just prior made 11 minor ones in a short timeframe to reach autoconfirmed status) is him attempting to insert the same controversial line that was reverted before.

Symphony_Regalia has a history of utilising socks to edit Yasuke/Samurai related topics and is indefinitely blocked from the .jp wiki for extensive sockpuppetry (plus multiple suspected IPs) for this.

Prior to being sanctioned Symphony Regalia frequently got into exactly the same arguments concerning wording/source material with User:Tinynanorobots that Ethiopian Epic is now. One could assume based on their relationship that he is aggrieved that Tinynanorobots was not sanctioned by ArbCom during the case and is now continuously feuding with him to change that through edit warring and multiple administrator incidents/arbitration requests in the past few weeks. Eronymous (talk) 22:31, 12 December 2024 (UTC)

Statement by Nil Einne

I was ?one of the editors who suggested Tinynanorobots consider ARE in the future. I did this mostly because after three threads on ANI with no result, I felt a change of venue might be more productive especially since the more structured nature of ARE, as well as a likely greater concern over low level of misconduct meant that some outcome was more likely. (For clarity, when I suggested this I did feel nothing would happen from the third ANI thread but in any case my advice being taken onboard would likely mean the third thread had no result.) I did try to make clear that I wasn't saying there was definitely a problem requiring sanction and also it was possible Tinynanorobots might themselves end up sanctioned. Since a topic ban on both is being considered, I might have been right in a way. If a topic ban results, I'd like to suggest admins considered some guidance beyond broadly constructed on how any topic ban would apply. While the entirety of the Yasuke article and the list of foreign born samurai stuff seem clear enough, one concern I've had at ANI is how to handle the editing at Samurai and its talk page. A lot of the recent stuff involving these editors seems to relate to the definition of samurai. AFAIK, this is generally been a big part of the dispute of Yasuke (he can/can't be a samurai because it means A which was/wasn't true about him). Nil Einne (talk) 12:42, 15 December 2024 (UTC)

Result concerning Ethiopian Epic

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • I've never been very impressed with retaliatory filings, and the one below is no exception. I will also note that I'm never too impressed with "must be a sock" type accusations—either file at SPI or don't. In this case, though, I think Yasuke would be better off if neither of these two were participating there. Seraphimblade 19:33, 12 December 2024 (UTC)
    Red-tailed hawk, what are your thoughts after the responses to you? Seraphimblade 16:18, 17 December 2024 (UTC)
    I think that it would be declined if it were an WP:SPI report and the editor should be mindful not to throw sock accusations around willy-nilly going forward. But I typically don't see any sort of sanction imposed when someone makes a bad SPI report, particularly if they're newer or aren't quite clueful yet. So I don't see much to do on that front other than tell them that we need more specific evidence of socking when reports are made than merely shared interest, particularly when the IPs are scattered across the world. — Red-tailed hawk (nest) 02:24, 18 December 2024 (UTC)
    I'm still inclined to topic ban both these editors from Yasuke, but would be interested in hearing more thoughts on that if anyone has them. Seraphimblade 07:10, 23 December 2024 (UTC)
  • I also generally don't like "might-be-a-sock"-style accusations; when we are accusing someone of sockpuppetry by logged out editing we typically need evidence to substantiate it rather than just floating the possibility in a flimsy way. Filer has provided several diffs above as possible socks, but each of those IPs geolocates to a different country (Germany, Norway, and Argentina respectively) and I don't see evidence that any of those IPs are proxies.@Tinynanorobots: Can you explain what led you to note the IP edits? Is it merely shared interest and viewpoint, or is there something more?— Red-tailed hawk (nest) 02:01, 13 December 2024 (UTC)
  • Looking at this .... mess... first, I'm not sure what actually was against the ArbCom decision - I don't see a 1RR violation being alleged, and the rest really appears to me to be "throw stuff at the wall and see if it sticks". But, like Seraphimblade, I'm not impressed with either of these editors actual conduct here or in general. I could be brought around to supporting a topic ban for both of these editors in the interests of clearing up the whole topic area. Ealdgyth (talk) 14:33, 13 December 2024 (UTC)
  • @Tinynanorobots: you are well above the 500 word limit. Please request an extension before adding anything more. Barkeep49 (talk) 16:18, 17 December 2024 (UTC)

Tinynanorobots

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 Tinynanorobots

User who is submitting this request for enforcement
EEpic (talk) 19:14, 12 December 2024 (UTC)
User against whom enforcement is requested
Tinynanorobots (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced
Misplaced Pages:Arbitration/Requests/Case/Yasuke
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. 09:21, 14 November 2024. Tinynanorobots removes As a samurai from the lead text and replaces it with signifying bushi status against RFC consensus (There exists a consensus to refer to Yasuke as a samurai without qualification).
  2. 17:12, 15 November 2024. Tinynanorobots removes who served as a samurai from the lead text and adds who became a bushi or samurai against RFC consensus (There exists a consensus against presenting Yasuke's samurai status as the object of debate).
  3. 12:43, 20 November 2024. On List of Foreign-born Samurai, Tinynanorobots removes the longstanding definition and adds This list includes persons who ... may not have been considered a samurai against RFC consensus (There exists a consensus against presenting Yasuke's samurai status as the object of debate).
  4. 07:48, 23 November 2024. Tinynanorobots reverts to remove As a samurai in the Yasuke article after Gitz6666 opposes at , again ignoring WP:ONUS.
  5. 03:13, 4 December 2024. I restore and start a talk page discussion so that consensus can be formed.
  6. 14:10, 6 December 2024 . Tinynanorobots, when consensus fails to form for his position, becomes uncivil and engages in a sarcastic personal attack What you are saying doesn't make sense. Perhaps there is a language issue here. Maybe your native language handles the future differently than English?
  7. 14:22, 11 December 2024. Tinynanorobots removes "As a samurai" again, ignoring WP:ONUS and BRD even though no consensus has formed for his position, and no consensus has formed to change existing consensus.
  8. 08:37, 6 December 2024. Tinynanorobots explains their reasons, I don't know if samurai is the right term which is against consensus.
  9. 07:27, 28 November 2024. POV-pushing - With no edit summary Tinynanorobots tag bombs by adding Slavery in Japan.
Diffs of previous relevant sanctions, if any
  1. Date Explanation
  2. Date Explanation
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

Tinynanorobots frequently edits against consensus, restores his edits when others revert, doesn't wait for consensus, and engages in feuding behavior. He seems to think WP:BRD or WP:ONUS don't apply to him which is disruptive, and I don't know why.

Unaccounted removals of sources 23:44, 14 September 2024 - Warning from other editor about repeated removal of content when multiple users are objecting.

AGF 12:21, 15 September 2024 - Warning from yet another editor about not assuming good faith and making personal attacks

It seems to be chronic which suggests behavior problems. Tinynanorobots also frequently fails to assume good faith in others. I don't know why as I don't have any issues with him.

Their preferred edit for Yasuke against the RFC consensus is now still in the lead section.

@Relm Sorry for the confusion. I think we talking about different edits, so I'll adjust that part. I am referring to Tinynanorobot's repeated removal of As a samurai against RFC consensus, which states There exists a consensus to refer to Yasuke as a samurai without qualification.

Notification of the user against whom enforcement is requested

18:40, 12 December 2024

Discussion concerning Tinynanorobots

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 Tinynanorobots

The accusations made by EE are so misleading as to be evidence against him. Most of what he is discussing is in reference to a successful BRD. I actually discussed the bold edit first on the talk, but didn't get much of a response. I decided a bold edit would get more feedback. The edits were reverted and then discussed. Gitz's main problem was OR, not a RfC violation. This was because he didn't read the cited source. Anyway, since Atkin says "signifying bushi status", I have no objection to restoring this text.

I never used any sarcasm, I know that some languages handle how they talk about time differently. It seems reasonable that a translation error could be the reason for EE asking me not to change the article, althoug my edit had already been restored by someone else and at the same time asking me to discuss that I had already discussed and was already discussing. I am disappointed that EE didn't point out that he felt attacked, so that I could apologize.

This was written in response to another user, and the whole thought is I don't know if samurai is the right term. It is the term a fair amount of sources use, and the one that the RfC says should be used. It is also consistent with common usage in reference to other historical figures. In fact earlier in that post I said this: I am not qualified to say whither or not Yasuke having a house meant that he was a samurai This is blatantly taking a quote out of context in order to prejudice the Admins against me.

@User:Ealdgyth I filed here, because the last time I filed at ANI it was suggested that I bring things here if things continue by an Admin. I try to follow advice, although I keep getting conflicting signals from Admins. I am most concerned that you find my work on Samurai and List of Foreign-born Samurai in Japan not adding anything helpful. My suggestion to rewrite the way samurai was defined on the List in order to reduce OR and bring it in line with WP:LSC was meant with unanimous approval by those who responded. Samurai is a high importance article that has tags on it from years back, is unorganized and contains outdated information. I am not the best writer, but I have gotten some books, and am pretty much the only one working on it.
I just thought that the Admins here should know about the ongoing SPI

Statement by Relm

I am the editor alluded to and quoted as 'protesting' Tinynanorobots edit. When I originally made that topic, I was fixing a different edit which left the first sentence as a grammatically incomplete sentence. When I looked at it in the editing view, one of the quotes in the citation beforehand was quoting Atkins Vera, and I mistook this for the opening quote having been changed. When I closed the editing menu I saw 'signifying samurai status' in the second paragraph and confused the two for each other as I had not noticed the addition of the latter phrase a little under a month ago. I realized my mistake almost immediately after I posted the new topic, and made this (1) edit to clarify my mistake while also attempting to instead direct the topic towards making sure that the edit recieved sufficient assent from Gitz (it did) and to talk about improvements that could be made to the opening sentence. I further clarified and made clear that I was not accusing Tinynanorobots of having done anything wrong in a later response (2).

Though many of their earlier edits on the page may show some issues, as they grew more familiar with the past discussions I believe that Tinynanorobots has made valuable contributions to the page in good faith. Relm (talk) 03:21, 13 December 2024 (UTC)

Statement by Barkeep49


Statement by (username)

Result concerning Tinynanorobots

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • As above, I'm failing to see what exactly is against the ArbCom case rulings - I don't see a 1RR violation. But also as above, I'm coming to the view that neither of these editors are adding anything helpful to the topic area and am leaning towards a topic ban for both. Ealdgyth (talk) 14:35, 13 December 2024 (UTC)

Rasteem

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 Rasteem

User who is submitting this request for enforcement
NXcrypto (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:06, 13 December 2024 (UTC)
User against whom enforcement is requested
Rasteem (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. 23:21 12 December 2024 - removed wikilink of an Indian railway station thus violating his topic ban from India and Pakistan.

This violation comes after he was already warned for his first violation of the topic ban.

Upon a closer look into his recent contribution, I found that he is simply WP:GAMING the system by creating articles like Arjan Lake which is overall only 5,400 bytes but he made nearly 50 edits here. This is clearly being done by Rasteem for passing the 500 edits mark to get his topic ban overturned.

I recommend increasing the topic ban to indefinite duration. Nxcrypto Message 03:06, 13 December 2024 (UTC)

Diffs of previous relevant sanctions, if any
"topic banned from the subject of India and Pakistan, broadly construed, until both six months have elapsed and they have made 500 edits after being notified of this sanction."
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 agree that there are genuine CIR issues with Rasteem, for example while this ARE report is in progress they created Javan Lake, which has promotional statements like: "The lake's stunning caluts, majestic desert topographies, and serene lakes produce a shifting destination. Its unique charm attracts a wide range of guests, from adventure contenders to nature suckers and beyond". Nxcrypto Message 03:26, 14 December 2024 (UTC)
Notification of the user against whom enforcement is requested


Discussion concerning Rasteem

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 Rasteem

This approach seems to be a coordinated attack to abandon me from Misplaced Pages indefinitely. Indeed, after my ban for 6 months. I was banned on 6 December, and in just 7 days, this report is literally an attempt to make me leave Misplaced Pages.

1. I rolled back my own edit; it was last time made unintentionally. I was about to revert it, but my internet connection was lost, so when I logged in again, I regressed it.

The internet is constantly slow and sometimes goes down. I live in a hilly location and I had formerly mentioned it.

My edits on Arjan Lake isn't any WP:GAMING factual number of edits I made; it is 45, not 50. Indeed, I made similar edits before in September and December months on the same articles within a single day or 2-3 days.

2. List of villages in Khoda Afarin on this article, I've added 5680 bytes & made 43 edits.

3. List of villages in Tabriz on this article I've added 4000 bytes & made 49 edits.

Statement by (username)

Result concerning Rasteem

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • While I don't see a change in editing pattern that indicates gaming, the edits to Arjan Lake indicate issues with competence, as the article is weirdly promotional and contains phrases such as "beast species", "emotional 263 proved species". —Femke 🐦 (talk) 20:57, 13 December 2024 (UTC)
  • Adding to Femke's point, magnific 70- cadence-high waterfalls in this area is not prose that inspires confidence in the editor's competence to edit the English Misplaced Pages. So, we have violations of a topic ban and questions about the editor's linguistic competence and performance. Perhaps an indefinite block appealable in six months with a recommendation to build English competency by editing the Simple English Misplaced Pages, and to build general Misplaced Pages skills by editing in the version of Misplaced Pages in the language they speak best during that minimum six month period. As for Arjan Lake, although the prose is poor, the references in the article make it clear to me that the topic is notable, so the editor deserves some credit for starting this article that did not exist for two decades plus. Cullen328 (talk) 08:57, 14 December 2024 (UTC)
  • Brief comment to avoid the archive bot. Seraphimblade 17:46, 25 December 2024 (UTC)

KronosAlight

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 KronosAlight

User who is submitting this request for enforcement
Butterscotch Beluga (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:16, 16 December 2024 (UTC)
User against whom enforcement is requested
KronosAlight (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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


Sanction or remedy to be enforced
Misplaced Pages:Arbitration/Requests/Case/Palestine-Israel articles 4#ARBPIA General Sanctions
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. 14 December 2024
  • Adds "depiste being an ex-Muslim" to dismiss accusations of Islamophobia MOS:EDITORIAL.
  • Adds MOS:SCAREQUOTES around ‘promoted Islamophobia’ & ‘Islamophobia’ while removing the supporting context.
  • Changed "interpreted that statement as a threat and incitement to violence" to "claimed was a threat and incitement to violence, though no threats or violence in fact occurred" MOS:CLAIM & MOS:EDITORIAL
  1. 14 December 2024 - MOS:TERRORIST
  1. 14 December 2024 - MOS:TERRORIST
  2. 14 December 2024 - MOS:TERRORIST
  • Unnecessarily specific additions that may constitute WP:POVPUSH such as adding "against civilians" & changing "prevent the assassinations of many Israelis" to "prevent the assassinations of many Israeli civilians and soldiers"
  1. 14 December 2024 - MOS:TERRORIST
Diffs of previous relevant sanctions, if any
  1. 24 June 2024 Warned to abide by the one-revert rule when making edits within the scope of the Arab-Israeli conflict topic area.
  2. 22 October 2024 Blocked from editing for 1 week for violating consensus required on the page Zionism
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

All edits were made at Mosab Hassan Yousef. After I partially reverted their edits with an explanation, I brought the issue to their attention on the talk page, asking for their rationale. They replied that they were "correcting factual errors introduced by previous antisemitic editors" & asked if I "perhaps have a deeper bias that’s influencing decisions in this respect?"

They then undid my partial revert

Ealdgyth - While I can't find any comments where they were explicitly "warned for casting aspersions", they were asked back in June to WP:AGF in the topic area.
Also, apologies for my "diffs of edits that violate this sanction" section, this is the first time I've filed a request here & I thought it'd be best to explain the preamble to my revert, but I understand now that I misunderstood the purpose of that section & will remember such for the future. - Butterscotch Beluga (talk) 15:37, 16 December 2024 (UTC)
@Vanamonde93 I was able to find a copy of the opinion article being cited 'They Need to Be Liberated From Their God'. Butterscotch Beluga (talk) 20:14, 16 December 2024 (UTC)
Notification of the user against whom enforcement is requested


Discussion concerning KronosAlight

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 KronosAlight

This is a complete waste of the Arbitration Committee’s time.

1. That Yousef was born and raised a Muslim is important and neutral context for readers to be aware of when the article refers to claims of ‘Islamophobia’.

2. The scarequotes indicate that the claim comes from the sources provided, rather than being an objective ‘fact’ determined by a few Misplaced Pages Editors with an axe to grind.

3. This was already addressed on the Talk page and I updated the sentence to say settlers/soldiers with a further label that it needed further clarification because the source does not in fact unambiguously say what Butterscotch Beluga claims.

A few lines above what Butterscotch Beluga quotes is the following lines: “AMANPOUR: How did you take part in that? Were you one of the small children who threw rocks at Israeli soldiers?

YOUSEF: The model for every Palestinian child is a mujahid (ph) or a fidahi (ph) or a fighter. So, of course, I wanted to be one at that point of my life. It wasn't -- it's not my only dream. It's every child's dream in that territory.”

The updated Wiki page noted both settlers/soldiers and included a note that this requires further clarification, perhaps based on other sources, because it isn’t clear (contra Butterscotch Beluga) whether he is referring to soldiers or settlers.

4. It is not controversial to accurately describe Hamas as a terrorist organisation. It is simply a fact. To suggest otherwise is POV-pushing.

5. This is not POVPUSH; ‘assassinations’ against civilians during peacetime are usually called ‘murders’.

I in fact didn’t even remove the word ‘assassinations’, I merely broadened the description from ‘Israelis’ to ‘Israeli civilians and soldiers’ (as Butterscotch accepted) to indicate the breadth of the individuals in question included both civilians and combatants. This is not POVPUSH, it is simply additional information and context verified in the source itself.

All in all, a vexatious claim and a waste of the Arbitration Committee’s time.

Statement by Sean.hoyland

Regarding "I was correcting factual errors introduced by previous antisemitic editors", it would be helpful if KronosAlight would explicitly identify the antisemitic editors and the edits they corrected so that they can be blocked for being antisemitic editors. Sean.hoyland (talk) 08:17, 16 December 2024 (UTC)

The editor has been here since 2012. It is reasonable to assume that they know the rules regarding aspersions. It is reasonable to assume they are intentionally violating them, presumably because they genuinely believe they are dealing with antisemitic editors. So, this report is somehow simultaneously a vexatious complete waste of time and the result of the someone interfering with their valiant efforts to correct errors made by antisemitic editors. Why do they have this belief? This is probably a clue, a comment they had the good sense to revert. For me, this is an example of someone attempting to use propaganda that resembles antisemitic conspiracy theories about media control to undermine Misplaced Pages's processes and then changing their mind. But the very fact that they thought of it is disturbing. Their revert suggests that they are probably aware that there are things you can say about an editor and things you cannot say about an editor. From my perspective, what we have here is part of an emerging pattern in the topic area, a growing number of attacks on Misplaced Pages and editors with accusations of antisemitism, cabals etc. stemming in part from external partisan sources/influence operations. Sean.hoyland (talk) 17:35, 16 December 2024 (UTC)

Statement by Zero0000

Aspersions:

Zero 10:36, 16 December 2024 (UTC)

Statement by Vice regent

KronosAlight, you changed on 14 Dec 2024: "An open letter signed by Christian and Muslim religious leaders interpreted that statement as a threat and incitement to violence" to "An open letter signed by Christian and Muslim religious leaders claimed was a threat and incitement to violence, though no threats or violence in fact occurred".

Can you show where either of the sources state "though no threats or violence in fact occurred"? VR (Please ping on reply) 18:07, 17 December 2024 (UTC)

Statement by Smallangryplanet

Wanted to add some pertinent evidence:

Talk:Zionism:

Talk:Allegations of genocide in the 2024 Israeli invasion of Lebanon:

Talk:Relations between Nazi Germany and the Arab world:

Talk:2024 Lebanon electronic device attacks:

Talk:Anti-Zionism:

Talk:Gaza genocide:

Talk:Nuseirat rescue and massacre:

Talk:Al-Sardi school attack:

Talk:Eden Golan:

Other sanctions:

Statement by (username)

Result concerning KronosAlight

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • Much of the "diffs of edits that violate this sanction" fail to explain "how these edits violate" the sanction - to me, much of these diffs look like a content dispute. However, the "additional comments" section DOES have a diff that is concerning and violates the CT by casting an aspersion that is not backed up by a diff - the "antisemitic editors" diff. Has KA been previously warned for casting aspersions? If they have, I'm inclined to issue a topic ban, but many other editors get a warning for this if they lack a previous warning. The diffs brought up by Zero (not all of which I necessarily see as aspersions, but the "Jew-hatred" one is definitely over the line - but it's from September so a bit late to sanction for just that) - did anyone point out that aspersions/incivility in this topic area is sanctionable? I see the warnings for 1RR and consensus required... Ealdgyth (talk) 13:30, 16 December 2024 (UTC)
    • @KronosAlight: - can you address the fact that saying "correcting factual errors introduced by previous antisemitic editors" and "Is there no limits you will not cross in order to seek to justify your Jew-hatred"? Neither of these are statements that should ever be made - and the fact that you seem to not to understand this is making me lean towards a topic ban. Ealdgyth (talk) 14:45, 17 December 2024 (UTC)
  • KronosAlight, can you please provide quotes from the references you cited for - for instance - "for his terrorist activities" in this addition, showing that the sources explicitly supported the content you added? Calling a person or an organization is perfectly acceptable if you support that with reliable sources; if it is original research, or source misrepresentation, it isn't acceptable. I cannot access some of the sources in question. You may provide quotes inside a collapsed section if you wish to save space. Vanamonde93 (talk) 19:28, 16 December 2024 (UTC)
    I missed Zero's comments earlier. A lot of those comments, while concerning, are generic, not directed at a specific editor. this, however, is beyond the pale. I would need some convincing that this user is able to edit this area constructively. Vanamonde93 (talk) 20:56, 16 December 2024 (UTC)
    @KronosAlight, can you please respond to this? I too am concerned...the quote you're objecting to wasn't from DrSmarty. It was a direct quote, scare quotes and all, from the US Holocaust Memorial Museum. You seem to have reacted to it as if it were DrSmarty. Valereee (talk) 16:06, 17 December 2024 (UTC)
  • I don't like to sanction in absentia, and I'm not yet suggesting we do so, but I want to note that not choosing not to respond here, or going inactive to avoid responding, will not improve the outcome as far as I am concerned. Vanamonde93 (talk) 17:20, 18 December 2024 (UTC)
    They're a pretty sporadic editor...many edits over a period of a few days, then nothing for two weeks. Maybe we pin this until they edit again? Valereee (talk) 17:26, 18 December 2024 (UTC)
    I agree with Valereee that this editors contribution history shows a pattern of editing for a day or two at a time followed by several weeks of inactivity. So I don't think it's fair to say they went inactive here but also holding this open for multiple weeks waiting for a response places some burden on the other other interested editors. Barkeep49 (talk) 17:33, 18 December 2024 (UTC)
    Welp, it's been nearly ten days since they first posted here, calling this a waste of time and vexatious. They're fully aware it's happening, and it's not even like they haven't been to AE before.
    I've gone through the diffs here, and it seems to me the basis of KA's problematic editing is that they're on a mission to WP:right great wrongs, specifically w/re what they see as antisemitic bias on WP. The exchange at Talk:Algeria a few weeks ago makes that pretty clear: they come into Algeria and open a section to post a content complaint about the article not covering changing Jewish demographics in the country, saying "Many people have edited it, but apparently not one has seen fit to explain" this. Another editor suggests KA fix whatever problem they're seeing, and KA responds: I made that comment to highlight the obvious problem of antisemitism among Misplaced Pages editors. The question was rhetorical. And many of their other talk contributions are focussed on these accusations of systemic bias.
    And @KronosAlight, in case you're paying attention: of course WP has systemic bias. It's usually unintentional, but in most CTOPs there are editors who consciously try to push a POV. The solution for that isn't to go 'round making accusations. It's to go 'round fixing the problem either by adding missing content or by discussing biased content in nonproblematic ways. It's the "nonproblematic ways" part you're missing, here. And if you are paying attention: You cannot make an AE case go away by ignoring it. I very strongly recommend you come in here and respond to the questions. Valereee (talk) 13:40, 26 December 2024 (UTC)

Arbitration enforcement action appeal by Nicoljaus

Procedural notes: Per the rules governing arbitration enforcement appeals, a "clear and substantial consensus of uninvolved administrators" is required to overturn an arbitration enforcement action.

To help determine any such consensus, involved editors may make brief statements in separate sections but should not edit the section for discussion among uninvolved editors. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see WP:UNINVOLVED).

Appealing user
Nicoljaus (talk · contribs · deleted contribs · logs · filter log · block user · block log) – ScottishFinnishRadish (talk) 13:09, 19 December 2024 (UTC)
Sanction being appealed
To enforce an arbitration decision, and for edit warring, and intent to game 1rr, you have been blocked indefinitely from editing Misplaced Pages.
Administrator imposing the sanction
ScottishFinnishRadish (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Notification of that administrator
I'm aware. ScottishFinnishRadish (talk) 13:18, 19 December 2024 (UTC)

Statement by Nicoljaus

The circumstances of my blocking were:

  • I was looking for a Misplaced Pages account for Hiba Abu Nada to add it to Wikidata. I couldn't find it, so I did a little research. The reference in the article indicated that she participated in some WikiWrites(?) project. I didn’t find such a project, but I found the WikiRights project: https://ar.wikipedia.org/ويكيبيديا:ويكي_رايتس. It was organized by a certain Euro-Mediterranean Human Rights Monitor. I read the Euro-Mediterranean Human Rights Monitor article and didn't see any outside perspective, "controversy" or anything like that, just self-representation. I surfed the Internet and instantly found information that must be in the article to comply with the NPOV. I started adding , everything went well for two days. Then:
  • 12:53, 23 April 2024 - Zero0000 made a complete cancellation of all additions
  • 13:14, 23 April 2024 - (20 minutes later!) Selfstudier wrote on my TP
  • 14:20 - 14:22, 23 April 2024 -‎ With two edits (first, second) I partially took into account the comment of Zero0000 about "ethnic marking", but returned the last .
  • 14:27, 23 April 2024 (7 minutes later!!) Selfstudier makes a second complete cancellation of all my edits, blaming POV editing
  • 14:45, 23 April 2024‎ - I’m returning the version where I partially took into account Zero0000’s comments (removed "ethnic marking")
  • 15:10, 23 April 2024 - Selfstudier accuses me of 1RR breach. In the dialogue, I explained that the group that really violated the rule was Selfstudier&Zero0000, who obviously acted in close coordination. My first undo was part of a counter edit User talk:Nicoljaus#1RR_breach
  • 15:41, 23 April 2024 Selfstudier writes on Misplaced Pages:Arbitration/Requests/Enforcement
  • 16:10, 23 April 2024 (30 minutes later!) ScottishFinnishRadish issues an indefinite block . No opportunity to write my “statement”, as well as an extremely bad faith interpretation of my remark as "an intent to game 1rr".

Given that the both Selfstudier and Zero0000 are currently being discussed in Arbcom (https://en.wikipedia.org/Wikipedia:Arbitration/Requests/Case/Palestine-Israel_articles_5/Evidence), I humbly ask you to take a fresh look at my indefinite block and soften the restrictions in some way". Nicoljaus (talk) 19:32, 18 December 2024 (UTC)

@ScottishFinnishRadish: - You mean, I need to discuss my previous edit war blocks? Well, the last one was almost four years ago and that time I simply forgot that I was under 1RR (there was a big break in editing) and tried to get sources for a newly added map, and the opponent refused to do so . As it turned out later, the true source was a book by a fringe author, which the RSN called "Usual nationalistic bullshit, no sign of reliability". Yes, it was a stupid forgetfulness on my part. Nicoljaus (talk) 16:18, 19 December 2024 (UTC)
@Aquillion: Even if you were correct that Selfstudier & Zero0000 were WP:TAGTEAMing (always a tricky accusation, because it's hard to separate that from just your edits being so obviously problematic that two people independently reverted them) -- That's why I wrote that my "so problematic edits" attracted attention only after two days, but two users appeared within 20 minutes. However, after months, a lot of data about the cooperation of these users appeared (and this is not my imagination): "While a single editor, Shane (a newbie), advocated for its inclusion, a trio of veterans including Zero0000, Nishidani and Selfstudier fought back. After Selfstudier accused Shane of being a troll for arguing for the photo’s inclusion, Zero0000, days later, “objected” to its inclusion, citing issues of provenance. Nishidani stepped in to back up Zero0000, prompting a response by Shane. The following day, Zero0000 pushed back against Shane, who responded. The day after, Nishidani returned with his own pushback. The tag-team effort proved too much for Shane, who simply gave up, and the effort succeeded: the photo remains absent" . I'll add that after Selfstudier accused Shane of trolling, Zero0000 appeared on Shane's page and said: "Kindly keep your insults to yourself I won't hesitate to propose you for blocking if you keep it up" . According to the table at the link , these two users cooperated like this 720 times. Probably hundreds of people were embittered, forced out of the project, or led to blocking like me.--Nicoljaus (talk) 13:02, 20 December 2024 (UTC)
@ScottishFinnishRadish: Hello, thank you very much for transferring my remarks, now I understand how it works. I would like to clarify the issue of meatpuppetry. You directly accused me of such intentions in justifying the block, and now this accusation has been repeated . Let's figure out whether my hint that Selfstudier and Zero0000 are working too closely was so absurd? Was it really and remains so absurd that it could not be perceived as anything other than my self-exposure? I don't think so.

As for the "edit war" - I understand that edit wars are evil. In the spirit of cooperation, I tried to meet my opponents halfway, as in this case, taking into account their claim, which I could understand, in the counter edit. If such an action is also considered an edit war and a violation of the 1RR/3RR rule - I will of course avoid it in the future.--Nicoljaus (talk) 16:00, 20 December 2024 (UTC)

@Valereee: Hello, I understand your point that edit wars can be disruptive, particularly in a CTOP context. However, I believe it is essential to recognize that not all reverts carry the same implications. While it is true that a revert is a revert, the context and intent behind the action should also be taken into account. In this instance, I made efforts to address the concerns of the other party involved, which reflects a willingness to engage in dialogue rather than simply reverting. Furthermore, I acknowledge your reference to the 1RR/3RR rule and my history of blocks for edit-warring. However, given the amount of time that has passed, I believe I have gained valuable insights and learned a great deal. Moreover, given this topic, I think I actually learned something unlike the other side, whose history of blocks for edit-warring remains clean.--Nicoljaus (talk) 4:24 am, Today (UTC−5)

@Valereee: In response to this, I can say that I already know very well how carelessly admins impose blocks. If any further statements are needed from me, just ping me. With best regards.--Nicoljaus (talk) 09:51, 25 December 2024 (UTC)

Statement by ScottishFinnishRadish

Absent from the appeal is discussion of the five prior edit warring blocks and any indication that they will not resume edit warring. ScottishFinnishRadish (talk) 13:18, 19 December 2024 (UTC)

I said They have a long history of edit warring, so I'd like to see that addressed rather than blaming others above, twelve days ago. ScottishFinnishRadish (talk) 16:30, 19 December 2024 (UTC)
Nicoljaus, you should be focusing on convincing people that you won't edit war in the future rather than more WP:NOTTHEM. ScottishFinnishRadish (talk) 13:11, 20 December 2024 (UTC)

Statement by (involved editor 1)

Statement by (involved editor 2)

Discussion among uninvolved editors about the appeal by Nicoljaus

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 Simonm223

This edit looks like a bright-line WP:BLP violation via WP:ATTACK and WP:WEASEL - and removing BLP violations are generally somewhere where there is some latitude on WP:1RR which makes the actions of Zero0000 and Selfstudier more justified, not less. Simonm223 (talk) 13:50, 19 December 2024 (UTC)

Statement by Aquillion

Selfstudier accuses me of 1RR breach. In the dialogue, I explained that the group that really violated the rule was Selfstudier&Zero0000, who obviously acted in close coordination. My first undo was part of a counter edit - I feel like this is obvious enough that I probably don't have to point it out, but "counter edit" is not a WP:3RR / WP:1RR exception. Even if you were correct that Selfstudier & Zero0000 were WP:TAGTEAMing (always a tricky accusation, because it's hard to separate that from just your edits being so obviously problematic that two people independently reverted them), it still would not justify your revert. The fact that they're parties to an ArbCom case (which hasn't even yet found any fault with them!) doesn't change any of this. You should probably read WP:NOTTHEM. --Aquillion (talk) 14:15, 19 December 2024 (UTC)

Statement by Sean.hoyland

"the group that really violated the rule was Selfstudier&Zero0000, who obviously acted in close coordination"...yet another conspiracy-minded evidence-free accusation against editors in the PIA topic area, the third one at AE in just a few days. Sean.hoyland (talk) 14:59, 19 December 2024 (UTC)

Statement by (uninvolved editor 1)

Result of the appeal by Nicoljaus

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • I do not see any indication that Nicoljaus actually realizes the problem. The edit warring blocks were indeed some time ago, but one might think they would remember it after being blocked for it repeatedly, not to mention that being issued a CTOP notice might call a CTOP restriction to mind. And the remark in question sure looks to me like a threat to game 1RR via meatpuppetry, too. Given all that, I would decline this appeal. Seraphimblade 23:10, 19 December 2024 (UTC)
  • I see nothing in this appeal that makes me think they've taken on board the changes that they'd need to do to be a productive editor. It reads to me like "my block was bad, here's why", and that's not working as a reason for me to support unblocking. Ealdgyth (talk) 23:21, 19 December 2024 (UTC)
  • Nicoljaus, what we need to see is you demonstrating you understand edit-warring at a CTOP, which is what you were blocked for, and convincing us you won't do it again. Arguing the block should be lifted because other editors did something you thought looked suspicious isn't going to convince us. Just FWIW, Nicoljaus, the source doesn't actually say these two users cooperated like this 720 times. It says they edited the same articles 720 times, and that's not unusual. Most editors see the same other editors over and over again in articles about their primary interest. And edit by editor 1>2 days>revert by editor 2>revert by editor 1>20 minutes>revert by editor 3 is also not at all unusual anywhere on the encyclopedia and isn't evidence of tag-teaming. People read their watch lists. Any editor with that article on their watchlist, which is nearly fifty editors, might have investigated the large revert of an edit by an experienced editor at a contentious topic. Valereee (talk) 15:18, 20 December 2024 (UTC)
    @Nicoljaus, it's not that edit wars are evil. It's that they're disruptive, and particularly in a CTOP we really really don't need additional disruption and drama. A revert is a revert, even if you tried to meet my opponents halfway, as in this case, taking into account their claim, which I could understand, in the counter edit. Re: If such an action is also considered an edit war and a violation of the 1RR/3RR rule: a revert is a revert and is covered in the policy around reversions. And you have a history of blocks for edit-warring, including at other CTOPs.
    It's been seven months since the block. I'm trying to come around to a way to at least allow this editor a chance to show us they've taken this stuff on board...maybe a 0RR at all CTOPs? Valereee (talk) 17:44, 23 December 2024 (UTC)
    @Nicoljaus, re I believe it is essential to recognize that not all reverts carry the same implications. While it is true that a revert is a revert, the context and intent behind the action should also be taken into account. In this instance, I made efforts to address the concerns of the other party involved, which reflects a willingness to engage in dialogue rather than simply reverting. Some editors at talk pages will take your apparent intentions into account. Some will just take you to ANEW. Some admins at ANEW will take your apparent intentions into account. Some will just reblock you.
    No one anywhere is promising that your intentions will be taken into account -- or even that they'll try to figure out what your intentions are -- and therefore it's completely your responsibility to read the situation you're in correctly. If you read it wrong, you're likely to be blocked again, and honestly another block for edit-warring at a CTOP is likely to be another indef, and it would absolutely not surprise me for the blocking admin to require 12 months to appeal. Valereee (talk) 15:25, 24 December 2024 (UTC)
    No need to reply, but I'll tell you plainly I've been trying to give you opportunities to convince other admins here, and you keep wanting to dig the hole deeper. I'd support an unblock with an editing restriction of 0RR at any article with a CTOPs designation on the talk page. Valereee (talk) 13:13, 25 December 2024 (UTC)

PerspicazHistorian

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

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)

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)

Walter Tau

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 Walter Tau

User who is submitting this request for enforcement
Bobby Cohn (talk · contribs · deleted contribs · logs · filter log · block user · block log) 20:51, 24 December 2024 (UTC)
User against whom enforcement is requested
Walter Tau (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. 4 December 2024 Creation (and subsequent editing and AfC submission) of Draft:Maternity capital. See it's page history, there's no need to supply the entirety of the diffs here.
    • For context on how this subject falls under the purview, see the context given by the news article as shared on the talk page: Russia using adoption of Ukranian children during the Russo-Ukranian war. Then note how this state program directly discusses adoption support, which was adapted by Putin following the start of the war. A citation given in the draft article. The Google translated version specifically notes the changes "At the same time, residents of the new regions will receive maternity capital regardless of the basis and timing of their acquisition of Russian citizenship" (emphasis mine).
    This draft, as it is written, is extremely promotional in areas and could basically be hosted on a state-sponsored website. Given the context, I believe this falls under the topic ban.

References

  1. Bruce, Camdyn (14 December 2022). "Ukrainian official rips Russia for 'kidnapping' more than 13,000 children". The Hill.
  2. "Путин подписал закон, уточняющий условия выплаты материнского капитала" . interfax.ru.
Diffs of previous relevant sanctions, if any
  1. 26 November 2024 Notice given by Rosguill (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) that they were now subject to an arbitration enforcement sanction
  2. 5 December 2024 Blocked by Swatjester (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) for violating the sanction based on the edits to a project page.
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

It has been repeatedly pointed out to Walter Tau that they are skirting the line of the their topic ban by specifically not mentioning the "elephant in the room", see the diff by Asilvering above. They have also repeatedly chosen to ignore advice that they stop editing in the subject area and have repeatedly claimed to fail to see how their editing is problematic. As such, I have opened this discussion here so as to get an answer for Walter Tau on their editing, see "Also, since you mentioned a "topic ban", I would appreciate, if you provide a reference to it, as well as explain how it relates to this article Materniy Capital." They claim to continuously be unaware of the ban, see also their talk page discussions.

Notification of the user against whom enforcement is requested

Notified 24 December 2024.


Discussion concerning Walter Tau

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 Walter Tau

I feel, that the decision by Boby Cohn regarding my draft https://en.wikipedia.org/Draft:Maternity_capital, is "arbitrary and capriciuos" to use US legal terms : ], for the following reasons:

1) nowhere my draft mentions the words "Ukraine" or "Ukrainian".

2) this draft ] is a translation of the original Russian wiki- article : https://ru.wikipedia.org/%D0%9C%D0%B0%D1%82%D0%B5%D1%80%D0%B8%D0%BD%D1%81%D0%BA%D0%B8%D0%B9_%D0%BA%D0%B0%D0%BF%D0%B8%D1%82%D0%B0%D0%BB . I have heard the argument, that different languages in Misplaced Pages use different standards for articles' notability etc. Can someone please provide a web-link to Misplaced Pages rules, that actually confirms, that different standards for different languages is the currently accepted policy. I have been unable to find such statement.

3) In fact, my draft focuses mostly on the policies before 24 February 2022, i.e. before full-scale Russian invasion of Ukraine.

4) Please correct me, if I am wrong, by it seems that Boby Cohn's only argument of my ban violation is the following statement in my draft of Maternity Capital. "Residents of new regions are paid maternity capital regardless of the time and basis for obtaining Russian citizenship." In my defense: I did not write that statement- it is a Google translation from the Russian wiki, actually a small part of the translated text. And with all honesty, when I was reading the translated text, it did not cross my mind, that someone may interpret so broadly. Also, this sentence-in-question does not really add much to the main subject to the article, and I do not object to its deletion.

5) Considering, that a) I did not write, but only translated the text-in-question; b) the relevance to the text-in-question to my topic ban is not apparent, particularly in the larger context of the whole article; c) I do not object deleting the text-in-question from the draft; may I suggest changing the draft to fix this controversy?

6) If there are other controversial sections/sentences in my translated draft, it may be better if someone re-writes them. Most wiki-readers, can agree with a statement, that this draft ] may not reach an "Article of the Day" status, but it has a value as a stand-alone article as well as a source of references (more-to-be-added). Walter Tau (talk) 13:45, 25 December 2024 (UTC)

I can see now, why some editors consider the translated addition, that I made, a violation of my ban on editing Russia-Ukraine topic. It was not my intention. I fact, I agree with the deletion of the questionable sentence "Residents of new regions are paid maternity capital regardless of the time and basis for obtaining Russian citizenship.". At the same time, I would like to keep the rest of draft, so that myself and other keep working on getting it published. Do I understand correctly, that the notability of this topic is not being questioned?

Statement by TylerBurden

Walter Tau doesn't seem to think they have done anything wrong on Misplaced Pages, so it's honestly not surprising to see them continuing to push the limit despite the sanctions they have received. At some point you have to wonder if there is a foundational WP:COMPETENCE or trolling (or a combination of both) issue. Either way, yes they are clearly violating their topic ban by writing about the Russian kidnapping of Ukrainian children from the war, because that is what this whole ″adoption″ thing is. --TylerBurden (talk) 17:22, 25 December 2024 (UTC)

Statement by (username)

Result concerning Walter Tau

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • Sidestepping for now the question of whether simply not mentioning anything conflict-related would have been enough to avoid a TBAN violation, the references to "new regions" make this a violation much more straightforwardly. Justice is blind but not stupid. Walter, I think we're going to need to see recognition from you that this was a TBAN violation, if we're going to find a good path forward here. I'd also like to know who you are referring to when you reference other editors working on the draft? Auric has made some gnomish edits but you appear to be the only substantive editor. And why are you implying, on Bobby's talk, that y'all have been corresponding by email, when he denies that? -- Tamzin (they|xe|🤷) 22:29, 24 December 2024 (UTC)
  • I'll be direct: I think Walter knows what he is doing and has no intention of abiding by his TBAN, even when it was exhaustively explained to him, and I don't think we should be wasting further time here when we're almost certainly going to be right back here again within a few weeks. SWATJester 05:29, 25 December 2024 (UTC)
  • Back off a one week block for violating the topic ban, and already violating it again? (The "new regions" material is unquestionably a violation.) It seems that Walter Tau is either unwilling or unable to abide by the restriction, and does not, even after explanation, understand any of the issues here (or even understand something so simple as that different language Wikipedias are independent from one another and each have their own policies and practices). Given that, I don't see anything to be done here except to indef. Seraphimblade 17:45, 25 December 2024 (UTC)
Categories: