Wikipedia:Bureaucrats' noticeboard

Bureaucrats' noticeboard archives

1, 2, 3, 4, 5, 6, 7, 8, 9, 10
11, 12, 13, 14, 15, 16, 17, 18, 19, 20
21, 22, 23, 24, 25, 26, 27, 28, 29, 30
31, 32, 33, 34, 35, 36, 37, 38, 39, 40
41, 42, 43, 44, 45, 46, 47, 48, 49, 50

This page has archives. Sections older than 7 days may be automatically archived by .

To contact bureaucrats to alert them of an urgent issue, please post below.
For sensitive matters, you may contact an individual bureaucrat directly by e-mail.

You may use this tool to locate recently active bureaucrats.

Click here to add a new section

Shortcuts

The Bureaucrats' noticeboard is a place where items related to the Bureaucrats can be discussed and coordinated. Any user is welcome to leave a message or join the discussion here. Please start a new section for each topic.

This is not a forum for grievances. It is a specific noticeboard addressing Bureaucrat-related issues. If you want to know more about an action by a particular bureaucrat, you should first raise the matter with them on their talk page. Please stay on topic, remain civil, and remember to assume good faith. Take extraneous comments or threads to relevant talk pages.

If you are here to report that an RFA or an RFB is "overdue" or "expired", please wait at least 12 hours from the scheduled end time before making a post here about it. There are a fair number of active bureaucrats; and an eye is being kept on the time remaining on these discussions. Thank you for your patience.

To request that your administrator status be removed, initiate a new section below.

Crat tasks
RfAs	0
RfBs	0
Overdue RfBs	0
Overdue RfAs	0
BRFAs	15
Approved BRFAs	0

Requests for adminship and bureaucratship update
No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)

It is 07:40:20 on December 28, 2024, according to the server's time and date.

Admin inactivity notices for criterion 2

The first round of inactivity notices for the new activity criterion are planned for 1 October. I would like the crats to provide input on the notice text. I have put a quick draft below for the first notice based on {{inactive admin}}. Please feel free to edit it directly or make a template as you see fit. I'll also need the ones for the second notice and annual reminder. — JJMC89 (T·C) 06:30, 27 September 2022 (UTC) [reply]

Now at {{inactive admin 2}}

== Pending suspension of administrative permissions due to inactivity ==

