Revision as of 03:00, 3 June 2012 view sourceLord Roem (talk | contribs)Autopatrolled, Administrators10,811 edits →Motion on decision elements: enacted← Previous edit | Latest revision as of 12:56, 24 December 2024 view source Cabayi (talk | contribs)Edit filter managers, Autopatrolled, Checkusers, Oversighters, Administrators142,159 edits →Motion 2: WMF staff support: opp | ||
Line 1: | Line 1: | ||
<noinclude>{{ArbComOpenTasks}}</noinclude> | <noinclude>{{pp-semi-indef|small=yes}}{{ArbComOpenTasks}}</noinclude> | ||
= |
=<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 ==== | |||
=== Motion #1 === | |||
{{ARCAImplNotes | |||
In order to ensure that the wider community is given adequate notice of and opportunity to comment on proposed changes to the Arbitration Committee's processes and procedures, the following procedure is adopted: | |||
|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 === | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
; Nine-month trial | |||
; Modification of procedures | |||
{{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. | |||
All significant changes to the Arbitration Committee's procedures shall be made by way of formal motions on the Committee's ], and shall be advertised on the ], the ], and the ] when first proposed. The motions shall remain open for a period of no less than one week, and shall otherwise be subject to the standard voting procedures enacted by the Committee for other motions. | |||
</div> | |||
The specific responsibilities of correspondence clerks shall include: | |||
==== Votes ==== | |||
* 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: | |||
; Support | |||
* Participating in the substantive consideration or decision of any matters before the Committee; or | |||
:# Proposed, based on recent concerns that we're not providing sufficient opportunity to comment on proposed changes before they're enacted. ] <sup>]]</sup> 21:43, 27 May 2012 (UTC) | |||
* Taking non-routine actions requiring the exercise of arbitrator discretion. | |||
:# I request you change "all changes" to "all significant changes", to exclude unimportant fixes and changes from the transparency requirement this motion creates. ] ]] 12:09, 28 May 2012 (UTC) | |||
:#: Changed as requested. ] <sup>]]</sup> 12:12, 28 May 2012 (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. | |||
; Oppose | |||
:# Having slept on this, I cannot support this in its present form. It is a sweeping measure, with very broad unintended consequences. As drafted, this requires a formal motion, advertised in three locations, and up for a week, to make a non-controversial copy edit to a procedural template, to make a non-controversial redirect to a better location, or to modify the precise sequence or number of procedural steps clerks take in opening cases etc etc. This runs directly counter to ]. ] <sup>]</sup> 09:34, 28 May 2012 (UTC) | |||
:#: Is the change to "significant changes" requested by AGK sufficient to allay your concern regarding the sweeping nature of the motion? ] <sup>]]</sup> 12:15, 28 May 2012 (UTC) | |||
:#:: No, because the unqualified expression "processes" is also overbroad. Pre-announcing '''everything''' in three locations is also OTT. To put this into perspective, the evidence length proposals were up for seven weeks and reported in Signpost on 9, 16, 23 and 30 April, and in Open Tasks for the duration. Which does not seem to me to be hiding anything away. ] <sup>]</sup> 12:27, 28 May 2012 (UTC) | |||
:#::: Interesting; I wasn't considering the preliminary recitations to be material. Generally speaking, do you think that they should be interpreted that way? ] <sup>]]</sup> 12:31, 28 May 2012 (UTC) | |||
:#:::: It's probably responsible to assume that people will interpret this in the light most favourable to whatever their position happens to be as that's normally how people operate. Best therefore to pin it down. ] <sup>]</sup> 12:45, 28 May 2012 (UTC) | |||
:# I understand the impetus for this motion but I do not believe it is necessary. The Committee has pledged before, and should reaffirm, that it will seek community input on significant changes that will affect the relationship between the Committee and its constituents, including all aspects of the editor community. This does not, however, mean that every change in process, or even every "significant" change in process, requires a week's worth of advertising in three different places. I am particularly concerned that giving undue weight to relatively minor changes that may occur to our processes over time may have the effect of diminishing the attention given to more significant issues, both ones involving this Committee and others. Or put more simply, I favor motion #2. ] (]) 14:41, 29 May 2012 (UTC) | |||
:# Per those above me, favor motion #2. ] (]) 12:44, 30 May 2012 (UTC) | |||
:# Oppose for the same reason as opposing motion #2 ] (]) 17:13, 30 May 2012 (UTC) | |||
:# Not convinced on motion 2, but it is clearly superior to this one. ] 17:50, 30 May 2012 (UTC) | |||
:# Oppose, per Roger above and Risker below ] (]) 21:09, 31 May 2012 (UTC) | |||
:# Oppose as overly bureaucratic. ] (] '''·''' ]) 05:37, 1 June 2012 (UTC) | |||
:# ''']''' ''']''' 17:18, 2 June 2012 (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. | |||
; Abstain | |||
:# | |||
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. | |||
==== General discussion ==== | |||
</blockquote> | |||
'''Oppose''' Per not bureaucracy. We're getting in a tizzy because clarifications and amendments get merged? Whether a ''Hey ArbCom, you didn't quite get it right, please fix this'' process is called amendment / clarifications / have a ] is just so not important. <small>]</small> 00:13, 28 May 2012 (UTC) | |||
}} | |||
:While I happen to agree that the particular change that spurred this discussion was a fairly trivial one, I think the request that we be more consistent in soliciting community input is a reasonable one in and of itself, regardless of which specific change we neglected it for. | |||
<!-- change the number depending on active count --> | |||
:Beyond that, my intent is not only to provide more transparency to the process, but also to create a defined place for decisions on procedure to be made in the first place; at the moment, the Committee can hold such discussions in a variety of places, making it rather difficult to follow them at times. ] <sup>]]</sup> 01:01, 28 May 2012 (UTC) | |||
{{ACMajority|active=10|motion=yes}} | |||
::Nobody Ent, you are right, but it is a slippery slope - where is the limit. I fully endorse this change - it does not necessarily change the basics, but it does somewhat improve the transparency (something I have been asking for a long time). ''IF'' something is proposed by the ArbCom that the community would then massively oppose against, then at least that is seen - even the members of the ArbCom are only human. I presume that the motion about merging the Amendments and Clarifications pages would have passed without opposition, only some questions, concerns or suggestions which may have made the actual transition even smoother. --] <sup>] ]</sup> 05:48, 28 May 2012 (UTC) | |||
;Support | |||
:Agree whole heartedly that this particular change was minor, and had I not been editing the page simultaneously to the merge would probably never have been brought up. But anything to improve transparency and accountability is good. ''] ]'', <small>02:41, 29 May 2012 (UTC).</small><br /> | |||
# 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 | |||
=== Motion #2 === | |||
# 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) | |||
;Abstain | |||
To provide an opportunity for community comment on proposed changes to the Arbitration Committee's processes and procedures prior to enactment, the following procedure is adopted: | |||
# | |||
<!-- | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
;Arbitrator discussion | |||
; Modification of procedures | |||
--> | |||
==== 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 ] (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) | |||
*: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) | |||
*::@]: 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) | |||
*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) | |||
*:Whimsy is important -- ] <sup>]</sup> 08:55, 4 December 2024 (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) | |||
* 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) | |||
{{reflist-talk}} | |||
====Motion 1.1: expand eligible set to functionaries ==== | |||
Significant or substantive modifications of the ] shall be made by way of formal motions on the Committee's ], and shall be announced on the ] by the clerks when first proposed. Such motions shall remain open for at least one week prior to enactment; otherwise, the Committee's standard voting procedures apply. | |||
{{hat|1=If any arbitrator prefers this way, unhat this motion and vote for it.}} | |||
{{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 | |||
</div> | |||
# | |||
;Oppose | |||
==== Votes ==== | |||
# | |||
; Support | |||
:# Alternative to the ] above, and addressing my objections to that motion. ] <sup>]</sup> 09:35, 28 May 2012 (UTC) | |||
:#: The major and lingering remaining concern that I have about this is the seven-day provision, which has been highlighted by recent events. A lot of stuff whistles through in less than a day or two; and may often be time-sensitive because we want to apply it to an upcoming case. Delaying the opening of a case by say five or six days for process sake is likely to antagonise a lot of people, ] <sup>]</sup> 18:17, 30 May 2012 (UTC) | |||
:# Works for me. ] <sup>]]</sup> 12:06, 28 May 2012 (UTC) | |||
:# ] (]) 22:47, 28 May 2012 (UTC) | |||
:# This is acceptable as long as "significant or substantive" is interpreted in a reasonable way, which I guess is something that will play out over time. Re the comment that the ArbCom noticeboard is watched less than some other pages, I think passage of this motion would be fair notice that people interested in monitoring for potential changes in our procedure should watchlist that page. ] (]) 14:44, 29 May 2012 (UTC) | |||
:#: <s>Second choice to Motion #1. ] ]] 16:55, 29 May 2012 (UTC)</s> | |||
:#:*Change to oppose. ] ]] 13:43, 1 June 2012 (UTC) | |||
:# ] (]) 12:44, 30 May 2012 (UTC) | |||
:# While I see Risker's point, I think that any rule can be wikilawyered to death but I think there's ample room for sound judgement. <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 22:33, 30 May 2012 (UTC) | |||
;Abstain | |||
; Oppose | |||
# | |||
:# I am quite certain that there will be plenty of people who will insist that any change whatsoever is "significant or substantive", even if it is making a grammar correction. ("But you changed the meaning by fixing the words!!!") Things we have motions for, I'm fine for discussing publicly onwiki and posting on the noticeboard. However, this requires lengthy deliberations even for going forward with a trial of something a little different. I don't think we need 7 days to discuss the majority of even substantive changes. ] (]) 17:12, 30 May 2012 (UTC) | |||
:# Per Risker. ] (]) 17:38, 30 May 2012 (UTC) | |||
:# Per Risker. I'm in favour of opportunities for community input, but not if the only input is wikilawyering. ] (]) 21:10, 31 May 2012 (UTC) | |||
:# Oppose as overly bureaucratic and arbitrary. Some discussions take longer, some take shorter. If folks are open and engaging, I think this is unnecessary and overly formalises interactions with the community at large. ] (] '''·''' ]) 05:37, 1 June 2012 (UTC) | |||
:# On reflection, I am not sure that it is sensible or necessary to impose on ourselves a one-week minimum period of exposure for motions, even considering our absolute discretion over whether to ignore or adapt procedures in a given case. ] ]] 13:43, 1 June 2012 (UTC) | |||
:#The point should be, "hold our procedural discussions here" not "wait a week to pass anything". A mandatory holding period of this long is too bureaucratic. ] 13:50, 1 June 2012 (UTC) | |||
:# ''']''' ''']''' 17:18, 2 June 2012 (UTC) | |||
:# | |||
<!-- | |||
==== General discussion ==== | |||
;Arbitrator discussion | |||
* Of the three pages in the initial proposal Misplaced Pages:Arbitration Committee/Noticeboard has far less watchers than the other two. AC/N has to AN's and VPP's . In a project with less than 10,000 highly active users, you are dealing in huge percentage differences. I'm not sure if your intent is to actually increase transparency or just to make a feint and point to it next time people complain, but with this motion you're doing a much better job of the second than you are the first. ] ] 14:10, 28 May 2012 (UTC) | |||
--> | |||
* I'm actually mindful of the complaints we've had in the past about focusing on procedure when we've posted this stuff publically. How much transparency does whether Amendments and Clarifications are on one page or two need? ] <sup>]</sup> 14:23, 28 May 2012 (UTC) | |||
**If the objective is to inform the community, you're going to have to break from Arbspace. The people who are complaining are most likely not watching the AN/C. The people watching AN/C are already involved enough that they'd be in the loop anyways. ] ] 17:16, 28 May 2012 (UTC) | |||
***Sven is absolutely right. There are still people like me who will remain in blissful ignorance most of the time, being too busy running bots and editing protected templates, but with those pages you will at least get about 3-5% of the active editors, and probably a good chunk of those who can make useful contributions. ''] ]'', <small>02:53, 29 May 2012 (UTC).</small><br /> | |||
*I don't care about the procedural details, but the idea of Arbcom requiring itself to give notice of substantial changes is a great one in my mind. I likely won't pay attention, because arbitration is really something I've ignored most of the time, but it will definitely help those who care more about it. Typos and other things definitely don't need to get prior notice; we're not where everything requires votes first. ] (]) 12:04, 29 May 2012 (UTC) | |||
*I also agree this is a good step in the right direction and also agree that the notice should be somewhere, like a village pump, that folks are actually likely to see it. ] (]) 17:37, 30 May 2012 (UTC) | |||
{{hab}} | |||
=== Motion #3 === | |||
==== Motion 1.2a: name the role "scrivener" ==== | |||
To provide an opportunity for community comment on proposed changes to the Arbitration Committee's processes and procedures prior to enactment, the following procedure is adopted: | |||
{{ivmbox|1=If motion 1 passes, replace the term "correspondence clerks" wherever it appears with the term "scriveners".}} | |||
{{ACMajority|active=10|motion=yes}} | |||
;Support | |||
#Nicely whimsical, and not as likely to be confusing as correspondence clerk. ] <sup>]</sup>] 04:11, 7 December 2024 (UTC) | |||
;Oppose | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
# 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) | |||
; Modification of procedures | |||
# 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) | |||
;Abstain | |||
Significant or substantive modifications of the ] shall be made by way of formal motions on the Committee's ]; shall be announced on the ] and the ] by the clerks when first proposed; and shall remain open for at least 24 hours after those announcements are made. | |||
# 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 | |||
</div> | |||
==== Motion 1.2b: name the role "coordination assistant" ==== | |||
==== Votes ==== | |||
{{ivmbox|1=If motion 1 passes, replace the term "correspondence clerks" wherever it appears with the term "coordination assistants".}} | |||
; Support | |||
{{ACMajority|active=10|motion=yes}} | |||
:#Okay, the core idea here is a good one, but it doesn't take anywhere near a week to get the community's input. Sorry to propose another motion at this late date, but I just can't get behind a week's waiting period above. A day gives the community plenty of time to object, without stretching into days of silence. ] 14:10, 1 June 2012 (UTC) | |||
;Support | |||
:# Fair enough. ] <sup>]]</sup> 14:22, 1 June 2012 (UTC) | |||
# | |||
:# Better. ] ]] 14:48, 1 June 2012 (UTC) | |||
:# ] <sup>]</sup> 21:35, 1 June 2012 (UTC) | |||
:# I can live with this. ] (]) 02:37, 2 June 2012 (UTC) | |||
:# ''']''' ''']''' 17:18, 2 June 2012 (UTC) | |||
:# | |||
; |
;Oppose | ||
# bleh. ] <sup>]</sup>] 04:12, 7 December 2024 (UTC) | |||
:# | |||
; |
;Abstain | ||
# 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 | |||
:How about "Significant or substantive modifications of the Arbitration Committee's procedures, as assessed by the committee itself, shall ..." ] (]) 02:14, 2 June 2012 (UTC) | |||
:: Or simpler: "Modifications of the Arbitration Committee's procedures that the Committee determines are significant or substantive shall be made etc etc", ] <sup>]</sup> 02:25, 2 June 2012 (UTC) | |||
A word of warning here. A day is not really enough time both for significant changes to be advertised and for public discussion to conclude (many people, including some arbs, may miss a few days here and there, so the unit of a week works best for most discussions). Trivial changes, I agree, shouldn't need bureaucracy, but the "days of silence" referred to above usually only occur when trivial changes are proposed. When something that objections are raised to is proposed, is a day enough time to assess opposition to it and whether the proposal needs to be withdrawn or reworked? The above will only work if any discussion that arises is allowed to ''continue'' for more than a day after a change is proposed. What something like this will need is arbitrators to exercise judgement on whether to close a proposal after a day of no input, or whether to allow discussion to continue for as long as needed, followed by the proposal being reworked. Or thanking people for their input but going ahead anyway (which may be needed at times, but will always irk some). Best to make a named someone (an arbitrator, not a clerk) responsible for any discussion that ensues and what to do afterwards, preferably the arbitrator who drafted or proposed the change in the first place.<p> What is also not clear is whether this advertising period of a day takes place before a public vote by arbitrators or is just a required period of notice following an internal (possibly informal) vote that passed the proposal. If you are advertising a public arb vote on a proposed change, this works less well if people turn up and find the arbs have all voted publicly already within minutes or hours of the proposal going up (something that is intensely annoying - why ask for input and then vote before any input arrives?). Also, beware of arbitrators proposing alternative wording that substantially changes the nature of the proposal, and that wording passing without the required 24-hour notice period, or any updates being made to the notice.<p> I would suggest a day of something being proposed with no voting by taking place (that is something clerks can enforce as arbitrators, being very busy and all that, tend to forget things like this), and then voting starts with input from any public discussion that may or may not have started. But really, the judgement starts at the point of deciding whether something is a trivial change, or a 'significant or substantive' change. Good luck with that. ] (]) 06:30, 2 June 2012 (UTC) | |||
== Motion |
==== Motion 1.3: make permanent (not trial) ==== | ||
{{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}}.}} | |||
{{ACMajority|active=10|motion=yes}} | |||
To provide greater clarity regarding the purpose of each element of an arbitration decision, the following statement is adopted: | |||
;Support | |||
# | |||
;Oppose | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
# 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) | |||
; Elements of arbitration decisions | |||
# 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) | |||
For standard hearings, decisions are posted in the form of "Principles", "Findings of Fact", "Remedies" and "Enforcement". | |||
# ] (]) 19:10, 14 December 2024 (UTC) | |||
Principles highlight key provisions of policy, procedure, or community practice which are relevant to the dispute under consideration; and, where appropriate, include the Committee's interpretation of such provisions in the context of the dispute. | |||
Findings of fact summarize the key elements of the parties' conduct in the dispute under consideration. Difference links may be incorporated but are purely illustrative in nature unless explicitly stated otherwise. | |||
Remedies specify the actions ordered by the Committee to resolve the dispute under considerations. Remedies may include both enforceable provisions (such as edit restrictions or bans) and non-enforceable provisions (such as cautions, reminders, or admonitions), and may apply to individual parties, to groups of parties collectively, or to all editors engaged in a specific type of conduct or working in a specific area. | |||
Enforcement contains instructions to the administrators responsible for ], describing the procedure to be followed in the event that an editor subject to a remedy violates the terms of that remedy. Enforcement provisions may be omitted in decisions that contain no independently enforceable remedies. | |||
</div> | |||
Additionally, the ] is modified to replace the first sentence ("For standard hearings, proposed decisions will be posted in the form of 'Principles', 'Findings of Fact', 'Remedies' and 'Enforcement', with a separate vote for each provision.") with the following: | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
Proposed decisions will be posted with a separate vote for each provision. | |||
</div> | |||
*<s>Will be '''enacted''' at 5:30, 1 June 2012 (UTC) if there are no further changes to voting or the text of the motion. -- ] (]) 04:38, 1 June 2012 (UTC)</s> | |||
**Please hold until 17:30, 1 June 2012 (UTC) to allow final changes, ] <sup>]</sup> 04:54, 1 June 2012 (UTC) | |||
***Will be '''enacted''' at 3:00, 3 June 2012 (UTC). If any arbitrators are still working on final changes (as mentioned above), please strike this comment. -- ] (]) 03:00, 3 June 2012 (UTC) | |||
=== Votes === | |||
; Support | |||
:# Proposed. It's been suggested that the existing ] is rather vague as to what constitutes each part of the decision; this attempts to remedy that. ] <sup>]]</sup> 13:27, 28 May 2012 (UTC) | |||
:# . Revert if you disagree. ] <sup>]</sup> 13:48, 28 May 2012 (UTC) | |||
:#: That looks fine to me. ] <sup>]]</sup> 13:56, 28 May 2012 (UTC) | |||
:# ] (]) 14:14, 28 May 2012 (UTC) | |||
:# ] (]) 16:23, 28 May 2012 (UTC) | |||
:# ] (]) 18:03, 28 May 2012 (UTC) | |||
:# The motion is generally acceptable to me although I am not certain it is necessary. I do have one reservation: a diff link in a finding can be other than "strictly illustrative" without this being being "expressly designated". If a decision reads "Foo has been uncivil " then those links are illustrative; but if the decision reads "on May 29, 2012, Foo was uncivil in a comment to Bar " then it is not "illustrative" but specific. A more straightforward way to reflect when diffs are "purely illustrative" would be to precede lists of illustrative diffs by "e.g." or the like, rather than allay confusion by pointing to a policy page. Also a proposed copyedit (about which arbitrators have had friendly disagreements before): I believe the word "admonition" is much more common than "admonishment". ] (]) 14:50, 29 May 2012 (UTC) | |||
:#: In practice, though, almost all diffs cited in findings are indeed illustrative; specific diffs are the exception rather than the rule, because specific findings are far rarer than general "pattern of conduct" ones. Given that, I think it would make sense to have the illustrative interpretation be the default, and the specific interpretation to require some conscious action on our part. ] <sup>]]</sup> 22:14, 30 May 2012 (UTC) | |||
:#:: I concur with Kirill here. Can we find language that succinctly reflects this?<p>No problems here about the proposed "admonition" change. (Later: which I've made.) ] <sup>]</sup> 02:59, 31 May 2012 (UTC) | |||
:#:: @ Brad: As illustrative diffs are far more common than probative diffs, and as they are frequently preceded with "(Examples: , )" or similar, I don't have too much trouble with illustrative being the default. In the example, you give - "on May 29, 2012, Foo was uncivil in a comment to Bar " it only needs the diff to be piped "Foo was uncivil in " or even "Foo was uncivil in this comment to Bar" to make it explicitly specific. ] <sup>]</sup> 05:15, 1 June 2012 (UTC) | |||
:# ] ]] 16:55, 29 May 2012 (UTC) | |||
:# ''']''' ''']''' 12:33, 30 May 2012 (UTC) | |||
:# ] 17:47, 30 May 2012 (UTC) | |||
:# ] (] '''·''' ]) 20:04, 30 May 2012 (UTC) | |||
:# <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 22:33, 30 May 2012 (UTC) | |||
:# I think I'm OK with this - it seems a lot of words for a relatively small - but highly focused - change. In an email I received recently, someone used the phrase 'whack his winkle' instead of 'admonish'. Suggest employing this as a measure of moving away from quasi judicial speak. ] (]) 21:16, 31 May 2012 (UTC) | |||
; Oppose | |||
:# | |||
; Abstain | |||
:# Not really convinced this is needed, but don't object in principle to it. However, I do not think it is really ready for "prime time" until we sort out the issues raised by NYB with respect to diffs, which is a substantive issue in my mind. ] (]) 17:19, 30 May 2012 (UTC) | |||
=== General discussion === | |||
* This starts off by talking about ''proposed'' decisions, and then appears to relate to final decisions without making the distinction clear. That an individual member of the Committee has proposed an interpretation of policy doesn't follow that it is a Committee interpretation until there is a consensus in the Committee for the proposed interpretation. If the intention of this motion is to refer to proposed decisions only, then I cannot support; if the intention is to talk about both proposed and final decisions, then that needs to be made clearer before I can support. ''']''' ''']''' 16:54, 28 May 2012 (UTC) | |||
*: The intent was, indeed, to describe the final end product rather than delving into the drafting process; I've the text to clarify that. Does the change address your concern? ] <sup>]]</sup> 17:04, 28 May 2012 (UTC) | |||
*:: I was thinking earlier that this would probably work better in the present tense i.e. "decisions are posted in the form of 'Principles', 'Findings of Fact'" (instead of "decisions will be posted" etc) as that is the usual way of expressing general principles. If no one objects, this can still be done. ] <sup>]</sup> 19:21, 28 May 2012 (UTC) | |||
*::: I have now put this into the present tense, Revert if you hate it. ] <sup>]</sup> 02:02, 29 May 2012 (UTC) | |||
*:::: I'm not sure I see any substantive difference, but I have no objection to it either way. ] <sup>]]</sup> 12:12, 29 May 2012 (UTC) | |||
;Abstain | |||
== Motion on standardized enforcement == | |||
# 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) | |||
;Arbitrator discussion | |||
To provide for standardized enforcement of editing restrictions imposed by the Committee, and to reduce the amount of boilerplate text in decisions, the following procedure is adopted, and shall apply to all cases closed after its adoption: | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
; Standard enforcement provision | |||
==== Motion 1.4: expanding arbcom-en directly ==== | |||
The following standard enforcement provision shall be incorporated into all cases which include an enforceable remedy but which do not include case-specific enforcement provisions passed by the Committee: | |||
{{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: | |||
:"Should any user subject to a restriction in this case violate that restriction, that user may be blocked, initially for up to one month, and then with blocks increasing in duration to a maximum of one year. Appeals of blocks may be made to the imposing administrator, and thereafter to ], or to the Arbitration Committee. All blocks shall be logged in the appropriate section of the main case page." | |||
<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> | |||
</div> | |||
}} | |||
{{ACMajority|active=10|motion=yes}} | |||
=== Votes === | |||
; |
;Support | ||
# Much less trouble to have them on the main list than to split the lists. ] <sup>]</sup>] 04:13, 7 December 2024 (UTC) | |||
:# Proposed. We've discussed having a standard enforcement provision in just about every case over the past few months, since we inevitably just repeat the boilerplate; this wording appears to be the form that we typically use. ] <sup>]]</sup> 13:27, 28 May 2012 (UTC) | |||
:# Go for it, ] <sup>]</sup> 13:51, 28 May 2012 (UTC) | |||
:# ] (]) 14:19, 28 May 2012 (UTC) | |||
:# Since this is update-our-procedures-to-reflect-reality week, this is pretty high on my list. We've had closes delayed for no better reason than a topic ban was added late, and then an enforcement had to be added on later and voted on appropriately. ] (]) 16:25, 28 May 2012 (UTC) | |||
:# Yes. ''']''' ''']''' 16:45, 28 May 2012 (UTC) | |||
:# ] (]) 01:52, 29 May 2012 (UTC) | |||
:# ] ]] 16:52, 29 May 2012 (UTC) | |||
:# Like NYB, though, this should be placed on the final case page if it applies, so everyone is clear. ] 14:09, 30 May 2012 (UTC) | |||
:# Given the response to my comment I will support, though I'd still welcome some discussion of the initial maximum block length. ] (]) 15:23, 30 May 2012 (UTC) | |||
:#: How about replacing "initially for up to one month, and then with blocks ..." with "initially for between one day and one month, depending on the circumstances, and then with blocks ..."? This makes it abundantly clear that admins are expected to exercise judgment on the duration, rather than dishing out a standard one month block. ] <sup>]</sup> 05:05, 1 June 2012 (UTC) | |||
:# Support provided that it is actually placed on all decisions AND we have a method for declaring that this standard provision does not apply in a specific case. I don't think it is to the project's benefit for us to be inflexible. ] (]) 17:22, 30 May 2012 (UTC) | |||
:#:As the motion says, "Unless explicitly stated otherwise in a particular decision". In order to revise something for a specific case, all that would need be done is pass an enforcement provision disagreeing with this one, which would control that case. It wouldn't hurt to add a line like "This enforcement provision shall be placed on the final case page of all cases where the Committee has not passed a different enforcement provision in that case" though to make this expectation clear instead of being forgotten about in these votes. ] 17:31, 30 May 2012 (UTC) | |||
:#:: Perhaps add something alomg those lines as a copy-edit? In the unlikely event it's reverted we can always discuss further. ] <sup>]</sup> 18:29, 30 May 2012 (UTC) | |||
:#::: . Revert or copy-edit further as needed. ] 18:51, 30 May 2012 (UTC) | |||
:#::::Made simpler. ] 19:28, 30 May 2012 (UTC) | |||
:#:::::And even simpler. ] <sup>]]</sup> 22:16, 30 May 2012 (UTC) | |||
:#:::::: And . Revert if you disagree, ] <sup>]</sup> 03:10, 31 May 2012 (UTC) | |||
:# <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 22:33, 30 May 2012 (UTC) | |||
:# ] (]) 21:06, 31 May 2012 (UTC) | |||
:# ] (] '''·''' ]) 12:48, 1 June 2012 (UTC) | |||
;Oppose | ;Oppose | ||
# 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 a 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) | |||
:# | |||
# Motion 1 is already problematic for privacy reasons; this would make it worse. ] (]) 19:14, 14 December 2024 (UTC) | |||
; |
;Abstain | ||
# 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 | |||
; Comments | |||
* Proposed per ]. ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 03:24, 7 December 2024 (UTC) | |||
:* I can support this in general, but would still like to see this enforcement paragraph included in decisions, to make sure the parties to cases (who may not be aficionadoes of the arbitration process who are familiar with all the relevant policies) are aware of how enforcement works. Also, I think we should discuss whether one month as the maximum block for a first violation of a restriction fits well for every case. Traditionally, it said "one week" here although we have gone with "one month" in several decisions more recently. This may not be a crucial point given that one month is the ''maximum'' block, but we might want to emphasize that fact in some fashion. ] (]) 14:53, 29 May 2012 (UTC) | |||
:*: Yes, It can be added to the page template so that the information is there but doesn't require a separate vote every time. ] <sup>]</sup> 13:05, 30 May 2012 (UTC) | |||
:*: Given that a month is the ''maximum'' and that admins remain free to decide a less severe block better fits the situation, I can support them having the flexibility to go up to a significant length when it is actually necessary. Admins aren't in the habit of blocking for the absolute longest stretch they can when there's no call for it. ] 17:18, 30 May 2012 (UTC) | |||
=== |
=== Motion 2: WMF staff support === | ||
{{ivmbox|1= | |||
Take out the long words. ''] ]'', <small>02:42, 29 May 2012 (UTC).</small><br /> | |||
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. | |||
<div style="border: 1px silver solid; padding: 1em; margin-bottom: 1em; background: white;"> | |||
; Standard enforcement provision | |||
The following provision applies to all cases which include an enforceable remedy, unless they say otherwise. | |||
:"If a user subject to a restriction violates it, they may be blocked, for up to a month to start with, and then with blocks increasing in length to a maximum of a year. Appeals against blocks may be made to the administrator who blocked the user, and afterwards to ], or to the Arbitration Committee. All blocks will be recorded on the main case page." | |||
</div> | |||
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. | |||
Something like this. ''] ]'', <small>02:46, 29 May 2012 (UTC).</small><br /> | |||
:I would suggest using a standard one week initial block and go from their. In many cases one month could be considered excessive for the first offense especially considering the vague way that some of the recent arb decisions have been worded. One could easily find themselves blocked for a month because of the way someone interpretted the decision, right or wrong. ] (]) 17:36, 30 May 2012 (UTC) | |||
:Any response? This seems like clearer simpler wording. It is of course a standard that committees and people writing rules tend to use more complex wording, as a form of code switching, to be charitable. However it is also demonstrated that clearer language improves understanding and leads to less conflict. ''] ]'', <small>22:07, 2 June 2012 (UTC).</small><br /> | |||
The specific responsibilities of the staff assistants shall include, as directed by the Committee: | |||
== Motions to block or ban Rich Farmbrough == | |||
* 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: | |||
=== Motion RF1 (indefinite - one year appeal) === | |||
* 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. | |||
: ''For this motion, there are 13 active arbitrators but 1 is recused, so 7 votes is a majority.'' | |||
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. | |||
Proposed: | |||
Staff assistants shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.}} | |||
: The Arbitration Committee has established (through the checkuser tool) that {{user|Rich Farmbrough}} has, in recent days, used ] and other forms of automation. Use of such tools is in gross violation of the prohibition on his use of any form of scripting or automation to edit Misplaced Pages. Therefore, Rich Farmbrough is banned indefinitely from the English Misplaced Pages. He may appeal this ban after one year. | |||
<!-- change the number depending on active count --> | |||
==== Votes RF1 ==== | |||
{{ACMajority|active=10|motion=yes}} | |||
; Support | |||
;Support | |||
:#Proposed. This was pretty much what the arbitrators who voted to ban Rich in the first place had feared, and I confess myself seriously disappointed that their predictions on the case pages proved correct. ] ]] 23:50, 31 May 2012 (UTC) | |||
# | |||
:# Regretfully. We've made the desire that you continue to contribute to the project without using any automation at all as clear as reasonable, and then some. You've repaid us for our leniency by wikilawyering everything in sight. None of this was necessary, and I personally counseled you to take a Wikibreak and reflect before coming back. I wish you had chosen that path, rather than this one. ] (]) 01:56, 1 June 2012 (UTC) | |||
:# 2nd choice after RF3. The evidence strongly suggests that Rich has been using AWB in one browser and then copying and pasting the edits in another browser, and for two edits he made a mistake and used the wrong browser. As Rich has been caught and now admits using AWB, a ban is the only option. A short block would be inappropriate as it is clear that he cannot be trusted to a) stay away from automation and b) be honest. Even when caught he tried to wriggle out of it until the evidence couldn't be denied. A short block would be like playing ], allowing Rich another shot at hitting the target of concealing his automation. ''']''' ''']''' 02:05, 1 June 2012 (UTC) | |||
:#The question is this. Is this a one-time, two edit mistake, or is this trying to modify the tools in such a way as to be undetectable via standard means. What is not in dispute is that Rich made at least two edits using a version that skirts usual controls of its use. The CU evidence, does not, I believe, bear out Rich's story that this was a two-edit mistake. I don't buy it, and the only way left to stop him evading his sanction is, sadly, this. I don't like it, but that's what's left. ] 02:08, 1 June 2012 (UTC) | |||
:# Per Courcelles. ] <sup>]]</sup> 02:11, 1 June 2012 (UTC) | |||
:#: <s>Second choice. Firstly, the apparent deception ''is'' an aggravating factor and that justifies extending the ban beyond one month. On the other hand, whether a minimum period of twelve months is too long is an entirely different question. I'm supporting this for now mainly because I'd like assurances from Rich Farmbrough before any ban is lifted and this remedy provides for that. If there's a glimmer of consensus for reducing the waiting period before reconsideration say to three or six months, I'll propose an alternative along those lines, ] <sup>]</sup> 05:35, 1 June 2012 (UTC)</s> Striking for now, ] <sup>]</sup> 23:42, 2 June 2012 (UTC) | |||
:# Second choice. <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 19:36, 1 June 2012 (UTC) | |||
; |
;Oppose | ||
# 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) | |||
:# Excessive. The case already provides for an initial block of one month. I think that is more reasonable. In particular, refusing to even consider an appeal for a full year is completely out of proportion to the violation. ] (]) 02:46, 1 June 2012 (UTC) | |||
# Per my comment on motion 4. - ] (]) 01:31, 7 December 2024 (UTC) | |||
:# Ok, here's my (lengthy) thoughts after going over this whole situation in my head time and time again. It's obvious from our review that Rich had no willingness to comply with the injunction. He went so far as to prepare his edits using automation, and then copy them into Misplaced Pages manually. This does breach the letter of the restriction, and it mangles the spirit of it all to heck and back. For that, I think he needs to take some time away from Misplaced Pages, get rid of automation, come back as a regular editor, and work his way back into the Community's trust. I think a fixed block/ban of several months would be the best way to solve that. Quite frankly, I don't blame my fellow arbs for thinking the ban above is a fair and just response. The path to getting rid of restrictions you don't believe in isn't to go ahead and violate them secretly, it's to show that the reason for them no lnger applies. However, the fact that when caught he immediately A)Owned up to it, B) Apologized (not to us.. but to his supporters) for it, and C) indicated that he would accept any ban placed here tips the scales for me into opposing this ban and proposing a shorter, fixed term ban. ] (]) 03:00, 1 June 2012 (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) | |||
:# Per the comments above, prefer a shorter, fixed term ban. ] (]) 03:25, 1 June 2012 (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 | ||
# | |||
<!-- | |||
; Comments by arbitrators | |||
;Arbitrator discussion | |||
::*The explanation given on the ArbCom mailing list is that Rich Farmbrough has used AWB after altering it not to leave an edit summary, but that it has left a trace signature which CheckUser has picked up. Given his clear frustration at the case result in which he was banned from using automation, and which he has been protesting about in various places, and that it was proposed in that case that he be banned because he was likely to do something like this, it seems highly likely that this is what has happened. However, I am prepared to wait 24 hours to allow Rich Farmbrough to explain himself. If he is unable to satisfactorily explain the situation then I agree that a ban is more appropriate than a block because a ban was proposed in the case and narrowly avoided by some of us wishing to allow Rich Farmbrough a chance to prove himself. ''']''' ''']''' 01:04, 1 June 2012 (UTC) | |||
--> | |||
::*Waiting, as per SilkTork. <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 01:08, 1 June 2012 (UTC) | |||
==== Motion 2: Arbitrator views and discussions ==== | |||
::First off, Rich, thank you for being honest and forthright, not only to us, but to the supporters who have backed you in these past weeks. That's going to play a role in any vote I make. I think I'm still going to vote for a ban, but I think I might put a fixed-length time ban on the table instead of the indefinite with an appeal after a year that has been proposed. I need to spend some time thinking about it. ] (]) 02:04, 1 June 2012 (UTC) | |||
*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) | |||
:::* Concur. I do not believe we are in a position to do anything except issue a site-ban of significant duration, but I do hope there may be a successful appeal at some point. ] ]] 11:39, 1 June 2012 (UTC) | |||
=== |
=== Motion 3: Coordinating arbitrators === | ||
{{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. | |||
: ''For this motion, there are 13 active arbitrators but 1 is recused, so 7 votes is a majority.'' | |||
The specific responsibilities of coordinating arbitrators shall include: | |||
Proposed: | |||
* 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. | |||
: The Arbitration Committee has established (through the checkuser tool) that {{user|Rich Farmbrough}} has, in recent days, used ] and other forms of automation, taking steps to conceal the automation used in preparing his edits. Use of such tools is in gross violation of the prohibition on his use of any form of scripting or automation to edit Misplaced Pages. Therefore, Rich Farmbrough is banned for six months from the English Misplaced Pages. When this ban expires, {{user|Rich Farmbrough}} must show at least a further six months of trouble free editing before any appeal to remove or loosen the restriction on automation will be heard. | |||
</blockquote> | |||
}} | |||
<!-- change the number depending on active count --> | |||
==== Votes RF2==== | |||
{{ACMajority|active=10|motion=yes}} | |||
; Support | |||
;Support | |||
:# Rich went to a lot of trouble to try to conceal his use of automation. I don't think we can let that slide without at least some action here. However, the fact that when he was caught, he admitted to it, and apologized to his defenders for disappointing them is the reason I did not support the indefinite ban above. I think it would be best for Rich if he took this time off and came back, and showed that he can edit successfully without any use of automation. ] (]) 03:16, 1 June 2012 (UTC) | |||
# 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) | |||
:# During the recent ArbCom case, I supported a 3 month ban, so given the recent automated editing in defiance of the ban, 6 months seems about right. ] (]) 03:22, 1 June 2012 (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) | |||
; Oppose | |||
#Per Primefac. ] (]) 19:19, 14 December 2024 (UTC) | |||
:#The evidence is of a willful and highly deliberate effort to circumvent the sanctions. And Rich only fessed up, not when asked, but when shown proof beyond any ability to deny. This won't be fixed by sending him away for 180 days, the problems here are fairly fundamental. Letting him ''ask'' to come back in six months would be one thing, but not an automatic return. ] 03:40, 1 June 2012 (UTC) | |||
:#Opposing for the opposite reason as Courcelles; I think that six months is too severe for this first violation of the sanctions. Granted, it is not as if Rich Farmbrough had a trouble-free record up until that point (or we wouldn't have had a case in the first place), but even so. The decision calls for a block of up to one month for a first offense. I think that would be more than sufficient and even that would arguably be excessive. ] (]) 04:00, 1 June 2012 (UTC) | |||
:# Opposing because such bans, being preventative, shouldn't come with a ]. As I've indicated in ], I'd consider a shorter ban than a year (perhaps even a much shorter ban than one year) providing there's an opportunity to review the position based on input from Rich Farmbrough about modified behaviour prior to lifting it. ] <sup>]</sup> 05:41, 1 June 2012 (UTC) | |||
:# I would be in favour of hearing an appeal after six months, but I have been convinced by previous arguments that fixed term bans are more in the nature of punitive than preventive, and would rather have assurances in six months time that any banned person has recognised they were causing a problem and what steps they would take to prevent further problems. Giving that Rich was informed that his editing is a problem and was restricted in October 2010, which is more than six months ago, I don't see the mere passage of time as being a convincing argument that he will amend his ways, especially as he has long shown that he is in denial that his behaviour is a problem, and doesn't go along with consensus, which is the basic model of how Misplaced Pages operates. ''']''' ''']''' 08:35, 1 June 2012 (UTC) | |||
:#] ]] 11:31, 1 June 2012 (UTC) | |||
:# per comment I made above. ] (] '''·''' ]) 12:51, 1 June 2012 (UTC) | |||
:# Per Courcelles. ] <sup>]]</sup> 14:08, 1 June 2012 (UTC) | |||
:# Per SilkTork ] (]) 01:42, 2 June 2012 (UTC) | |||
; Abstain | |||
:# | |||
; Comments by arbitrators | |||
: | |||
=== Motion RF3 (indefinite - six month appeal) === | |||
: ''For this motion, there are 13 active arbitrators but 1 is recused, so 7 votes is a majority.'' | |||
Proposed: | |||
: The Arbitration Committee has established (through the checkuser tool) that {{user|Rich Farmbrough}} has, in recent days, used ] and other forms of automation. Use of such tools is in gross violation of the prohibition on his use of any form of scripting or automation to edit Misplaced Pages. Therefore, Rich Farmbrough is banned indefinitely from the English Misplaced Pages. He may appeal this ban after six months. | |||
==== Votes RF3 ==== | |||
; Support | |||
:# First choice. ''']''' ''']''' 08:41, 1 June 2012 (UTC) | |||
:#: <s>First choice. I'm okay with this too. ] <sup>]</sup> 08:47, 1 June 2012 (UTC)</s> Striking for now, ] <sup>]</sup> 23:52, 2 June 2012 (UTC) | |||
:#: <s>Very reluctantly. I'm afraid of all that changes between proposal 1 and this one is when the first appeal will be declined, I would much prefer a fixed length ban. But I hope six months down the road, the ill will and frustration we all feel at being in this situation will have faded and we can grant an appeal at that time. ] (]) 10:39, 1 June 2012 (UTC).</s> Switching to procedural oppose, as we discuss something less then a full ban here. if it makes a difference, I prefer this motion over 1, but I'm trying to see if we can keep this open long enough to hash out something agreeable to the committee as a whole. ] (]) 23:31, 2 June 2012 (UTC) | |||
:#: On reflection, I agree with Jclemens and Casliber's comments - this isn't substantially different from an indefinite ban. ] (]) 23:51, 2 June 2012 (UTC) | |||
:# If and only if motion 1 does not pass, otherwise this is an oppose. ] 13:34, 1 June 2012 (UTC) | |||
:# Second choice. ] <sup>]]</sup> 14:08, 1 June 2012 (UTC) | |||
:# First choice. <font color="#cc6600">]</font><sup><small>(<font color="#ff6600">]</font>)</small></sup> 19:37, 1 June 2012 (UTC) | |||
:# If and only if motion 1 does not pass, otherwise this is an oppose, per Courcelles. Six months is December, with the same committee. I think Rich's violation of our good faith has been so extensive that I would be hard pressed to imagine a world in which he would be let back in in six months. I personally have no particular qualms with this being more severe than past appeal timetables--not because Rich is any better or worse than anyone else, but because we've ''never'' accepted an appeal from a case-banned user in six months during my tenure on the committee, so the fact that we'll "hear" such an appeal is just a polite fiction. ] (]) 01:47, 2 June 2012 (UTC) | |||
; Oppose | |||
:# A secondary motive of the first motion is to send Rich away for long enough that he changes his perspective. Half a year doesn't really do that. ] ]] 11:34, 1 June 2012 (UTC) | |||
:# Per my comments on motion. I understand completely why my colleagues deplore Rich Farmbrough's recent behavior, and everyone can be assured that I am not impressed with it either. Nonetheless, I am not prepared to conclude that this editor must be separated from the project for such a period of time. ] (]) 12:34, 1 June 2012 (UTC) | |||
:#:Help us here, Brad ;) What do ''you'' conclude is an appropriate period of time? ] <sup>]</sup> 12:48, 1 June 2012 (UTC) | |||
:#::A few days would be ample. A month would clearly be enough. I think from his comments today that it is possible that Rich Farmbrough is getting the message, and I want to see how that plays out before we send away for months an editor with close to one million edits on this project. ] (]) 00:26, 2 June 2012 (UTC) | |||
:# This won't work as we'll be arguing about whether to lift it in six months. ] (] '''·''' ]) 12:55, 1 June 2012 (UTC) | |||
:# Concur with Casliber. ] (]) 00:03, 2 June 2012 (UTC) | |||
:# Proceedural Oppose. for the moment. ] (]) 23:31, 2 June 2012 (UTC) | |||
:# ] (]) 23:51, 2 June 2012 (UTC) | |||
; Abstain | |||
:# | |||
; Comments by arbitrators | |||
::*Proposing this as a midway point between the existing two motions, and also as it fits better with my own feelings. ''']''' ''']''' 08:41, 1 June 2012 (UTC) | |||
===Motion RF4 (three month ban) === | |||
: ''For this motion, there are 13 active arbitrators but 1 is recused, so 7 votes is a majority.'' | |||
Proposed: | |||
: The Arbitration Committee has established (through the checkuser tool) that {{user|Rich Farmbrough}} has, in recent days, used ] and other forms of automation, taking steps to conceal the automation used in preparing his edits. Use of such tools is in gross violation of the prohibition on his use of any form of scripting or automation to edit Misplaced Pages. Therefore, Rich Farmbrough is banned for three months from the English Misplaced Pages. When this ban expires, {{user|Rich Farmbrough}} must show at least a further six months of trouble free editing before any appeal to remove or loosen the restriction on automation will be heard. | |||
==== Votes RF4==== | |||
; Support | |||
:# Proposing this for two reasons - (i) fixed is fixed, so we don't waste time arguing the point once it's wound up, and (ii) it's a transgression of the decision we made. The reason for the shorter length is because I am still getting my head around the fact we have an editor with a million edits and until very recently was an admin can end up perma-banned so quickly. ] (] '''·''' ]) 13:01, 1 June 2012 (UTC) | |||
:# Equal second choice. ] (]) 13:42, 1 June 2012 (UTC) | |||
:# <s>First and only choice.</s> I don't think, for a user who has been on Misplaced Pages for hours of just about every day for years on end, that this is a "useless" ban; I think this will have a more effective impact than an even longer one, because there is the hope of returning. ] (]) 00:06, 2 June 2012 (UTC) Now second choice. ] (]) 14:09, 2 June 2012 (UTC) | |||
;Oppose | ;Oppose | ||
# | |||
:#For the same reasons as motion2,except this one is pretty much useless as a ban term goes, even if you think fixed bans are useful. ] 13:36, 1 June 2012 (UTC) | |||
:# ] <sup>]]</sup> 14:09, 1 June 2012 (UTC) | |||
:# Useless. ] ]] 14:50, 1 June 2012 (UTC) | |||
:# Still excessive, in my view, per my comments on the motions above. However, this vote can be counted as very reluctant support if it makes the difference between this motion passing and one of the earlier ones. ] (]) 00:28, 2 June 2012 (UTC) | |||
:# I'm not comfortable making an assumption about someone's mindset in three or six months times - I'd rather get the feedback at the time and make an assessment then. ''']''' ''']''' 00:32, 2 June 2012 (UTC) | |||
:# The time for this is past. We should have banned him for a month right off the bat, to give him time to get his mindset straight. If there's anything I regret about this case, it's not enacting a short-duration ban right off the bat, to get through to Rich that no, we were not going to reconsider things, and his status with respect to the project was changed for the foreseeable future. I'm afraid that by allowing Rich (and certain other editors in good standing who empowered his challenges) free rein to attack the process, Rich developed an "I'm going to get ArbCom!" mindset, which probably helped him justify his ] behavior. Unfortunate, indeed, but now is not the time for such gentle measures. ] (]) 01:52, 2 June 2012 (UTC) | |||
;Abstain | |||
===Motion RF5 (30 day block) === | |||
# | |||
<!-- | |||
The Arbitration Committee has established (through the checkuser tool) that {{user|Rich Farmbrough}} has, in recent days, used ] and other forms of automation, has taken steps to conceal the automation used in preparing his edits, and thus is in flagrant violation of his editing restrictions. | |||
;Arbitrator discussion | |||
--> | |||
==== 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) | |||
=== Motion 4: Grants for correspondence clerks === | |||
Ordinarily, because of the aggravating factors, a ban of significant length would be contemplated. While noting that this editor's prior contributions are not grounds for exoneration, the Committee nevertheless is prepared to accept on this one occasion his past work in mitigation. Rich Farmbrough is therefore blocked for thirty days from the English Misplaced Pages. | |||
{{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}} | |||
After the block expires, Rich Farmbrough is encouraged to work constructively within the limits of his restriction and advised that once he can demonstrate at least six months of trouble free editing he may request reconsideration of the restriction on automation. | |||
;Support | |||
# | |||
==== Votes RF5==== | |||
; Support | |||
:# I am prepared to accept that Rich Farmbrough did not act typically ''on this occasion'' and will therefore give him the benefit of doubt. I also see this very much as a wake up call. ] <sup>]</sup> 12:36, 2 June 2012 (UTC) | |||
:# First choice. In answer to your question, Kirill: I believe that if Rich is going to have a change of heart, it won't take longer than 30 days for it to happen. Now, he might never have a change of heart, but it is no less likely to happen in 30 days than in 365. ] (]) 14:08, 2 June 2012 (UTC) | |||
:# Equal second choice. ] (]) 15:49, 2 June 2012 (UTC) | |||
:# In my view, more reasonable and proportionate than other choices. ] (]) 15:58, 2 June 2012 (UTC) | |||
:# Yes, in line with infraction. ] (] '''·''' ]) 22:37, 2 June 2012 (UTC) | |||
;Oppose | ;Oppose | ||
# 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) | |||
:# ] (]) 12:55, 2 June 2012 (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) | |||
:#:The effort spent to conceal his evasion of sanctions (and no semantics, he flat out knew they were an evasion of sanctions, he was just surprised to have screwed up in such a basic manner. Rich and Misplaced Pages need to seperate for a time, and then rebuild the bridges he burnt down because he was going to do it his way, come hell or high water. ] (]) 22:12, 2 June 2012 (UTC) | |||
:# The length of the ban is not the issue here, it is that we don't know either now or at the end of the period if Rich will be ready to adjust his behaviour. This motion has no mechanism in place for making an assessment of his attitude. That is important because it is Rich's attitude that is the issue. It is not that he has had a heated response in a certain topic area, or with certain individuals which might warrant a short block, it is that his approach to editing sometimes needs adjusting through negotiation and compromise, and he has shown himself unwilling to do that. He has been given a chance to show he can work within reasonable parameters (the same parameters that the majority of Wikipedians use - not unreasonable or restrictive sanctions), and he has demonstrated that he is unwilling or unable to do that, even with the threat of a 30 day block hanging over him. Until he changes his attitude, and is prepared to stop contentious editing on request, discuss the concerns in a reasonable and polite manner, and then make appropriate adjustments to his editing in line with consensus, regardless of whether he thinks it is right or wrong, then he will continue to be a problem. It may be worth going back to the principles and findings in the case to remind ourselves why we are considering this ban. Plus, we have not convened the Committee to decide on an action that a single AE admin can action today - . The reason we are here discussing it is, I have assumed, because we feel that the situation is serious enough for us to go further than the enforcement remedy. Having said all that, I would not object to an indef ban with a shorter review period of three months if it is the length of the ban that is causing this impasse. ''']''' ''']''' 15:27, 2 June 2012 (UTC) | |||
:#Not nearly sufficient for the intentional effort to hide evasion of sanctions. ] 18:13, 2 June 2012 (UTC) | |||
; Abstain | |||
:# | |||
; Comments | |||
:* | |||
=== General discussion === | |||
Whoa! Do you think I'm a complete idiot? <ref group="notes"></ref> I just posted on my talk page that I was aware that Arbs could see my user agent string. | |||
I am awaiting the response from AGK to which edits are claimed to have this user-agent string, and have asked Rjwilmsi to email me to establish if there is any possibility that the code could post on it's own. | |||
''] ]'', <small>23:58, 31 May 2012 (UTC).</small><br /> | |||
: The privacy policy precludes disclosure of the information in question, but I have responded to your e-mail. ] ]] 00:42, 1 June 2012 (UTC) | |||
::It appears that I may have inadvertently made two edits correcting spellings using AWB, although I am still not clear how this happened, I do of course accept that it is a breach of the decision, and accept a ban. ''] ]'', <small>01:31, 1 June 2012 (UTC).</small><br /> | |||
{{Footnotes|group="notes"}} | |||
::Rich, I'm willing to listen here. I can accept that you're having a really difficult time making the transition back to editing without tools. I'd really prefer not to impose a longterm ban. But you're going to have to help us here. I suggest you start by reviewing your monobook.js and stripping out anything that could possibly lead you into temptation; just remove those scripts, they'll still be in the page history in the future. (I don't think any of us even considered touching your monobook.js, which I think most editors view as being a very personal page; it would kind of be the online equivalent of rooting around in your underwear drawer.) Second, start looking for categories where you can make a difference without using scripts or AWB or any other form of automated editing. Join the Guild of Copyeditors, or look for references for BLP stubs, or just keep clicking "random article" and trying to improve each article that comes up. This is going to be hard, I know. And perhaps it is necessary for you to take a break for a bit to help you change your editing habits; right now, there is a very good chance that such a break might be of the "enforced" kind. But if you want to continue to participate in the project, this is how it's going to have to be. I'd rather have you helping to improve the project, if you can find a way to do that without extra tools, but ultimately it's up to you to figure out how you can do that. ] (]) 02:05, 1 June 2012 (UTC) | |||
:::That's extremely positive. I don't have to look for things to improve on Misplaced Pages - and this is something that NewYorkBrad was interested in, they find me. Either by requests or because I see something wrong. In the latter case not being able to fix it would be an irritant, just as it is in printed matter or on most web sites - but no more after a day or so - and remember I just had a month with no article edits, though annoyingly I did not get much of a break. Similarly doing stuff manually is annoying. But in the short term it's not my loss if one article gets fixed instead of a hundred. And I don't have to deal with people who think I added tags that the Pixie dated, not that I minded. I'm not sure what you mean by "a really difficult time making the transition back to editing without tools" if you mean it in the same way you might say to the engineer fixing your car "I guess you are finding it really hard to do up all those nuts by hand" then yes, having deliberate obstacles thrown in one's path is difficult. Antifacilitation is by no means an unusual trope, but it is always an annoying one (and generally harmful). If on the other hand you are implying that I have a compulsion to use automation, not so. Back when I was sorta half allowed to use automation, compared with now when I'm sorta half not allowed, I was aware that I was doing far more manually than I should, partly because I hadn't invented the tools, partly because of the rules, and partly because it's so much easier just to do a few more edits, than actually crack the process and fix it. And by process I mean both the extrinsic and intrinsic aspects. ''] ]'', <small>12:59, 1 June 2012 (UTC).</small><br /> | |||
::::Rich, you're not "sorta half not allowed". You're not allowed, period. Similarly, your editing restrictions are still in effect, and you have been violating those as well. There's only so much that people can do to argue against a lengthy ban when you seem to go out of your way to encourage one. I had been letting your edits slide without comment to give you a chance to calm down, but the use of AWB seems to have brought the issue to a head. Can you give any assurance that you will follow the arbcom sanctions and your edit restrictions when you are allowed to edit again? — Carl <small>(] · ])</small> 13:29, 1 June 2012 (UTC) | |||
:::::The committee cannot decide what constitutes automation. That was my point. They said I think that rollback is allowed. Other attempts at clarification have failed. ''] ]'', <small>13:51, 1 June 2012 (UTC).</small><br /> | |||
::::::Rich, I don't think anyone (including you) thought that AWB (including your personal modification of it) is anything other than automated editing. AWB is in no way comparable to rollback. ] (]) 18:21, 1 June 2012 (UTC) | |||
It is quite remarkable that Rich Farmbrough saved any edits with AWB (because he is not listed on the ]). Nevertheless, the ban on automation has been effective, so far, in reducing the scope of the problematic editing, and Rich has taken up editing content on turtles, which is a positive development. Any "nontrivial" use of automation would be visible in Rich's contribs, but I have not seen any evidence of that. Given that there was use of AWB somehow, it appears from the editing history to have been unintentional. I would like to argue for a significant block (e.g. two weeks or one month) in lieu of a one-year ban, with the proviso that additional violations would lead to more severe sanctions. — Carl <small>(] · ])</small> 02:08, 1 June 2012 (UTC) | |||
Responding to SilkTork's comment of 02:05, 1 June 2012, I agree that is a real risk, but I think that the edit history will reveal if "hidden" automation is used to actually ''do'' anything. It's been apparent from the edit history (without any checkuser info) that Rich was still using some sort of code to remove whitespace etc., and was still occasionally violating his edit restriction, but the scope was so small that I didn't see a benefit in raising the issue. — Carl <small>(] · ])</small> 02:12, 1 June 2012 (UTC) | |||
The job of ArbCom is to ]. | |||
{{quotation|all models are wrong, but some are useful|]}} | |||
While arbcom is "not a court" they are much more like a court than a legislature or executive. In the Rich Farmborough decision, rathering than rendering a '''final''' decision, in expounding this ArbCom appears to have set itself up as some sort of probation officer / nanny -- not a "judicial" function. | |||
The admissions a change was needed because ArbCom didn't finish the job in the first place are troubling. Traditionally ArbCom has taken the time needed to craft complete decisions (even if some editors complain when they run past decision date estimates). | |||
Unfortunately, now, having painted itself into a metaphorical corner, ArbCom is faced with the ridiculous decision point of banning a long term prolific editor for correcting ''spelling mistakes''??? At least two of you (JClemens, AGK) concurred on 19 May that "In the context of the case, automation is clearly intended to be that allowing an editor to modify multiple articles or other pages in rapid succession." <small>can't find diff right now cause of page move</small>. | |||
;Abstain | |||
But there's good news -- it's not ''real'' paint... | |||
# | |||
{{quotation| A foolish consistency is the hobgoblin of little minds,|]}} | |||
Did Misplaced Pages elect little minds to ArbCom? I think not. | |||
<!-- | |||
Do the right thing. Suspend the decision, go back and hash out a ''workable'' defined of automation so Rich & the admin corps & the community knows what is allowed and what is not without ridiculous restrictions against spellcheck. <small>]</small> 02:15, 1 June 2012 (UTC) | |||
;Arbitrator discussion | |||
--> | |||
==== Motion 4: Arbitrator views and discussions ==== | |||
*Proposing for discussion; thanks to {{U|voorts}} for the idea. Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 19:00, 1 December 2024 (UTC) | |||
*:I am leaning no on this motion. The potential downsides of this plan do seem to outweigh the benefit of being able to compensate a correspondence clerk for what will ultimately likely be something like 5 hours a week at most. Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 02:13, 3 December 2024 (UTC) | |||
=== Community discussion === | |||
:I think everyone realizes that going out of your way to edit the source code of AWB so that you can run it violates a restriction against all forms of automation. The name of the program is ''auto''wikibrowser, after all. The main question to me is whether a one-year block is proportional. I can see the arguments on both sides, but I think a shorter time off might be reasonable. In any case the issue here is not the arbcom decision, however flawed it might be. — Carl <small>(] · ])</small> 02:22, 1 June 2012 (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) | |||
::I think before Arbcom decides to ban Rich they need to perform some due diligence and find out A) How did AWB post edits for Rich when he has been removed from the AWB checkuser page and B)Clearly define in non vague terms what his automation ban covers. Its still entirely too wishy washy to be enforceable. Aside from that, his ban is working and holding these 2 unconfirmed edits against him is just petty and not in the best interests of the pedia. This is of course what the Arbcom has been trying to do since the case was opened and it was only a matter of time before something was brought up. I am not surprised that this happened but I am a little curious why the checkuser tool was used to check on Rich's edits unless there was some reason to do so other than just sheer curiousity. ] (]) 02:32, 1 June 2012 (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) | |||
::Concur with Kumioko. But, it's already 5-0. ArbCom just needed an excuse. Now they have a paper airplane of one. --] (]) 02:39, 1 June 2012 (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) | |||
::: Carl: Allow me to explain my own thinking. In discovering these directly-automated edits, we realised that Rich has a copy of AWB on his computer that is tweaked to skip the security check. In reviewing his recent edits (many of which, for example, only remove white-space or single spaces from templates, or change the template's case), it also seems as though he is using automated assistance for those. My own suspicion is that he is loading and previewing the edit in "Rich's AWB", then copying the edit over and making it in his browser; the handful of exceptions where he directly edited from AWB were misclicks. In any case, why do you suppose that he would be any less inclined to automate his edits after a week or a few months than a longer period of time? Where does this end? How much time to we devote to working ''with'' this editor to allow him to continue editing, if he'll just side-step us at every juncture and do it his own way anyway?<p>Hammersoft: You know that we gave Rich a last chance (by choosing an automation ban over a site ban) in the arbitration case. You know that I was the first arbitrator to oppose the site-ban. Now you imply that this is all some form of "cover-up" for a secret plot to site-ban him all along. This is utter nonsense, and you know it. ] ]] 11:28, 1 June 2012 (UTC) | |||
---- | |||
::::I understand that argument, and I share the concern. I had seen the recent edits already, and it was apparent that he either had code to perform various changes or was going out of his way to make it look like he did. Those who had dealt with Rich before already knew that he had a modified version of AWB on his main account, although I don't know if that ever came up during the arbcom case. I agree that some sanction is justified, but I think that a year is too long given that there have also been some signs of improvement. — Carl <small>(] · ])</small> 11:59, 1 June 2012 (UTC) | |||
Why does "coordinating arbitrators" need a (public) procedures change? ] (]) 18:34, 1 December 2024 (UTC) | |||
::::"many of which, for example, only remove white-space or single spaces from templates, or change the template's case" I asked you by mail for an example. When you gave an example you gave you said "apart from fixing the typo". I accept the possibility that I may have made such an edit but I find it unlikely. ''] ]'', <small>13:46, 1 June 2012 (UTC).</small><br /> | |||
: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) | |||
:::::It doesn't matter; you are entirely prohibited from making various cosmetic changes, whether they are made in conjunction with other changes or not. Arguing about whether other changes were made is just a distraction from the issue. Can you give some assurance that you will follow your edit restrictions when your ban expires? — Carl <small>(] · ])</small> 13:54, 1 June 2012 (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) | |||
::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) | |||
---- | |||
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. | |||
*Since I'm recused as an Arb, I'm going to post down here. Rich is in the position of someone topic banned from Israel-Palestine under ] who had been editing ]. It doesn't matter what his edits are, he's banned from using AWB and he used it. The thing isn't sentient (I hope) - it didn't turn itself on. But I do think any kind of a ban is excessive. There was a remedy of increasing blocks - block his ass for a month (or however long the first one was). And tell him to strip all the stuff out of his monobook.js...just in case it decides to start editing as well. ] (]) 10:40, 1 June 2012 (UTC) | |||
:*No, Rich is in the position of being banned from ''Foo'', and nobody has defined what ''Foo'' is. Some members of ArbCom think rollback is automation and some don't, for example. Is using AWB to find something automation? If it is, why isn't using Google search? Is using AWB to generate an edit that it then copied from one window to another automation? Some arbs think it requires more than that, that it requires changing multiple articles at speed (another undetermined metric). Rich was set up to fail by this decision. I'm not going to claim he's perfect. I'm not going to claim he's the antithesis of perfect. Why? Because I CAN'T using the arbitrary and vague metrics ArbCom came up with. If he comes back from this ban, what's he supposed to do? Say "I won't use automation"? What's the definition? A crime isn't a crime if you don't define what it is. --] (]) 12:58, 1 June 2012 (UTC) | |||
::: You guys are just looking for a martyr arent't you. And you call yourselves his friends. ] (]) 13:34, 1 June 2012 (UTC) | |||
:::* No Elen, I do not call him my friend, nor call myself his friend. I have no friends here, and have no desire to have any. That would require me to be subservient to ]. I am not. --] (]) 13:36, 1 June 2012 (UTC) | |||
:::Elen, Hammersoft is quite right to take that approach, if he believes it is the right. While we diverge over several points relating to the current situation, we both believe in expressing ourselves without fear or favour. In my case I will do it despite social capital, despite position, despite authority, despite power. This has been ascribed to me being "angry" or "frustrated" or "not internalizing my guilt" or similar motives. It is not, I have seen anomalies, I report them in good faith, and it is interesting and somewhat heartening to see who takes them in good faith, at least apparently. There is more work to do, but it will probably take a couple of years to create and implement the needed reforms, and while I think it important it I am sure there are many in the community who will tackle the task. ''] ]'', <small>14:10, 1 June 2012 (UTC).</small><br /> | |||
::::Elen no one is looking for a Martyr but what we are looking for is leadership. There is no reason for Arbcom to continue to dodge the question that has been pointed out repeatedly. Arbcom needs to be clear with their determinations or '''expect''' pushback from the community when they fail to do so. If Arbcom would make a clear determination of what an automated edit is this would be a big benefit to their credibility but what I and Hammersoft and others have been stating is that even among the members of Arbcom there is no clear idea of what no automation means. There is no standard punishment of violations (thats currently being depated in a motion so thats good). Arbcom has up till recently been free to do as they wish but their decisions have become more and more erratic so additional controls are needed. Thats the bottom line. ] (]) 14:19, 1 June 2012 (UTC) | |||
::::: All this is flannel. Rich was very clearly topic banned from using AutoWikiBrowser to make edits. He used it to make edits. Arbcom would probably find it easier to impose a lesser sanction if you lot weren't creating drama and posting what to me appears to be frank nonsense all the time, and making it look as if Rich is ignoring the sanction because you are all encouraging him to do so. ] (]) 14:41, 1 June 2012 (UTC) | |||
::::::Actually, I view it a bit different. If Arbcom had any clarity whatsoever in their decision or their method for arriving at it a lot of this "drama" would have been avoided. Since Arbcom seems incapable or unwilling to give any definitive statement on the results or methods of the trial it leaves a lot of holes in what and how they arrived their. When Arbcom cannot even define what automation is there is or how it should be enforced pushing the blame on us is just nonesense. Arbcom is the one that set Rich up for failure by creating a vague determination that was left wide open to interpretation or misinterpretation. The way it was worded Arbcom clearly never intended for Rich to be able to edit and it was only a matter of time before he did a series of edits that in some way could be construed as automation. I agree it was a poor decision on his part to make it easy but I have absolutely no doubt whatsoever that it would have happened soon either way. If you want us to quite complaining then make better and more clearly defined decisions. Then we will have nothing to complain about! ] (]) 14:52, 1 June 2012 (UTC) | |||
:::::::And just to add a bit of clarity, I do view the sanctions against Rich as mostly baseless and banning him or any other long time editor from editing is both counterproductive to building an encyclopedia and pointless. I also think that banning him for a year for breaking a nearly baseless sanction based almost primarily on minor edits is also just about as poor of a decision as anyone could make. ] (]) 15:01, 1 June 2012 (UTC) | |||
:::::* No Elen, I am not encouraging Rich to ignore the sanctions. In fact, I . I understand there's a desire to ascribe feelings to people who are upset about this decision. Please do not do so, without evidence. Thank you. As to the use of AWB; you state that Rich was clearly topic banned from using it. Could you please point to where this was made clear, in that AWB was specifically mentioned? Subsequent to the case closing, there were discussions regarding what on-wiki tools should be considered automation or not. There was no consensus on that, so far as I'm aware. But, maybe I missed it. --] (]) 14:54, 1 June 2012 (UTC) | |||
::::::: Hammer and Kumioko - more flannel. Do you guys not realise that by suggesting that Rich is too...what...stupid?... to realise that editing using AWB counts as automated editing, you're making it more likely that he would just be banned, because really, what would the alternative be for someone who was so incompetent that they didn't think AWB was included in a ban on automated editing. Why don't you buy him a headstone while you're at it. ] (]) 15:12, 1 June 2012 (UTC) | |||
::::::::You know Elen for an Arbcom member I am hearing a whole lot of ] or at least{{WP:IDONTCARE]], neither is particularly encouraging. I don't really expect Arbcom to change their minds in this case or even agree with me on this case but if any of what I am saying sinks in and causes mambers to reevaluate how they review and comment on future cases then I feel my time is better spent. As with some of the recent motions for changes which are a positive sign. To answer your question non I don't think Rich is stupid, I do think that Rich, as with many of us are frustrated by Arbcoms complete failure to properly adjudicate the case in a fair and unbiased manner. ] (]) 15:47, 1 June 2012 (UTC) | |||
:::::::::ArbCom has failed to provide a workable definition of automated, AWB describes it as ]. <small>]</small> 20:19, 1 June 2012 (UTC) | |||
* You mostly struggled to communicate what was intended the first time; there was some improvements over time, though there were some clearly unanswered questions remaining too. Now, the first thought given to enforcing the existing decision is apparently an indefinite ban motion which locks his ability to appeal until after 1 year. And apparently, even that is headed by the same person who started using CU access in this case. Is it any wonder that you appear, to some people, to invite the sorts of allegations which have been raised here? ] (]) 15:00, 1 June 2012 (UTC) | |||
* It is irresponsible to pass unenforceable sanctions; if ArbCom was unable to come up with workable definition of restrictions that would allow RF to edit while preventing disruption due to excessive automated edits, it would have been better to simply ban the editor in the first place. In addition to the previously documented variance in arbitrators statements regarding the scope of the ban, the , with multiple recent changes including an arbitrator reverting the action of a arbcom clerk, clearly shows that the committee itself didn't know what the sanction meant, let alone the rest of the community. Misplaced Pages editing is a client server interaction; the only thing that ArbCom has control over is the server side, so restrictions should only reference that. A professional coder could easily implement an automated client that would be indistinguisable from a browser. The fact that AWB user agent strings were detected indicates either programming error or intentional limit testing, not that the sanction is valid. The ] analogy is a false one, as all involved components of the restriction are server side. As I'm seeing seven votes for one or more of the proposals I anticipate this discussion will terminate soon; if an appeal is heard in the future I urge the committee to ensure any restrictions are clearly defined, reasonable, and comphrehensible to itself, the restricted party, and the rest of the community. <small>]</small> 20:19, 1 June 2012 (UTC) | |||
* This totally sucks; Rich is useful and skilled. Do-over. ] (]) 02:34, 2 June 2012 (UTC) | |||
** I second Br'er Rabbit here: Do-over (though I do not trust that ArbCom ''can'' do it properly - their solution will be the same, or harsher, but still without properly being able to show the proper evidence for it - e.g. ArbCom bans Rich from using automation on his main account while not being able to show that he is substantially and continuously abusing automation on his main account and while not being able to define what is the automation that he was abusing and not being able to define the boundaries of what is automation). --] <sup>] ]</sup> 06:23, 2 June 2012 (UTC) | |||
<small>Adding comment here from User:Varlaam that was to the voting section for motion RF1. ] (]) 07:58, 2 June 2012 (UTC)</small> Excessive. ].<br />Fixed term of four weeks sounds right to me. ] (]) 07:31, 2 June 2012 (UTC) | |||
I think you can do a much better job of making your case. ] (]) 20:05, 1 December 2024 (UTC) | |||
=== Use of checkuser === | |||
Who has been using checkuser to investigate Rich and when were each of these checkusers done? --] (]) 02:57, 1 June 2012 (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) | |||
:Hi Hammersoft, in answer to your query, AGK was the first person to checkuser Rich, which was in the last 12 hours. After AGK informed the rest of the committee of his findings, other arbs, including me, have confirmed the result. ] (]) 03:31, 1 June 2012 (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) | |||
---- | |||
In any event the ] is quite broad in allowing use to 'limit disruption', there would be no violation if RIch was routinely checkusered during the period that he is banned from using automation. There is no requirement that a separate new reason has to be established for each use of the tool, the arbcom sanction in itself justifies it. — Carl <small>(] · ])</small> | |||
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. | |||
:Oh for heaven's sake, Hammersoft. Take a look at Rich's recent editing history. Most of them are almost exactly the same type of edits he was doing before he was sanctioned - except for archiving the talk page of an arbitrator with whom he had just had a recent dispute. That was practically begging for arbitrators to look at his contribs, see he was doing the same thing, and verify that he was or was not using an automated tool. It would have been a great kindness on the part of his supporters to help Rich to adjust to editing without scripts and tools rather than to keep fighting a battle that had already been decided. Now he's shot himself in the foot using a hacked version of AWB, but he managed to screw that up too. ] (]) 03:42, 1 June 2012 (UTC) | |||
: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) | |||
::It doesn't really matter how or why, the end result is how it was always going to be. He did make it easier for Arbcom to make the decision but the way the sanctions were written it was an open ended noose waiting for a neck. I think its a great loss to the pedia and I hope he chooses to participate in one of the sister projects like commons where his edits are wanted. I have had a problem with the decision from day one and this is just another aspect that sours my opinion of Arbcom and the pedia. ] (]) 04:04, 1 June 2012 (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) | |||
*I asked for a timestamp. --] (]) 12:49, 1 June 2012 (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) | |||
:*Yesterday evening (UTC). ] ]] 13:38, 1 June 2012 (UTC) | |||
---- | |||
::*I want a date and time stamp, for example: 13:47, 1 June 2012, for checkusers done towards Rich from 15 May 2012 through now, along with who performed each. Thank you, --] (]) 13:48, 1 June 2012 (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) | |||
::::Checkuser logs (and their information) are not public information, Hammersoft, and they're covered by the privacy policy. The subject of the check, Rich, has been provided with information in accord with the privacy policy. I'm going to assume that you have read what is written and can figure out that it occurred between the time that Rich archived Elen of the Roads' talk page, and the time that this motion was made. ] (]) 13:55, 1 June 2012 (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) | |||
:::::Not only that but Rich has admitted what he did so there isn't really any reason to doubt or question what the checkuser data says. Regardless of my personal feelings about the validity or manner in which the Arbcom decision was carried out this much at least isn't worth arguing. Personally I still have '''major''' problems with the Arbcom decision against Rich, how it was written and other aspects of the case so IMO there are still way too many problems and questions pertaining to the Arbcom decision to justify a year long ban. If I was a member of Arbcom I would start with a month and go from there. In general I would not start with a year long ban for a user unless there where significant mitigating circumstances (off wiki harrassment, severe socking, vandalism, threats, things of that nature). ] (]) 14:04, 1 June 2012 (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) | |||
::::Per Risker. ] ]] 14:07, 1 June 2012 (UTC) | |||
:::Yeah, these are great questions. Responses to your points: | |||
The privacy policy does not cover the date and timestamp on the logs and who performed the check. I am not asking for any identifying information. I am not asking for any private information about Rich whatsoever. I am asking for a list of the checkusers performed from 15 May 2012 through present towards Rich, with ''only'' a date and timestamp for each check, and who performed the check. I have asked several times now for this information. I would appreciate a straightforward answer this time. Thank you, --] (]) 14:26, 1 June 2012 (UTC) | |||
:::* 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. | |||
:You have a straightforward answer, Hammersoft: No. ] (]) 14:34, 1 June 2012 (UTC) | |||
:::* 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. | |||
:*Why? The date/timestamp of when checkuser was used and by whom is not covered by the privacy policy. Under what reason is this request being denied? --] (]) 14:45, 1 June 2012 (UTC) | |||
:::* 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. | |||
::::Hammersoft, the first checkuser was AGK, which was done late yesterday evening UTC, I was the second, again late yesterday evening UTC. I don't understand why you need more precise information. Perhaps you could explain. ] (]) 14:54, 1 June 2012 (UTC) | |||
:::Best, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 21:59, 2 December 2024 (UTC) | |||
::::*I shouldn't have to explain, and I'm astonished that so many members of ArbCom a refusing to provide specifics. Are you transparent or not? --] (]) 14:55, 1 June 2012 (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) | |||
:::::*{{ec}} I can think of a number of reasons:<p>(1) The checkuser log is confidential. (2) Disclosing data from the log is a slippery slope, and one onto which this project has determined we will not take even the tiniest step. We do not quote the log to those who are not identified to the Foundation. (3) You have not given a good reason to be given any excerpt from the log. (4) Checkusers are accountable to your representatives on the AUSC, to the Foundation's ombudsmen, and to one another—not to you. (5) The log does not exist for you to create drama.<p>Take your pick of those. I too decline your request. ] ]] 14:57, 1 June 2012 (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) | |||
:::::* (1) The privacy policy covers personally identifiable information. I have not requested such information. (2) The slippery slope argument does not hold water. I am not asking for private information in any respect. The data I am asking for is no different than the data available in the various public logs here; just who did what and when. (3) I believe there has been a misuse of the tools. While I have not stated as much here, I have stated as much on Rich's talk page. (4) ArbCom is accountable to the community. (5) You are assuming bad faith. The refusal to provide this data creates drama, not the request. --] (]) 15:02, 1 June 2012 (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 very much disagree with your intepretation of whether or not the privacy policy includes data from the Checkuser Log. It is explicitly a non-public log. If you want to know whether or not *you* have been checked, I will gladly provide that information directly to you via email. You are not entitled to that information about any other contributor to this project. This has nothing to do with transparency. ] (]) 14:58, 1 June 2012 (UTC) I shall expand briefly to refer you to the ], which is to be read in concert with the ]. The checkuser log is non-public and information can be released from it under very limited circumstances. ] (]) 15:10, 1 June 2012 (UTC) | |||
::::::@] 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) | |||
::::::I might be wrong, but Hammersoft does seem to have a point in part of this at least; the apparent reason for using CU here was, by what I have read above, AGK's suspicion that this user was breaching an ArbCom remedy he supported in that case, and this led him to make a choice to use his tools to investigate. I don't think those privacy-related policies are something functionaries should be using as an excuse for, apparently, making an inflammatory remark or assumption of bad faith (that is, "The log does not exist for you to create drama") against an editor who clearly is concerned by the use of such serious tools. On the other hand, Hammersoft, based on Risker's comment, maybe you could just ask Rich to volunteer the information you are requesting, if in your view, there is no apparent loss to him by disclosing the time at which checks were done on his account (presuming that is all that you are seeking and that is all of the information Rich permits to release to you - the time at which checks were done and who did those checks). ] (]) 15:39, 1 June 2012 (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) | |||
::::::::The answer is still going to be "No, we are not releasing any checkuser log information about a contributor to this project." If Rich wants to provide Hammersoft with the information he was provided, that is his decision. Hammersoft has not indicated that he is, in fact, concerned about the use of the checkuser tool, and has shown no indication that he believes they were used outside of policy. If he has such concerns, he can request a review by the AUSC or the ]. He doesn't get to have access to information held only in a non-public log. ] (]) 15:50, 1 June 2012 (UTC) | |||
::::::::I agree, having someone managing the work could really help smooth things out. ] (]) 11:36, 4 December 2024 (UTC) | |||
::::::::::Risker, I have not asked you to change your answer to him; I have said that he does have a point about the type of inflammatory or bad faith commentary which was used in response to his query, and noted the apparent starting point of his concern. While you have said Hammersoft has not indicated his concern with the use of the tools, if you read his comment above at 15:02, 1 June 2012, it says "I believe there has been a misuse of the tools...I have stated as much on Rich's talk page." ] (]) 16:07, 1 June 2012 (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) | |||
::::::::::::My apologies, Hammersoft and Ncmvocalist; Hammersoft did indeed say that he believed there was inappropriate use of tools. I'll point out that the bad faith commentary goes both ways here; it would not matter *who* did the CU, the result would have been exactly the same, and we would still be debating the motions that are here. There's also little doubt that Rich's editing created legitimate concerns for which use of the checkuser tool was appropriate. They look like AWB edits, and they are AWB edits, and all the defensiveness and off-topic argument in the world isn't going to change that. Nonetheless, if Hammersoft wishes to take this to the Ombudsman, he is very welcome to. (I can understand that he would be less likely to want to take it to the AUSC.) ] (]) 16:50, 1 June 2012 (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) | |||
::::::::::Hammersmith I would suggest that if you wish to push the issue go through the ]. The AUSC is controlled by the Arcom so you are unlikely to get an unbiased response. ] (]) 16:00, 1 June 2012 (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) | |||
::::::::::: In regard to Kumioko's comment above, I served on the Audit Subcommitte last year, and I can advise that the Audit Subcommittee only ever gives out information of the type 'no, there wasn't a misuse of tools' or 'yes, there was, and we've removed checkuser priviliges as a result'. Or in other words, the Audit Subcommittee doesn't release this kind of information. ] (]) 16:27, 1 June 2012 (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) | |||
::::::::::::Thank you Phil. Just to clarify I wasn't trying to indicate that the AUSC would give the checkuser info but that they were unliklely to find an Arbcom member negligent in the use of the checkuser tool since Arbcom has a defacto control over the AUSC and loss of the checkuser privilage would likely result in the member being removed as a member of Arbcom. ] (]) 16:34, 1 June 2012 (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) | |||
:::::::::::::: Way to go on the good faith Kumioko. Why don't you go tell the non-arb members of AUSC that they are just patsies. Or put your money where your mouth is and ask the Ombudsman to investigate any incident where an Arb has been accused of misuse and cleared by AUSC. Or just take a step back and look at what you are saying. Telling somebody who has signed up to a position of trust, who has pledged to act with fairness and integrity, that of course they're just going to hide the evidence and back their friends, is a huge insult. You need to either put up some evidence, or stop making these massive allegations. ] (]) 18:12, 1 June 2012 (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) | |||
::::::::::::::: Elen, the facts of life are that this sort of thing happens all the time in every walk of life. Taking the Kumiko's statement and turning it into an attack on the one member of the AUSC who has no other connection with the functionary structure, or indeed on the other members of the committee jointly or severally is to miss the point. Even if (as we believe and hope) all these people are fine and upstanding pillars of the Wiki, the lack of separation of functions is not a good thing. In general these types of issue come to a head when there is abuse of the system. In this case we have the opportunity to work on improvements while there is still no serious accusation of impropriety. This should be seen as a good thing, not a bad. ''] ]'', <small>18:30, 1 June 2012 (UTC).</small><br /> | |||
:@] 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) | |||
{{od|:::::::::::::::}} Kumioko, I do not want to explain again why I (or any other arbitrator) ran checkuser queries on Rich Farmbrough. I refer you to our previous statements on this subject, and respectfully ask that you not continue repeating this same, tired line. If you have a concern, refer it to the Wikimedia Foundation Ombudsman Commission. ] ]] 18:44, 1 June 2012 (UTC) | |||
:@Elen and AGK, You are taking offense where non is directly implied but the bottom line AGK is that your name is all over the subcommittee and all over this case. You have been pushing for a ban from the beginning. It is human nature to support those with whom you have had a positive working relationship with and have grown to trust. Additionally, the fact that Arbcom has a controlling number of votes in AUSC makes it quite obvious to how an Arbcom member would be excused from guilt if an incident were submitted their affecting an Arbcom member. I stated before I haev no desire to pursue the case but was merely giving Hammersoft my advice if he was intent to do so. With that said and as I have stated before. Arbcom has made some questionable decisions lately that give way to a lot of questions. Thats a fact that has been brought up repeatedly by multiple editors and not just my opinion. If you are offended at some or all of my statements then I suggest you devote some time and take this opportunity for growth and developement to address some or all of the concerns about the processes and functions of arbcom that open the door to allegations of impropriety. ] (]) 18:57, 1 June 2012 (UTC) | |||
::"...fact that Arbcom has a controlling number of votes in AUSC..." I was under the impression there were three arbitrators and three non-arbitrators. ? ] (]) 19:12, 1 June 2012 (UTC) | |||
:::Lord Roem: That is correct; there are three arbitrator-auditors and three community-auditors. (Risker, an arbitrator, is also a part of the subcommittee, but serves in the role of subcommittee co-ordinator: this forms part of the wider role of co-ordinator of advanced permissions, and the role does not give the co-ordinator a vote in our proceedings.) If anything, the community out-weighs the committee members: during the "cross-over" when Keegan was still seated, there were ''four'' voting community members and three arbitrators. ] ]] 20:27, 1 June 2012 (UTC) | |||
::::I was counting Risker as the 4th and extra vote but even still thats 3-3 and an Arbcom member is fairly unlikely to vote another one off so the best that could be hoped for would be a draw. Either way it still proves my point that it would not be the place to take a case involving an Arbcom member. ] (]) 23:30, 1 June 2012 (UTC) | |||
:::::Two misunderstandings 1) Risker doesn't have a tiebreaking vote, and 2) We really don't vote per se anyways. We handle things in the good old fashioned Misplaced Pages model of ''consensus''. Polls are taken, objections listened to, positions adjusted, and we come up with something everyone can live with, or we would go back for more info if we couldn't get there on a first pass. Cheers, ] (]) 02:01, 2 June 2012 (UTC) | |||
::::::I admit that I misunderstood Risker's role in the process but the second part of your statement isn't exactly true. IN order to garner consensus there must be some discussion and some sort of vote such as a support/oppose discussion. My point though is that if an Arbcom member were ever accused of inappropriately using their tools and were ever to come before the AUSC as a defendant it is unlikely that the AUSC would determine anything other than the use was appropriate. ] (]) 13:13, 2 June 2012 (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) | |||
=== Why Arbcom is discussing five motions === | |||
To address SilkTork's : Having five motions for an alleged ArbCom restriction violation is simply ''additional'' evidence of the inadequacy of the automated sanction (previously raised by myself et. al.). If, using Elen's example, someone violates 1rr on ] arbcom wouldn't even be involved; a utility admin would simply deal with the situation. Because of your role as the final arbitrator for dispute resolution on Misplaced Pages it is important that you ''collectively'' act in a manner that instills confidence in the process. Ya'll got two decent options. | |||
* Stop the circle the wagons denialism and go back and fix the remedy. (I understand that much of the nature of the criticism -- arbcom conspiracy theories and demands for checkuser data in blatant violation of WMF policy -- has been way off base, but that doesn't make the decision correct in the first place. ) First choice. | |||
* Simply indef the editor and be done with it. Let's face it, no one ends up as a sanctioned party at ArbCom without missing multiple opportunities to figure out how to get along with others. Second choice. | |||
* Anything else -- speculating or expecting the editor to "change their attitude" in the face of a vague bogus sanction; or reopening the fracas in 3 or 6 or 12 months -- won't benefit Misplaced Pages. If RF decides at some future point he wants to be a team player he can file the appeal using the standard protocol. <small>]</small> 16:04, 2 June 2012 (UTC) | |||
::Personally I think they should stick with the original motion they voted and agreed on of escalating blocks. Otherwise it reduces credibility in the process if they just go back and retry the case every time because it didn't go the way they wanted the first time. Additionally, The problems go way beyond Rich's case. ] (]) 17:10, 2 June 2012 (UTC) | |||
:::So what positive action are you going to take with regard to the go way beyond problems? <small>]</small> 17:33, 2 June 2012 (UTC) | |||
:::: Kumioko, what on ''earth'' are you talking about? The case went the way ''this same committee'' decided it should go (are we forum shopping ourselves?!)—and as for individual arbitrators, many of the supporters of the first ban motion were opposed to the proposal to ban Rich that was made in the original case. You need to stop posting utter nonsense on this page. ] ]] 21:02, 2 June 2012 (UTC) | |||
:::::What I am saying AGK is that the Arbcom could not ban him like several members wanted to do from the beginning so instead they wrote a loose sanction that no one would be able to follow because its so open to interpretation. Then all they need do is sit back and watch and then when the individual does something that can be construed as a violation they get banned. I also was pointing to the fact that in the original proposal to a vote of 8 - 0 I believe the Arbcom agreed to an excalating series of blocks starting at 1 month. Now you and the other members want to revote because they didn't like how that vote went less than a week ago to be harsher. How do you expect us to not criticize decisions like that? ] (]) 21:09, 2 June 2012 (UTC) | |||
---- | |||
*Some good points raised. The reason we are here voting on these motions is that Rich didn't just use automation, but used a system to conceal he was using automation. That ties in with the in the case that he be banned because it would be difficult to enforce the restriction on using automation. Because he has been caught not just using automation (for which an AE admin could block him), but for doing so in manner designed to avoid detection, we need to return to that proposal. That there are a number of motions is because ArbCom is a committee of individuals - we do not have a hive mind, though I suppose there are core values that we share. We work things out through discussion, negotiation, and consensus. I think that, messy though it appears, that we have this public working through of a variety of motions to find the most suitable one, is a good example of the sort of transparency that I and others want from the ArbCom process. ''']''' ''']''' 17:41, 2 June 2012 (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. }} | |||
:To be frank I still don't think that banning Rich or his bots benefits Misplaced Pages. Restricting his edits to a vague definition of automation was even more unhelpful and ensured that we'd end up right back here regardless of how he edited. He just gave Arbcom a reason but it would have happened eventually either way. Now Arbcom can point and say see we told you this was going to happen. ] (]) 18:16, 2 June 2012 (UTC) | |||
::You are of course entitled to your viewpoint, but it may be helpful to you to know that I didn't want to ban Rich in the case, and did not support that proposal. If Rich had not used automation after being told not to, and specifically if he had not done so in a manner to conceal that he was doing so, then I would not be here now voting to ban him. If there is a conspiracy to ban Rich, then he has played a larger part in the plot than I have. ''']''' ''']''' 18:29, 2 June 2012 (UTC) | |||
:::@Kumioko. You seem to be RF's biggest supporter and probably Arbcom's biggest critic this last 2 months. Can you answer a couple of simple questions please? Do you think RF has at any time used subterfuge to conceal his actions? Is technical brilliance more important to you than ]? ]] 19:01, 2 June 2012 (UTC) | |||
::::I admit I am a supporter and that's because I think Rich and his bots do more good than harm. Anyone who is responsible for 5+million edits between them and their bots are going to make some mistakes but the majority of his edits are positive. That he spent many hours a day every day for several years shouldn't be a noose. To answer the first question Yes, and to answer the second question no. I don't think the 2 are mutually exclusive either. ] (]) 19:15, 2 June 2012 (UTC) | |||
:::::You might want to correct the Freudian slip in your first sentence. On the wider point, because an editor is exceptionally productive does not entitle them to leave their ethics at the door before entering Misplaced Pages. ]] 19:25, 2 June 2012 (UTC) | |||
The concept 'RF concealed automated edits' is doubly invalid: 1. no workable definition of "automated" has been provided and 2. if the edits were concealed, how he get caught? <small>]</small> 19:31, 2 June 2012 (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) | |||
*This is absolutely ridiculous: A) By ANY definition of automation useing AWB counts as it (Auto mean anything to you) and B) He screwed up and on a couple edits made a couple edits with his hacked AWB script. Otherwise, he was setting up the edits in an AWB window, and C&Ping to a regular browser window to conceal the fact he was using automation. ] (]) 20:43, 2 June 2012 (UTC) | |||
::Ah. So, copying and pasting now counts as automation. Good to know. Unfortunately, that wasn't described in the remedies in the case anymore than the use of AWB was, though I directly asked Elen for a pointer to that supposed conclusion. All of ArbCom keeps spinning in circles saying it's automation, it's not automation, it's automation and any definition will do, not it's not, yes it is, and on and on. I concur with Nobody in the initial posting in this subthread. The onus isn't on ArbCom to ban Rich from the project because they screwed up their case against him. The onus is on ArbCom to grant a mea culpa and fix it. Is it so insanely hard to admit you (collectively) blew it? --] (]) 20:53, 2 June 2012 (UTC) | |||
::*Your right about one thing SF and that's the comment this is ridiculous. Our reasons for calling it ridiculous are completely opposite but there result is the same. a ridiculous scenario that could have been prevented a number of ways not the least of which would have been for the Arbcom to clearly define automation. There is no doubt what Rich did was against the sanction. What I consider a problem is that the Arbcom worded it in such a way that would have eventually led to Rich breaking it one way or another. Yes he used AWB and thats the reason at this point but if he would have used the same edit summery to correct the same typo someone would have complained it was automation and we would still be here. I also '''do not''' think that using AWB to generate a change '''without saving it''' and then pasting that change to WP manually counts as automation anymore than using word to find typos does. Or does it? How about if I create a template for Infobox person in word and then as I fill it in for individual articles I cut and paste if from word? How about using google search? Does that count as automation? What about using an addin like or the Misplaced Pages toolbar? Do you see where I am going with this? '''If''' the Arbcom would have clearly defined what automation was then I would not have a leg to stand on but because Arbcom decided to use a 5th grader version of a sanction that was loosely defined and vaguely written to ensure that the user (in this case Rich) would not be able to follow it, Arbcom has left the door wide open to comments. ] (]) 20:59, 2 June 2012 (UTC) | |||
:::*That's a fairly ridiculous argument; ArbCom could have simply indef'd RF from the get go if that was the goal. It's also likely to be counterproductive; attacking editors motivations is unlikely to persuade them to change their action. What goal are you trying to achieve by repetitive badgering approach? <small>]</small> 21:15, 2 June 2012 (UTC) | |||
::::*Actually if you look at the original voting several members wanted to ban him from the start and it was only because the idea couldn't garner enough votes that the chose to go with the lesser option. To answer your other statement I really have better things to do. Every moment I spend here arguing about this means that other more meaningful edits aren't getting done. The reason I persist is because I am getting frustrated by Arbcoms constant ] and ] rebuttals and because frankly they did such a lousy job of writing the sanction in the first place (along with several other cases in the last few months that I regret not commenting on then) that I feel obligated to correct for future cases. I do not have anything against the individuals members and respect several of them that I have interacted with before this and have met and personally like several of the ones I have met. That doesn't mean that they are above reproach as a group nor that they are infallible. ] (]) 21:22, 2 June 2012 (UTC) | |||
::{{editconflict}}"auto" means lots of things to me; meaning depends on context. I drive my auto to work. I do repetitive tasks (e.g. unloading dishwasher) on auto. Is "semi-automation" the same as "automation"? (In the US, semi-automatic firearms are regulated quite differently than automatic). Misplaced Pages itself describes ] as a "a semi-automated MediaWiki editor," so no, it's not obvious to me that it what ya'll mean by automation. In any event, what is means to me is irrelevant -- what does it mean to ArbCom? JClemens/AGK's prior definition (high speed mass edits) was quite different than SilkTork's (which included spell check). <small>]</small> 21:08, 2 June 2012 (UTC) | |||
:::The whole ''point'' of that type of sanction is to avoid defining "automation". The point of the sanction is that Rich needs to make a complete break from using automated tools. He would have the ability to do so if he chose; many people never use automated tools at all. Instead Rich decided to keep using AWB, sometimes by copying its edits into his browser, and a few times erroneously saving its edits directly. The problem is not that an intentionally vague sanction passed; the problem is that Rich decided to flout it instead of following it. It might be harder for some robot to enforce a vague sanction, but arbcom is a bunch of humans who can handle the vagueness and judge each situation on its merits. — Carl <small>(] · ])</small> 01:02, 3 June 2012 (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 ] 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. | |||
===Concealment=== | |||
: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) | |||
I am annoyed and somewhat hurt that there is a suggestion I concealed automation. I know a similar accusation was made in the case, by an Arb (I forget which, I suppose it must have been Kirill). When I found I had a score of identical typos to fix I seriously considered fixing them with AWB and reporting myself for Arbitration Enforcement, so ridiculous the situation has become. In some ways I wish I had followed that route, but doubtless I would have been tagged as sociopathic, or "pointy" or something. Although I do not make much of my professional history on Misplaced Pages it includes running security for a major Internet banking property, reading the CERT advisories every day for years, and taking a deep interest in Internet security in general. Should I wish to "hide automation", with all due respect I doubt that the committee would be able to see through it, especially with blunt tools like Checkuser. (I have already told AGK why and how he can see that apart from one or two inadvertent edits, all my edits were made through the standard interface, though this could be hidden it would take more time than has been available, and is of no interest to me. The improvements I suggested to Checkuser should be taken up with the developers without delay.) | |||
::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) | |||
:::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) | |||
::::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) | |||
::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) | |||
::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) | |||
:::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) | |||
:FWIW, I oppose splitting arbcom-en a second time -- ] <sup>]</sup> 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.) ] (]) 06:08, 7 December 2024 (UTC) | |||
::What does this mean – when was the ''first'' time? ] 15:52, 10 December 2024 (UTC) | |||
:::@]: In 2018, arbcom-l became arbcom-en and the archives are in two different places. -- ] <sup>]</sup> 18:54, 10 December 2024 (UTC) | |||
---- | |||
I have always conducted myself scrupulously on Misplaced Pages, editing under my own name, have never sought "office", never traded on my credentials, rarely used email prior to this case, rarely used IRC, believing in openness and honesty. The only information I have deliberately withheld is that private to or tending to damage other people, or posing a risk to the project. | |||
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, ] (]) 01:32, 3 December 2024 (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) | |||
: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) | |||
::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) | |||
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) | |||
''] ]'', <small>22:44, 2 June 2012 (UTC).</small><br /> | |||
:The statements made thus far indicate you made two edits on the Misplaced Pages server using AWB -- is that correct? If it was your understanding AWB was covered under the ban, why would you even start the thing in the first place? <small>]</small> 23:03, 2 June 2012 (UTC) | |||
::AWB is an invaluable tool for listmaking. I wanted all articles which either SunCreator or I had edited, which contained the mis-spelling. Later I widened to all all Chelonian articles and picked up a couple of other issues. There was no intent to edit with it, and I am still surprised that the two edits are adjacent. As I said to AGK, when he raised the issue it was conceivable that I had misclicked either through a motor error or a cognitive error, once or twice or, out at maybe four sigmas three times. He replied that there were plenty of examples which had me doubting my sanity, but it seems he meant two were plenty. In answer to your first question, since the AWB edits were marked minor I am assuming that's all there are. ''] ]'', <small>23:23, 2 June 2012 (UTC).</small><br /> | |||
{{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) | |||
:::@Rich, @Arbcom: Does ''reading'' Misplaced Pages content with AWB constitute automation? <small>]</small> 23:48, 2 June 2012 (UTC) | |||
:Or "cat-herder". --] (]) 00:18, 5 December 2024 (UTC) | |||
:Following parliamentary tradition, perhaps "whip". (Less whimsically: "recording secretary".) ] (]) 00:31, 5 December 2024 (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) | |||
---- | |||
My approach to this is that the community have raised concerns with Rich regarding some of his edits, and Rich has not been helpful enough in his response to those concerns. It is not the actual edits for which he was brought to ArbCom, it is for his reluctance to deal appropriately with people's concerns. The concerns centred on Rich's use of automation because a) automation is so quick it spreads a contentious edit across a number of articles, and b) individual mistakes are harder to trace when someone's editing history consists of thousands of edits with the same edit summary. But, again, it was not the use of automation that brought Rich to ArbCom, but his reluctance to comply with restrictions on his use of automation. Again, I want to stress that during the case I was not looking at sanctioning Rich for any individual or group of edits, nor for his use of automation, but for his behaviour and attitude regarding concerns about his editing that were made via automation. Was a ban on using automation an appropriate remedy? Even without discussing the actual wording, or definitions of "automation", in retrospect it was perhaps not addressing the real issue, which is Rich's attitude. But how do we address that effectively? The case itself with the principles and findings about collegiality and responsiveness to people's concerns should have assisted in bringing home to someone that an adjustment in attitude was needed. And, as the concerns did centre on Rich's use of automation, then restricting Rich's use of them was appropriate. | |||
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) | |||
Where am I now? Well, Rich can correct me if I'm wrong, but it appears from what I am told, and from what I have looked at, that he has used a hacked AWB in one browser to select changes in an article, and has then copy and pasted those changes over to the article in another browser. Should he have done that? Well, he is no longer an admin so his permission to use AWB would have been removed. Any non-admin user of Misplaced Pages has to apply to use AWB. He did not apply. He used a hacked version. This, already, is not in the spirit of openness and collegiality. Without going further I am concerned. That he then doesn't make the edits directly in the browser with the hacked AWB, but instead copy and pastes them over, indicates an intent to conceal what he is doing. I am now of the mind that even if Rich was not already under ArbCom sanctions not to use automation, that such behaviour warrants a block; considering all the circumstances, an indef ban seems appropriate as I would now want clear assurances from Rich that he recognises what he has done is wrong, and that he intends to amend his behaviour. Having said that, I am still open to discussing other avenues and approaches to find out the best way of dealing with this situation. ''']''' ''']''' 01:30, 3 June 2012 (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): | |||
:::Rich, why didn't you just request access to AWB if you wanted to use it, instead of modifying it to bypass the check page? — Carl <small>(] · ])</small> 00:46, 3 June 2012 (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). | |||
::::I just made a suggestion for possible terms that several members of the Committee were thinking about offering to Rich on his talk page. For that, if we do formally give him that offer, automation will mean "nothing more than what you see when you hit the edit button and manually make the changes in the window that pops up". No scripts of any kind, no using any AWB-like tools to prepare the edits and then copying it into a normal browser window, just what any editor new to Misplaced Pages gets when they hit the edit button. ] (]) 01:08, 3 June 2012 (UTC) | |||
:* Daily, ~10 minutes: took care of any filtered emails on the list (spam and not-spam). | |||
:::::It appears ya'll are trapped in a conceptual box. You do not, and can not know what happens client side. TCP/IP packets arrive at Tampa or Amsterdam on ports 80 or 443 with some data in them and WP servers send some packets back; all you ''know'' is what happens on the server end: If you think you can actually know for sure what's happening client side you're mistaken. Whatever solution(s) ya'll arrive at should be '''server side, server side, server side.''' <small>]</small> 02:41, 3 June 2012 (UTC) | |||
:* 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). | |||
::::::No, there's no conceptual box. Rather, if it looks like automation, it ''is'' automation for the purposes of Rich's sanctions, with the onus on Rich to avoid anything that looks like automation. Given the issues to date, I think that's an appropriate way of apportioning the burden of compliance. Rich has demonstrated that he has the ability and know-how to continue problematic editing using only client-side automation. ] (]) 02:46, 3 June 2012 (UTC) | |||
:* 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 12:56, 24 December 2024
Arbitration Committee proceedings
- recent changes
- purge this page
- view or discuss this template
Currently, there are no requests for arbitration.
Open casesCase name | Links | Evidence due | Prop. Dec. due |
---|---|---|---|
Palestine-Israel articles 5 | (t) (ev / t) (ws / t) (pd / t) | 21 Dec 2024 | 11 Jan 2025 |
No cases have recently been closed (view all closed cases).
Clarification and Amendment requestsCurrently, no requests for clarification or amendment are open.
Arbitrator motionsMotion 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 12:56, 24 December 2024 (UTC)
Motion name | Support | Oppose | Abstain | Passing | Support needed | Notes |
---|---|---|---|---|---|---|
Motion 1: Correspondence clerks | 2 | 3 | 0 | 4 | One support vote contingent on 1.4 passing | |
Motion 1.2a: name the role "scrivener" | 1 | 2 | 1 | 4 | ||
Motion 1.2b: name the role "coordination assistant" | 0 | 1 | 3 | 4 | ||
Motion 1.3: make permanent (not trial) | 0 | 3 | 1 | 5 | ||
Motion 1.4: expanding arbcom-en directly | 1 | 2 | 1 | 4 | ||
Motion 2: WMF staff support | 0 | 5 | 0 | Cannot pass | ||
Motion 3: Coordinating arbitrators | 4 | 0 | 0 | 2 | ||
Motion 4: Grants for correspondence clerks | 0 | 3 | 0 | 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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- 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 todesignate individuals for particular tasks or roles
andmaintain 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) - 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
- 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)
- Might as well make it formal per my opinions elsewhere on the page. Primefac (talk) 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. ~ ToBeFree (talk) 19:16, 14 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 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)
- 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
- Misplaced Pages:Arbitration/Policy § Scope and responsibilities
- 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 For this motion there are 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.
|
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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- Nicely whimsical, and not as likely to be confusing as correspondence clerk. CaptainEek ⚓ 04:11, 7 December 2024 (UTC)
- Oppose
- 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)
- 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)
- Abstain
- 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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- Oppose
- Abstain
- I am indifferent between this and "correspondence clerk". Best, KevinL (aka L235 · t · c) 03:11, 7 December 2024 (UTC)
- 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)
- 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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- Oppose
- 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)
- 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)
- ~ ToBeFree (talk) 19:10, 14 December 2024 (UTC)
- Abstain
- 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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- Much less trouble to have them on the main list than to split the lists. CaptainEek ⚓ 04:13, 7 December 2024 (UTC)
- Oppose
- 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 a 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)
- Motion 1 is already problematic for privacy reasons; this would make it worse. ~ ToBeFree (talk) 19:14, 14 December 2024 (UTC)
- Abstain
- 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
- Proposed per Guerillero's comment below. KevinL (aka L235 · t · c) 03:24, 7 December 2024 (UTC)
Motion 2: WMF staff support
The Arbitration Committee requests that the Wikimedia Foundation Committee Support Team provide staff support for the routine administration and organization of the Committee's mailing list and non-public work.
The selected staff assistants shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work. Staff assistants shall perform their functions under the direction of the Arbitration Committee and shall not represent the Wikimedia Foundation in the course of their support work with the Arbitration Committee or disclose the Committee's internal deliberations except as directed by the Committee.
The specific responsibilities of the staff assistants shall include, as directed by the Committee:
- Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
- Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
- Reminding members of the Committee to vote or otherwise take action in pending matters;
- Organizing related correspondence into case files; and
- Providing similar routine administrative and clerical assistance to the Arbitration Committee.
The remit of staff assistants shall not include:
- Participating in the substantive consideration or decision of any matters before the Committee; or
- Taking non-routine actions requiring the exercise of arbitrator discretion.
To that end, upon the selection of staff assistants, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and staff assistants.
The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by staff assistants.
Staff assistants shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.
For this motion there are 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- Oppose
- 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)
- Per my comment on motion 4. - Aoidh (talk) 01:31, 7 December 2024 (UTC)
- Might as well make it formal per my opinions elsewhere on the page. Primefac (talk) 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. ~ ToBeFree (talk) 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 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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- 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. Primefac (talk) 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. CaptainEek ⚓ 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. - Aoidh (talk) 23:21, 9 December 2024 (UTC)
- 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:
- 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)
- @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)
- 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)
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.
Abstentions | Support votes needed for majority |
---|---|
0 | 6 |
1–2 | 5 |
3–4 | 4 |
- Support
- Oppose
- 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)
- 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)
- ~ ToBeFree (talk) 19:18, 14 December 2024 (UTC)
- Abstain
Motion 4: Arbitrator views and discussions
- Proposing for discussion; thanks to voorts for the idea. Best, KevinL (aka L235 · t · c) 19:00, 1 December 2024 (UTC)
- I am leaning no on this motion. The potential downsides of this plan do seem to outweigh the benefit of being able to compensate a correspondence clerk for what will ultimately likely be something like 5 hours a week at most. Best, KevinL (aka L235 · t · c) 02:13, 3 December 2024 (UTC)
Community discussion
Will correspondence clerks be required to sign an NDA? Currently clerks aren't. Regardless of what decision is made this should probably be in the motion. * Pppery * it has begun... 18:29, 1 December 2024 (UTC)
- Good catch. I thought it was implied by "from among the English Misplaced Pages functionary corps" – who all sign NDAs as a condition to access functionaries-en and the CUOS tools; see Misplaced Pages:Functionaries (
Functionary access requires that the user sign the confidentiality agreement for nonpublic information.
) – but I've made it explicit now. KevinL (aka L235 · t · c) 18:31, 1 December 2024 (UTC)- You're right that that was there, but I missed it on my first readthrough of the rules (thinking correspondence clerks would be appointed from the clerk team instead). * Pppery * it has begun... 18:37, 1 December 2024 (UTC)
Why does "coordinating arbitrators" need a (public) procedures change? Izno (talk) 18:34, 1 December 2024 (UTC)
- As Primefac mentioned above, it seems reasonable to assume that having something written down "officially" might help make sure that the coordinating arbitrator knows what they are responsible for. In any event, it probably can't hurt. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)
- It is a pain in the ass to get formal procedures changed. There is an internal procedures page: I see 0 reason not to use it if you want to clarify what the role of this arbitrator is. Izno (talk) 19:13, 1 December 2024 (UTC)
- On top of that, this doesn't actually change the status quo much if at all. It is almost entirely a role definition for an internal matter, given "we can make an arb a CA, but we don't have to have one" in it's "from time to time" clause. This just looks like noise to anyone reading ARBPRO who isn't on ArbCom: the public doesn't need to know this arb even exists, though they might commonly be the one responding to emails so they might get a sense there is such an arb. Izno (talk) 19:21, 1 December 2024 (UTC)
While I appreciate that some functionaries are open to volunteering for this role, this borders on is a part-time secretarial job and ought to be compensated as such. The correspondence clerks option combined with WMF throwing some grant money towards compensation would be my ideal. voorts (talk/contributions) 18:35, 1 December 2024 (UTC)
- Thanks for this suggestion – I've added motion 4 to address this suggestion. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)
In the first motion the word "users" in "The Committee shall establish a process to allow users to, in unusual circumstances" is confusing, it should probably be "editors". In the first and second motions, it should probably be explicit whether correspondence clerks/support staff are required, permitted or prohibited to:
- Share statistical information publicly
- Share status information (publicly or privately) with correspondents who wish to know the status of their request.
- Share status information (publicly or privately) about the status of a specific request with someone other than the correspondent.
- For this I'm thinking of scenarios like where e.g. an editor publicly says they emailed the Committee about something a while ago, and one or more other editors asks what is happening with it.
I think my preference would be for 1 or 2, as these seem likely to be the more reliable. Neither option precludes there also being a coordinating arbitrator doing some of the tasks as well. Thryduulf (talk) 18:49, 1 December 2024 (UTC)
- Thanks for these suggestions. I've changed "users" to "editors". The way I'm intending these motions to be read, correspondence clerks or staff assistants should only disclose information as directed by the committee. I think the details of which information should be shared upon whose request in routine cases could be decided later by the committee, with the default being "ask ArbCom before disclosing until the committee decides to approve routine disclosures in certain cases", because it's probably hard to know in advance which categories will be important to allow. I'm open to including more detail if you think that's important to include at this stage, though, and I'd welcome hearing why if so. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)
- I see your point, but I think it worth clarifying certain things in advance before they become an issue to avoid unrealistic or mistaken expectations of the c-clerks by the community. Point 1 doesn't need to be specified in advance, maybe something like "communicating information publicly as directed by the Committee" would be useful to say in terms of expectation management or maybe it's still to specific? I can see both sides of that.
- Point 2 I think is worth establishing quickly and while it is on people's minds. Waiting for the committee to make up its mind before knowing whether they can give a full response to a correspondent about this would be unfair to both the correspondent and clerk I think. This doesn't necessarily have to be before adoption, but if not it needs to be very soon afterwards.
- Point 3 is similar, but c-clerks and community members knowing exactly what can and cannot be shared, and especially being able to point to something in writing about what cannot be said publicly, has the potential to reduce drama e.g. if there is another situation similar to Billed Mammal's recent case request. Thryduulf (talk) 19:30, 1 December 2024 (UTC)
What justification is there for the WMF to spend a single additional dollar on the workload of a project-specific committee whose workload is now demonstrably smaller than at any time in its history? (Noting here that there is a real dollar-cost to the support already being given by WMF, such as the monthly Arbcom/T&S calls that often result in the WMF accepting requests for certain activities.) And anyone who is being paid by the WMF is responsible to the WMF as the employer, not to English Misplaced Pages Arbcom.
I think Arbcom is perhaps not telling the community some very basic facts that are leading to their efforts to find someone to take responsibility for its organization, which might include "we have too many members who aren't pulling their weight" or "we have too many members who, for various reasons that don't have to do with Misplaced Pages, are inactive", or "we have some tasks that nobody really wants to do". There's no indication that any of these solutions would solve these kinds of problems, and I think that all of these issues are factors that are clearly visible to those who follow Arbcom on even an occasional basis. Arbitrators who are inactive for their own reasons aren't going to become more active because someone's organizing their mail. Arbitrators who don't care enough to vote on certain things aren't any more likely to vote if someone is reminding them to vote in a non-public forum; there's no additional peer pressure or public guilt-tripping. And if Arbcom continues to have tasks that nobody really wants to do, divest those tasks. Arbcom has successfully done that with a large number of tasks that were once its responsibility.
I think you can do a much better job of making your case. Risker (talk) 20:05, 1 December 2024 (UTC)
- I think there is a need to do something as poor communication and extremely slow replies, if replies are made at all, has been an ongoing issue for the committee for some time. However I agree that asking the foundation to pay someone to do it is going too far. The point that if you are paid by the foundation, you work for them and not en.wp or arbcom is a compelling one. There's also a slippery slope argument to be made in that if we're paying these people, shouldn't we pay the committee? If we're paying the committee, shouldn't we pay the arbitration clerks....and so on. Just Step Sideways 20:26, 1 December 2024 (UTC)
- I fully share Risker's concern about a paid WMF staffer who, no matter how well-intentioned, will be answerable to the WMF and not ARBCOM. Vanamonde93 (talk) 21:55, 1 December 2024 (UTC)
- The 2023-2024 committee is much more middle aged and has less university students and retirees, who oftentimes have more free time, than the 2016-2017 committee. -- Guerillero 08:56, 2 December 2024 (UTC)
- It seems to me that the issue of there often being some Committee members who, for whatever reason, are not "pulling their weight", is at the core of the problem to be addressed here. Because this happens "behind the scenes", the community has no way to hold anyone accountable in elections, and because of human nature and the understandable desire to maintain a collegial atmosphere within the Committee, I don't really expect any members to call out a colleague in public. I suppose there could even be a question of what happens if whoever might be filling the role proposed here nudges a member to act, but the member just disregards that. It's difficult to see how to make it enforceable. I don't have any real solutions, but this strikes me as central to the problem. --Tryptofish (talk) 23:31, 2 December 2024 (UTC)
- I think this is largely correct. I was reluctant on the committee to even note this committee's inactivity problem (worst of any 15-member arbcom ever), even though it was based on a metric that is public, when I was still on the committee. And it gets further complicated by the fact that some people not visibly active in public more than pull their weight behind the scenes - the testimonials Maxim received when running for re-election being a prime example. Best, Barkeep49 (talk) 00:00, 3 December 2024 (UTC)
- During my first term it was Roger Davies. He was barely a presence on-wiki but he kept the whole committee on point and up-to-date about what was pending. Trypto is right that it isn't enforceable, it is more a matter of applying pressure to either do the job or move oneself to the inactive list.
- I also think the committee can and should be more proactive about declaring other arbs inactive even when they are otherwise present on-wiki or on the mailing list" That would probably require a procedures change, but I think it would make sense. If there is a case request, proposed decision, or other matter that requires a vote before the committee and an arb doesn't comment on it for ten days or more, they clearly don't have the time and/or inclination to do so and should be declared inactive on that matter so that their lack of action does not further delay the matter. It would be nice if they would just do so themselves, or just vote "abstain" on everything, which only takes a few minutes, but it seems it has not been happening in practice. Just Step Sideways 00:14, 3 December 2024 (UTC)
- And Roger was a pensioner which kinda proves my point -- Guerillero 08:53, 4 December 2024 (UTC)
- Roger may have been a pensioner at the end of his time on the committee (7 years), but he certainly wasn't at the beginning of his term. He was co-ordinating arbitrator for a lot of that time, and did a good job without a single bit of extra software. The problem with that software is that people have to already be actively engaged to even contemplate using it. My sense is that the real issue here is the lack of engagement (whether periodic or chronic) on the part of many of the arbitrators. People who are inactive on Arbcom tasks aren't going to be active on any tasks, including reading emails asking them to do things or special software sending alerts. Simply put, if people aren't going to put Arbcom as their primary Misplaced Pages activity for the next two years, keeping in mind other life events that will likely take them away, they should not run in the first place. Yes, unexpected things happen. But I think a lot of the inactivity we've seen in the last few years involved some predictable absences that the arbs knew about when they were candidates. (Examples I've seen myself: Oh, I have a big exam to write that needs months of study; oh, I have a major life event that will require a lot of planning; oh, I'm graduating and will have to find a job.) No, I don't expect people to reveal this kind of information about themselves; yes, I do expect them to refrain from volunteering for roles that they can reasonably foresee they will have difficulty fulfilling. Risker (talk) 04:21, 6 December 2024 (UTC)
- I might as well ask a hard question. Is there a way to make public enough information for the community to be able to evaluate ArbCom candidates for (re)election, in terms of behind-the-scenes inactivity? If individual Arbs were to make public comments, that would do it, but it would also potentially be very contentious and could reduce effectiveness instead of improving it. Could ArbCom initiate a new process of posting onsite information about the processing of tasks, without revealing private information (such as: "Ban appeal 1", "Ban appeal 2", instead of "Ban appeal by "), and list those members who voted (perhaps without listing which way they voted)? Maybe do that monthly, and include all tasks that had not yet gotten a quorum. Yes, I know that's difficult. --Tryptofish (talk) 20:48, 6 December 2024 (UTC)
- I question an answer to the problem of "we're having trouble finding enough people to do the secretarial work we have already" being "let's create substantially more secretarial work" even accepting the premise that people would then get voted off if they didn't pull their weight. While I think that premise is correct, what this system would also encourage - even more than it already exists - is an incentive to just go along with whatever the first person (or the person who has clearly done the most homework) says. And that defeats the purpose of having a committee made up of individual thinkers. Best, Barkeep49 (talk) 20:55, 6 December 2024 (UTC)
- That's a fair point. I'll admit that, even from the outside, I sometimes see members who appear to wait to see which way the wind is blowing before voting on proposed decisions. --Tryptofish (talk) 20:59, 6 December 2024 (UTC)
- That's something that's hard to know or verify, even for the other arbs. The arbs only know what the other arbs tell them, and I've never seen anyone admit to that. Just Step Sideways 23:44, 6 December 2024 (UTC)
- 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)
- 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)
- 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)
- 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)
- And Roger was a pensioner which kinda proves my point -- Guerillero 08:53, 4 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)
- 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 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)
- 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)
- 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)
- 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)
- 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)
- 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)
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)
- 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)
- 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)
- 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)
- 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 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)
- 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)
- Yeah, these are great questions. Responses to your points:
- 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)
- @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)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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)
- The original announcement of the Coordinating Arbitrator position was here. Regards, Newyorkbrad (talk) 21:29, 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)