User:Elonka/ACE2024

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 2024, an RfC took place concerning the format of the 2024 elections, at Wikipedia:Arbitration Committee Elections December 2024.

Candidates self-nominated from November 3 to 12, and the voting period will run from November 19 to December 2. For details on voting eligibility, see the 2024 election page.

For this 2024/2025 cycle, there are nine 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.

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.

To see my thoughts on previous elections, check:

1. CaptainEek (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    Y Support. Current arbitrator.

2. Daniel (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    N Weak oppose. Past ArbCom clerk, and longtime admin, then requested a de-sysop on 29 October 2024, in part because he needed a wiki-break. So, I am opposing both because he is not currently an admin, and also because if he doesn't think he has time to be an admin, he definitely does not have time to be an Arb. That said, if Daniel does have time, and takes back the admin bit, he could be a good arb.

3. Elli (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    Y Support. Strong RfA, 207/6/3 in June 2024. Hasn't been an admin for very long, but on looking through Namespace contribs, appears to have a nice well-rounded view of different areas of the project, including article-writing.

4. Guerillero (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    Y Support Current arbitrator.

5. Just Step Sideways (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    N Oppose. This is the new username of User:Beeblebrox, who has been involved in controversies in the past. A previous arbitrator, shortly before the 2023 ArbCom election he was suspended due to conduct violations, with a vote of 11-0. At the time, ArbCom voted that he could run again after six months, so here he is again, but under a different name. Details in a December 2023 Signpost article can be read here.

6. KrakatoaKatie (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    Y Support Past arbitrator.

7. Liz (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    Y Support. Has been an admin since 2015, and also an ArbCom Clerk.

8. Primefac (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

    Y Support Current arbitrator.

9. ScottishFinnishRadish (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

   Undecided. Had a somewhat controversial RfA in 2022 that also required some Bureaucrat weigh-in. I haven't yet taken a look at the backlog to get a good sense of what was going on.

10. Simonm223 (talk · contribs · count · logs · block log · lu · rfa · rfb · arb · rfc · lta · socks) • statement • questions

     N Oppose. Should become an administrator first, before trying for ArbCom.

11. Theleekycauldron (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

     Y Weak support. Had a very strong showing at RfA on 17 August 2023, her second, with a score of 313/1/2. Her first RfA in January 2022 was withdrawn with a final score of 95/50/13. Lots of good article work, especially at DYK. My only quibble is that I'm not seeing much hands-on work with the Dispute Resolution processes. There is still, however, enough reason for me to support.

12. Worm That Turned (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks) • statement • questions

     Y Weak support. Has been both an arbitrator and a bureaucrat in the past. Trusted member of the community, and knows what they're in for. However, practically no edits on the project since July 2023. Resigned as an Arb in Sep 2023, stating they were concerned about time-available. And now he's back again. So, if he's willing to prioritize wiki-work, I definitely support. I'm just not entirely certain that he could...