Jump to content

User:Maxim/ArbCom and desysops

From Wikipedia, the free encyclopedia

This page presents two tables on all ADMINCOND cases, as well as other cases where specific administrators were sanctioned, from 2010 to present. The purpose of compiling this data was to assess the likelihood of an admin "getting off" when the subject of an accepted ADMINCOND case. During the review, it became useful to additionally note other cases, typically broader in scope, that have resulted in a specific administrator being sanctioned. A full survey of Wikipedia:Arbitration/Index/Cases was performed from 2010 to present. The cut-off year of 2010, while slightly arbitrary, was used because it is when the committee could be said to have "matured". At this point, it started to take on significantly less cases per year (30 in 2009, 14 in 2010), and to not take "easier" cases that could be more easily handled by the community. A cut-off also helps compare like to like with respect to expected standards of administrator conduct, which have changed with time.

Some preliminary findings as follows:

  • The Arbitration Committee, on average, hears 3 ADMINCOND cases per year.
  • Since 20122013, there has been a precipitous decline in administrators being sanctioned during cases with a broader scope.
  • The chances of an administrator avoiding a loss of permissions as a central party to a case are very poor. While 5 of the 41 listed cases (~12%) did not end up in a desysoping or resignation, consideration must be made for some of these cases that weren't quite purely ADMINCOND cases (e.g. Magioladitis, Gamaliel and others) or where the final decision suggests that perhaps the case ought not have been accepted (Michael Hardy). As far as cases that most fit the mold of having a scope to "examine an administrator's conduct with regards to ADMINCOND", GiantSnowman is the only strong example of administrator not being desysoped as a result of such a case.

And some further thoughts (19 November 2021):

  • The idea to tabulate this data probably came out of some combination of an arbcom-en thread which was sort of a post-mortem on the RexxS case and an Iridescent-talk megathread. While there was a range of topics in those discussions—from case naming to RfA reform—the overall context was the aftermath of the contentious RexxS case.
  • The numbers are just that: numbers. This essay just appears to be the first time someone went and tabulated the outcome of what can be construed as "modern" ADMINCOND cases. I'm not trying to pass any value judgment on the numbers, but to give a population analysis for a given definition of a "modern" ArbCom.
  • I didn't consider declined cases, nor did I consider similar ANI threads, because that wasn't really the point of the table. To be specific, the point was to answer what happens if an administrator is involved in an accepted arbitration case, particularly an ADMINCOND one. Dear reader, you may make of these numbers what you will.

Further thoughts, 5 June 2023:

Another update, 18 June 2026:

  • Since late 2024, involuntary desysops overwhelmingly go through the administrator recall process. ArbCom remains a possible venue, but recall is a much lower-friction venue.
Table 1: ADMINCOND-style cases
YearCaseResult
2026PbsouthwoodSuspend and desysop
2024MzajacSuspend and desysop
2023AlisonWDesysop
2023ScottywongDesysop
2022StephenLEVEL2 desysop overturned[1]
2022Reversal and reinstatement of Athaenara's blockTwo admonishments, loss of CU and OS
2022GeschichteSuspend and desysop
2022JonathunderSuspend and desysop
2021Carlossuarez46Suspend and desysop
2021RexxSDesysop
2020RHaworthDesysop
2020KudpungDesysop
2019FramDesysop[2]
2019Reversion of office actionsAdministrator resigned[2]
2019RamaDesysop
2019EnigmamanDesysop
2019Alex ShihSuspend and desysop
2019GiantSnowmanRestriction on tool usage
2018Fred BauderDesysop
2018AndrevanResignation
2017Arthur RubinDesysop
2017Magioladitis 2Desysop
2017MagioladitisEditing restriction
2016The Rambling ManResignation
2016Michael HardyReminder for administrator and committee
2016Gamaliel and othersTwo administrators admonished
2016Kevin GormanDesysop
2015NeelixResignation
2015Kww and The Rambling ManDesysop (Kww)
2015Sockpuppet investigation blockDesysop (Chase me)
2015Toddst1Inactivity removal under cloud
2015WifioneResignation and ban
2014DangerousPandaDesysop
2014KafzielDesysop
2014NightscreamDesysop
2013Kiefer.Wolfowitz and IronholdsDesysop
2013SchuminWebSuspend and desysop
2012FaeResignation and ban
2012Rich FarmbroughDesysop; another administrator admonished
2011Cirt and Jayen466Desysop, I-ban and editing restrictions
2011RodhullandemuDesysop and ban[1]
2010MZMcBride 2Resignation and admonition
Table 2: Broader-scope cases
YearCaseResult
2025Article titles and capitalisation 2Administrator warned
2025Palestine-Israel articles 5Administrator warned
2024Conflict of interest managementLoss of administrator and bureaucrat permissions
2023Industrial agricultureAdministrator admonished, restricted
2020MedicineAdministrator topic-banned
2020PortalsAdministrator desysoped
2018Conduct of Mister Wiki editorsAdministrator desysoped/resigned
2015Arbitration enforcement 2Administrator admonished
2014Media Viewer RfCAdministrator resigns
2013Ebionites 3Administrator resigns, topic-banned, I-banned
2013Manning naming disputeAdministrator admonished
2013InfoboxesAdministrator admonished
2013Tea Party movementAdministrator admonished
2013DoncramAdministrator admonished
2012PerthTwo administrators admonished, one administrator desysoped
2012TimidGuy ban appealAdministrator desysoped and banned
2012Civility enforcementAdministrator desysoped
2011RacepacketAdministrator admonished
2011AE sanction handlingAdministrator advised
2010Climate changeMultiple administrators sanctioned

Notes

[edit]
  1. 1 2 Case was largely off-wiki
  2. 1 2 Fram-related, may be useful to disregard as gross outlier

See also

[edit]