Misplaced Pages

:Arbitration/Requests/Motions: 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 | Requests Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 07:34, 9 March 2013 view sourceCallanecc (talk | contribs)Edit filter managers, Checkusers, Oversighters, Administrators72,962 edits Oversight-related blocks: Motion enacted← Previous edit Latest revision as of 15:01, 27 December 2024 view source Aoidh (talk | contribs)Autopatrolled, Checkusers, Oversighters, Administrators58,053 edits Motion 1.4: expanding arbcom-en directly: typo 
Line 1: Line 1:
<noinclude>{{pp-semi-indef|small=yes}}{{ArbComOpenTasks}}</noinclude> <noinclude>{{pp-semi-indef|small=yes}}{{ArbComOpenTasks}}</noinclude>
= <includeonly>]</includeonly> = =<includeonly>]</includeonly>=

{{Misplaced Pages:Arbitration/Requests/Motions/Header}} {{Misplaced Pages:Arbitration/Requests/Motions/Header}}
== Arbitrator workflow motions ==
{{Shortcut|WP:A/R/M}}
=== Workflow motions: Arbitrator discussion ===
{{Clear}}
* 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. {{pb}} '''Motivation:''' We've known about the need for improvements to our workflow and capacity for some years now{{snd}}I wrote about some of these suggestions in my ]. 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 ], which was partially caused by our failure to address a private request that had been submitted to us months earlier. {{pb}} '''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) ]; 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. {{pb}} '''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. {{pb}} '''Other efforts:''' There is one more technological solution for which there was interest among arbitrators, which was to get a CRM/ticketing system{{snd}}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. {{pb}} 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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 ====
==Motions with respect to functionaries==
{{ARCAImplNotes
|updated = an automatic check at {{#time:H:i, j F Y|{{REVISIONTIMESTAMP}}}} (UTC)
|motions =
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 1: Correspondence clerks |active = 10 <!--|support = |oppose = |abstain = -->|notes=One support vote contingent on 1.4 passing}}
<!--{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 1.1: expand eligible set to functionaries |active = 10 }} -->
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 1.2a: name the role "scrivener" |active = 10 <!--|support = |oppose = |abstain = -->}}
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 1.2b: name the role "coordination assistant" |active = 10 <!--|support = |oppose = |abstain = -->}}
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 1.3: make permanent (not trial) |active = 10 <!--|support = |oppose = |abstain = -->}}
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 1.4: expanding arbcom-en directly |active = 10 <!--|support = |oppose = |abstain = -->}}
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 2: WMF staff support |active = 10 <!--|support = |oppose = |abstain = -->}}
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 3: Coordinating arbitrators |active = 10 <!--|support = |oppose = |abstain = -->}}
{{ARCAImplNotes/Motion/Automatic|page=ARM|pattern=%c#.-UTC|name = Motion 4: Grants for correspondence clerks |active = 10 <!--|support = |oppose = |abstain = -->}}
}}


=== Motion 1: Correspondence clerks ===
'''Preamble''': In early January 2013, the Arbitration Committee reviewed several aspects of the appointment and review processes related to Checkusers, Oversighters and AUSC members, including the appointment extension of advanced permissions to former arbitrators. In preparation for this review, arbitrators retiring as of 31 December 2012 were permitted to retain Checkuser and Oversight permissions at their request on an interim basis until the completion of the review and decisions on next steps. Below are the motions that the Arbitration Committee will vote on; other motions may be proposed as well. All functionaries and community members are invited to participate in the discussion.
; Nine-month trial
{{ivmbox|1=
The ] 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:
<blockquote>
; 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 ] and sign the Foundation's non-public information ].


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 ] assist in the administration of the Committee's on-wiki work.


The specific responsibilities of correspondence clerks shall include:
===Motion on Audit Subcommittee===
* Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
Audit Subcommittee (AUSC) members are provided with Checkuser and Oversight tools in order to carry out their responsibilities. Community appointees to the AUSC are discouraged from routine or regular use of either tool; however, they are permitted to use the tools in order to develop a sufficient skill level to adequately assess the actions of Checkusers and Oversighters, and may assist in addressing time-sensitive situations, or serious backlogs. Community AUSC appointees who held advanced permission(s) prior to their term will retain the permission(s) they held prior to their appointment. Community AUSC appointees who did not hold advanced permissions prior to their term may apply to retain Checkuser and/or Oversight during any Checkuser/Oversight appointment cycle that occurs during their term and, if successfully appointed, will assume their new role at the end of the AUSC term.
* 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:
''{{ACMajority|active = 13 |inactive = 1 |recused = 1 |motion = yes}}''
* 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.
'''Support'''
:# ] (]) 03:00, 20 February 2013 (UTC)
:#I do not believe that members of the audit subcommittee should risk putting themselves in situations where their own use of the tools could be brought into question. Clearly uncontroversial circumstances, such as emergencies, should be fine, but in general I believe the less the tools are used, the better. The primary reason the tools are given to the members of AUSC (the community members, at least) is to allow them to review the logs; the way things are set up on our project, access to the logs comes hand-in-hand with access to the tools themselves. I also believe that arbitrator members should be subject to this as well, and so I would prefer that this motion be extended to include them, however this is at least (I believe) a step in the right direction. ] <sup>(]/]/])</sup> 03:04, 20 February 2013 (UTC)
:# ]&nbsp;<sup>]]</sup> 04:29, 20 February 2013 (UTC)
:# On the whole, ''"discouraged from routine or regular use of either tool"'' is tempered enough that I can live with it provided the exceptions listed are interpreted as exemplary and not exhaustive as is my current reading. &mdash;&nbsp;]&nbsp;<sup>]</sup> 14:12, 20 February 2013 (UTC)
:# ] (]) 01:17, 21 February 2013 (UTC)
:# ]<sup>TT</sup>(]) 08:31, 21 February 2013 (UTC)
:# Auditors need to remain aloof, yet we have not required them to be so; I think that needs to change. I don't accept the argument that this unjustifiably restricts the effectiveness of AUSC members; while it might restrict their ability to function as "regular" checkusers or oversighters, I don't think they should be performing such a function in the first place. ] ]] 23:18, 21 February 2013 (UTC)
:# &nbsp;] <sup>]</sup> 03:59, 22 February 2013 (UTC)


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.
'''Oppose'''
</blockquote>
:#Fixes a non existent problem, and reduces the discretion and judgment of the AUSC members. I would expect AUSC members to avoid ''controversial'' use of the tools, but this goes way too far in tying their hands. ] 02:26, 20 February 2013 (UTC)
}}
:#Not particularly convinced that we need this. ] (]) 17:27, 21 February 2013 (UTC)
<!-- change the number depending on active count -->
:#'''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 21:24, 21 February 2013 (UTC)
{{ACMajority|active=10|motion=yes}}
:#Substantially per Courcelles. I agree, as I think everyone does, that both arbitrator and non-arbitrator members of the Audit Subcommittee should best refrain from controversial uses of the Checkuser or the Oversight tools. But I don't see a need for them to refrain from routine uses (bearing in mind that the ability to distinguish between routine and potentially controversial use is a function of the cluefulness that would lead the community to elect someone as an arbitrator or an AUSC member in the first place). And the next time a serial vandal comes along and engages in massive on-wiki harassment that must quickly be addressed and undone, I see no benefit if six of the most knowledgeable checkusers and oversighters are virtually disqualified from helping with the problem. ] (]) 20:40, 24 February 2013 (UTC)
;Support
# This is my first choice and falls within ArbCom's community-granted authority to {{tqq|1=approve and remove access to mailing lists maintained by the Arbitration Committee}}<ref>{{slink|Misplaced Pages:Arbitration/Policy#Scope_and_responsibilities}}</ref> and to {{tqq|1=designate individuals for particular tasks or roles}} and {{tqq|1=maintain a panel of clerks to assist with the smooth running of its functions}}.<ref>{{slink|Misplaced Pages:Arbitration/Policy#Procedures_and_roles}}</ref> {{pb}} Currently, we have ] 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). {{pb}} 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 ], although ArbCom correspondence clerks would be a higher-trust position (functionary-level appointments only). {{pb}} 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 18:28, 1 December 2024 (UTC)
# 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. ] <sup>]</sup>] 05:29, 7 December 2024 (UTC)


;Oppose
'''Abstain'''
# 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 ] and that only the current arbitrators evaluating and making decisions based on that private information have ongoing access to it. - ] (]) 23:36, 9 December 2024 (UTC)
:#
# Might as well make it formal per my opinions elsewhere on the page. ] (]) 13:24, 10 December 2024 (UTC)
# 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. ] (]) 19:16, 14 December 2024 (UTC)
# 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 - ]. ] (]) 11:32, 27 December 2024 (UTC)


;Abstain
====Comments from arbitrators====
#
:I'm of two minds about this. On the one hand, I believe this is a reasonable proposal given that the subcommittee members must also be ''seen'' as impartial regarding the use of those tools; but on the other hand, I feel that good recusal hygiene suffices to prevent us from loosing the help of three trusted contributors with those tools. I would be more inclined to support this if it counseled ''light'' usage of the tools (thus minimizing the risks) rather than discourage their use entirely. &mdash;&nbsp;]&nbsp;<sup>]</sup> 02:19, 20 February 2013 (UTC)
: There are problems with AUSC members being near the top of the activity table, as has happened on several occasions; it makes it difficult to assess whether there is too much work to be done, or whether AUSC members are carrying out tasks before those users who have been specifically vetted for those permissions have even had a chance to see them. Just as importantly, this formalizes the position that AUSC members must go through the community review process in order to retain CU or OS after their term.<p>This is an important separation between the functions. The community members are elected to oversee the issues, not to become active participants on a regular basis, which is what has happened on several occasions. We would be in a better position to assign them specific reviews if some of them weren't so busy using tools. ] (]) 03:00, 20 February 2013 (UTC)
:Fluffernutter, just to be clear, I'm suggesting that all arbitrator members ''of AUSC'' be subject to this. You are very correct in that some of our most active functionaries have been members of the Committee; restricting the entire Committee from using their tools during their term would be a severe detriment to the project. Of course, we also have arbitrators who wouldn't know an IP address from a potato (the people I'm thinking of have more-or-less admitted this at one point or another), so I suppose for them it could be a moot point with regard to checkuser, and I myself tend not to use oversight very much mainly because the OTRS interface scares the willies out of me. Anyway, the point is, when it comes to managing who has access to the tools, there are enough members on the Arbitration Committee where one recused member wouldn't make a whole lot of difference in most cases. When it comes to simply reviewing them, there's only six people on the Audit Subcommittee; a recusal there can make a substantial difference when it comes to the final vote (or discussion, I've no idea how they do things). If we had substantially more active volunteers for both CU and OS, that may change things, but as things currently are, the loss of at least half a dozen or so additional active users of each tool (beyond that which we would lose from AUSC if the above passes) would be a fairly large blow to the project. ] <sup>(]/]/])</sup> 03:32, 20 February 2013 (UTC)
*The problem with his motion is that it doesn't say something along the lines of "If you can pass it off to a normal functionary, or let it wait, do so" which would be reasonable guidance. Instead it tries to micro-manage their judgment, and doing it by using such meaningless terms as "time-sensitive". Most functionary tasks, are, by definition, time-sensitive to some degree (esp. the Oversight task); these aren't CFD closes that pretty much survive languishing until someone feels like dealing with them, if you're oversighting something, there's damned good reason, and that means sooner is better than later. Checkuser is often able to wait, through stopping persistent vandals often needs to be done ''now'' and not in three hours, but oversight tasks almost always should be done as soon as someone is there. This motion doesn't say pass it off if you can, don't wade into anything even remotely controversial, it says "see obvious problem, remember vague motion, walk away." Because are we '''really''' going to start judging not whether an action was proper under CU/OS policy, but whether it was or was not time-sensitive enough to justify acting? That's a bad road to go down. ] 04:46, 20 February 2013 (UTC)
**I hear your concerns, Courcelles. Let's look at Checkuser: I can't think of a good reason why an AUSC member would handle SPIs on a regular basis; they're generally not time-sensitive. About a third of the suppression requests are on old pages, or require second/third opinions; and those that have already been revision deleted (another good chunk) are generally not time sensitive and can wait for an hour or two. Indeed, I'd suggest that AUSC members shouldn't regularly be monitoring the Oversight OTRS queue, referring to it only when they are addressing a concern, or trying to work out some statistical information. I'd suggest that their use of the tools should be approximately equivalent to that of a steward: only when no other checkuser/oversighter can be located, and it's a suppression on a highly active page like ANI, that cannot be addressed with revision deletion. ] (]) 05:18, 20 February 2013 (UTC)


