Jump to content

Stewards/Confirm/2025

From Meta, a Wikimedia project coordination wiki
(Redirected from SC)

Translate this page at Template:Steward confirmations.

Warning

The 2025 steward elections are finished. No further votes will be accepted.

The 2025-26 Confirmation will begin on 06 February, and will finish on 27 February.

The 2025-26 Steward Confirmations are an opportunity for the Wikimedia community to comment on the performance of existing stewards. To make the process as smooth as possible, the confirmations are organized as follows.

To comment, please log in with an account that has edits (on any wiki) before 06 February. During the 2025 Elections, please mention if you are comfortable or unhappy with the use of steward tools of any of the people listed below and why.

After the election, stewards (including the newly-elected ones) are invited to review the confirmation comments and to give their impression of the outcome (consensus to confirm/remove etc.) on Talk:Stewards/Confirm/2025 for every steward who stood for confirmation. Of course, they are not required to do this for every candidate and will be especially careful to do it regarding someone about whom they expressed strong opinions in the confirmation. Non-steward comments are welcome outside of the "Final Decision" section, subject to the usual expectations of civility. Confirmation discussions will last one week after the appointment of the newly elected stewards. This may be extended to two weeks for one or more confirmations at the discretion of the Election Committee if the committee believes further input is required before concluding. The Election Committee will close these discussions and implement the outcome (which also means making a decision in non-obvious cases).

All stewards elected before February 2025 will undergo this process.

See also:

Purge the cache of this page?


Stewards should create their statements. They can use the preload below:



logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en-N, fr-3
  • Personal info: Hello everyone! I have served as a steward from 2014-2020, and again from 2024 to present. Over the last year, I have focused on responding on the various steward requests pages, and fall in the middle range of stewards by activity. Since the end of the summer I have also served on the U4C, and while I am slightly over-extended in my current wiki-obligations, I think it is useful to have an (active) steward on the U4C. I am also one of the more active stewards in our regular engagement with the WMF on various topics, including temporary accounts. With your support, I would be happy to continue to serve as a steward for this next year, and I am also happy to respond to any questions or hear any concerns you may have (including those privately raised, either through email or on Discord). Thanks for your consideration, – Ajraddatz (talk) 00:36, 16 January 2025 (UTC)[reply]

Comments about Ajraddatz

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: pt, en-3
  • Personal info: Hello everyone! This is my first confirmation as a steward, so I would like to take this opportunity to thank the community for the trust given to me. I have not been as active as I would have liked, mainly because all of our request queues have been quickly emptied, even faster than my mouse can click. Despite this, I am (almost) always available and I try to solve all demands that are presented to me, whether on-wiki or off-wiki, whether complex technical issues or simple doubts, whether participating in meetings with the foundation, or just responding to messages via Telegram. ━ Albertoleoncio Who, me? 13:43, 31 January 2025 (UTC)[reply]

Comments about Albertoleoncio

[edit]
After demonstrating good judgement and no evidence of abuse was proven, I'll be Neutral Neutral now. Will definitely be a remove vote next year if activity levels do not improve. --Stïnger (会話) 19:53, 24 February 2025 (UTC).[reply]
On third thoughts, I'm striking my remove – willing to give Alberto another year but I do agree with most of the arguments for removing; will probably caption= abstain. //shb (tc) 23:13, 23 February 2025 (UTC)[reply]
Base on respond of answers and voice from other steward, switching to  Weak keep. aqurs ❄️ 15:53, 9 February 2025 (UTC)[reply]
Keep Keep, albeit less strong than other votes. After a lot of extra thought, and given the arguments and additional information by Vermont and Ajraddatz, I'll change my initial vote; there's indeed a valid explanation for the activity level, other stewards have confirmed participation in internal channels, and at the end of the day there's nothing else that would make me lose confidence to you. In my original vote I said I would most probably welcome/support a future request, but there's no obvious benefit for the community and the project not to give that chance now instead. I'm covered by your response below. Good luck. KonstantinaG07 (talk) 00:17, 8 February 2025 (UTC)[reply]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en, fr-2
  • Personal info: I'm AmandaNP, and this is my 4th steward confirmation. I have worked over the past year to continue to make an impact with almost 6000 actions this year, particularly in proxy blocks or spam-level networks. This past year, my work has started moving toward being more on an advocacy level and providing advice on years of experience. I will note my activity has dropped this year, especially as of late because of a role at my job that I started at the start of the last steward election. I'm starting to roll into a comfort into the role, and hope to have more activity within the next few months. In the meantime, my role will focus on contributions that push quality over quantity, and assist in the onboarding of new stewards, guiding the existing path, and helping driving the future. -- Amanda (she/her) 07:04, 31 January 2025 (UTC)[reply]



    At this point in time, I appreciate the support I may get to continue as a steward. A lot of my steward work has become advocacy work due to the nature that the work is changing, and while that is normally a very engaging topic for me, other parts of my life are draining that battery to have the energy to do it to start. It can be evidenced by edits not even making it to 25 last month. I also had to lay question to the imposed 31 January deadline for this statement. It's not fair to the community that I continue on this year, with no date in which things will improve. I hope to run in future years, but this year, I will not be running for confirmation. -- Amanda (she/her) 02:18, 4 February 2025 (UTC)[reply]

Comments about AmandaNP

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en-N, fr-2
  • Personal info: Hello! I was elected as a steward in 2022, this is my third confirmation. My activity this year has continued to focus on response to active abuse, as well as helping with VRT and ACC requests. I am also an active and regular participant in the monthly steward meetings, the mailing lists, and other discussion spaces. Since last year, I became an administrator of the Wikimedia Community Discord server and now serve as its coordinator. Due to a combination of external factors, it is difficult for me to make forward-looking statements about the next year, but I hope to remain active. With the community's support, I would be glad to continue to serve as a steward. AntiCompositeNumber (talk) 00:45, 26 January 2025 (UTC)[reply]

Comments about AntiCompositeNumber

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: uk-N, ru-4, en-2.5, be-3 (understanding only), es-0.5, slavic-0.5, nl-0.25, romance-0.25
  • Personal info: Hello. This seems to be my sixth confirmation.

    This year my activity was even worse than before, mostly due to my personal circumstances changing for the worse because of having a very unstable internet access both in actual connectivity availability and in ability to utilise it when available, all of which is the result of my country taking away a bunch of my human rights and forcing me to be where I do not want to be and do the job I do not want to do.

    When I can, though, I still try to keep my finger on the pulse of the Wikimedia world, and that includes the steward bit. In those few actions that I did do this year, which are SRP, SRGP actions, some responses to off-wiki requests and information and I think I also participated in one of the stewards—WMF calls and occasional input on stewards' role in public Wikimedian centred chats, I do see value, as I feel like my experience around some areas, especially permissions management, as well as my better connection to some of the language communities (mostly intersecting with Mykola7), is helping the communities. My return to a more reasonable activity is now even more dependent on the change in the circumstances my country is facing, it is up to the community to decide whether it makes sense to tolerate it as it is now or not.

    As always, be I confirmed or not I would still be around Meta and steward-related things.