[[File:Information.svg|25px|alt=Information icon]]
Established [[Wikipedia:Administrators#Procedural removal for inactive administrators|policy]] provides for the removal of the administrative permissions of users who have made fewer than 100 edits over a 60-month period. Your administrative permissions will be removed if you do not return to the required activity level before the beginning of {{{{{|safesubst:}}}#time:F Y|{{CURRENTMONTHNAME}} 1 {{CURRENTYEAR}}+3 months}}. {{{{{|safesubst:}}}#if:{{{crat|}}}|As bureaucrat inactivity requirements are [[Wikipedia:Bureaucrats'_noticeboard/Archive_47#Request_for_comment_on_Bureaucrat_activity_requirements|tied to administrator activity]], failure to reach acceptable activity levels will also result in the loss of your bureaucrat permissions.}}

Inactive administrators are encouraged to engage with the project in earnest rather than to make token edits to avoid loss of administrative permissions. Resources and support for re-engaging with the project are available at [[Wikipedia:WikiProject Editor Retention/administrators]]. If you do not intend to re-engage with the project in the foreseeable future, please consider voluntarily resigning your administrative permissions by making a request at [[Wikipedia:Bureaucrats' noticeboard|the bureaucrats' noticeboard]].

Thank you for your past contributions to the project. ~~~~

Looks good to me. Primefac (talk) 08:30, 27 September 2022 (UTC)[reply]

Whilst I think it's noble to ask for people to give the tools up voluntarily, I feel like most will just wait out the period - this message doesn't give a date for that to happen. Lee Vilenski ^{(talk • contribs)} 09:37, 27 September 2022 (UTC)[reply]

Interesting point, though I feel like if it is posted on 1 October "the next three months" indicates Oct-Dec, and inactivity is generally done at the beginning of the month (i.e. January). I'm not opposed to adding some sort of {{CURRENTDATE}}+3 trigger in there, but I don't really see it as necessary. Primefac (talk) 09:43, 27 September 2022 (UTC)[reply]

I think for me, it's a bit of a difficult ask to request users to increase activity but not give them a deadline. "Within the next three months" seems quite soft, rather than a "you'll lose access by X month". Lee Vilenski ^{(talk • contribs)} 09:46, 27 September 2022 (UTC)[reply]

Ah, so change "return to the required activity level within the next three months" to "return to the required activity level by <month>"? I guess that would work (and alleviates one of the concerns I had about being too specific about the dates). Primefac (talk) 09:54, 27 September 2022 (UTC)[reply]

Indeed. I don't think we gain anything by being super specific, but having a month would make it a bit easier, especially as we are targetting these at users who may spend months away from the site. Lee Vilenski ^{(talk • contribs)} 10:17, 27 September 2022 (UTC)[reply]

Done. Replaced with code that will subst in the fourth month. Primefac (talk) 10:22, 27 September 2022 (UTC)[reply]

You'll get people complaining that they thought January included January. Better to say "start of January" of just within three months of the date of this message, which is clear enough. — Martin (MSGJ · talk) 11:30, 27 September 2022 (UTC)[reply]

Done. Primefac (talk) 11:38, 27 September 2022 (UTC)[reply]

Me too, thanks @JJMC89 Worm^TT(talk) 09:37, 27 September 2022 (UTC)[reply]

We will need a bureaucrat version as well, although that could be just case of replacing administrative with bureaucrat and updating the links. -- WOSlinker (talk) 10:57, 27 September 2022 (UTC)[reply]

Just as a quick reminder for me - the crat activity requirements are the same as for admins, no? Presumably once someone looses the mop, they would also lose cratship? In that case it wouldn't need specifying. Lee Vilenski ^{(talk • contribs)} 11:44, 27 September 2022 (UTC)[reply]

Yes, as of April. Primefac (talk) 11:47, 27 September 2022 (UTC)[reply]

"Presumably once someone looses the mop, they would also lose cratship?". There is no rule that says you need to have admin permissions if you have the bureaucrat permissions, so I think there would still be a need to notify about the bureaucrat permissions as well. -- WOSlinker (talk) 12:43, 27 September 2022 (UTC)[reply]

As of April (see my link) bureaucrat inactivity is tied to admin inactivity, so if a 'crat loses the mop because of inactivity, they will also be de-cratted. Otherwise your statement is correct, as Xeno demonstrated a few years ago.

That being said (sorry for the double post), it wouldn't be that hard to add a |crat=yes option, which would tack on "and your status as a bureaucrat" or similar to the notice. Primefac (talk) 12:51, 27 September 2022 (UTC)[reply]

I can't really think of a situation where one would be suitable for crat, but not adminship (and was probably why this was implemented across both groups). A non-admin promoting an admin wouldn't sit well with the community. However, if it's a simple fix, there's no real reason to not put administrative permissions "and bureaucrat status". Lee Vilenski ^{(talk • contribs)} 12:59, 27 September 2022 (UTC)[reply]

Yes, they would now be removed from both roles due to inactivity but they would still need to be notified that they will loose it. -- WOSlinker (talk) 13:30, 27 September 2022 (UTC)[reply]

Done. Feel free to tweak the wording; I was trying to be as succinct as possible, mainly to avoid placing a ton of #if statements everywhere. Primefac (talk) 13:39, 27 September 2022 (UTC)[reply]

Looks good to me. SilkTork (talk) 15:33, 27 September 2022 (UTC)[reply]

The above time formula currently evaluates to January 2023. Based on prior discussion, my understanding is that the activity requirements themselves are effective on January 1, 2023, meaning desysops begin that day. Were we to send notifications on the October 1, this would evaluate to February 2023, which is either a bug, or a mis-specified requirement. :) Izno (talk) 16:33, 27 September 2022 (UTC)[reply]

It's a bug because I'm a bit of a numpty and tested the code in my sandbox forgetting that it's still September. Fixed. Primefac (talk) 16:34, 27 September 2022 (UTC)[reply]

:D

Izno (talk) 16:55, 27 September 2022 (UTC)[reply]

I'm assuming this is per individual not per account, so if someone has a declared alt account that brings them over the threshold could we give them the opportunity to link that account? Ϣere SpielChequers 16:53, 27 September 2022 (UTC)[reply]

Previous inactivity has considered it per individual. See Nyttend's removal a few times from the inactive list because he was last active on his backup account. I don't think the amendment that was made altered that part of tracking. Izno (talk) 16:55, 27 September 2022 (UTC)[reply]

Is "reengage" better than "re-engage"? Useight (talk) 18:55, 27 September 2022 (UTC)[reply]

reëngage? -- Tamzin^{[cetacean needed]} (she|they|xe) 08:51, 28 September 2022 (UTC)[reply]

Amended to re-engage per Useight. Most common spelling. SilkTork (talk) 09:20, 28 September 2022 (UTC)[reply]

Thank you for the input. I have created {{inactive admin 2}} based on the above. If anyone would like to start the annual reminder notice, that would be helpful. — JJMC89 (T·C) 04:06, 29 September 2022 (UTC)[reply]

I've only been slightly following the kick-off process for this, are we intending to have these notifications bot-managed? — xaosflux ^Talk 00:30, 1 October 2022 (UTC)[reply]

@Worm That Turned: - did you want to manage the first round of notifications somewhere? We should track that status on a page somewhere prob too, like we do for WP:INACTIVE. — xaosflux ^Talk 09:05, 1 October 2022 (UTC)[reply]

Nevermind, the bot did get these sent. @JJMC89: is there report the bot will maintain like it does for the traditional inactives? — xaosflux ^Talk 09:13, 1 October 2022 (UTC)[reply]

Not yet. I've been thinking about the best way to handle it that accommodate both criteria. — JJMC89 (T·C) 17:14, 2 October 2022 (UTC)[reply]

@JJMC89 perhaps just continue to use WP:INACTIVE - just fork and tweak that table and have a second table per month (when needed), the second table will just be 3 months in advance instead of 1 month in advance. Some months will have multiple tables, but that's not a problem, just use a different header on the other table? (New table needs less columns of course, just the edit count, 3month warning stamp, 1month warning stamp. (Note the 'email' requirement also lapses in January for the existing bot report). — xaosflux ^Talk 13:51, 3 October 2022 (UTC)[reply]

I wasn't intending to change the venue (unless the crats want to move to just a final report like the ones that you post here when desysoping). I'll backfill the page once I get the code updated. — JJMC89 (T·C) 03:22, 7 October 2022 (UTC)[reply]

This list should be up to date, other than alt accounts. —Cryptic 00:51, 1 October 2022 (UTC)[reply]

That is a surprisingly long list. I note that User:Tim Starling is on there. Also, the list is based on edit counts only and not logs? For example, User:Trialsanderrors has 98 edits, but would be over 100 if you considered logged actions. --B (talk) 13:09, 6 October 2022 (UTC)[reply]

@B yes it is edits only, see the policy here: Wikipedia:Administrators#Procedural_removal_for_inactive_administrators. That someone happens to work for WMF has no bearing, their work-related access is managed via staff accounts such as here for Tim: meta:Special:CentralAuth/Tim_Starling_(WMF). — xaosflux ^Talk 13:38, 6 October 2022 (UTC)[reply]

Even if logs were included, those moves are, if anything, overcounted - they'll all be represented as edits both in the automatically-created redirects and the empty revisions like Special:Diff/913321933. The creation logs will all have associated edits, too. I'm only seeing the one delete log besides those. —Cryptic 04:05, 7 October 2022 (UTC)[reply]

Discussion at RFA

This discussion at WT:RFA has the potential to significantly change our workflow and remit. I have already voiced my opinions, and am stepping back now, but I feel that more 'crat opinions could be useful. Primefac (talk) 18:37, 2 October 2022 (UTC)[reply]

Just noting this is now the subject of a request for comments: Wikipedia talk:Requests for adminship#RfC: should RfAs be put on hold automatically? –xeno^talk 14:25, 7 October 2022 (UTC)[reply]

Request for interface administrator (TheresNoTime)

TheresNoTime (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}

Hey, I'm requesting IA so that I can help out with the odd edit request and general JS/CSS/MediaWiki: maintenance — plus, it'll stop me accidentally editing an interface page with my steward bits and getting in trouble. I don't mind this being a temporary (6mo?) grant to see how much I end up needing it. Many thanks! — TheresNoTime (talk • they/them) 11:01, 6 October 2022 (UTC)[reply]

48 hour hold as this, as far as I can see, is your first request for interface. TheresNoTime, do you have two factor authentication in place? SilkTork (talk) 11:07, 6 October 2022 (UTC)[reply]
- @SilkTork: Indeed I do — it's required for steward access — TheresNoTime (talk • they/them) 11:09, 6 October 2022 (UTC)[reply]
  - I'm curious about your comment that you may accidently edit an interface page. I understand that as a steward you have the interface admin right, but are not able to use that right on wikis, like ours, which have Crats. Is the restriction not physical? SilkTork (talk) 11:21, 6 October 2022 (UTC) The Stewards page says "stewards will not use their technical access", so I assume there is no physical restriction. SilkTork (talk) 11:25, 6 October 2022 (UTC)[reply]
    - @SilkTork: Nope, no technical barrier to stumbling upon an edit request in the queue, helpfully fulfilling it and then realising it's a MediaWiki namespace page — I do use a script to tell me if I'm the wiki I'm viewing is a GS wiki (or if I am a local admin) but no such thing exists for IA. — TheresNoTime (talk • they/them) 16:07, 6 October 2022 (UTC)[reply]

Do we need a 48 hour hold for Stewards? SilkTork (talk) 11:26, 6 October 2022 (UTC) TheresNoTime already holds the right, so could requests from Stewards be treated as a re-admin request from someone not under a cloud, and the rights be given immediately? SilkTork (talk) 11:35, 6 October 2022 (UTC)[reply]
- As stewards are not supposed to steward in their home wiki, I don't think this should be automatic or accelerated. I fully support giving intadmin to TNT, but their steward status should play no major role in granting that right. —Kusma (talk) 12:15, 6 October 2022 (UTC)[reply]
  - There's no rush, and besides, have you seen who they'll make a steward? ^[FBDB] — TheresNoTime (talk • they/them) 16:07, 6 October 2022 (UTC)[reply]

No objection to giving the right. Also see no urgency and would rather process followed. Worm^TT(talk) 12:33, 6 October 2022 (UTC)[reply]

@TheresNoTime if you don't "use it" we pull it (generally in response to a once-a-month bot managed report) - if pulled you can always just ask for it back. We certainly can do a temp-grant if that's what you want, but I don't think it is necessary - you know how to resign things :D — xaosflux ^Talk 13:33, 6 October 2022 (UTC)[reply]
- @Xaosflux: A fair point — I'm fairly well versed at resigning tools ^^ — TheresNoTime (talk • they/them) 16:07, 6 October 2022 (UTC)[reply]

Support of course. TheresNoTime is a talented software engineer. Will surely find useful things to do as an interface administrator. –Novem Linguae (talk) 13:34, 6 October 2022 (UTC)[reply]
No objections, standard process can be used. — xaosflux ^Talk 13:39, 6 October 2022 (UTC)[reply]
(I know this is not what this process is supposed to be but) [c]lear need, clearly trusted, good idea. ~ Amory (u • t • c) 15:28, 6 October 2022 (UTC)[reply]

Done, TheresNoTime. Have fun! SilkTork (talk) 11:11, 8 October 2022 (UTC)[reply]

Thanks 🙂 — TheresNoTime (talk • they/them) 15:26, 8 October 2022 (UTC)[reply]

Voluntarily Resigning Administrative Privileges (Atama)

Atama (t · th · c · del · cross-wiki · SUL · edit counter · pages created (xtools · sigma) · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)^{(acc · ap · ev · fm · mms · npr · pm · pc · rb · te)}

Hello, I have not been able to be very active for a number of years due to changes in my life, and I very much enjoyed my time serving the project in my administrative role. But I think it is best for me to voluntarily resign my privileges, as I will not be able to commit to an extended activity level any time soon. Thank you to the community that put their trust in me, and I hope whatever changes I have made over the years were a net benefit to the project. I will likely still be around from time to time as a regular editor. -- Atama頭 00:00, 12 October 2022 (UTC)[reply]

Done And added rollbacker to your account. Thank you for your service, Atama. Acalamari 00:05, 12 October 2022 (UTC)[reply]