Disclaimer: This page expresses my personal opinions and observations only. I encourage all voters to do their own research on the candidates.

Alert: Just before voting began, current arbitrator Beeblebrox was suddenly suspended from the Arbitration Committee due to conduct violations, with a vote of 11-0. Details here. Since his 2-year term was ending anyway, and he said he wasn't planning on running again, this does not affect the current election, except that ArbCom voted that he can run again after six months. So, he might choose to run again in 2024. Stay tuned . . .

Voting is now closed, and the results should be posted some time in late December.

Overview

edit

For those who aren't sure what this is about: The Arbitration Committee is part of the Wikipedia dispute resolution process. In fact, ArbCom is pretty much the last stop. For a general real world analogy, ArbCom is sort of like the Supreme Court of Wikipedia. The arbitrators don't make decisions on article content, but they do issue rulings on complex disputes relating to user conduct, and they have considerable authority within the wiki-culture. Members of the Committee are usually elected for two-year terms (sometimes one or three), with a new batch elected each year.

In September 2023, an RfC took place concerning the format of the 2023 elections, at Wikipedia:Arbitration Committee Elections December 2023/Candidates.

Candidates self-nominated from November 12 to 21, and the voting period will run from November 28 to December 11. For details on voting eligibility, see the 2023 election page.

For this 2023/2024 cycle, there are up to eight empty seats, for candidates who will be elected for either a one-or two-year term, with a minimum of 50% or 60% support, respectively. For details on required percentage of support, check here.

User:Z1720User:ToBeFreeUser:SdrqazUser:MaximUser:HJ MitchellUser:FireflyUser:CabayiUser:AoidhUser:Worm That TurnedUser:WugapodesUser:Opabinia regalisUser:IznoUser:EnterpriseyUser:Donald AlburyUser:CabayiUser:BeeblebroxUser:SilkTorkUser:PrimefacUser:MoneytreesUser:L235User:GuerilleroUser:GeneralNotabilityUser:CaptainEekUser:Barkeep49User:PrimefacUser:MaximUser:L235User:BDDUser:BradvUser:CaptainEekUser:Barkeep49Wikipedia:Arbitration Committee Elections December 2023Wikipedia:Arbitration Committee Elections December 2022Wikipedia:Arbitration Committee Elections December 2021Wikipedia:Arbitration Committee Elections December 2020

My standards

edit

This page that you are reading contains my (Elonka's) thoughts on the current crop of ArbCom candidates. My general standards for a candidate are:

  • Admin access
  • Integrity
  • Experience with article-writing
  • Time-available for the project
  • Hands-on knowledge of the dispute resolution processes.

I am also a strong supporter of civility, as I believe that rude behavior on the project can drive away other editors, and I would hope that ArbCom would help support that view; however, I also understand that not everyone has the same feelings about civility, so I am willing to support arbitrator candidates for other reasons than just that one.

Past votes

edit

To see my thoughts on previous elections, check:

Candidates

edit
Note: Voting is now closed, and the results should be posted some time in late December.


  1. ToBeFree (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Administrator since 2019. My one quibble would be about article-editing, they don't seem to have brought any articles up to Good or Featured status.
  2. Firefly (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Two RfAs, one over a decade ago in 2008 under the name Richard0612 when he was a new editor, and one with unanimous support in 2022.
  3. Aoidh (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Has only been an admin since March 2023, but is very active on the project.
  4. Z1720 (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Has only been an admin since August 2022, but has strong article-editing experience, as well as experience with dispute resolution.
  5. Maxim (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Past arbitrator.
  6. HJ_Mitchell (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Trusted member of the community with Oversight access. Has been through RfA process three times: 2009, 2010, 2011.
  7. Sdrqaz (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Support. Admin since March 2022.
  8. Cabayi (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Weak support. Current arbitrator, already a trusted member of the community. I do wish they had a bit more article-writing experience, bringing at least one article up to Good or Featured status, but Cabayi does so much other good work on the project, that's not really a reason to oppose. However, the fact that Cabayi is one of the arbitrators who voted to expel Beeblebrox puts just enough of a question in my mind, that I can't fully support at this time.
  9. Robert McClenon (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Oppose. Needs to garner community support to become an administrator, before trying to become an arbitrator.
  10. Wugapodes (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) statementquestions
    Weak support. Current arbitrator, already a trusted member of the community, but there is so much chaos related to the Beeblebrox situation, that I am not comfortable fully supporting at this time.