Comments about Base

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: English
  • Personal info: Hello everyone. This will be my 14th year of being a steward and my 13th confirmation. This past year I have been focused (along with my peers) on handling the threats the Wikimedia projects face which include crosswiki vandalism and spam (which has been increasing). I have been plenty active as a steward these past 14 years and plan to continue.

Comments about Bsadowski1

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: de, en-3, es-1
  • Personal info:
    Hi again, I’ve been a steward since 2007 and changed my field of work a couple of times. Nowadays, my main focus lies on supporting the governance the group which mainly takes place in the background. For example, since my last confirmation I served in the Steward Election Committee, reviewed candidates for some Wikimedia Foundation committees, held presentations about steward-related activities, joined several meetings with WMF staff and tried to be available on all communication channels (IRC/Discord, email, stewardwiki, …).
    Furthermore, I'm co-contact for the Wikimedia Stewards User Group whose annual report of the group I wrote for which I have to be up to date in all fields of Stewards’ works. In this role, I have represented the group at the Wikimedia Summit 2024 and Wikimania 2024 where my long-time commitment as a Wikimedia Steward was recognized as the 2024 Wikimedia Laureate of the Year. You can read more about my steward work in this related Diff blog post.
    My other field of work is also one of those that is often not completely visible in public logs: When I am around and find an obvious or familiar long-term abuser, I try to be quick and stop them immediately. This often affects activities that have to be suppressed and therefore are not publicly logged. Although this is not my main focus area, I'm still performing some hundreds of logged actions on Metawiki, loginwiki checkuser actions and suppressed actions per year and try to support my colleagues who are more active there. My main focus as an active contributor to Metawiki where I'm holding some additional rights, are CentralNotice banner campaigns.
    Altogether, I'm filling some of the gaps and bring in some expertise from the early years and good connections to WMF as well. It'd be my pleasure to continue this service for another term in my 20th year in the Wikiverse.

Comments about DerHexer

[edit]
Striking out my keep vote per Special:Diff/28286933. Won't replace it with anything, though. Nothing wrong with DerHexer regarding trust, but it did leave a bad taste in my mouth. //shb (tc) 04:30, 19 February 2025 (UTC)[reply]
Comment striked out. Aopou {talk} 23:37, 18 February 2025 (UTC)[reply]
Comment striked out. --Galahad (sasageyo!)(esvoy) 23:33, 18 February 2025 (UTC)[reply]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages:
  • Personal info: I've been a steward since the elections last year. I found myself having quite a hard time getting to know stuff in the beginning, one of the reasons being that I didn’t have any functionary experience, and I made quite some mistakes because contrary to how I had planned I had taken too quick of an approach, but I feel that the more time that has passed the more familiar I have become with the toolkit and stewarding in general.

    With that being said I've been one of the most active stewards this year and performed over 60,000 actions in total, and I’ve been the steward with the most loginwiki checks this year. Most of my usage of the tools has went towards helping at Steward requests pages, as well as handling IRC requests and emails sent to the VRT oversight queue. I'm also one of the list owners of the global renamers' mailing list, and therefore I also help out in that end.

    I had thought a lot about whether to run for confirmation or not, but I believe I've proved the opposition in my initial candidacy wrong and continue to find myself making good use of the tools, and I'm willing to continue serving for another year if the community wants it that way. Let me know if you have any other questions or concerns you want me to respond to. EPIC (talk) 00:00, 15 January 2025 (UTC)[reply]

Comments about EPIC

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: pt, en-2, es-1
  • Personal info: Hello everyone. I was elected in 2017. I have been active in the past year, mainly handling cross-wiki abuse/vandalism/LTAs/spammers/spambots and processing oversight requests. I would like to continue to help out as a steward for another year if the community is willing to confirm me. Please feel free to ask any question or provide feedback. Thank you for considering. — Elton (talk) 21:16, 30 January 2025 (UTC)[reply]

Comments about Elton

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: tr, en-3, az-3, es-2, de-1
  • Personal info: Hello everyone,

    I am HakanIST. Over the past year, I have remained active in steward duties, focusing on addressing vandalism, supporting Wikimedia projects with increased activity. I've been available on IRC throughout the year and I've also monitored VRTS, and helped with handling tickets. I'm also serving as a member of Elections committee. I'd like to serve another year with the same amount of activity.

    Thank you for your consideration.

    HakanIST

Comments about HakanIST

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: es, en-3, ca-2
  • Personal info: Hello, everyone.

    As much as I would love to continue, I will step down this year. I thought I was able to resume my usual activity quickly. Unfortunately, the problems that made me unable to be active persist and multiplied, alongside some health-related issues that I have been burdened with for almost a decade but progressed over the past year. However, I still intend to continue helping in other areas.

    Thanks to everyone I have worked with; it has been an honour and a pleasure serving with everyone who works on this movement, and I wish you all the best of luck. Best, Sgd. —Hasley 16:03, 31 January 2025 (UTC)[reply]

Comments about Hasley

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en-3, de
  • Personal info: Hello! I am a Wikimedian since 2008 and a steward since 2014. In addition to my on-wiki work, I am or have been active in several other areas around Wikimedia, including volunteer software development (user scripts, MediaWiki extensions, …) and work on Wikidata.

    In addition to my volunteer activities, I'm employed by Wikimedia Germany as a software developer for Wikidata.

    Last year, I have primarily processed requests for global locks and blocks and participated in small wiki monitoring and spam fighting, helping smaller communities clean up after spam bots and vandalism. This year, I plan to to keep up my work on handling the backlog of global lock and block requests, while also dedicating time to volunteer software development for steward related MediaWiki extensions, tools, and my user scripts. Cheers, Hoo man (talk) 17:40, 2 February 2025 (UTC)[reply]

Comments about Hoo man

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en-N
  • Personal info: I am seeking confirmation for my second term. Since being elected last year, I performed ~9,000 publicly logged Steward actions, performed ~750 checks on loginwiki, closed ~1,200 Steward VRT tickets (excluding a mountain of spam/junk), and closed many global UTRS appeals. I have routinely provided feedback to the WMF on projects that (may) impact Steward tools/work.
    I expect my activity to be similar over the next year. I will continue to be available on IRC and, if really necessary, Discord.

Comments about JJMC89