<!--
====Discussion and comments from functionaries and community====
;Arbitrator discussion
*In my two terms on AUSC, I've done this as a general best practice, so I don't think it's unreasonable to formalize it. However, I believe I am in the minority of current/former AUSC members in this practice. ''']''' <sup>]</sup> 02:07, 20 February 2013 (UTC)
-->
*The trouble I see with this approach is that the caseload of AUSC (from what I understand) is extremely small. So in any case where an active functionary was appointed to AUSC (which in my mind is the ideal for at least some of that committee), the community would be trading hands that do work that needs doing in exchange for very occasional supervision. I understand the ''goal'' of discouraging AUSC members from being too heavily involved with tool use, but I can't escape the feeling that it nevertheless amounts to a net negative for a community which fairly commonly has backlogs of functionary-related tasks. ] (]) 02:22, 20 February 2013 (UTC)
==== Motion 1: Arbitrator views and discussions ====
*:Hersfold make a very good point in his vote. If the goal is that (as NE Ent phrases it) "those that audit should not do", it would make sense for ''all'' parties involved in auditing and supervising permissions use to be discouraged from using the tools. I still think that's probably a net negative (we rely on annual appointments of arbs and AUSC members to fill out the ranks of functionaries so work gets done), but if arbcom chooses to go the route of "auditors must remain neutral", it should apply to arbs as well, since they're the ones who ultimately give and take functionary permissions. ] (]) 03:15, 20 February 2013 (UTC)
*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 ] (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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 18:28, 1 December 2024 (UTC)
*::Reply to Hersfold: Yeah, I realized after I saved that comment that given that the whole reason arbs are given CU/OS is to use them for arb work, it wouldn't make sense to flatly discourage/deny them use of the tools. However, I still think that if the goal is to keep those who supervise out of circumstances where their tool use might be one of the supervisory issues, it would be more consistent to discourage ''all'' arbs from using their tools in non-arbcom, non-emergency circumstances. This should go for AUSC arbs, at a minimum, but if the true concern is clean supervisory hands, it should also go for non-AUSC arbs. The fact that we lack the manpower to really take that approach sort of highlights the point that if we can't afford to do it with arb manpower, we probably can't afford to do it with AUSC manpower either, at least not without additional appointments of non-supervisory functionaries to take up that slack (which, come to think of it, would be a rather neat way to fix the entire "omg but manpower" issue regarding both arbs and non-arbs in supervisory positions). ] (]) 03:54, 20 February 2013 (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. ] <sup>]</sup>] 01:31, 3 December 2024 (UTC)
*Those that ''audit'' should not ''do,'' the solution to not enough doers is to get more doers, not blur the distinction between auditors and doers. <small>]</small> 02:56, 20 February 2013 (UTC)
*::@]: 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 02:07, 3 December 2024 (UTC)
*:Agreed! As in "isn't that obvious?" (seems like it is not...) - ] (]) 11:02, 20 February 2013 (UTC)
*I also think that if we adopt this we should choose a better name. I know ] meant this suggestion as a bit of a joke, but I actually think he was on the money when he suggested "]." I like "]" even more, which I believe he also suggested. They capture the sort of whimsical Misplaced Pages charm evoked by titles like ] while still being descriptive, and not easily confused for a traditional clerk. ] <sup>]</sup>] 03:21, 4 December 2024 (UTC)
*I personally feel that those that audit shouldn't be active functionaries for the duration of the terms. It not only is a question of neutrality, but also - perhaps I should say mainly - of an appearance of neutrality. Not being active users of the permissions they are entrusted to watch over would give a perception of a true super partes status and of the neutral court where one's grievances can be heard. One cannot truly be neutral when he's aware that a decision of his might have an impact on his own actions (if the Audit Subcommittee decides that an action taken by Checkuser X is disallowed, this will impact the Audit Subcommittee members' own practices and could even mean that some of their past actions would be disallowed and inappropriate). I would go so far as to suggest that the AUSC be given an ad-hoc userright that provides access to checkuser logs, checkuser and suppression logs (as I believe Checkuser might be needed in the course of their investigations) and that highlights their non-partisan and different role, much in the way as the Ombudsmen Commission does it (and yes, I am aware that now OC members can keep acting as local CU or stewards, but I believe that decision to have been taken in error, for again, the controllers should not be the controlled). <i><b>] <sup><small>]</small></sup></b></i> 11:21, 20 February 2013 (UTC)
*:Whimsy is important -- ] <sup>]</sup> 08:55, 4 December 2024 (UTC)
* Technical question – if I understand Oversight correctly, those with the permission have two capabilities – the ability to oversight something, and the ability to see material that has been oversighted. I can imagine that the Audit role requires the second function, so they can review and confirm that the usages were correct, but it isn't obvious to me why they need the ability to oversight something. I suspect that giving them just the second half (i.e. read, but not edit) might not be technically trivial , but if it is possible should it be a consideration?--]] 14:24, 20 February 2013 (UTC)
* {{re|CaptainEek|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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:10, 7 December 2024 (UTC)
** This is the case with Checkuser as well - on the English Misplaced Pages, the "checkuser" and "oversight" usergroups contain both the ability to review the logs ''and'' use the tools (and in the case of oversight, view suppressed data). While I can imagine in some cases relating to checkuser it may be necessary to perform additional checks to verify that the checks in question were reasonable, that does not apply to oversight. It is possible to set up a usergroup that only has access to the logs and not the tools themselves, however to do so we'd need a developer's assistance and likely the Foundation's approval - it's a change that has to be made in the LocalSettings.php file used by Mediawiki, and the Foundation is (understandably) very sensitive about who can gain access to sensitive data. ] <small>]</small><sup>(]/]/])</sup> 19:17, 20 February 2013 (UTC) P.S. - Also, as the motion indicates, it can be helpful (especially with checkuser) to have some familiarity with how the tool is meant to be used so that an auditor has a better idea of what is a reasonable check and what is not. Granting them access only to logs prevents them from gaining this basic knowledge if they've never seen either tool before. ] <small>]</small><sup>(]/]/])</sup> 19:20, 20 February 2013 (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. ] (] • she/her) 21:40, 17 December 2024 (UTC)
***I did think about the possibility that there is some value in actually using the tool to gain more appreciation of how it is used. However, that can be accomplished by giving them the authority in the test wiki, if they want to try an oversight, so they can be sure they understand the process. While I understand it would take some work by a developer, I see value in letting the functionaries have the read and write capabilities in a test wiki, but only the read capabilities This isn't a major issue – if we have enough trust to choose someone as an auditor, it is highly unlikely they are going to abuse the tool, but it would be cleaner if we made the distinction. To use an analogy from the real world, we give financial auditors to ability to review checks issued by a corporation, but we would find it absurd to simultaneously give them the right to issue a check on behalf of the organization. Read and write access are very different, and in most systems, separable. We should separate them, and give them the read access.--]] 15:08, 21 February 2013 (UTC)
{{reflist-talk}}
****I don't think that the testwiki would really provide a good environment to give actual experience with the tool. That will help them see what the tool is ''capable'' of doing; however, it does not permit them to determine how a checkuser or oversighter would apply their judgment to determine when and how to use the tool. With checkuser in particular, there is a lot to be taken into account when looking for socks, and the checkuser must be able to correctly interpret the data to know if further checks are merited. Oversight does tend to be a bit more straight-forward, and that likely could be learned without actually using suppression at all. ] <small>]</small><sup>(]/]/])</sup> 18:43, 21 February 2013 (UTC)
*****I echo Hersfold's comments. Checkuser is very complicated and a bit of practice really helps figure out what is appropriate and what isn't. The way that I see it, letting AUSC members practice using the tools is a poor solution, but it's better than the only other solution, namely where AUSC would only recruit active checkusers. --] ] 19:14, 21 February 2013 (UTC)
******I grant that checkuser and oversight are different enough that the answer may be different. My comments were made solely thinking about oversight. I contend that oversight read access, possibility coupled with oversight write access in a test wiki is sufficient for an auditor. I'll defer to others about checkuser.--]] 19:23, 21 February 2013 (UTC)
*Semi-related question: is there any way to remove a member of AUSC? --''']]]''' 18:02, 20 February 2013 (UTC)
**<small>Leaving reply down here, phooey on the separate sections.</small> If there were reasonable cause to do so, I'd imagine the Committee could remove a member of AUSC using Level I or II procedures as appropriate, as we would with any other functionary who had seriously crossed some line. ] <small>]</small><sup>(]/]/])</sup> 19:12, 20 February 2013 (UTC)
*@SilkTork: Noting here that per your comments I have marked you as recusing on the three motions. I draw your attention to the fact that this affects the majority calculations. ] (]) 18:29, 20 February 2013 (UTC)
*The Ombudsman Commission faced a similar situation recently; if a checkuser from a very quiet wiki (say, a wiki with only a small handful of checkusers) was appointed as an Ombudsman then that would be very detrimental to that project. To get around this, the size of the Commission was expanded and the requirement that Commission members not use their local checkuser rights was removed (although it should be noted that all of us, including myself, have either scaled back our usage significantly or stopped altogether). I'm not sure it's feasible to expand AUSC's membership (AUSC wouldn't appear very impartial if a significant number of the project's checkusers were in it), but that is something that could be considered as an alternative in the future. --] ] 01:11, 21 February 2013 (UTC)
*Personally, when it comes to the line "''Community appointees to the AUSC are discouraged from routine or regular use of either tool,''" I think it may depend on whether or not the AUSCmember was an active OS/CU prior to AUSC service. I would think that someone who is already engaged in project-protection prior to AUSC service should not be forced to diminish/cease their activity because they are on AUSC, so long as they recuse from anything to which they are connected. -- ] (]) 18:42, 5 March 2013 (UTC)


===Motion on CheckUser/Oversight and inactivity=== ====Motion 1.1: expand eligible set to functionaries ====
{{hat|1=If any arbitrator prefers this way, unhat this motion and vote for it.}}
The Arbitration Committee confirms the ] as approved in March 2011, with the exception of retitling the provision ''"CheckUser/Oversight permissions and inactivity"''.
{{ivmbox|1=If motion 1 passes, replace the text {{tqq|1=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 {{tqq|1=The Arbitration Committee may appoint, from among the ] (and preferably from among former members of the Arbitration Committee), one or more users to be correspondence clerks for the Arbitration Committee.}}.}}
{{ACMajority|active=10|motion=yes}}


;Support
''{{ACMajority|active = 11 |inactive = 1 |recused = 3 |motion = yes}}''
#


;Oppose
'''Support'''
#
:#I'm not sure it's important that this be done &ndash; or that a motion to do so is worthwhile &ndash; but the change itself is innocuous and indeed a bit more accurate. &mdash;&nbsp;]&nbsp;<sup>]</sup> 02:40, 20 February 2013 (UTC)
:# It doesn't just change the title. It confirms that we reviewed this procedure, and that we still believe it is appropriate. ] (]) 03:01, 20 February 2013 (UTC)
:# It basically just changes the title. The very presence of these motions confirm that we've reviewed our procedures, but whatever. ] <sup>(]/]/])</sup> 03:05, 20 February 2013 (UTC)
:# I see Courcelles' point, but I think it's useful to affirm policy is still practice. <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 03:22, 20 February 2013 (UTC)
:# ] (]) 03:29, 20 February 2013 (UTC)
:# ]&nbsp;<sup>]]</sup> 04:30, 20 February 2013 (UTC)
:# Reaffirming the general provision after a period of time is not a completely useless gesture. Genuine housekeeping would be updating the wording per Philippe's comment below. I would support that as well, but such a wording change could be done without any formal motion. ] (]) 01:19, 21 February 2013 (UTC)
:#The community doesn't really see the activity standards being enforced (because that always happens off-site), so letting it know that the standards continue to apply is worthwhile. ] ]] 23:18, 21 February 2013 (UTC)
:# &nbsp;] <sup>]</sup> 04:00, 22 February 2013 (UTC)
:# Although as noted by many this motion is hardly essential, I see this as a reminder to everyone (including ourselves) of what the current policy is, as much as anything else. ] (]) 20:42, 24 February 2013 (UTC)


;Abstain
'''Oppose'''
#
:#Not in opposition to the change, per se, but opposed to the idea of motions that change nothing. ] 02:37, 20 February 2013 (UTC)


<!--
'''Abstain'''
;Arbitrator discussion
:#For similar reasons as Courcelles. I'm not keen on the bureaucracy of ArbCom at the best of times and motions that change nothing embody this bureaucracy. However, I don't oppose the motion itself, so will abstain. ]<sup>TT</sup>(]) 08:33, 21 February 2013 (UTC)
-->
:#Per WTT. If we can make the housekeeping changes to the point that Philippe and Avi bring up, then we don't need this. '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 21:23, 21 February 2013 (UTC)


{{hab}}
====Comments from arbitrators====
* Retitling because our section on refers to all types of advanced permissions, including administrator and bureaucrat. ] (]) 02:02, 20 February 2013 (UTC)
**@MBisanz, it's housekeeping to be certain, but it's useful to publicly demonstrate that the change isn't just the whim of one arbitrator without discussion. ] (]) 02:22, 20 February 2013 (UTC)
**@Philippe and others, some members of the Ombudsman Commission elect to not use their tools or to do so sparingly during their appointment. The wording used at present accommodates that, while not obligating them to refrain from tool use. I'd suggest an explanatory note as a "footnote" to the procedure identifying that refraining from use of tools is optional for Ombudsman Commission appointees, effective February 2013. ] (]) 03:56, 3 March 2013 (UTC)


==== Motion 1.2a: name the role "scrivener" ====
====Discussion and comments from functionaries and community====
{{ivmbox|1=If motion 1 passes, replace the term "correspondence clerks" wherever it appears with the term "scriveners".}}
I'm not exactly sure why this clarification is needed, but sure, have fun continuing to do what you've been doing since 2011! ''']''' <sup>]</sup> 02:10, 20 February 2013 (UTC)
{{ACMajority|active=10|motion=yes}}
*I believe Ombudsmen may keep their bits now (at least the steward ones) so that last point may need to be reworded a tad. -- ] (]) 05:31, 20 February 2013 (UTC)
;Support
** Avi is correct. The line that ends "or (c) holders who have temporarily relinquished access, including CheckUsers or Oversighters who accept appointment to the Ombudsman Commission" may be confusing. The Wikimedia Foundation currently does not require that those who hold the tools relinquish them for the duration of their time on the commission. ] (]) 07:29, 20 February 2013 (UTC)
#Nicely whimsical, and not as likely to be confusing as correspondence clerk. ] <sup>]</sup>] 04:11, 7 December 2024 (UTC)
*I am not sure why this is felt needed, or even felt that a full motion is necessary, but of course I trust the ArbCom's judgement that this deserves a vote. <i><b>] <sup><small>]</small></sup></b></i>


;Oppose
A few points from me here.
# 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. - ] (]) 04:12, 11 December 2024 (UTC)
*I notice you're reconfirming this motion. However, before resigning my oversight rights on 29 December 2012, I had not used them for over eight months. I certainly qualified as inactive under this motion, so why were my rights not removed? Additionally, it didn't take me very long to find a person with checkuser rights who qualifies as inactive, and there may well be more. So my question is, are you actually enforcing this? Because, from my experience, it appears you are not, which makes me question why you reconfirmed this motion.
# 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. ] (]) 19:07, 14 December 2024 (UTC)
*Five logged actions per three months does not qualify as "active" in my books, especially with checkuser where most SPI cases will have you make, as a minimum, four logged actions.
# Follows on from my vote on ]. ] (]) 11:38, 27 December 2024 (UTC)
*The section regarding the Ombudsman Commission should be reworded as it is not correct anymore. Ombudsman Commission members now retain their local rights as the requirement that they do not use them has been removed. Although the Ombudsman user group has global checkuser rights, we are obviously not allowed to use them unless it's on Commission business, so retaining local checkuser rights is the indicator that we are allowed to use them on that wiki. I would personally like for Ombudsman Commission members to be exempt from this provision for the duration of their appointment, but that is up to you to decide.
--] ] 01:29, 21 February 2013 (UTC)
: I did suggest that we adopt higher (and, as you argue, more accurate) standards of activity, but some of my colleagues disagreed—and in any case that suggestion does not appear to have made it into these proposals. I certainly agree that the current activity standards are a token gesture that are essentially useless in all but the most extreme cases of functionary inactivity. ] ]] 23:18, 21 February 2013 (UTC)
::I appreciate that that's difficult for everyone to agree on. My other point remains, however; to date this inactivity policy has not been enforced, so does this reconfirmation actually change anything? --] ] 23:50, 24 February 2013 (UTC)
As for Ombudsmen, I think we should treat them the same as we do with AUSC members, where they are exempt from the activity requirements while they're in office like Deskana said above. This motion should be expanded to reword the sentence in part c so it's brought up to current practise. ]] 05:52, 23 February 2013 (UTC)


;Abstain
===Motion on removal of CheckUser/Oversight for reasons other than inactivity (Level II procedures)===
# 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:11, 7 December 2024 (UTC)


;Arbitrator discussion
==== Motion 1 ====
Holders of CheckUser and/or Oversight permissions are presumed to continue to have the confidence of the Arbitration Committee under normal circumstances. CheckUser and/or Oversight may be removed by the Arbitration Committee for reasons other than inactivity, including recommendation by the Audit Subcommittee, conduct inappropriate to a user trusted with CheckUser and/or Oversight permissions, or breach of the ] or other related policy. Should the Arbitration Committee consider such removal, the holder of the permissions will be notified of this consideration, and will have the opportunity to respond to questions or concerns prior to a final decision by the Committee. Removal of advanced permissions may occur when:
:(i) the holder of CheckUser and/or Oversight permissions has been notified of the concerns leading to consideration of removal of permissions and has had the opportunity to respond to those concerns, and
:(ii) a majority of the committee supports the motion (irrespective of recusal or inactivity).


==== Motion 1.2b: name the role "coordination assistant" ====
Note that ] procedures for removal of advanced permissions applies equally to removal of CheckUser and Oversight permissions, and that this motion does not affect Level I procedures.
{{ivmbox|1=If motion 1 passes, replace the term "correspondence clerks" wherever it appears with the term "coordination assistants".}}
{{ACMajority|active=10|motion=yes}}
;Support
#


;Oppose
=====Appeal of removal of CheckUser or Oversight permission=====
# bleh. ] <sup>]</sup>] 04:12, 7 December 2024 (UTC)
Appeal may be made to the Arbitration Committee six months or more after the removal of CheckUser and/or Oversight permissions.
# Follows on from my vote on ]. ] (]) 11:38, 27 December 2024 (UTC)


;Abstain
''{{ACMajority|active = 13 |inactive = 1 |recused = 1 |motion = yes }}''
# I am indifferent between this and "correspondence clerk". Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:11, 7 December 2024 (UTC)
# If we're going to use a role like this, either this or correspondence clerk is fine. - ] (]) 04:13, 11 December 2024 (UTC)
# That would be okay. ] (]) 19:08, 14 December 2024 (UTC)


;Arbitrator discussion
'''Support'''
:# ] (]) 03:30, 20 February 2013 (UTC)
:# ]&nbsp;<sup>]]</sup> 11:28, 21 February 2013 (UTC)
:# &nbsp;] <sup>]</sup> 04:17, 22 February 2013 (UTC)


==== Motion 1.3: make permanent (not trial) ====
'''Oppose'''
{{ivmbox|1=If motion 1 passes, omit the text {{tqq|1=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}}.}}
:#Holding a functionary position is a role that requires a great deal of trust. Someone untrusted by a significant part of the committee should not continue to hold such a flag, and to make a recusal, abstention, or even an arb we haven't heard from in a while a de facto no vote is just wrong. ] 02:33, 20 February 2013 (UTC)
:# No. This makes it ''harder'' to remove permissions for which trust of the committee at large is critical than it is for adminship. I could see a quorum being required (for this and other removals) but not something that effectively hobbles the committee after a handful of recusals or absences. &mdash;&nbsp;]&nbsp;<sup>]</sup> 02:34, 20 February 2013 (UTC)
:# Per Coren. An arbitrator recusing themselves from a vote is ''removing'' themselves from a vote. This procedure turns a recusal into an oppose vote in all but name, essentially making it impossible to remove oneself from a vote due to an actual or perceived conflict of interest. This also does not take into consideration the difference between a week's inactivity and an I've-fallen-off-the-face-of-the-planet-you-haven't-seen-or-heard-of-me-in-the-last-few-months inactivity, the latter of which has happened from time to time. The former should be treated as this motion describes; the latter should not. ] <sup>(]/]/])</sup> 03:16, 20 February 2013 (UTC)
:# ] (]) 03:28, 20 February 2013 (UTC)
:# ]<sup>TT</sup>(]) 08:38, 21 February 2013 (UTC)
:#I missed "''irrespective of recusal or inactivity''" when these motions were being word-smithed. I consider it to be quite problematic: in the event that one or more members are on long-term leave from the committee, this motion (if adopted and in a case where the balance of opinion is moderately divided) would prevent us from removing a functionary whose use of their permissions, while not abusive enough to warrant the use of Level I procedures, is nevertheless so subpar that removal under Level II is necessary. We should make CU/OS as easy (and difficult) to remove as is adminship. ] ]] 23:18, 21 February 2013 (UTC)
:#It seems silly that we could pass a motion to desysop someone but still not have the votes to remove checkuser or oversight from them. '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 19:16, 23 February 2013 (UTC)
:#In principle, recused or long-term inactive arbitrators should not count in determining the majority on any issue; thus I can't support this motion as written. However, where recusals or inactivity situations are inherently temporary (as occurred for example in the situation that arose during the election last year), the solution is simply to postpone permanently addressing the issue until afterwards. That is in essence what happened, and no harm done. If there were to be a significant number of instances in which the Committee is unable to act due to multiple recusals or the like, we would want to discuss and establish a backup mechanism (which would extend well beyond functionary appointments). However, in the six and one-half years in which I've been following the Committee's work, this has virtually never been an issue, and in the absence of real need, I am reluctant to add to what already can be described as elephantiasis of the procedures manual. ] (]) 20:50, 24 February 2013 (UTC)
:#Per NW and NYB. ] (]) 01:01, 5 March 2013 (UTC)


{{ACMajority|active=10|motion=yes}}
'''Abstain'''
;Support
:#
#


;Oppose
====Comments from arbitrators - Motion 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. ] <sup>]</sup>] 04:19, 7 December 2024 (UTC)
* I note the comments of my colleagues and others. It should be *more* difficult to remove the tools from users who have already gone through three separate vetting procedures (acceptance of application, community review, final acceptance), including two by the Arbitration Committee, particularly when all of the evidence related to removal is by definition not available to the community for review and comment. It is very important that there is no possibility of removal for "political" reasons, which is very possible in situations where a significant number of arbitrators are unavailable for the short term. (Examples include travel to/from Wikimedia-related events like Wikimania, holidays such as Christmas or Thanksgiving weekends, where we frequently will have half the committee largely unavailable for several days in a row.) I agree with Fluffernutter that the Committee does need to address longterm inactivity on the part of arbitrators (my own inclination would be automatic removal of the arbitrator after x weeks of inactivity on Arbitration-related pages onwiki, or inactivity in three consecutive Arbcom cases); arbitrator inactivity has a deleterious effect on the Committee, especially if longtime inactive arbitrators suddenly appear (or disappear) in the middle of cases or other significant activities. The purpose of these motions is to address functionary-related matters, and I believe that the Committee should also address arbitrator inactivity, but arbitrator inactivity was not discussed as part of the functionary review and we do not currently have any consensus on how it should be addressed. Recusal is a trickier matter: while there have been improvements in the last term or so, recusal on matters has been used by some arbitrators to escape the fallout of having to address certain "hot potato" issues. There are very, very few situations where an arbitrator should recuse on a discussion of this import. At present, I can think of only one scenario where an arbitrator recusal would be necessary, and maybe one other where it might possibly be acceptable. Just as some see recusals as an oppose in all but name under this scenario, it can just as easily be seen as an automatic support if permitted as it reduces the number of real supports that are required to take an action. It is not a huge issue when the matter is public and the rest of the committee can appreciate the opinions and comments of the community; it is a much bigger issue when the discussion is entirely private and the community cannot evaluate and opine on the matters being considered. <p>As to the point Fluffernutter makes about not "voting" on matters until there are enough people around to properly resolve them, all I can say is that in recent years we've had multiple arbitrators suddenly and unexpectedly make proposals without input from the rest of the committee, or publicly making different proposals than were made to the rest of the committee. It's bad practice, I'll be the first to admit, but it is essentially impossible to stop. It only takes one arbitrator posting a motion to set things on the path, even if the rest of the committee doesn't want to proceed that way, and premature motions do indeed often result in poor results. ] (]) 03:57, 20 February 2013 (UTC)
# 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. - ] (]) 01:34, 8 December 2024 (UTC)
*:I disagree. Those users have already gone through three separate vetting procedures ''because'' the tools are so sensitive. Checkuser isn't a badge of honor we should only remove gingerly once granted, it's a delicate tool that requires ''continuing'' utmost trust in its holders; it is &ndash; and ''must be'' &ndash; hard to get and easy to remove. &mdash;&nbsp;]&nbsp;<sup>]</sup> 04:37, 20 February 2013 (UTC)
# ] (]) 19:10, 14 December 2024 (UTC)
*::Agree with Coren (again). I can think of a number of situations in which a recusal would be appropriate in this situation, and I'm not sure why a decision of this nature should be considered to be more important than (for example) voting on a case. While under normal procedures a recusal ''can'' affect the majority, the proposed motion above ''will'' cause it to affect the majority. See the table below, which assumes the Committee has 15 active members. Under current procedures, only odd-numbered recusals impact the majority (the first, third, fifth, etc.). Under the proposed motion, every recusal means one less person has to oppose the motion in order to make it mathematically impossible. If we have a situation such as occurred during the elections, where four arbitrators feel they must recuse from voting, that means a minority of four arbitrators - about a quarter of the Committee - can prevent the rest of the Committee from acting, even if all seven of the others support the motion. Under current procedures, the number of supports needed to pass a motion does decrease with recusals, but only half as quickly, and the voting is not unfairly weighted towards one outcome. ] <small>]</small><sup>(]/]/])</sup> 19:50, 20 February 2013 (UTC)
# Follows on from my vote on ]. ] (]) 11:38, 27 December 2024 (UTC)
{{cot|Table collapsed for readability}}
{| class="wikitable" style="text-align:center;"
|-
! rowspan="2" | Number of recusals
! colspan="2" | Number of opposes needed to fail
! colspan="2" | Number of supports needed to pass
|-
! Under current procedures
! Under proposed motion
! Under current procedures
! Under proposed motion
|-
| 0 || 8 || 8 || 8 || 8
|-
| 1 || 7 || 7 || 7 || 8
|-
| 2 || 7 || 6 || 7 || 8
|-
| 3 || 6 || 5 || 6 || 8
|-
| 4 || 6 || 4 || 6 || 8
|-
| 5 || 5 || 3 || 5 || 8
|-
| 6 || 5 || 2 || 5 || 8
|-
| 7 || 4 || 1 || 4 || 8
|}
{{cob}}
*:I think the prospect that a small minority of arbs could take advantage of the absence/inactivity of a good number of arbs and do something bad is quite overblown and frankly inconsistent with AGF. In a number of our recent internal discussions, we've had little problem holding back proposals that are technically passing for votes from temporarily inactive arbs and potential vote changes. Moreover, if the lots-of-inactive-arbs problem requires a solution, the proper solution is simply to say that the committee would not act on non-emergency matters at all during those periods, rather than creating arbitrary heightened standards for some votes but not others. Surely, for example, banning a long-term editor is as serious a matter as removing a userright this committee granted in the first place, and which no one actually needs to edit? Does that mean that we need to pass a special procedure for remedies that bans someone as well? ] (]) 22:46, 20 February 2013 (UTC)
*I recuse from voting on matters related to the advanced tools, and I have not taken part in the formal selection or removal process of functionaries, so I'm concerned regarding comments above that a recusal can equal a vote in some situations. If a Committee member is consistent in their recusal, rather than selective, then their recusal should not effect the vote. It would, surely, only have an impact if the member suddenly or inconsistently voted on a functionary issue. Following that line of thinking, my intention is not to take part in the voting on these motions, though I am open to being persuaded otherwise, if it is felt my vote is important. ''']''' ''']''' 09:29, 20 February 2013 (UTC)
**NE Ent - Recuse is probably too strong a word. I historically haven't got involved. When I first joined the Committee we were actually quite busy, and few Committee members get involved in everything we do, and the thing that I decided not to get involved in was selecting the new functionaries as I was not familiar enough with the tools to make an informed judgement. Having not been involved in deciding functionary matters for over a year it seemed inappropriate to change that stance for an individual vote. And having not been previously involved and having recused on an individual vote, it seems appropriate to continue that stance, though I am open to the notion that I should get involved. I am simply interested in consistency - I have no personal objections to voting on the motions. ''']''' ''']''' 14:02, 20 February 2013 (UTC)


;Abstain
*@snowolf: The ASUC reports are not strictly binding, but I can honestly not remember a single case of a report of that subcommittee that was not heeded verbatim by the committee at large. &mdash;&nbsp;]&nbsp;<sup>]</sup> 14:16, 20 February 2013 (UTC)
# 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:13, 7 December 2024 (UTC)
:*There was one case where it turned out that AUSC based its report and recommendation on a factual mistake. ] (]) 20:01, 20 February 2013 (UTC)


;Arbitrator discussion
*Not sure about this yet. It does seem an imbalance that arbitrators only hold their positions for two years and have to stand for re-election after that period of time, but CU and OS holders don't have to sustain that level of scrutiny. I do think that functionaries should be ''rigorously'' reviewed at least every two years, more likely every year, and possibly some reconfirmation may be appropriate, both by the community and by the then-current ArbCom (who are able to assess the quality of CU and OS actions taken). I also think that former arbitrators, and those who have not gone through a vetting and community scrutiny process, should provisionally retain the rights if the then-ArbCom does not object, but should be required to apply formally through the existing process to retain the rights. ] (]) 01:35, 21 February 2013 (UTC)


====Motion 2==== ==== Motion 1.4: expanding arbcom-en directly ====
{{ivmbox|1=If motion 1 passes, strike the following text:
<blockquote>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.</blockquote>


And replace it with the following:
Holders of CheckUser and/or Oversight permissions are presumed to continue to have the confidence of the Arbitration Committee under normal circumstances. CheckUser and/or Oversight may be removed by the Arbitration Committee for reasons other than inactivity, including recommendation by the Audit Subcommittee, conduct inappropriate to a user trusted with CheckUser and/or Oversight permissions, or breach of the ] or other related policy. Should the Arbitration Committee consider such removal, the holder of the permissions will be notified of this consideration, and will have the opportunity to respond to questions or concerns prior to a final decision by the Committee. Removal of advanced permissions may occur when:
<blockquote>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.</blockquote>
:(i) the holder of CheckUser and/or Oversight permissions has been notified of the concerns leading to consideration of removal of permissions and has had the opportunity to respond to those concerns, and
}}
:(ii) a majority of the committee, not including recused or inactive arbitrators, supports the motion.


{{ACMajority|active=10|motion=yes}}
Note that Level I procedures for removal of advanced permissions applies equally to removal of CheckUser and Oversight permissions, and that this motion does not affect Level I procedures.
;Support
# Much less trouble to have them on the main list than to split the lists. ] <sup>]</sup>] 04:13, 7 December 2024 (UTC)


;Oppose
=====Appeal of removal of CheckUser or Oversight permission=====
# 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. - ] (]) 04:21, 11 December 2024 (UTC)
Appeal may be made to the Arbitration Committee six months or more after the removal of CheckUser and/or Oversight permissions.
# Motion 1 is already problematic for privacy reasons; this would make it worse. ] (]) 19:14, 14 December 2024 (UTC)
# Follows on from my vote on ]. ] (]) 11:38, 27 December 2024 (UTC)


;Abstain
''{{ACMajority|active = 13 |inactive = 1 |recused = 1 |motion = yes }}''
# 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:24, 7 December 2024 (UTC)


;Arbitrator discussion
'''Support'''
* Proposed per ]. ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:24, 7 December 2024 (UTC)
:# Dispels any uncertainty over the status quo. This also emphasizes the "opportunity to respond" part over current procedures, and creates a special appeal provision rather than "normal arbitration proceedings" in current procedures, which frankly can't usually be held for CU/OS related issues. ] (]) 14:26, 24 February 2013 (UTC)
:# This works for me. Regarding the appeals procedure, it's probably not terribly ideal due to the echo chamber concerns Roger notes, but I think according to Foundation Policy we're the only body they ''can'' appeal to - the Arbitration Committee holds sole jurisdiction over who does and does not have CU and OS. Changing that would take a great deal of time and discussion with the Community and Foundation, and this will suffice in the meantime. For the latter half of the year, a delay of six months means that you're guaranteed to have a few new faces on the Committee anyway, so the appeal won't be heard entirely by those who voted for removal in the first place. ] <sup>(]/]/])</sup> 03:54, 25 February 2013 (UTC)
:#This works, as does simply treating CheckUser and Oversight as no different than Adminship or Bureaucratship. '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 18:52, 5 March 2013 (UTC)


=== Motion 2: WMF staff support ===
'''Oppose'''
{{ivmbox|1=
:# I am concerned about the lack of effective appeal arrangements, which are greatly exacerbated by the lowered bar for removing permissions. As this is something which could be handled independently by the ], and as the commission's remit is ], this motion is probably premature. &nbsp;] <sup>]</sup> 06:53, 26 February 2013 (UTC)
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.
:# Current procedures are sufficient. We should leave this aspect for now and return to this later in the year. ] (]) 01:04, 5 March 2013 (UTC)


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 ] 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.
'''Abstain'''
:#


The specific responsibilities of the staff assistants shall include, as directed by the Committee:
====Comments from Arbitrators - Motion 2====
* 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:
*Timotheus, I'm not certain what you mean by "special provisions". These are the current provisions, and indeed they're the current provisions for any case. The only difference is the description of reasons for contemplating removal of checkuser or oversight permissions. ] (]) 16:23, 24 February 2013 (UTC)
* Participating in the substantive consideration or decision of any matters before the Committee; or
**The current level 2 procedures says that "If the editor in question requests it, or if the Committee determines that a routine reinstatement of permissions is not appropriate, normal arbitration proceedings shall be opened to examine the removal of permissions and any surrounding circumstances." For obvious reasons, we can't open "normal arbitration proceedings", i.e., a case, for most CU/OS removals. The point is that this changes ''something'' over the status quo. ] (]) 16:39, 24 February 2013 (UTC)
* Taking non-routine actions requiring the exercise of arbitrator discretion.
***Thanks, TC; that makes sense. Now, on the mailing list after the initial motion was posted, there was some talk of either (a) outlining a minimum period for such a discussion, to ensure that there was input from at least the overwhelming majority of the non-recused committee members (i.e., ensuring it extended long enough for those inactive for very short periods, such as holidays, to be able to participate) or alternately not initiating a motion until the end of periods where a significant number of arbitrators were temporarily inactive. (Examples of the latter were Christmas and Thanksgiving breaks when many are traveling and have limited access; and Wikimania, where multiple arbitrators usually participate and again have periods of travel and very limited availability.) Did you have any thoughts about including something along this line? For example, discussion before a motion to remove is posted and voted on? ] (]) 17:57, 24 February 2013 (UTC)
*** Interesting point there. Given that the committee can sometimes be a terrible ], is there much point in appealing to the committee? Might be not a different route, say to the community members of AUSC, or a panel of CU or OS peers, be better? &nbsp;] <sup>]</sup> 18:28, 24 February 2013 (UTC)


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.
====Discussion and comments from functionaries and community====
What is "conduct inappropriate to a user trusted with CheckUser and/or Oversight permissions"? It seems fairly open-ended. --''']]]''' 02:09, 20 February 2013 (UTC)
:Specification of all possible examples is inappropriate. "Wrong stuff" will do. ] ] 02:17, 20 February 2013 (UTC)
::Of course, per ], but this sort of ambiguity is part of what led to the stalemate before the elections last year, because arbitrators couldn't agree on what was "inappropriate". --''']]]''' 02:23, 20 February 2013 (UTC)
:::Rschen has a point here. When what constitutes "inappropriate" is the very crux of the issue, it doesn't do a lot of good to say "well, you can be removed for inappropriate activity." It would be more valuable for arbcom to draw up at least a rough guideline for what, excactly, is behavior unbecoming of a functionary. Leaking? Personal attacks? Using one's powers to one's own good? Having generally poor judgment? Any of these things ''could'' be perceived as inappropriate by some or all arbs, and as long as it's a matter of each arb's personal judgment where the line is, we're inevitably directed back to square one in any specific case. ] (]) 02:29, 20 February 2013 (UTC)
* To echo something I just said to Risker at another venue, it would make more sense to me to discount inactive/recused arbs in votes like this than to count them as ]s (in the sense that if this motion is implemented, the mere existence of any recused or inactive arb numerically counts against the passing of a removal motion). In cases where, for whatever crazy reason, only a small proportion arbs remain unrecused and active, it would make more sense to say "] is not available to hear this matter, so it will be deferred until quorum is available" (in normal cases) and "well, we're stuck with X arbs able to vote, so X arbs voting it has to be" (in emergencies) as opposed to what would happen with this motion, which would be to hear matters when not enough arbs are available to reach any decision, and then go "welp, not enough arbs are voting, so you're free to go, person who may or may not have done something terrible". <small>This also raises the issue of why we're not just dealing with long-term arb inactivity in itself, to head off the need to do these case-law acrobatics.</small> ] (]) 02:52, 20 February 2013 (UTC)
*I think we (functionaries) serve at the pleasure of the committee and are or should be removable even without just cause or have to provide a reason in public. We are appointed by the committee, we are not elected, the committee is. The community, at least thru the directly-elected Committee, should have the last word on who should and shouldn't be a functionary. Obviously, to remove a functionary is no small matter, having us being entrusted with advanced and sensitive tools and having us being vetted and checked before hand, and most likely us being trusted and respected community members for some time. However, the Committee should have a way to remove those who have not abused their tools but who do no longer retain the Committee's trust, be it for consistently poor judgement, personal attacks or other behavior unbecoming of a functionary and that casts a shadow on our work, conflict of interest violation, and so on. In fact, I strongly believe the committee should have an open-ended option to remove functionaries, provided it obviously notify the user in question as to what the reasons for the removal are, as that is only fair. I do not believe this should create major issues or that the Committee would start removing those "they don't like", that would be petty and silly, and the Committee members are, whatever our personal disagreements with them may be, entrusted with some aspects of the governance of the project among which is specifically managing the permissions of Checkuser and Oversighter. I much dislike the fact that the community has no real way of removing admins in such circumstances (that is, consistently poor judgement that does not raise to the level of abuse) as it might lift some of the pressure that some of us feel when commenting on Requests for Adminship, that it is, short of flat out abuse, a life tenured position and that a decision made there and then is not reversible by the community. This should also go for the Arbitration Committee and functionaries. They should feel that if, no matter their rigorous vetting, a functionary has shown that for whatever reason (s)he's not a good fit for the job, they can remove him. Also I suggest that an Audit Subcommittee's "recommendation" should be binding as it pertain to the exercise of their functions, that is, that the Committee should be delegating to the AUSC all matters relating to functionary '''abuse''' and violation of policies and as such that their decision would have the effect of removing the functionary's access. The neutral role of the AUSC and their decisions should not have to be validated by the full Arbitration Committee to be effective. In the specific of the voting system, I have to agree with the Arbitrators who opposed a qualified majority rule for such decisions to be made, the committee is fairly small and a few recuses could bring any such motion to a halt. I suggest a 2/3 majority of the voting arbitrators should be enough to both ensure that such decisions would be feasible and that extra-consensus would be required. <i><b>] <sup><small>]</small></sup></b></i> 11:56, 20 February 2013 (UTC)
@SilkTork -- why do you recuse? <small>]</small> 12:01, 20 February 2013 (UTC)


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.
*I must say I respectfully disagree with Snowolf. The idea that the functionaries are mere minions of Arbcom, to be appointed or dismissed at will, is perfectly acceptable in terms of Mediaeval monarchs, but I find it quite disturbing in the context of Misplaced Pages. And the idea that Arbcom can remove a functionary essentially because some members don't like them - rather than because the rules relating to the use of the tools has been breached or threatened, or some other agreed definition of 'wrongdoing' has occurred - would surely create an open door to politicking and abuse, as Risker has pointed out above. And I am minded that if Risker is raising it as a concern, the possibility of it happening is not negligible. ] (]) 13:33, 20 February 2013 (UTC)
::@Carcharoth - admins are for life as well. Although if you could institute a review system for functionaries, it might encourage one for admins. ] (]) 16:29, 21 February 2013 (UTC)
*The problem with passing motions of any sort is, as that ArbCom's existing rules are biased against anything happening at all, and the pocket veto Fluffernutter refers to above is something regularly exercised by at least a couple of rather senior arbitrators. Consider that even in a regular vote, there are really only three sorts of responses:
:*1) Support. Increments the number of supports by one.
:*2) Abstain, Recuse, or Inactive. Decrements the number of voting arbitrators by one, and every other such vote decrements the number of supports needed by one.
:*3) Oppose or no vote. Doesn't do anything to the number of supports or the number of supports needed.
:I think to solve the more general problem, the committee should reorganize voting into two different ''classes'' of voting:
:First, traditional pass-then-implemented-in-24-hours voting, where clerks are watching the events unfold like hawks.
:Second, a "net four to close" motion, used traditionally under one umbrella in cases.
:The first sort of vote, which is a "rush" vote (inasmuch as anything the committee ever does is a rush), could probably stand to stay like it is. However, when there's a "net four for closure" rule, there's a second layer of protections, in that arbitrators are rarely shy about opposing a closure because other arbs have yet to vote, even if their own votes have been set for days or weeks. I would suggest to the current committee that any vote that is to be closed by a "net four for closure" process treat a no-vote as an abstention, reducing the number of voting arbitrators and the passing threshold, rather than as an oppose as is currently done and would continue to be done in the first sort of vote. ] (]) 02:40, 21 February 2013 (UTC)


Staff assistants shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.}}
I read all the stuff above, and am fully ''unconvinced'' of the need thereof. ArbCom has the ability, through normal processes already existing, to remove admin privileges ''for cause'' - and checkuser and oversight privileges should surely be treated in the same manner -- that is, requiring the use of the ''currently existing'' processes. Creating a strange new process which is less restrictive on ArbCom than the extant processes is, IMO, improper, unnecessary, and ''a solution in search of a problem.'' As an aside, I find the "net vote" system to be arcane at best where use of "2/3" or the like is customary in the "real world". The current system may require "more than unanimity" if only 3 arbs are voting, and if only 7 are voting (as is not all that uncommon in the past) two arbs have an absolute veto power over any decisions. In the outside world, if only 7 people can vote, then 5 is generally the maximun vote required for decisions. Aside to Snowolf: the use of "without cause" would open up the committee to pure politicking - and is also a "solution without a problem." Noting here my agreement with points made by Elen and Jclemens as well. ] (]) 14:46, 24 February 2013 (UTC)
:I don't think it would. I feel I am very independent of the arbitration committee in my duty as an oversighter, yet I would have no objection to being removed if the ArbCom didn't feel I was doing a good job. In fact, ArbCom and the other oversighters are the only users who can tell whether I'm doing a good job as an oversighter or I'm making a mess. So to me it seems natural that they should have the power to remove me if I'm not suited for the job... Nobody else can: the community at large can't really review my actions given they're privacy-related and suppressed, and I for one, if I am doing a disservice to the community as an oversighter (not talking about abuse, just saying what if I am not cut out for the job but this was found out after I got it), somebody ought to be able to remove me. That is the general point on why I feel the Arbitration Committee should have the power to remove me. On the specifics of "without just cause", it's precisely so that they have the freedom to act in the best interests of the English Misplaced Pages (in my experience with the Committee, the folks there try to act in the best interest of this project, tho of course different people have different ideas about what's best for the project, but none of them would remove a functionary on a whim or personal dislike) without having to go into details of why such a removal would take place. This doesn't mean that it should be taken lightly, just that they wouldn't have to announce the reasons behind it, tho I would of course expect them to disclose them to the individual in question. I believe trust must exist between elected ArbCom and the "life-tenured un-elected functionaries" and if that relationship was broken, one shouldn't remain a functionary. That is of course my personal view, and as you've seen above other functionaries have different views but I want to clarify that I do personally thing such a concept would lead to politicking or whatever :) <i><b>] <sup><small>]</small></sup></b></i> 12:23, 5 March 2013 (UTC)


<!-- change the number depending on active count -->
== Oversight-related blocks ==
{{ACMajority|active=10|motion=yes}}
;Support
#


;Oppose
On {{diff|Misplaced Pages:Arbitration Committee/Noticeboard|prev|374236496|July 19, 2010}}, the Arbitration Committee issued a statement noting that blocks based on confidential Checkuser information should not be lifted without consulting a Checkuser who has the ability to review said information. Since that time, this has been incorporated into the ] ].
# 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, ] version is that this would destroy the line between us and the Foundation, which undoes much of our utility. ] <sup>]</sup>] 01:22, 3 December 2024 (UTC)
# Per my comment on motion 4. - ] (]) 01:31, 7 December 2024 (UTC)
# Might as well make it formal per my opinions elsewhere on the page. ] (]) 13:24, 10 December 2024 (UTC)
# 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. ] (]) 19:05, 14 December 2024 (UTC)
# 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 ] position. ] (]) 12:56, 24 December 2024 (UTC)


;Abstain
While that statement focused primarily on checkuser-based blocks, the Arbitration Committee reminds administrators that they should not be taking any action when they are unable to make themselves fully aware of the circumstances that led to the block under review. Specifically, an oversighter may note that a block should not be lifted without consulting a member of the oversight team; in these situations, administrators are expected to heed this request and not unilaterally remove the block.
#


<!--
:''{{ACMajority|active = 14 |inactive = 1 |recused = 0 |motion = yes}}''
;Arbitrator discussion
-->
==== 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 18:28, 1 December 2024 (UTC)


=== Motion 3: Coordinating arbitrators ===
'''Enacted''' - ''']''' (] • ] • ]) 07:34, 9 March 2013 (UTC)
{{ivmbox|1=
The ] are amended by adding the following section:
<blockquote>
; 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 ] assist in the administration of the Committee's on-wiki work.
; Support
:# Proposer. Basically, any block based on confidential evidence should be given the same deference we apply to checkuser blocks, because it's the same reason. ] <sup>(]/]/])</sup> 06:19, 5 March 2013 (UTC)
:# ] (]) 06:19, 5 March 2013 (UTC)
:# &nbsp;] <sup>]</sup> 06:21, 5 March 2013 (UTC)
:# Make it explicit, though this should have been so obvious no reasonable admin could have acted otherwise. ] 06:48, 5 March 2013 (UTC)
:# '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 06:49, 5 March 2013 (UTC)
:# I'm unhappy on principle at reducing administrator discretion, but oversighter blocks certainly need to be clearly exempted from the usual processes of action reversal. ] ]] 08:12, 5 March 2013 (UTC)
:#Without comment on the current situation, I do think this is a sensible motion to pass. ]<sup>TT</sup>(]) 08:48, 5 March 2013 (UTC)
:# ''']''' ''']''' 08:50, 5 March 2013 (UTC)
:#Full support of this motion. I would add that where consulting with one or more oversighters does not resolve the issue, it should be referred to the Arbitration Committee or its BASC subcommittee. ] (]) 12:50, 5 March 2013 (UTC)
:#:In response to comments below, as I just posted elsewhere: "As with checkuser blocks, it is important to realize that this policy does not apply to every block made by an administrator who happens to also be an oversighter, but only to blocks based on private information and expressly flagged as 'oversighter blocks.' It will be comparatively rare that such a notation will be made, but when it is, it should be respected." ] (]) 13:49, 5 March 2013 (UTC)
:# ]&nbsp;<sup>]]</sup> 12:59, 5 March 2013 (UTC)
:# Makes explicit what was already obvious. That said, I don't think this actually removes any admin discretion: there was already no possible deliberate judgment possible given that any action reverting an oversight-related block is necessarily done ''without'' all the information. &mdash;&nbsp;]&nbsp;<sup>]</sup> 13:21, 5 March 2013 (UTC)
:# ] (]) 13:44, 5 March 2013 (UTC)
:# Oversighter blocks and bans can certainly be appealed, but they shouldn't be unilaterally overturned. <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 13:57, 5 March 2013 (UTC)
:# Per all the above. ] (]) 08:47, 6 March 2013 (UTC)


The specific responsibilities of coordinating arbitrators shall include:
; Oppose
* 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.
; Abstain
</blockquote>
}}


<!-- change the number depending on active count -->
=== Arbitrator discussion ===
{{ACMajority|active=10|motion=yes}}
;Support
# 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. ] (]) 18:53, 1 December 2024 (UTC)
#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. ] <sup>]</sup>] 01:14, 5 December 2024 (UTC)
#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. - ] (]) 23:21, 9 December 2024 (UTC)
#Per Primefac. ] (]) 19:19, 14 December 2024 (UTC)


;Oppose
As a general comment to those below who feel that this is excessive, there are a few reasons why checkuser blocks (and with this motion, oversight blocks) are considered to be protected under a "do not remove on pain of desysopping" rule:
#
# As stated in the motion, the block is based on private information which the non-functionary administrator does not have access to (this would also apply to a non-CU oversighter lifting a CU block, or a non-OS checkuser lifting an oversight block, just to be clear). Administrators should not take action with their administrative tools unless they have made a good-faith effort to understand all aspects of a situation. This is inherently impossible with blocks based on confidential information; an administrator who lifts such a block is implying that their limited understanding of the case is greater than that of the functionary who placed the block with full knowledge of the situation. This clear contradiction is obvious evidence that an administrator is exercising extreme poor judgment when lifting such a block.
# In many cases, a block issued under the protection of a {{tl|checkuserblock}} template or similar is made with the consultation of one or more additional functionaries. In the case that prompted this motion, there was extensive discussion on the oversight mailing list. These blocks are not unilateral actions; they are based on the consensus of a number of informed users. In lifting these blocks, our (as discussed) uninformed administrator is also presuming that his or her opinion is superior to that of the consensus that led to the block in the first place. This violates the principles on which our community was founded, and calls into question the reliability of the administrator's actions elsewhere.
# In such cases, there are a number of indications to the administrator that there is a better course of action to take. The {{tl|checkuserblock}} template, and the block log involved in this particular incident, both clearly indicate that an administrator considering an unblock should discuss their action with appropriate functionaries before taking said action. The functionaries will not be able to explain everything due to the restrictions of the project's and Foundation's privacy policies, but they will be able to share enough to indicate whether they believe unblocking is a good or bad idea. If the functionary (or functionaries) say it's a bad idea, the administrator should defer to that judgment, because (as per point 1) the functionary/ies have more information than the administrator has, and it's entirely possible that there could be serious implications to the project, its volunteers, or even the Foundation if the user were to be unblocked.
An administrator who, despite all of this, continues to unblock a user blocked for these reasons is exercising extreme poor judgment beyond what could be reasonably explained as a simple mistake. As a result, the Arbitration Committee will, unfailingly, remove administrative and other advanced rights from said administrator. Absent a very clear an obvious danger to the project (which a single unblock of this nature would not be), this decision is not made without some deliberation; the Committee's procedures require a majority of the Committee support the motion, and require that the Committee allow the administrator to explain their actions and/or rectify the situation. When and if the desysop is carried out, it is a temporary measure, and the desysopped administrator may request a full arbitration case be opened to fully examine the circumstances of their unblock and subsequent desysopping. If, during that time, a more satisfactory explanation is presented or the Committee is otherwise satisfied that the desysopped administrator can be trusted to use their tools appropriately in the future, they will be restored. And, of course, the community may re-grant the administrative tools to the user through another RfA, if they beleive that the Committee's action was truly incorrect. ] <small>]</small><sup>(]/]/])</sup> 17:10, 5 March 2013 (UTC)


;Abstain
=== Clerk Notes ===
#
*While this motion is passing unanimously with every active Arb, at the time of the proposal, supporting, the clerks will keep this open for a bit longer for community input before closing and acting on the motion. For the clerk team, --] &#124; ] 20:18, 6 March 2013 (UTC)


<!--
=== General discussion ===
;Arbitrator discussion
*This seems a good idea. Unfortunately admins sometimes forget about the parts of WP:BLOCK that require discussion before unblocking (eg, "Except in cases of unambiguous error, administrators should avoid unblocking users without first attempting to contact the blocking administrator to discuss the matter."), and this is a major problem in cases such as this where the block is imposed due to information which isn't available on-Wiki. ] (]) 07:14, 5 March 2013 (UTC)
-->
==== Motion 3: Arbitrator views and discussions ====
*I am also open to this idea, though I am worried that it will be insufficient and haven't made up my mind on my vote yet. This idea was floated by a former arbitrator from back when the committee ''did'' have a coordinating arbitrator, though that role kind of quietly faded away. The benefits of this approach include that there's no need to bring anyone else onto the list. This motion also allows (but does not require) arbs to take a step back from active arb business to focus on the coordination role, which could help with the bifurcation I mention above. Cons include that this could be the least reliable option; that it's possible no arb is interested, or has the capacity to do this well; and that it's hard to be both a coordinator on ''top'' of the existing difficult role of serving as an active arb. I personally think this is better than nothing, but probably prefer one of the other two motions to actually add some capacity. {{pb}} 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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 ]. 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. ] <sup>]</sup>] 01:35, 3 December 2024 (UTC)
** {{yo|CaptainEek}} I think your last sentence actually kind of nails why I <em>don't</em> 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 <em>am</em> leaning towards voting for the scriveners motion, though, because I do love a good whimsical name {{Emoji|1F604|theme=twitter|size=20px}} ] (] • 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. ] (]) 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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. ] (]) 08:35, 27 December 2024 (UTC)


=== Motion 4: Grants for correspondence clerks ===
*We encourage non-wikipedians (and wikipedians) to contact oversight mailing lists off-wiki to resolve issues that need oversight intervention. It seems like a no-brainer that those decisions should not be overturned by someone just because "they can." Oversight intervention is arguably a protection level higher than CU and it seems that if checkuser blocks can't be undone unilaterally and arbcom blocks can't be undone unilaterally, then Oversight blocks (somewhere between CU and Arbcom) should be covered. CU protects the project. Oversight protects the project, its editors and the public from malicious content that needs deletion. Blocks arising from that action should only be overturned by Oversight or Arbcom as they would be the only ones with enough material to evaluate it. --] (]) 07:58, 5 March 2013 (UTC)
{{ivmbox|1=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.}}
{{ACMajority|active=10|motion=yes}}
;Support
#


;Oppose
*Noting for the record that a section has been added to ] to cover this: ] (]) 08:10, 5 March 2013 (UTC)
# 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. ] <sup>]</sup>] 01:09, 3 December 2024 (UTC)
# We should not have a clerk paid by the WMF handling English Misplaced Pages matters in this capacity. - ] (]) 01:48, 6 December 2024 (UTC)
# ] (]) 19:18, 14 December 2024 (UTC)
# I feel bound by my RFA promise - ] ] (]) 08:41, 27 December 2024 (UTC)


;Abstain
*And why exactly is it (see new section linked above) that such an unblock should result in an immediate de-sysopping? Is such an admin immediately reclassified as an extreme risk to the project? What would be wrong with restoring the block, with a warning to the unblocking admin not to do it again on pain of losing the tools? If ''then'' they did it again, obviously there would be a real problem. — ] ] 08:24, 5 March 2013 (UTC)
#
:* Please correct me if I'm wrong, but isn't it long-standing policy that desysopping is a remedy for overturning an ArbCom or Checkuser block? ] says that doing so "may lead to sanctions for misuse of administrative tools—possibly including desysopping—even for first time incidents." This was added by ] way back on 17 March 2008 and I don't think it's been challenged since. ] (]) 08:33, 5 March 2013 (UTC)

::*The remedy you quote applies to 3 specific circumstances, none of which are connected to Arbcom or oversight. ] (]) 08:45, 5 March 2013 (UTC)
<!--
:::*One of those circumstances is "when the block is explicitly enforcing an active Arbitration remedy", which is obviously connected to Arbcom. The prohibition on undoing checkuser blocks without first consulting checkusers was added in September 2008 and was strengthened in July 2010 by an ArbCom motion which established desysopping as a remedy. <small><span class="autosigned">— Preceding ] comment added by ] (] • ]) 08:58, 5 March 2013‎</span></small><!-- Template:Unsigned -->
;Arbitrator discussion
::::*"An ArbCom motion which established desysopping as a remedy" - huh? All that last link states is that "should be reviewed only by the Arbitration Committee" or "should only be lifted by ArbCom" block notes are only appropriate in the case of blocks that involve sensitive material best not discussed on-wiki. Would you care to present some actual factual basis for your argument for the policy/precedent basis of desysopping? — ] ] 10:03, 5 March 2013 (UTC)
-->
:* Desysopping is going to always be a case by case basis. A level II desysopping is discussed and then implemented by arbcom after discussion. After a full review, the tools can be restored. If you are referring to the case that started this, please note that the unblocking admin had not blocked or unblocked anyone in nearly 3 years and then decided to use the tools to overturn two Oversight user blocks. Removing the tools that he hadn't used in 3 years so his actions can be discussed is heavily weighted toward immediate desysopping in terms of value to the community. We waited 3 years for that action so a couple of weeks discussion is certainly more favorable than wheel-warring. He's not blocked and can continue to contribute to the project. --] (]) 08:51, 5 March 2013 (UTC)
==== Motion 4: Arbitrator views and discussions ====
{{hat|This is a discussion about the motion. The specific case referred to is being discussed ].}}
*Proposing for discussion; thanks to {{U|voorts}} for the idea. Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 19:00, 1 December 2024 (UTC)
::*To overturn block, I think you mean. An admin uses a tool once in three years and gets it wrong, so that's clearly grounds for immediate desysopping? That's ''Through the Looking-Glass'' logic at its finest. — ] ] 09:39, 5 March 2013 (UTC)
*:I am leaning no on this motion. The potential downsides of this plan do seem to outweigh the benefit of being able to compensate a correspondence clerk for what will ultimately likely be something like 5 hours a week at most. Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 02:13, 3 December 2024 (UTC)
:::* Not using it for 3 years and the 1st action is to unilaterally overturn an oversight block?? Umm yes, that's an immediate desysopping. If that's what he needed the tools to do, we can live without that. --] (]) 10:06, 5 March 2013 (UTC)

::::* Please ]. There is nothing about what Kevin did that mandates that kind of heavy-handed treatment. The issue could have been dealt with by a reversal of Kevin's action and giving him some education on appropriate usage, possibly an admonishment. — ] ] 10:24, 5 March 2013 (UTC)
=== Community discussion ===
:::::*The block was specifically labeled "do not undo". He undid it. What did he expect to happen, good things? Not only was that a very bad move, it shows a blatant lack of respect for privacy-related issues such as those in play here. --''']]]''' 10:28, 5 March 2013 (UTC)
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. ] ] 18:29, 1 December 2024 (UTC)
::::::*You can say anything you want in a block label. It doesn't mean anything unless it's backed up by policy. And if "lack of respect" was a blockable offense, half of the regular editors on this project would be gone by now. Again, nothing you're saying justifies this iron fist treatment. — ] ] 10:35, 5 March 2013 (UTC)
:Good catch. I thought it was implied by "from among the English Misplaced Pages functionary corps"{{snd}}who all sign NDAs as a condition to access functionaries-en and the CUOS tools; see ] ({{tqq|1=Functionary access requires that the user sign the ].}}) {{snd}}but I've made it explicit now. ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 18:31, 1 December 2024 (UTC)
:::::::*]. Furthermore, even if that was not enough, ArbCom already had emailed Kevin about the matter, and ''Kevin had plenty of time to reblock Cla68 of his own accord''. The fact that he did not do so, and persisted in this makes this even worse. --''']]]''' 10:44, 5 March 2013 (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). ] ] 18:37, 1 December 2024 (UTC)
:::::::::*What knowledge do you have of discussions between myself and Arbcom? I woke this morning to see a generic note on my talk page asking me to email them, which I did. I received a single question in reply, which I answered. ] (]) 11:30, 5 March 2013 (UTC)
----
:::::::* How is a temporary removal of tools, pending review, "heavy-handed" and "iron fist treatment?" --] (]) 10:45, 5 March 2013 (UTC)
Why does "coordinating arbitrators" need a (public) procedures change? ] (]) 18:34, 1 December 2024 (UTC)
::::::::* I ask you again, what danger was posed to the project by Kevin retaining his sysop bit? — ] ] 11:05, 5 March 2013 (UTC)
:As ], 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 19:08, 1 December 2024 (UTC)
:::::::::*He might do it again? I'd support a temporary sysop of anyone who did what Kevin did, and in particular I don't see how this is going to greatly handicap Kevin or Misplaced Pages to have the bit removed pending review. ] (]) 11:34, 5 March 2013 (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. ] (]) 19:13, 1 December 2024 (UTC)
:::::::::* If you had asked me two days ago, I'd have said 'None' as he doesn't use the block tools anymore. But his ill-thought-out unblock was rash and showed incredibly poor judgement that has already harmed the project by wasting everyone's time and amping up the dramafest. But your argument is a strawman argument as level II desysopping doesn't require danger, only mistrust and a response to Arbcom that isn't satisfactory. --] (]) 11:39, 5 March 2013 (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. ] (]) 19:21, 1 December 2024 (UTC)
{{hab}}
----
While I appreciate that some functionaries are open to volunteering for this role, this <s>borders on</s> <ins>is</ins> 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. ] (]/]) 18:35, 1 December 2024 (UTC)
:Thanks for this suggestion{{snd}}I've added motion 4 to address this suggestion. Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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. ] (]) 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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. ] (]) 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. ] (]) 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 ] 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. ] ] 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. ] (]) 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. -- ] <sup>]</sup> 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. --] (]) 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 ], 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, ] (]) 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. ] ] 00:14, 3 December 2024 (UTC)
:::::And Roger was a pensioner which kinda proves my point -- ] <sup>]</sup> 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. ] (]) 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. --] (]) 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, ] (]) 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. --] (]) 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. ] ] 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, ] (]) 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. ] ] 23:12, 1 December 2024 (UTC)
::Since ] 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. - ] (]) 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, ] (]) 00:28, 2 December 2024 (UTC)
::Regarding "timing is wrong": I think you both would agree that these are a long time coming{{snd}}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. <br>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{{snd}}as JSS says, this is my last year on the committee, so it's not like this will benefit me. Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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, ] (]) 01:47, 2 December 2024 (UTC)
::::Here's what I'll leave you with overall. What you may see as a downside{{snd}}these proposals being voted on relatively late in the year{{snd}}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{{snd}}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. {{pb}} If what really concerns you is locking in the new committee to a particular path, as I wrote ], 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 22:58, 2 December 2024 (UTC)
:*As a 3-term former arb and a 3-term current ], 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. ] 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, ] (]) 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. ] 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, ] (]) 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. ] (]) 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? ] <sup>(]) </sup> 02:15, 2 December 2024 (UTC)


:@] Yes, but probably only after an additional step. The penultimate paragraph of motions 1 and 2 says {{tpq|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). ] (]) 03:01, 2 December 2024 (UTC)
All too often, admins overturn justified blocks without any discussion first. Its entirely too bold for any admin to be overturning an oversight block without discussion, so this motion seems appropriate.--] 12:03, 5 March 2013 (UTC)
----
*I likewise agree with this motion, tho I feel the block policy already incorporates this and common sense should suggest that any admin should not unblock if they have not access to key details of what led to the block. I am a bit sad to see that this motion is actually required. <i><b>] <sup><small>]</small></sup></b></i> 12:11, 5 March 2013 (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? <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 07:20, 2 December 2024 (UTC)
**Agree. Sometimes it can't hurt to state the obvious. ] (]) 12:20, 5 March 2013 (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{{snd}}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{{snd}}that was an idea that came from ], 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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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? <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 21:40, 2 December 2024 (UTC)
:::Yeah, these are great questions. Responses to your points:
:::* On volunteers: As I wrote ], four functionaries (including three former arbs) expressed initial-stage interest when this was floated when I consulted functionaries{{snd}}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 {{tqq|1= all of the work of an arbitrator (or more) without any ability to influence the results}}{{snd}}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 ] but I know there are many.
:::Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 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. ] (]) 07:19, 3 December 2024 (UTC)
:::::{{tpq|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. ] (]) 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.
::::::@] 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 @] 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. ] (]) 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. ] <sup>]</sup>] 02:18, 4 December 2024 (UTC)
::::::::I agree, having someone managing the work could really help smooth things out. ] (]) 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? ] (]) 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. ] (]) 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? ] (]) 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. ] (]) 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, ] (]) 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. ] (]) 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 {{em|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. ] (]) 00:26, 3 December 2024 (UTC)
:@] 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. ] <sup>]</sup>] 01:29, 3 December 2024 (UTC)


I touched upon the ] 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.) ] (]) 23:18, 2 December 2024 (UTC)
*I'm not too concerned about the current situation; it's all grudge politics, and almost without exception, everyone involved on both sides acted like a dick. People who play The Game shouldn't complain when they lose The Game. Well, I guess that's part of The Game too, but don't expect normal humans to care about the complaint too much.


----
:However, Monty845 made a very good point last night at ], where this was being discussed before being preempted here. He was more eloquent than I am: please read it: . His point didn't make it into this motion. While I don't expect a new motion, I would at least like some of the less rules-oriented arbs, in their comments, to say that OS blocks should only be considered "OS and AC only" when that is actually necessary; that oversighters should attempt to provide the community with enough information that they can resolve it themselves, where practical, and limit this type of block to cases where it is necessary. --] (]) 13:16, 5 March 2013 (UTC)
{{tq2|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. }}
:I'm happy to go on record stating that this should be an unusual situation. In my opinion, oversighters should not commonly be blocking for reasons associated with oversight, so these blocks should not be considered frequent. Indeed, I never blocked nor saw a situation where I might have blocked with my oversight hat on. The important point that needs to be noted is that people should not unblock without trying to get an understanding of the big picture, and in certain circumstances (Arbcom, CU and OS blocks), an admin cannot get that picture. ]<sup>TT</sup>(]) 13:26, 5 March 2013 (UTC)
:*(@Flo) That is indeed already the case, Flo. Blocks are "checkuser and oversight" blocks only when ''explicitly'' marked as such, and not just by virtue of having been made by someone holding the bit, and we demand that they do so only in cases where it would ''not'' be possible for the community to review them because doing so would require discussing private information. Any functionary misusing this would not be a functionary for much longer. We also expect that they (especially oversighters) err on the side of caution so some allowance needs be made for that. The balance is delicate, which is why any other functionary can review the situation and "downgrade" the block at need. &mdash;&nbsp;]&nbsp;<sup>]</sup> 13:31, 5 March 2013 (UTC)
::*Ditto Floq and Monty. There are certainly good reasons (rarely) for OS to put a special OS block, but as with any bits, there is an opportunity that it be overused or used inappropriately and the lack of admin oversight makes this problematic unless we have just enough disclosure to understand why the block is in place. ] - ] ] <small>]</small> 13:35, 5 March 2013 (UTC)
::::Drawing your attention to sensible process, as stated by NYB: "I would add that where consulting with one or more oversighters does not resolve the issue, it should be referred to the Arbitration Committee or its BASC subcommittee." -- ] (]) 13:46, 5 March 2013 (UTC)
*I commend the current committee for its swift, decisive, and common-sense action. It's unfortunate that the implicit needs to be made explicit, but it does. ] (]) 15:18, 5 March 2013 (UTC)
*I think there are two distinct types of unblock request in this context, and that we need to distinguish between them. First, an editor can challenge the basis for their block, arguing either that they did not do what they were accused of, or that it didn't warrant a block. It is totally understandable that if the evidence that resulted in the block is oversighted, a non-oversight admin cannot in most cases determine if the oversight block is justified, and should not unblock. Second, and editor can acknowledge what they did, and request an unblock under the premise that they will change their behavior such that the block is no longer necessary to protect Misplaced Pages. It is not clear to me why in most cases, the second type of unblock request could not be handled by a non-oversight admin, if at least general information about the nature of the oversighted material is publicly known. In essence, the non-oversight admin knows what they don't know, and they, or the community can make a sufficiently informed decision that it can be done in public. Of course we don't know what we don't know, and there may be additional evidence that is totally secret, and where even a general description of the evidence would violate privacy. Such totally secret evidence is the reason why designated checkuser blocks are privileged, and rightly so. If the committee passes this motion, which it looks like it will, I would urge it to provide clear guidance to oversighters that they should only invoke the oversight block privilege where there is important secret information that weighs against an unblock beyond the exact nature of the oversighted edits themselves, as the nature of the oversighted material can be described generally without violating privacy, which would allow the unblock to be considered by non-oversighters in the case of the second type of block. ]] 16:36, 5 March 2013 (UTC)
**Other relevant evidence that would be unavailable to non-oversighters could include prior suppressed/oversighted edits by the same editor, as well as discussion contained on the oversighters' or functionaries' mailing lists. Please bear in mind that only a small percentage of blocks by oversighters are marked with a "do not unblock without consulting the oversighter team," so this new or reinforced (take your pick) policy will apply relatively infrequently. ] (]) 16:41, 5 March 2013 (UTC)


Something I raised in the functionary discussion was that this doesn't make sense to me. What is the basis for this split here? ] (]) 00:08, 3 December 2024 (UTC)
*I don't necessarily oppose oversighter blocks in principle, but '''I oppose this motion because it is ''ultra vires'''''. Policy is made by the community, not by the Arbitration Committee, and certainly not when that committee is only making the policy to retrospectively justify an action which had no basis in policy. If this amendment to the blocking policy is needed, then it should be discussed in a Request for Comment like any other policy change. There is no emergency that means it cannot wait for the established process to conclude, and if Hersfold wishes to propose a policy change, he should do so the same way as any non-arbitrator—policy proposals from members of the "Arbitration" Committee are no more (and indeed no less) valid than those of any other Wikipedian. ] &#124; ] 17:08, 5 March 2013 (UTC)
:*If I could +1 this ten times, I would. There is no emergency, and this motion is an abuse of process. — ] ] 17:21, 5 March 2013 (UTC)
:* Any user group whose members can access restricted or privileged information have special protection afforded to their actions by long-standing policy and convention. Checkuser blocks and OTRS agent protection/deletions are examples of this special protection; the present motion proposes that Oversighter blocks are also based on restricted information. If you agree with that thinking, then you cannot reasonably oppose the motion without also suggesting that the other specially-protected actions should also have their special status revoked. You cannot have the basic policy that "blocks based on special data can't be overturned by people who can't see that data" apply to some special-data actions and not others. As for the method of extending this status to Oversight blocks (through an ArbCom motion rather than the ordinary methods), it seems appropriate to me to make "OS block" a special entity through the protectorship of ArbCom. If the policy is sound ''and'' relates to administrator misconduct, then it should be confirmed by ArbCom so that our administrators know to take the policy seriously. ] ]] 17:34, 5 March 2013 (UTC)
::* Protectorship of ArbCom? I thought the committee was supposed to resolve issues the community had come to an impasse on. Now they're a protectorship? <small>]</small> 17:39, 5 March 2013 (UTC)
:::* I understand AGK's meaning to be that the thing being protected is the action, i.e. the OS block. It's not ArbCom that protects it but policy - and it's long-standing policy (going back at least to 2008) that certain types of admin actions, like arbitration and CU blocks, ''are'' protected. Perhaps "protection" is the wrong way to think of it, though. "Special handling" might be more apposite. ] (]) 19:05, 5 March 2013 (UTC)
::*Anthony, you know I have a lot of respect for you, but I didn't say I opposed oversighter blocks (there's a more general point about actions based on private information, but this isn't the best place to discuss that); I said I opposed it being shoehorned into policy by ArbCom motion (which is ''ultra vires'' by my interpretation of the Arbitration Policy, but you didn't address that point). There is nothing so urgent that this amendment can't go through the process that every other policy change has to go through (and actions based on OTRS tickets and other sorts of private information can be included in that if you want). ] &#124; ] 17:52, 5 March 2013 (UTC)
*What's all this now about a full case? ] (can't bring myself to use the silly term "Level II Procedures") says: "''Return of permissions... Removal is protective, intended to prevent harm to the encyclopedia while investigations take place, and the advanced permissions will normally be reinstated once a satisfactory explanation is provided or the issues are satisfactorily resolved. If the editor in question requests it, or if the Committee determines that a routine reinstatement of permissions is not appropriate, normal arbitration proceedings shall be opened to examine the removal of permissions and any surrounding circumstances.''". --] (]) 17:20, 5 March 2013 (UTC)
**Yes. "Normal arbitration proceedings" == full case. ] <small>]</small><sup>(]/]/])</sup> 17:27, 5 March 2013 (UTC)
***Yes, I know that, I think you're either misreading this, or changing the procedures on us. Currently, a full case is only required if "the Committee determines that a routine reinstatement of permissions is not appropriate", after discussion with the person who's been desysopped. You're changing this? Or you're preemptively saying that a desysop under this motion, unlike any other type of desysop, is ''automatically'' assumed to be irreversible without a full case? I think you're over-reaching here. --] (]) 17:39, 5 March 2013 (UTC)
*I agree with HJ Mitchell. Why is this so urgent it can't go through normal policy-making discussions?--] 17:26, 5 March 2013 (UTC)
At the time of the unblock the policy stated (emphasis mine):


: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 ] 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.
{{quote|
:Conversely it would spare the clerks from having their inboxes flooded by every single arb comment, which as you know can be quite voluminous. ] ] 00:23, 3 December 2024 (UTC)
Administrators should not undo or alter any block that is specifically identified as a "Checkuser" block by use of the {{tl|checkuserblock}} template in the action summary without first consulting a ]. If an administrator believes that a Checkuser block '''has been made in error,''' the administrator should first discuss the matter with the Checkuser in question, and if a satisfactory resolution is not reached, should e-mail the ].<ref></ref>}}
::And it would also prevent them from seeing information related to themselves or something they should actively recuse on. ] (]) 01:15, 3 December 2024 (UTC)
Kevin did not assert the block was made in error, he didn't undo the block, he unblocked an editor after the editor agreed not to repeat the behavior (in Kevin's opinion). We can know and accept that the editor violated outing without knowing the dirty details; that doesn't preclude accepting their assertion they won't repeat the behavior under the blocks not punitive meme. What the committee seems to be saying here is some oversighted actions are so heineous as to preclude unblocking -- in other words, the editor must be punished. <small>]</small> 17:33, 5 March 2013 (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. ] (]) 01:39, 3 December 2024 (UTC)
:No. The Committee is saying that the editor's promise was not sufficient at the time that Kevin unilaterally decided it was, and that he had no way of properly evaluating whether it was or not, as he was not privy to the relevant discussions and evidence. I will be surprised if Cla68 is not unblocked eventually, but I will be surprised if he is unblocked before he makes additional assurances as to his future conduct. '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 17:54, 5 March 2013 (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. ] (]) 02:35, 3 December 2024 (UTC)
::* unilateral.
::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. ] (]) 01:43, 3 December 2024 (UTC)
::* relevant discussions? Last I knew, the appropriate forum for discussing unblocking was the user's talk page -- certainly the block template Beeblebrox indicates that. Additionally, the participation of oversighters NYB, Beeblebrox and Allison on the talk page makes it seem like that was the correct place. <small>]</small> 18:41, 5 March 2013 (UTC)
::Apologies{{snd}}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{{snd}}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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 01:54, 3 December 2024 (UTC)
:::*''All'' of the relevant discussions means a bit more when a) the reason that the user is blocked is oversighted and b) the user has been warned about similar behavior in the past. I would agree with you if Cla68 was willing to accept Newyorkbrad's terms, but he stated that he was not. Without knowing more of the background, something that Kevin would not be knowledgeable about, it was extremely foolish for him to decide that a lesser statement was enough to unblock. As the blocking policy said at the time of the block, "Administrators reviewing a block should consider that some historical context may not be immediately obvious. Cases involving sockpuppets, harassment, or privacy concerns are particularly difficult to judge. At times such issues have led to contentious unblocks. Where an uninformed unblock may be problematic, the blocking administrator may also wish to note as part of the block notice that there are specific circumstances, and that a reviewing administrator should not unblock without discussing the case with the blocking admin (or possibly ArbCom) to fully understand the matter. '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 18:50, 5 March 2013 (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. ] ] 03:15, 3 December 2024 (UTC)
::::*The question isn't whether the unblock was foolish, but whether it was sufficiently egregious to warrant desysoping. You don't use a ] when a {{tl|trout}} will suffice. It seems like the committee was hasty and is now making up reasons after the fact. Misplaced Pages has a longstanding policy of tolerating ] as long as such foolishness is can be construed as being in good faith. <small>]</small> 19:01, 5 March 2013 (UTC)
:FWIW, I oppose splitting arbcom-en a second time -- ] <sup>]</sup> 10:17, 3 December 2024 (UTC)
* It is my opinion that blocks specifically notes as OS-related should be treated similarly to blocks specifically noted as CU-related, as both depend on restricted information, their overturning must be addressed by people with access to that information. I would also hope that abuse of this kind of blocking would be considered reason for considering warning, and eventual removal of the OS privilege from the abuser, should it not cease. -- ] (]) 18:46, 5 March 2013 (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.) ] (]) 06:08, 7 December 2024 (UTC)
** How would we possibly know an oversighter was abusing their privilege? <small>]</small> 19:01, 5 March 2013 (UTC)
::What does this mean – when was the ''first'' time? ] 15:52, 10 December 2024 (UTC)
***By forwarding potential "bad blocks" or evidence of a sequence of such behavior to AUSC, ArbCom, or the functionaries as a whole who can review the actions, and warn or take further actions against the abuser appropriately. There are close to 40 people with oversight access, and there are the ombudsmen and stewards if necessary. There are enough people to investigate the actions. -- ] (]) 19:18, 5 March 2013 (UTC)
:::@]: In 2018, arbcom-l became arbcom-en and the archives are in two different places. -- ] <sup>]</sup> 18:54, 10 December 2024 (UTC)
****Keep in mind that the stewards and ombudsmen are not necessarily part of the enwiki community, so this ensures another level of objectivity. --''']]]''' 19:21, 5 March 2013 (UTC)
****What evidence? If it's been oversighted it's gone to most of us. <small>]</small> 20:09, 5 March 2013 (UTC)
*****But the fact that ''something'' has been oversighted is still apparent. Just check the history. -- ] (]) 05:45, 6 March 2013 (UTC)
***I would not expect them to be called in at first, or hopefully at all, but they are there if necessary. The point is we have enough people to take care of problems, although it may take more than 20 minutes for an investigation to reach a conclusion. -- ] (]) 19:36, 5 March 2013 (UTC)
*Re process, it seems there is enough give in Level II to allow proceeding by motion. If that is the case the ctte would either pass a motion to resysop, or call for a case -- and the user can demand a case and/or renominate at RfA. ] (]) 20:25, 5 March 2013 (UTC)


----
*I agree with the motion as a matter of policy, both for the reasons given by the Committee and also because I consider that it is is normally a serious error by an administrator to undo a block without a thorough discussion with the blocker and, failing agreement with them, the consensus of other colleagues. This should in principle apply whether or not the block was based on private information. However, as far as I know, the Arbitration Committee has no authority to enact policies, but ''only'' to settle disputes. It therefore has the authority to desysop an administrator who lifts an oversight block, if that becomes the subject of a dispute, but it should do so only to enforce community-enacted policies. The Committee certainly has no authority to amend blocking policy '']'', bypassing the normal consensus mechanism. I consider that this motion constitutes ] and should not be passed. If it does, it should be considered only an ] in terms of policy. <small><span style="border:1px solid black;padding:1px;">]</span></small> 20:38, 5 March 2013 (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&mdash;a carefully chosen title, as opposed to something like "Chair"&mdash;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, ] (]) 01:32, 3 December 2024 (UTC)
:* I think the argument would be that it merely makes explicit what is already implicit in the blocking policy. I note that Arbcom's statement July 2010 followed a similar course of codifying an implicit convention that was already well established. ] (]) 20:49, 5 March 2013 (UTC)
:Thanks for your comments. Regarding {{tqq|1=little community appetite}}{{snd}}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, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 02:01, 3 December 2024 (UTC)
:::That's the second time in twelve hours you've posted a link to that, Prioryman, and I am still waiting for your explanation of how an ArbCom statement that only clarifies the use of the block notes ''should be reviewed only by the Arbitration Committee'' and ''should only be lifted by ArbCom'' has any connection to desysopping at all. — ] ] 22:08, 5 March 2013 (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. ] ] 03:37, 3 December 2024 (UTC)
::*But if the blocking policy already provides for this then there is no need for this motion. To be clear, I do <u>not</u> disagree with the decision reported at ] to desysop an administrator for lifting an oversight block. But the fact that the decision was made prior to this motion shows that such desysops can be founded, at least in the Committee's opinion, on previously existing policy relating to administrator conduct, which means that there is no urgent need for the Committee to attempt writing new policy. The Committee should instead have made the desysop, explained it in terms of the existing policy it applied to reach this decision, and then left it up to the community whether or not to reflect this practice in the blocking policy. <small><span style="border:1px solid black;padding:1px;">]</span></small> 20:53, 5 March 2013 (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 ] 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). ] (]) 18:01, 3 December 2024 (UTC)
:::*Well, others have said (and I agree) that there is a lack of clarity about the scope of the blocking policy. That being so, making it explicit is not actually creating ''new'' policy, it is merely clarifying and spelling out what the existing policy already provides for. An argument that it should not be policy is moot if, in fact, it is already implicit. ] (]) 21:22, 5 March 2013 (UTC)
::::* Not it's not. Because we can go change blocking policy right now. <small>]</small> 21:59, 5 March 2013 (UTC)
*'''Wiki-lawyerish note''': As there are multiple facets to a "block", I wonder what the precise language should be. Suppose an OS/CU/ARB "blocks" an account. Later a regular admin. thinks that suspending or granting the talk page privileges is best. Even later a 'Crat wishes to remove or restore email abilities. A sane "regular" admin. might be left in a quandary. Also, a '''question''' for future reference: When the Arbitration Committee uses the word "temporary" in connection with a "desysop", should we infer now that this means unless or until a successful RfA (or RFAR) is presented? (or was discussion with Kevin unsatisfactory in some way?) It's enough to drive a man to drink I tell ya. — <small><span style="border:1px solid #000000;padding:1px;"><b>]</b> : ]</span></small> 21:07, 5 March 2013 (UTC)
**Like I said above it means "until the matter is settled one way or another"; RfA or RfARs are indeed ways to settle the matter, so might simple discussion with the Committee in many cases. &mdash;&nbsp;]&nbsp;<sup>]</sup> 13:31, 6 March 2013 (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. ] <small><sup>]</sup></small> 01:49, 3 December 2024 (UTC)
*Would an arbitrator please address the concerns raised by four people here by my count (including myself) that this matter should be dealt with through the community-based processes for changing policy rather than by ArbCom motion. If you're going to invite the community to comment, you could at least attempt to address their concerns even if you have already decided to pass the motion regardless of anybody else's opinion. ] &#124; ] 17:10, 6 March 2013 (UTC)
**I read it and simply think you and the others are wrong. This is a clarification of ArbCom is going to approach already existing policy (both explicitly stated and common sense norms) in my eyes, not anything more. '''<font color="navy">]</font>''' ''(<font color="green">]</font>)'' 17:57, 6 March 2013 (UTC)
*** If the community changed the policy, then obviously the committee would follow the revised policy, correct? <small>]</small> 18:02, 6 March 2013 (UTC)
**All I can tell you is my rationale, it may not be good enough for you, but it's why I've voted the way I have and why I did not oppose because "this should be a community decision". Functionaries on wikipedia are people who have been vetted by both the community and the arbitration committee. From this, they are given certain rights, which allow them to see certain non-public information. As the community is unable to see this information, they are unable to judge based upon it and any judgement is therefore based on second hand information.<br> The arbitration committee is in a unique position to make a statement in situations like this, and if you look about, we've made it. It's unanimously agreed. Rather than complaining about the bureaucracy here, do you disagree with the substance of the change? Look elsewhere on this motions page, where we change Arbitration policy, I'm not for needless changes. This is needed and sensible. ]<sup>TT</sup>(]) 18:48, 6 March 2013 (UTC)
***You didn't change Arbitration policy, you changed Misplaced Pages policy. Which is outside of the committee's purview. So yea -- disagree. <small>]</small> 18:59, 6 March 2013 (UTC)
***What you're missing, Dave, is that this sets a precedent of ArbCom a) changing policy by motion ''and'' b) doing so to justify a decision they've already made. So what happens next time Hersfold (or any other arbitrator thinks a policy needs to be revisited? Is he going to submit it to an RfC and let the community decide? Of course not. He's going to submit it here, because now there's a precedent for ArbCom tinkering with policy on a whim. And what happens next time an admin does something that ArbCom disapproves of but is not in reach of policy? He'll be <s>hanged, drawn, and quartered</s> desysopped, and then you'll pass another motion to retrospectively justify that, and there goes any notion that this is a self-governing community. We'll have a fully fledged GovCom with sweeping powers that are whatever it says they are. This is not bureaucracy for the sake of bureaucracy (trust me, my thoughts on bureaucracy are even less flattering than my thoughts on ArbCom); it's about the most basic principles of this community.<p>Now, neither you, nor NW, nor any other arb has explained why you think it is within the gift of the Arbitration Committee (ostensibly a dispute-resolution body, though that's rapidly becoming an old joke) to create this new policy. ] says "The arbitration process is not a vehicle for creating new policy by fiat." ] &#124; ] 19:18, 6 March 2013 (UTC)
****What ''you're'' missing, Harry, is that ArbCom has ''already'' "changed policy by motion", as you put it, way back in July 2010; see . AFAIK it didn't cause any particular controversy then and I'm not aware of it being discussed on-wiki prior to ArbCom issuing that statement. The current oversight block proposal may well have had more public discussion. If you're saying that it's wrong for them to pass a motion on oversight blocks, you're saying that it was wrong for them to pass a motion on checkuser blocks three years ago; and consequently that the section on checkuser blocks in ] should be removed as procedurally invalid. Is that what you're saying? Because that's the logic of your argument. ] (]) 20:45, 6 March 2013 (UTC)
*****That's the ''third'' time you've posted that link to this page, Prioryman, and have yet to answer my question posed to you twice above how it justifies the punishment of desysopping handed out to Kevin. Look, I'm going to quote it for you.
*****:{{tq|{{smaller|The Arbitration Committee has also noted that some administrators (other than Checkusers) have occasionally noted when making certain blocks that the block "should be reviewed only by the Arbitration Committee" or "should only be lifted by ArbCom." This notation is appropriate only when the block is based upon a concern that should not be discussed on-wiki but only in a confidential environment. Bases for such a concern could include information whose disclosure would identify anonymous users, could jeopardize a user's physical or mental well-being, or where the underlying block reason would be defamatory if the block proved to be unjustified. In every such case, the Arbitration Committee should be notified immediately by e-mail of the block and of the reasons for it. The designation "block should be reviewed only by ArbCom" should not be used simply to indicate that administrator feels strongly about the block. Where an administrator is unsure, he or she should feel free to email the Arbitration Committee mailing list before blocking.}}}}
*****See that? Not one word about what should happen if an unblocking administrator ignores such a request in a block log. Stop dissembling. Or is it your position now that this only justifies ArbCom altering policy by itself? — ] ] ] 21:03, 6 March 2013 (UTC)
******For goodness' sake, calm down - I'm not dissembling. No, ArbCom didn't specify a penalty in its July 2010 statement, but that's missing the point. ArbCom already has a long-standing policy that says " may be used if (a) the account's behaviour is inconsistent with the level of trust required for its associated advanced permissions, and (b) no satisfactory explanation is forthcoming." This gives ArbCom the right to desysop ''any'' arbitrator for ''any'' action that, in its judgement, "is inconsistent with the level of trust required". Note that Kevin wasn't desysopped under the terms of ]; the desysop motion (see ]) says explicitly "Kevin is temporarily desysopped '''in accordance with Level II procedures for removing administrative tools'''" (i.e. ]) (my bolding for emphasis). IOW, ArbCom doesn't need to specify a penalty in relation to WP:BLOCK - it's already covered by long-standing ArbCom procedures. ] (]) 21:15, 6 March 2013 (UTC)
*******So you are saying that ArbCom has written itself a blank check to desysop anyone, at any time, based on no public evidence, and a "level of trust" that is defined nowhere, if that person has dared to contravene this non-policy that has been enacted by fiat. And you're cool with that. Even though the "procedures" you link to explicitly state that {{tq|Removal is protective, intended to prevent harm to the encyclopedia}}. That means that such a removal is a de facto declaration of the admin being a danger to the project. ArbCom acting as judge, jury and executioner. Wonderful. Just wonderful. — ] ] ] 21:27, 6 March 2013 (UTC)
******* Incidentally, those procedures also state that {{tq|Once removal has been approved, an arbitrator will (a) directly request removal from a steward, (b) make a formal statement on the ] to confirm that the request is based on the authority of the Committee, and (c) post a notice...}} - oh yeah? Where is that formal statement? Hint, there isn't one. Either the ArbCom don't know their own procedures; the procedures contain outdated material that nobody has ever bothered to even remove (the requirement for such a statement); or ArbCom were in such a hurry to <s>wave their dicks around</s>flex their muscles that they simply forgot to fully comply with them. ''Great job.'' — ] ] ] 21:35, 6 March 2013 (UTC)
********Yes, ArbCom can desysop anyone, at any time, and it doesn't need public evidence to do so (though in this case there was ample public evidence in that Kevin's actions were in full public view). I really don't know why you're so shocked/surprised at this - it's been the case for a long time. The procedures I just cited were implemented four years ago. If you want to be blunt about it, the only criterion that really matters for any admin is having the trust of ArbCom. If you lose that, you're toast. ] (]) 23:10, 6 March 2013 (UTC)


{{ping|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, ] (]) 03:49, 4 December 2024 (UTC)
****{{ec}}Ah, but if you're talking about precedent, there's already some, it's mentioned in the motion, the statement on Checkuser blocks. This is an extension of that, and firming up a scenario of something that is already stated by policy - don't undo a block if you cannot be aware of all the details. You are complaining that we're not following bureaucracy and that argument is just not going to wash with me. I'm sure that an RfC can be called regarding the change if someone wants to do it, and if the community disagrees with the decision that would set an interesting precedent. In my head, the consensus should over-rule ArbCom. <br> As for "doing so to justify a decision", I stated on the decision that the committee made, so there's not much more I can say on it. However, I will say that "policy reflects the situation, not vice versa", Arbcom's <s>block</s><u> action</u> was within policy, even if it wasn't explicitly stated in the text. ]<sup>TT</sup>(]) 20:50, 6 March 2013 (UTC)
:Or "cat-herder". --] (]) 00:18, 5 December 2024 (UTC)
******"already stated by policy - don't undo a block if you cannot be aware of all the details" -- gotta a link for that? <small>]</small> 21:00, 6 March 2013 (UTC)
:Following parliamentary tradition, perhaps "whip". (Less whimsically: "recording secretary".) ] (]) 00:31, 5 December 2024 (UTC)
*******Certainly. From ]. {{xt|An uninvolved administrator acting independently reviews the circumstances of the block, the editor's prior conduct, '''and other relevant evidence''', along with any additional information provided by the user and others, to determine if the unblock request should be accepted.}} Highlighting my own. ]<sup>TT</sup>(]) 21:08, 6 March 2013 (UTC)
:{{yo|Newyorkbrad}}, if memory serves {{yo|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. ] ] 05:03, 10 December 2024 (UTC)
********"all other relevant evidence" &ne; "all the details." Whether or not knowing that an editor posted doxing information without knowing the actual content of the infraction is sufficient to meet the "relevant" criteria to evaluate an unblock request -- distinct from "reversing" an inappropriate block-- is a matter of opinion. Determining that should be a matter for the community through the consensus model not ac through fiat. <small>]</small> 21:18, 6 March 2013 (UTC)
********:If an oversighter makes a block, based on a comment they have oversighted and then takes the trouble to say "don't unblock without talking to an oversighter", that is clearly relevant information. Which takes us back to the point I was making, this is already policy. It fits squarely under ''The Committee's decisions may interpret existing policy and guidelines, recognise and call attention to standards of user conduct, or create procedures through which policy and guidelines may be enforced''. If you have a problem with a ''particular scenario'', for example blocking based on doxing, we have an audit subcommittee. For the general case, I stand by my statements. ]<sup>TT</sup>(]) 21:27, 6 March 2013 (UTC)
*********:(In this case oversighters had participated in the user talk page discussion, so that requirement was meant, maybe.) Like (almost) everything else around here, it's more shades of gray than black and white. At some point "interpreting" becomes "making it up." If everything the committee has done here is so clearly in alignment with policy, why are you bothering with the motion? The fact that you're making a motion is spinning the policy to something that maybe it didn't quite say at the time. <small>]</small> 21:51, 6 March 2013 (UTC)
*********::It's a statement for clarification to help reduce future confusion. ]<sup>TT</sup>(]) 21:56, 6 March 2013 (UTC)
********(e/c) Hmm? According to the arbitration policy, Arbitrators acting as a committee in charge of binding determinations related to desysopping and privacy related issues: "may interpret existing policy and guidelines, recognise and call attention to standards of user conduct, or create procedures through which policy and guidelines may be enforced." So, one would gather that's why this decision is their unanimous opinion of that. -- ] (]) 21:39, 6 March 2013 (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. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 06:56, 6 December 2024 (UTC)
*'''Key point''' If we're going to have a separate class of blocks that are NOT actionable by "regular" admins, then we need SPECIFIC blocking templates and common block-log entries that emphasize this point. Make up {{tl|uw-oversightblock}} and {{tl|uw-checkuserblock}} that are used in these specific situations. The standard unblock instructions would ''not'' appear - there would unique ones, and it would basically clearly say "admins - do not unblock". Likewise, templated blocking reasons that the blockee would see when they try to edit would emphasize the same point (]''']''']) 17:47, 6 March 2013 (UTC)
**That's a good point, though I should say those templates should concentrate on communication with the blocked user (i.e.: venues for appeal, etc). The block log is already there to inform admins &ndash; not to say that we can't duplicate some notes in the uw- too. &mdash;&nbsp;]&nbsp;<sup>]</sup> 20:08, 6 March 2013 (UTC)
***Why is this such a point of contention? It's not difficult to make a template, it's not an undue burden on the oversighter to use it, and it's an easy way to give a heads-up to both the user (who might otherwise try to email an uninvolved admin) and the admin.--]&nbsp;&#124;&nbsp;<sup>]</sup>✌ 22:59, 6 March 2013 (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):
*Let's get this straight: the committee is passing a motion which effectively makes a major modification to the blocking policy covering blocks made by certain people who are appointed by the committee. Am I missing something? --]&nbsp;&#124;&nbsp;<sup>]</sup>✌ 22:59, 6 March 2013 (UTC)
:* Daily, ~20 minutes: went into the list software and tagged the day's incoming new email chains with a label (think "upe", "duplicate", etc).
**Yes, the ''minor'' detail that there is, in fact, no modification to the blocking policy. It's a little sad that we have to spell out what was already clear &ndash; as we had to do with checkuser blocks in the past &ndash; because some people seem to think that "Cases involving sockpuppets, harassment, or privacy concerns" mysteriously does not include oversight. &mdash;&nbsp;]&nbsp;<sup>]</sup> 06:01, 7 March 2013 (UTC)
:* 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.) ] (]) 08:48, 6 December 2024 (UTC)
::The original announcement of the Coordinating Arbitrator position was ]. Regards, ] (]) 21:29, 6 December 2024 (UTC)
:::Archive zero: I love it! --] (]) 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. ] (]) 23:23, 6 December 2024 (UTC)
::::{{tq|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: {{tq|the Arbitration Committee has decided to appoint one of its {{em|sitting}} arbitrators to act as coordinator}} (emphasis mine). ] (]) 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 {{section link|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. ] (]) 00:01, 7 December 2024 (UTC)
::::::Oh, I see that now. ] (]) 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. ] (]) 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. ] ] 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. ] (]) 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.) ] (]) 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. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 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. ] (]) 04:02, 7 December 2024 (UTC)
::You made me laugh, {{u|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. ] (]) 04:43, 7 December 2024 (UTC)
:::+1. In my ] I said an hour a day for emails but that included far more appeals than the committee gets now. Best, ] (]) 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. ] (]) 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. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 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, ] (]) 16:26, 7 December 2024 (UTC)

Latest revision as of 15:01, 27 December 2024

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

Motions

Shortcuts

This page 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 15:01, 27 December 2024 (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)