[edit]
Neutral Neutral pending responses to questions and criticism; JJMC89 indeed did a good job as a steward, but communication and accountability are two key points as well. --Stïnger (会話) 23:51, 16 February 2025 (UTC).[reply]
Switching to Remove Remove for being unresponsive for 20 days(!) already. It seems they've been inactive since the confirmation started. I expect stewards to be responsive and take the feedback that the community is giving—and on time— which unfortunately this seems not to be the case. --Stïnger (会話) 16:40, 26 February 2025 (UTC).[reply]
  • Question Question: Your handling of the recent Feeglgeef case on Wikifunctions was quite frankly, poor, including 1 block that you are clearly not permitted to make (Special:Redirect/logid/58453510) as per Meta:Meta–steward relationship and rejecting a resignation (which stewards cannot really do...which in turn resulted in the ex-admin turning abusive). How do you think you'll address such situations going forward without a "my way or the highway" approach? //shb (tc) 14:06, 6 February 2025 (UTC)[reply]
    Given the lack of a response and JJMC having been active on-wiki since 14:06, Feb 6 (see w:en:Special:Diff/1274363337, made on 23:00 UTC the same day), I am voting a strong remove. JJMC's unwillingness to handle criticism, poor attempts of collaboration, poor communication, the enwiki OS issue, the Feeglgeef case, and going by a smart kitten's comment, the phab cases, the number of controversies is far too many for someone's first year as a steward. //shb (tc) 22:40, 8 February 2025 (UTC)[reply]
  • Keep Keep - XXBlackburnXx (talk) 14:16, 6 February 2025 (UTC)[reply]
  •  Weak keep --V0lkanic (talk) 15:36, 6 February 2025 (UTC)[reply]
  • {{k}} On SHB's note I've also noticed similar stuff from JJ which could seem like overriding or reversing other stewards' actions. One of the cases that I am the most disappointed about was the Seckends case. I initially locked the account for lock evasion, but some time later when they appealed their lock JJ unlocked - not because of the appeal but because I had provided "no clarification of lock evasion" in the lock summary. After I responded in the VRT ticket for clarification JJ still refused to re-lock. Granted, I should have provided information in the lock summary about who the "evader" was, but in situations like this I find it better to leave the user in question a note to clarify (such as this), before taking action, because communication is important, especially as a steward. However, I am still leaving a keep comment, as I find them active enough and they've been especially helpful for stuff like VRT/UTRS and as a checkuser-l list owner. EPIC (talk) 15:43, 6 February 2025 (UTC)[reply]
    {{neutral}} For now pending response to questions and the criticism here. As a fellow steward myself, I can confirm I've experienced similar stuff from my side, both the "my way or the highway" approach and their communication style, even with other stewards. With all that combined with the stuff that's come up here as well which I was previously unaware of, I would want to see an explanation. However, this is more of a conditional neutral pending a response - I'm willing to switch to keep should they explain this well. EPIC (talk) 13:54, 8 February 2025 (UTC)[reply]
    I just want to leave an additional note that the Seckends and Feeglgeef cases aren't the only cases of "overriding other stewards" - there are several of these that I've noticed during the time I've been a steward with JJ, particularly around my actions. I don't know if this has to do with any bias against me or just the fact that I have been performing a large amount of this year's actions - but I simply can't overlook the firstly mentioned , because, I'm going to admit, I've felt a bit uncomfortable with JJ's communication style towards me in private communication channels. I'm not alone in that - that communication style isn't really limited to me, but I've felt like I've been a "main target", which might also have to do with me being one of the more active stews. I'll add that JJ did provide some extra context around the Feeglgeef deal in the stewards' IRC channel, but I unfortunately found it more on the defensive side there as well (basically "my decline should stand"). With that being said I'd still like to see their response. EPIC (talk) 21:49, 12 February 2025 (UTC)[reply]
    Switched to remove, see below. EPIC (talk) 12:13, 13 February 2025 (UTC)[reply]
  • Keep Keep JrandWP (talk) 16:35, 6 February 2025 (UTC)[reply]
  • Keep Keep Not familiar with the whole situation so may change my !vote later if more comes up. I personally don't have too much of an issue with the partial block because it's exclusively on a steward page, and if someone is being uncivil on a steward page, I don't see why the stewards can't deal with it directly. --Ferien (talk) 19:06, 6 February 2025 (UTC)[reply]
    Yeah, I've just familiarised myself with the situation. Remove Remove, and a strong one at that. No thanks. The discussion is at Steward requests/Permissions/2025-01#Feeglgeef@wikifunctionswiki 3 for those interested in it. On this discussion, JJMC89 is virtually unresponsive to all criticism, while an admin is literally vandalising the site. JJMC89 then says that their resignation is conditional, even though he had been repeatedly reverting the admin's attempt to make the resignation unconditional! The logic of "let's not process this resignation even though they're being uncivil to me" is broken and the behaviour is appalling for a steward. The prying through oversight logs in enwiki and the following open criticism of an oversight action when he is not even an oversighter (linked below by A smart kitten) is very poor too. I don't want to endorse this sort of behaviour for a second term. --Ferien (talk) 13:40, 8 February 2025 (UTC)[reply]
    Just to be clear, as there has been some debate on a lack of response here, my remove suggestion is not primarily due to the enwiki oversight situation - it certainly is not banned by policy but looks poor, especially if you question an oversighter openly - nor due to the lack of answers here, because frankly, the Feeglgeef discussion already demonstrates a lack of accountability on its own to the stage I think a remove is necessary. The other poor decisions are additional reasons, but to reiterate, I'm not opposing based on whether JJMC responds here or not, he could be busy with real life at the moment. He had a chance to explain and/or apologise for his actions at the SRP request, and has had a month to do so otherwise, but during the discussion he persisted with the same flawed point and dodged comments the whole time, even as he saw the admin turning abusive (even blocking them locally) and others were starting to question his actions. Another point that doesn't seem to have been noted yet: JJMC asked EPIC not to override his decision when it arguably wasn't an override (JJMC said resign when you're ready, Feeglgeef made six further comments that clearly indicate that they were ready, JJMC was still not satisfied) yet saw absolutely no issue in overriding the lock EPIC gives above (Special:CentralAuth/Seckends) without any communication. If you aren't happy having your actions reversed without communication (primarily as a result of unclear explanation) then perhaps apply the same courtesy to other stewards. --Ferien (talk) 21:19, 12 February 2025 (UTC)[reply]
  • Keep Keep --Jan Myšák (talk) 19:54, 6 February 2025 (UTC)[reply]
  • Keep Keep per Ferien. Queen of Hearts (talk) 20:03, 6 February 2025 (UTC)[reply]
  • Keep Keep Aopou {talk} 20:14, 6 February 2025 (UTC)[reply]
  • Keep Keep Hey man im josh (talk) 20:25, 6 February 2025 (UTC)[reply]
  • Keep Keep Miniapolis 00:20, 7 February 2025 (UTC)[reply]
  • Keep Keep. Codename Noreste (talk) 00:26, 7 February 2025 (UTC)[reply]
  • Keep Keep HouseBlaster (talk) 02:50, 7 February 2025 (UTC)[reply]
  • Keep Keep Ternera (talk) 03:23, 7 February 2025 (UTC)[reply]
  • Keep Keep I don't believe that 'things turning abusive' was a result of JJMC89's actions, as the relevant user's behavior around January 9th, both on- and off-wiki, was generally erratic even before the SRP request. Mahir256 (talk) 05:27, 7 February 2025 (UTC)[reply]
    It was very much a case of an everyone sucks here situation, but the drama could have ended a day earlier had JJMC simply processed the resignation. The only reason why I have such an erratic block log on Wikifunctions is because of JJMC. //shb (tc) 11:35, 7 February 2025 (UTC)[reply]
  • Keep Keep --Lookruk 💬 (Talk) 09:48, 7 February 2025 (UTC)[reply]
  • There are a few things that cause me concern.
    • Firstly, in November, JJMC89 (who is not an Oversighter on the English Wikipedia) appears to have questioned an enwiki Oversighter on her public user talk page about a suppression action she took on that wiki. Due to the inherently non-public nature of suppressions, it feels iffy at best for a discussion about them to be held in public view; and the English Wikipedia's Oversight policy specifically states that [c]omplaints or inquiries about potential misuse of the oversighter user permissions should be referred to the Arbitration Committee. In addition, JJMC89 mentioned that he looked at the [enwiki suppression] log to know who to ask about reversing the suppression, but I don't understand why he did that instead of emailing the enwiki ArbCom, as the local policy says should be done with misuse enquiries.
    • Secondly, although I had noticed the Feeglgeef case mentioned by SHB2000 above, I was not previously aware of the block made on Meta-Wiki.
    • Thirdly, I have concerns regarding JJMC89's actions in security Phabricator tickets (which, if I understand correctly, he has access to in his role as a Steward). To my memory, I have had direct interactions with him in three security tasks, and all have been (in my opinion) less than ideal at the least:
      • in phab:T381442, he made several comments which (in my opinion) represent a lack of security consideration of the issue at hand;
      • in phab:T223501, he appears to have unilaterally closed as invalid a security issue that had been open for several years & had been reported by at least three separate people (including myself), with a closing summary that again (in my opinion) represents a less than full consideration of the matter at hand; and
      • in phab:T385792, he has made a comment which I believe does not show a full consideration of the situation from a security point of view.
      In my opinion, these comments matter, if for no other reason than because comments such as these in a security task may be some of the first responses that someone reporting a MediaWiki/Wikimedia security issue receives. Speaking personally, I remember it feeling quite exhausting in phab:T381442, when I felt that - in response to his comment - I had to further justify why the issue I'd reported was a valid security matter/one that needed action at all.
      I'm aware that these tasks won't be accessible to a majority of people reading this, for which I apologise; however, I'm raising them here as I feel that they are relevant to JJMC89's stewardship.
    Because of these, I am currently leaning remove, although I note that I am obviously personally involved with the Phabricator tickets I have mentioned above. ‍—‍a smart kitten[meow] 10:57, 7 February 2025 (UTC)[reply]
    Now to be fair with the Feeglgeef case, I did end up indeffing them based on further disruption, but IMO the nature of the initial block is very much that should be left to admins here as per Meta:Meta–steward relationship. Incivility blocks on steward-specific pages is not listed as an exception. //shb (tc) 11:34, 7 February 2025 (UTC)[reply]
    Comment Comment: Based on my experience, in practice questions about individual suppressions are just sent to the Oversight team or individual Oversighters instead of escalating to the Arbitration Committee immediately. The Oversight team generally has strong internal checks and balances, so queries sent to the Arbitration Committee are usually complaints of systematic abuse by an Oversighter instead of "can this suppression be undone?". Sdrqaz (talk) 21:02, 7 February 2025 (UTC)[reply]
    I reviewed the linked Phabricator tasks and they seem to be reasonable technical disagreement to me. I understand you have a different perspective than JJMC89, and given all three tasks are interrelated, it's spread out across multiple tickets, but if this were just a discussion about access to security bugs, I wouldn't be advocating for removal based on those three links. Legoktm (talk) 05:42, 8 February 2025 (UTC)[reply]
    @Legoktm: Thanks for taking a look at them -- I appreciate your reply & hearing your perspective.
    Like I say, I appreciate that I am personally involved with the tickets; however (for one of the examples), as my reply in T381442 may indicate, I think I felt quite shocked reading the comment JJMC89 left in that task saying that nothing should happen. To probably put it somewhat bluntly, I just couldn't really imagine how something that allows you to do what's described in that task's title & description could be thought to be an acceptable situation security-wise. That being said, I do note what you have said & I take it on board.
    In addition, the way in which T223501 was closed as invalid (without, e.g., a comment suggesting the action and asking for other opinions beforehand, in a ticket with the characteristics this one has) strikes me as a potential example of the inflexibility mentioned by arcticocean below.
    In terms of interrelatedness, I view the first and third as being more related than the second, which (trying here to intentionally word things as vaguely as possible!) I suppose could be said to be related in that it relates to the same underlying component, but to be honest I wouldn't have previously said that the second task was related to the others if I'd been asked.
    Thank you again for taking a look at the tickets - I appreciate you taking the time to do so. /gen ‍—‍a smart kitten[meow] 14:05, 8 February 2025 (UTC)[reply]
  • {{Neutral}} while I await candidate responses and consider other comments. While I commend JJMC89's dedication to the role, high activity is not a significantly important quality in stewards. Steward is an important role and not everybody is suited to it. I have concerns about JJMC89 as a steward, based on my observations the past year.
    • There is a communication style, a sort of "I'm going to do this, without warning or explanation" approach, that has caused issues.
    • There's also an inflexibility or reluctance to change position, listen, or engage with others.
    • There is also a tone issue: while everyone has their own style, JJMC89 often signals opposition without really explaining why or proposing a solution, which is subtly pernicious in an online community.
    Our steward elections do not effectively detect these kind of behaviours, because they manifest only once the user has the flag and starts interacting with others. But the behaviours have manifested this year and it is important to address them. --Arcticocean ■ 12:06, 7 February 2025 (UTC)[reply]
    • Remove Remove without opposition to re-election in future if there is improvement - (A) For years there have been concerns at his home wiki about disappearing during criticism of his actions or editing while ignoring it. That likely (the final decision-making is secret) led to his unsuccessful applications for CU in 2020 and 2022. For this confirmation, JJMC89 was online on 6 February (en.wiki) and 7 February (on UTRS) but has since disappeared. The benefit of the doubt of being busy offline only goes so far. (B) He frequently overturns other people without discussion, as other stewards and various people have said here, or steams ahead with doing something. This was also my experience on the Ombuds Commission, where it created problems several times. (C) The stern and unsettling tone is a permanent feature and has been previously highlighted to him, without improvement. Those are three significant concerns and confirmation this year would be highly controversial. At Masti's reconfirmation last year JJMC89 himself voted 'weak confirm' due to concerns about ignoring community concerns, so there is obviously an understanding of the problem, but this situation having lasted years and occurred on many more occasions is even more serious. Arcticocean ■ 10:46, 13 February 2025 (UTC)[reply]
      More unilateral overruling of another steward (in another context) followed by ignoring the subsequent comments challenging his actions: w:WP:VP/Archive 216. This behaviour has been all over every wiki for years and years. Arcticocean ■ 12:21, 14 February 2025 (UTC)[reply]
  • Keep Keep --cyrfaw (talk) 14:45, 7 February 2025 (UTC)[reply]
  • Regarding Arcticocean's comments, my feeling is that they're just being direct, and (as I noted when I voted on them in the SE2024 elections) some of their "rude-looking" actions have a sensible reason behind them, such as rejecting SRG requests with little to no context. That being said:
    • the incident that EPIC raised was not good. Even if EPIC technically made a mistake, you (JJMC89) should have checked with them. It's not like EPIC is inactive.
    • regarding the Feelgeef case, I can give slack to you for it. Refusing the resignation is OK, because the OP was making a mess of the whole situation and it's the OP's fault that the situation went out of control. As stewards cannot re-restore the rights once removed, asking them to be certain is reasonable. The block on the other hand was outside MSR but can be condoned in this instance.
    • The en.wiki oversight case was weird to see and while I do not consider JJMC89's explanation unreasonable and they didn't divulge anything that they shouldn't, it was outside of the rules.
    • I don't know what's in the phab tickets, so cannot comment there.
    Pinging @JJMC89: to give a response, which I expect from someone being reconfirmed as a steward. Leaderboard (talk) 15:41, 7 February 2025 (UTC)[reply]
    @Ferien's comment made me investigate this case a bit further. This revert is very weird and inappropriate to see, because you're reverting a steward? Why? It's not particularly uncommon for another steward to "take over" a pending case, even when you've previously declined it. I didn't also realise that Feelgeef was changing his own comment (he did make a mistake by not striking, but you could have checked with him). This needs a response from you or I'll oppose confirmation. Leaderboard (talk) 13:49, 8 February 2025 (UTC)[reply]
    Remove Remove - no response, no confirmation. Leaderboard (talk) 02:28, 13 February 2025 (UTC)[reply]
  • Keep Keep * Pppery * it has begun 16:11, 7 February 2025 (UTC)[reply]
  • I didn't support the candidacy in the first place mostly because of a gut feeling and would rather Remove Remove based on the concerns others have voiced. ~ ToBeFree (talk) 20:29, 7 February 2025 (UTC)[reply]
  • Keep Keep- Hasan (talk) 17:51, 8 February 2025 (UTC)[reply]
  • On the enwiki OS thing, I was aware of this at the time it was happening and was mildly surprised to discover that I don't think JJMC did anything wrong. The global oversight policy says ""Stewards can see oversighted revisions on all wikis and can grant themselves active oversight rights in emergency cases or on wikis without local oversighters when there’s a valid request."" (emphasis added) so I think the global oversight policy does allow him to have viewed the information he viewed. I also don't think the homewiki Steward policy applies (there was no action or user right granting involved). I think enwiki could amend our local policy in a way that would suggest Stewards should not use this outside of their actions as stewards (language along the lines of use "only while acting as a steward") but that would be about the future and not what JJMC did which I think followed the policy (and not for nothing was substantively correct about). Best, Barkeep49 (talk) 04:39, 9 February 2025 (UTC)[reply]
  • Keep Keep Helpful global user and steward. --نوفاك اتشمان (talk) 11:34, 9 February 2025 (UTC)[reply]
  • Remove Remove Here is my problem, I accept that the (allegedly abrasive) security bug comments might have a legitimate reason, the Feeglgeef case ha a legitimate explanation of why JJMC89 acted the way they did and the enwiki oversight case was technically within policy. However, the problem here is not that these incidents happened in the first place, but rather that adequate context/explanation was not given for taking these actions and criticism was not responded to. Even in this discussion itself, JJMC89, has had 3 days to respond to the variety of criticism levelled at them, but has not responded to a single comment. Instead, we have the commenters who are trying to reason and understand why they acted the way that they did. Now, I can understand if this was one case of having IRL commitments and that they weren't able to respond. However, having so many incidents with the first year to me implies a pattern of not taking criticism or responding to feedback/confusion about actions, which if exhibited on enwiki would potentially bring them to ANI or ArbCom (due to violating ADMINACCT). This kind of a pattern is incompatible with what we expect from stewards and that is why despite having complete confidence in JJMC89's technical capabilities, I cannot bring myself to support this reconfirmation and instead have decided to oppose it. -- Sohom (talk) 05:39, 10 February 2025 (UTC)[reply]
    We should be fair and recognise that Wikimedia is a charitable project and JJMC89 has not edited for a few days. People may have families, jobs, friends, other hobbies, even caring commitments. The confirmation process runs for two weeks and I am sure he will respond during it, when he's next available. Arcticocean ■ 09:13, 10 February 2025 (UTC)[reply]
    For the record JJMC was active on enwiki after my comment was made so it's hard to exactly justify using that as an excuse for not answering any of the questions asked about their controversial actions. //shb (tc) 12:01, 10 February 2025 (UTC)[reply]
    I get why you feel that way. On the other hand, a single edit on a different project (which is what he's done since your question) doesn't mean he had the time to come here and engage. I think it important to note that individual Stewards have no control over the timing of this process and so it may come at a time when they are less able to engage (and indeed the total amount of necessary engagement here might conversely make all replies slower). I am not trying to convince you to strike your oppose but want to reply so others don't get the wrong idea about JJMC's activity and in the hopes that we can, as articocean suggests, be kind to our fellow volunteers about their availability to participate in a process like this. Best, Barkeep49 (talk) 17:45, 10 February 2025 (UTC)[reply]
    I recognise that, but if you've done several major blunders as a steward, a reasonable and timely explanation is required – or at least a note saying that you're away and cannot respond until x date (which is more than understandable – we routinely do this on my home wiki). Seeing neither for what is the highest-risk role is what concerns me – and all the more so when communication was one of the core issues linking all of JJMC's controversies. //shb (tc) 04:45, 11 February 2025 (UTC)[reply]
    That's the key point here and is the major difference between this person and EPIC. EPIC did make some significant mistakes early on in his steward career, and there are still some lingering concerns in his SE2025 confirmation. However, EPIC has done well on resolving those concerns, and in particular makes an attempt to talk through and communicate whenever something wrong has happened (which is important - it's OK if ultimately there's a disagreement - what I want to see is a good-faith attempt). I'm still hoping that JJMC89 will respond - this indeed is a volunteer project, and real-life commitments could well be why we haven't seen a response from them. That's why I haven't formally voted yet. Leaderboard (talk) 10:06, 11 February 2025 (UTC)[reply]
  • Keep Keep --Ameisenigel (talk) 08:24, 10 February 2025 (UTC)[reply]
  • Strong remove, per Ferien. Not expecting drama from a stew, not answering questions is absolutely not appropriate. aqurs ❄️ 12:21, 10 February 2025 (UTC)[reply]
  • Remove Remove I don't like many of the situations outlined above. The Feeglgeef business alone isn't great, and particularly interactions with other stewards seem a bit, ahem, uncollaborative (per arcticocean's comment). The lack of response here is also not what I'd like to see from a steward. ProcrastinatingReader (talk) 17:48, 10 February 2025 (UTC)[reply]
  • Keep Keep Like I said in EPIC's confirmation, I'm lenient because the first year in a role is going to lead to mess ups (and some of them are not always easy to fix immediately). I am overall not concerned enough to remove at this time. Sennecaster (talk) 23:24, 10 February 2025 (UTC)[reply]
  • Remove Remove with regret. Activity looks good but not responding to questions or objections is not behaviour worthy of a steward. Svārtava (tɕ) 07:33, 11 February 2025 (UTC)[reply]
  • I've reviewed the concerns presented, and think I still land in the Keep Keep camp. I do think that JJMC89 should consider being a bit more tactful/polite in discussions, and if they have concerns with an oversighted revision they should ideally bring it up privately rather than publicly, but nothing listed above seems unrecoverable. I don't think that viewing a suppressed revision, even on enwiki, is outside of policy (either the global OS policy or the stewards' policy); this is a sensitive area, but as stewards are responsible for permissions management for functionaries (including the ability to do emergency removals), I wouldn't want to restrict the right of stewards to oversee and question suppression decisions within the scope of their responsibilities. I wouldn't expect a steward to be reviewing every suppressed edit on a project, and think that that would be going too far, but certainly examining suppressions that their attention is drawn to in some way seems fine. – Ajraddatz (talk) 09:52, 12 February 2025 (UTC)[reply]
  •  Weak keep – They've done good work this year as a steward, but the above concerns about a lack of response to objections and interactions with other stewards should be addressed. Chris ☁️(talk - contribs) 22:28, 12 February 2025 (UTC)[reply]
  • Keep Keep --M/ (talk) 09:47, 13 February 2025 (UTC)[reply]
  • I'm switching to a {{remove}} with a bit of regret. I had already previously brought up issues in this confirmation, but Arcticocean ultimately made me lean here for now. I feel like their comment shows that the concerns raised here, including the communication issues and them going inactive to avoid criticism, have been a long-term issue with numerous attempts at resolution without luck. Here we have several community members who have wanted to hear JJMC's side of the story and their response to the concerns, including myself, and they've had a lot of opportunity to address that here. But a week later, we have still heard nothing from them and they haven't been active anywhere since last week, neither on- nor off-wiki. I feel like it's important for stewards who expect to be confirmed that they take concerns into account, both from the community and from other stewards, and address them - and I just can't support someone who expects to be able to just "escape" it and still be confirmed. Combined with what I've already mentioned in my previous comments, I find this too serious to reasonably confirm at the moment, and I therefore change my opinion. All that being said, I've still appreciated their work and could still switch back to keep based on that - I just want them to properly address the concerns raised here, which hasn't been the case. EPIC (talk) 12:13, 13 February 2025 (UTC)[reply]
    After a lot of thought I'm doing a final switch to Neutral Neutral, even though it likely does not have much effect. My comment still applies for the most part and I'm still not very happy that there was no response - because I too would have been very happy to hear it - but I think JJ has done much good work as well, especially around VRT/UTRS and for the cu-l list. All that being said I simply don't feel like piling on anymore. EPIC (talk) 07:48, 27 February 2025 (UTC)[reply]
  • Remove Remove per concerns raised above and JMC's unwillingness to handle criticism, poor attempts of collaboration, poor communication.--Cactus🌵 spiky ouch 12:25, 13 February 2025 (UTC)[reply]
  • Remove Remove after reading all of the above. It has been a week since the first questions/concerns were posted and there has still been no response. This is a failure of accountability and looks like fleeing from criticism. Toadspike (talk) 14:57, 13 February 2025 (UTC)[reply]
  • Keep KeepDreamRimmer (talk) 15:42, 13 February 2025 (UTC)[reply]
  • Remove Remove -- as oper a number of other very knowledgable comments above. Scott Thomson (Faendalimas) talk 17:07, 13 February 2025 (UTC)[reply]
  • Remove Remove --Aca (talk) 20:34, 13 February 2025 (UTC)[reply]
  • Remove Remove. Subpar decisionmaking coupled with poor communication. -- Tamzin[cetacean needed] (they|xe) 08:33, 14 February 2025 (UTC)[reply]
  • Remove Remove - Sorry, the communication issues, as well as what Arcticocean mentioned above is enough for me to cast this vote. --Daniuu (talk) 16:23, 14 February 2025 (UTC)[reply]
  • Remove Remove poor communication on this very page about issues. JavaHurricane 17:00, 14 February 2025 (UTC)[reply]
  • Keep Keep - Per Ajraddatz --Seawolf35 (talk) 17:52, 14 February 2025 (UTC)[reply]
  • Remove Remove as per Epic and shb. Activity is one thing, behaviour is another. Honestly inactivity is a bit more forgivable. Ajraddatz's rationale just isn't good enough for me. All Tomorrows No Yesterdays (talk) 10:05, 15 February 2025 (UTC)[reply]
  • Remove Remove per lack of communication. Lepricavark (talk) 04:19, 16 February 2025 (UTC)[reply]
  • Keep Keep fully agree with Ajraddatz. 99% of what JJ did last year was of high quality and highly appreciated. The few (potential) mistakes do not justify removal for me. There are countless of possible reasons why they might not be able to respond at the moment. If this was their second/third/... confirmation where they don't respond to criticism, I would understand the votes to remove them, but it's their first year and no action so far is in any way problematic enough to remove, just because they didn't respond. --Johannnes89 (talk) 09:32, 16 February 2025 (UTC)[reply]
    Stewards are expected to be responsive as soon as possible – the issue isn't just they haven't responded here, the issue is they didn't respond at the request, or afterwards and they haven't responded even when their stewardship is on the line. In other words, this is the third opportunity they've failed to apologise/explain the problem. --Ferien (talk) 19:15, 16 February 2025 (UTC)[reply]
  • Remove Remove accountability within ~1.5 weeks should generally be compatible with having a life outside the Wikimedia Projects. Victor Schmidt (talk) 13:38, 16 February 2025 (UTC)[reply]
  •  Weak keep per Ajraddatz. –FlyingAce✈hello 22:18, 18 February 2025 (UTC)[reply]
  • Remove Remove per others here. Elli (talk) 18:37, 19 February 2025 (UTC)[reply]
  • Remove Remove I am not familiar with the incidents recounted above, although I do agree that the public posting of something that should have been confidential from the get-go, regardless of nothing substantive being shared, is very concerning (When I had the oversight tool, I was never contacted that way)

    If that were all there was, and JJMC had responded to these criticisms here in a timely fashion, I might still !vote keep.

    But it's clear from the mounting "removes", some from people I have the highest respect for and trust of, that this candidate has lost too much trust from the community to be retained as of the current moment. Daniel Case (talk) 19:30, 19 February 2025 (UTC)[reply]

  • Remove Remove, contingent that the steward fails to address concerns and questions outlined above. Lack of participation in this discussion is itself concerning. --Babegriev (talk) 07:31, 22 February 2025 (UTC)[reply]
  • Keep Keep per Ajraddatz. AramilFeraxa (talk) 19:46, 23 February 2025 (UTC)[reply]
  • Remove Remove due to poor communication. Previously, he declined task T379340 too quickly, stating that the tool was "not licensed under an OSI-approved Open Software license," without providing an alternative solution or giving me a chance to contact the user involved for potential tool adoption. Fortunately, the involved user has since added the license. However, I have been waiting for his response on this matter for over two months, and there has been no reply regarding the task to this day. Hakimi97 (talk) 12:02, 25 February 2025 (UTC)[reply]
    To be completely fair to JJMC89, I think that action was while wearing his hat of Toolforge standards committee member and not in his capacity as a steward. However, I agree with the rest of your rationale (particular the induction regarding poor communication). I think descision could have been communicated better. Sohom (talk) 15:22, 25 February 2025 (UTC)[reply]
    What I can personally conclude from the tool adoption task is that JJMC89 not only rushed to decline the task but also failed to follow up on subsequent responses in a timely manner. Not only does his lack of responses make things complicated (as I might need to seek advice from other Toolforge committee members), but it has also raised my doubts about whether he is capable of communicate professionally for the steward position. The steward role may have a greater and broader impact compared to that of a Toolforge Standards Committee member — not to say that I undermine the importance of the latter, though. Hakimi97 (talk) 18:55, 25 February 2025 (UTC)[reply]
  • Keep Keep --CFA (talk) 02:08, 26 February 2025 (UTC)[reply]
  • Keep Keep  @xqt 15:40, 26 February 2025 (UTC)[reply]
  • Remove Remove. Daask (talk) 18:44, 26 February 2025 (UTC)[reply]
  • Neutral Neutral Meiræ 21:59, 26 February 2025 (UTC)[reply]
  • Weak Remove Remove. I hope nothing bad happened (as JJMC89 had no activity at all in the past three weeks), which is why my remove is weak (happy to withdraw if there is a good reason why JJMC89 couldn't be active during the confirmation period). The lack of answers to legitimate concerns is a big problem — NickK (talk) 23:41, 26 February 2025 (UTC)[reply]
  • weak Remove Remove masti <talk> 10:53, 27 February 2025 (UTC)[reply]
  • Keep Keep, per Johannnes89. —DerHexer (Talk) 11:03, 27 February 2025 (UTC)[reply]
  • Remove Remove – valid concerns remain unaddressed. Extraordinary Writ (talk) 11:14, 27 February 2025 (UTC)[reply]
  • Keep Keep, per Ajraddatz and Johannnes89. --Melos (talk) 11:16, 27 February 2025 (UTC)[reply]
  • Keep KeepLeotalk 11:21, 27 February 2025 (UTC)[reply]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: de, en-4
  • Personal info: Hi, this is my first confirmation after being elected as a steward last year. As promised I used my steward permissions primarily for fighting xwiki vandalism/spam – see e.g. my steward stats [5], loginwiki CU stats [6] or SRG edits [7]. I particularly tried to assist with more complicated SRG requests which required opinions from multiple stewards. Other activities concerned (infrequently) SRGP, SRP and SRM [8][9][10]. I volunteered as a scrutineer for the Movement Charter ratification voting [11] as well as enwiki's admin election & ArbCom election [12] [13]. And I joined @DerHexer giving some talks on steward-related topics [14]. My activities have declined a little bit during the past 2-3 months due to off-wiki commitments, but I'm active almost every day even in busy times which should be sufficient. I would love to continue serving as a steward and hope for your confirmation. Looking forward to your feedback, questions and thoughts! --Johannnes89 (talk) 21:09, 15 January 2025 (UTC)[reply]

Comments about Johannnes89

[edit]
I do also echo what Ferien said below too – maybe a compliment in disguise. ;-) --shb (tc) 12:37, 7 February 2025 (UTC)[reply]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en, fr, es-2, de-1
  • Personal info: Hello all, this past year has been a busy for me in terms of work and other commitments. That said, I would like to reoffer for confirmation as I foresee having some more time to continue steward work this year.

    Our steward team has done a pretty good job at keeping the Noticeboards and VRT queues down, so understandably there's been a shift from having a constant backlog to chip away at when myself or another steward has some free time. This should provide some context as to why I had more limited activity this past year as these two factors contributed.

    I look forward to continuing to collaborate with the team both on wiki and off wiki to improve our processes and address the challenges that lay ahead. Thank you.

Comments about Jon Kolbert

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages:
  • Personal info: I've been a Wikimedian since October 2006 and have completed eleven terms as a steward. As usual, I don't believe I have courted any controversy either as a steward or on any project where I am active. I have maintained a reasonable level of activity this year (except for August when I was moving house) and would characterise myself as in the "middle band" of activity amongst stewards. Typically I tend to pick up the things left on the noticeboard for a day or so which require a bit more thought or investigation rather than just a quick lock or block. If the community wants me to, I am happy to continue.

Comments about MarcGarver

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages:
  • Personal info: Hello everyone! I'm a steward since 2020. In the past year, my work as a Steward heavily revolved around Temporary accounts, which affects patrollers of all kinds, including the stewards and other global functionaries. I am in regular contact with the Trust and Safety Product team (which is behind Temporary accounts), giving them advice from a steward perspective, helping to shape Temporary accounts in a way that doesn't make the work of functionaries unnecessarily complicated. Based on my advice, the team created several new features (and others are in process), such as IP Contributions or Global Contributions. Even though liasing with TSP doesn't result in any steward actions on the wikis, I consider this to be my most impactful project as a Steward in the past year.

    In addition to that, I am also working on automating the onboarding of Stewards and checkusers (to decrease the number of manual actions that need to be taken). I'm also available during most of European daytime, responding to requests on IRC or Discord as appropriate.

    As always, if you have any questions regarding my work as a steward, please feel free to reach out to me, and I will be happy to answer them.

    Disclaimers: I'm a Wikimedia Foundation staff member, for which I work as a Senior Software Engineer within the Growth team. More detailed information can be found at my staff user page. I'm currently serving as the Vice-Chair of the Wikimedia Czech Republic's Board of Trustees.

Comments about Martin Urbanec

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: pl-N, en-4, de-3, ru-2, several other European-1
  • Personal info: I am keeping my work in cross wiki vandalism mainly concentrating on Long Term Abusers and crosswiki spambots. I am easily available on stewards IRC so can react quickly on the incoming requests. This year was a little bit less on IRC reactions but with more work on multiple LTA's I think I will be able to keep with at least same level of activity in the coming year.

Comments about Masti

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: it, scn, en-3
  • Personal info: I would like to take a moment to thank the community and everyone who has reached out to me for general or technical support over the past year. Returning to supporting global stuffs alongside global sysops and patrollers has been a cornerstone for me. Maintaining a consistent presence throughout the year has been crucial in dealing with a wide range of LTAs. Additionally, the use of Discord and IRC has served as an additional tool in the fight against spam, spambots and LTAs (loginwiki stats), with an eye on the Steward VRT queues.
    If the community supports it, I'd be happy to continue for another year, with a particular focus on areas where there's still a lot of work to be done, such as the fight against spam, spambots and LTAs. Thanks, and feel free to ask any questions! --Melos (talk)

Comments about Melos

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: uk-N, en-2, de-1, pl-1, ru-4.
  • Personal info: Hello. I was elected as a steward in 2023, so this is my second confirmation. Over the past year, I have continued to carry out the usual steward duties. Primarily, I worked on SRG, SRGP, and SRP and handled several CU and OS requests. Compared to the previous year, my activity has slightly decreased but still remains above average. With the community's support, I would be happy to continue serving as a steward for another year. Thank you for your attention! --❄️Mykola❄️ 18:00, 27 January 2025 (UTC)[reply]

Comments about Mykola7

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: pt, en-3, es-2, fr-2, it-2, gl-1, (sq, sk, ms, hi)-0.5
  • Personal info: Hi, everyone! This is my tenth confirmation as a steward, and it has been a honor to be part of this team :) As a steward, I have been mostly focused on dealing with LTA and cross-wiki abuse/vandalism/spam over the years, but also have a bit of action in other areas such as user rights management, account renaming, private lists and stuff etc. 2024 was a very bad year for me. My father passed away, and my mother got sick. And all of this kept me away from wiki projects for a few months. Little by little, I started to get back to work a few months ago. I still aware of how many LTAs and cross-wiki trolls behave and some maintenance tasks. So I am interested in continuing serving as a steward for one more year, if I can count on your support and trust, of course :)

Comments about RadiX

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: it, en-3, ja-2
  • Personal info: Hi everyone, this is my fifth confirmation. I'm still around :-) mainly locking spambots, crosswiki spammers, crosswiki vandals, and LTAs from time to time. I usually check if they were editing from a proxy and block it for the appropriate period so that my actions can be more effective. I'll continue doing so if the community wants me to. Over the next year, I'll also be keeping up with the latest changes to anti-abuse workflows, hopefully. I know that there's a lot of work going on with the introduction of temporary accounts, and I personally regret not being able to join discussions about this topic, but I'm confident that the movement will manage to overcome this challenge and make the best out of it. Thank you for your attention--Sakretsu (炸裂) 09:55, 31 January 2025 (UTC)[reply]

Comments about Sakretsu

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: de-N, en-3
  • Personal info: Hello, I’m an administrator in the German Wikipedia since 2013 and a steward since 2019. Compared to the last term, there’s a clear drop in my activity. I am not happy about this (would have prefered to be more active), but be it as it may …
    If you still trust me enough I’d love to serve for another term as a steward. Regards --Schniggendiller (talk) 23:45, 31 January 2025 (UTC)[reply]

Comments about Schniggendiller

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: ko, en-2
  • Personal info: Community, everyone, hi! This is Sotiale. I never thought I would be in the role of a steward until now. Of course, you can make me quit the role. At this point, perhaps it's been almost 5 years? It feels amazing to me to be writing confirmation like this again.. Anyway, I'd like to state again what I'm going to do. I'm still focusing on the SRCU area, and using the steward tool to find some friends who are running around in various places. There are still some issues that I haven't fully addressed yet, so I'll address them and continue to do what I've been doing with this tool. I think this statistics show that my 5 years have been really long. I am glad that I have been able to do my work so far thanks to your support. I'll listen to your comments again. Thank you! --Sotiale (talk) 14:48, 15 January 2025 (UTC)[reply]

Comments about Sotiale

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: fi, en-3
  • Personal info: Hi. I've been a steward since March 2015 and I would be interested to continue for another year. My activity has been quite slow, similar to my previous term, but I still believe I can be helpful in this position now and in future. My steward activity has been focused mostly in blocking cross wiki vandals and spammers. I'm available on IRC when I can and I read my email. I'm an administrator on the Finnish Wikipedia and Meta-Wiki. I'm also a checkuser on Finnish Wikipedia.

Comments about Stryn

[edit]


Superpes15 has resigned, and as such, their confirmation process was stopped by the Election Committee. For the ElectCom, --Martin Urbanec (talk) 19:50, 6 February 2025 (UTC)[reply]

logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages:
  • Personal info: As Superpes15 did not create their confirmation statement prior to the deadline, this is a placeholder at this time. For the ElectCom, EPIC (talk) 09:50, 6 February 2025 (UTC)[reply]

Comments about Superpes15

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: sv, en-3
  • Personal info: I have now been a Steward since 2012. My activity this year has been similar to previous years with a lot of spam-bots and cross-wiki vandalism. I can often be found on IRC for dealing with emergencies. With your support I would like to continue for another year. -- Tegel (Talk) 21:54, 30 January 2025 (UTC)[reply]

Comments about Tegel

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages:
  • Personal info: Hi all! This is my third confirmation as a steward. Since February 2023, I've also been the stewards' observer on the Ombuds Commission, allowing me to provide input on cases that would benefit from a steward perspective.

    This past year, my steward work has centered around more behind-the-scenes tasks than in previous years, e.g., providing input for the Ombuds Commission, following and giving feedback on technical developments relevant to steward work, cross-wiki UPE investigations, and similar. I haven't been as active as I'd like in the more standard steward areas (e.g., SRG, RfCs, SRP), though I expect that to change in the next year as I'll have more free time. I'm available on IRC, Discord, and over email.

    As always, I recommend reading DerHexer's 2024 Stewards User Group Report, which presents highlights from the group's work over the last year.

Comments about Vermont

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages:
  • Personal info: I have been a Steward since 2019 and this year, despite some difficulties, I managed to help although not as I would have liked because fortunately for the community the requests were processed in a very short time, but I always put maximum effort and passion into what I did. Despite a drop in my statistics in the last year, I remained active, especially on external channels, for emergency actions, help to local admins and CUs, to compare data and fight vandalism and LTAs. I hope to continue to count on the trust of the community to continue fighting spambots and LTAs, and for other tasks.

Comments about Wim b

[edit]
Sorry, but I'm going to have to change to Remove Remove after what Ferien brought up. //shb (tc) 22:26, 6 February 2025 (UTC)[reply]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: en-N, es-1, de-1
  • Personal info: Hello all, I am seeking confirmation for my 3rd term. My most active area is VRT, where I focus on primary triage and first-call resolutions (having completed ~2600/5200 of 2024 requests, not counting thousands of junk/spam requests that are closed without action.) I also continue to be active in workflow improvements for the global rename/vanish processes. Thank you for your consideration. — xaosflux Talk 16:08, 15 January 2025 (UTC)[reply]

Comments about Xaosflux

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: bn-N, en-3, as-2, bpy-2
  • Personal info: Hello everyone, this is my first confirmation as steward, and I am honoured to be here. This term, I attempted to learn and participate in all aspects of stewardship competency. In terms of statistics, my figures are not the highest, but they are consistent. As in past years, I focused on dealing with LTA and cross-wiki abuse/vandalism/spam, but this time with more tools. I also worked on steward requests pages, handled some global lock/block-related VRT/UTRS tickets, and handled a large number of oversight requests. I volunteered as a scrutineer for many vote wiki elections, including the board election and the first enwiki administrator election. In the coming term, I hope to continue my work and put my first term's experience to good use. I would be delighted to serve another year as a steward for the community, and I am also happy to respond to any questions or concerns you may have. Thanks for your consideration ~ Yahya (talkcontribs) 18:55, 17 January 2025 (UTC)[reply]

Comments about Yahya

[edit]


logs: rights, globalauth, gblblock, gblrights | translate: translation help, statement

<2025 (translate this) not available, displaying English (help us translate!).>
English:
  • Languages: ar, en-4
  • Personal info: Hello. This is my seventh confirmation. During last year I was active dealing with requests mostly on SRG and various other tasks from time to time (around 2,127 steward action in 2024). In addition, I used my steward access for fighting cross-wiki abuse/vandals/spammers and LTAs. Over the past year, I'm being active on SRG, Global AbuseFilter and help on several SRUC complicated requests. Also, I cooperated with local CUs and sysops to solve cross-wiki issues.

    Generally(CentralAuth), I'm bureaucrat, sysop and checkuser on Arabic Wikipedia, and sysop on multiple projects (especially Wikidata, Commons and Meta) -home projects avoided-. Over the years, I have made more than 570K edits on Wikimedia wikis.

    I would be happy to continue for another term. If you have any questions or comments or suggestions, I would be glad to hear them. Thank you --Alaa :)..! 11:56, 31 January 2025 (UTC)[reply]

Comments about علاء

[edit]