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	2
RfBs	0
Overdue RfBs	0
Overdue RfAs	0
BRFAs	10
Approved BRFAs	0

Requests for adminship and bureaucratship update
RfA candidate	S	O	N	S %	Status	Ending (UTC)	Time left	Dups?	Report
Graham87	59	13	4	82	Open	10:11, 24 November 2024	6 days, 14 hours	no	report
Worm That Turned	272	5	9	98	Open	09:47, 18 November 2024	13 hours	no	report

It is 19:48:44 on November 17, 2024, according to the server's time and date.

Inactive admins for October 2024

The following inactive administrators can be desysoped due to inactivity. Thank you for your service.

Criteria 1 (total inactivity)

Babajobu (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Last logged admin action: March 2023
Jayron32 (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Last logged admin action: September 2023

Criteria 2 (100 edits/5-year rule)

Elf (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
Last logged admin action: August 2020

Graham87 (talk) 02:43, 1 October 2024 (UTC)[reply]

i'm sorry to see that designation go, but indeed I haven't done much in recent years. I gave it my all back in the early 2000s became horrifyingly addicted to editing, and finally had to pull away. I will always do small edits and sometimes bigger ones. but, thanks all who continued to contribute in bigger ways. Elf | Talk 03:45, 1 October 2024 (UTC)[reply]

Xaosflux: Haven't the rights been removed yet? I was updating the admin newsletter and thought I should remind you. – DreamRimmer (talk) 13:43, 1 October 2024 (UTC)[reply]

They are about to be - I usually do these and was travelling! — xaosflux ^Talk 14:01, 1 October 2024 (UTC)[reply]

Done with thanks for their prior service. — xaosflux ^Talk 14:08, 1 October 2024 (UTC)[reply]

Desysop request (Wugapodes)

Wugapodes (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)}

I continue to have less time to volunteer than I would like. It's gotten to the point where simple requests are piling up and I've lost touch with CENT-level discussions. I'm not using them and it's more of a liability than an asset for the community at this point. Hopefully I will have more capacity for volunteer work in the future and I may request them again at that point. But until then it's best to leave block-delete-protect to those with the time and enthusiasm. I'd like to retain page mover and template editor which were the tools I enjoyed most before +sysop and which I will be most likely to use when poking around. Thanks for the ride, and feel free to say hi if you see my name pop up while I'm on wikibreak. — Wug·a·po·des 04:58, 1 October 2024 (UTC)[reply]

Done Enjoy your Wikibreak, and thanks for all you've done here. Ϣere SpielChequers 05:48, 1 October 2024 (UTC)[reply]

Thank you for your prior service. — xaosflux ^Talk 08:22, 1 October 2024 (UTC)[reply]

Enjoy the break! You are always welcomed back. :) – robertsky (talk) 12:17, 1 October 2024 (UTC)[reply]

Resysop request (Crisco 1492)

Crisco 1492 (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)}

I would like to request a re-sysop for myself, with the intent of helping with DYK and alleviating some of the backlog. I have reviewed the criteria for re-sysopping outside of the RFA process, and I believe that I meet them. — Chris Woodrich (talk) 10:12, 1 October 2024 (UTC)[reply]
They resigned the admin tools in August 2018 (BN request, confirmed here). Last logged admin action was a 1-year self-block in 18 August 2018, previous action was a deletion two days prior. They returned to editing for three edits in October-November 2019, and then in batches from July 2020, so there has been no 2 year period of complete inactivity. Thryduulf (talk) 10:53, 1 October 2024 (UTC)[reply]
Over five years since administrative tools were last used might apply here. –Novem Linguae (talk) 11:08, 1 October 2024 (UTC)[reply]
That only applies in inactivity removals, while Crisco resigned their access. Sdrqaz (talk) 11:13, 1 October 2024 (UTC)[reply]
Hmm. Maybe Wikipedia:Administrators#Restoration of admin tools needs some clarifying then. The way I'm reading it it seems like any of the bullets in that bulleted list are disqualifying for resysop requests. –Novem Linguae (talk) 23:18, 1 October 2024 (UTC)[reply]
In the case of removal due to inactivity, for any administrator who does not have a logged administrator action in five years, bureaucrats should not restore administrator access upon request seems fairly clear that this point only applies in cases of removal for inactivity. I'm not sure policy ever anticipated this particular scenario. Just Step Sideways ^{from this world ..... today} 00:44, 2 October 2024 (UTC)[reply]
It's hard to imagine any other scenario it would be there for. (And IIRC we rejected a modification to remove it in the ~~same RFC that added the 5 year/100 edit rule~~. Nope, the one before it.) —Cryptic 01:01, 2 October 2024 (UTC)[reply]
The scenario it is there for is for an admin who is procedurally desysopped for inactvity, for example Jayron32 has just been desysopped for inactivity. Their last admin action was September 2023, so they can request the tools back at any point until August 2028 (assuming they don't have any two-year period of complete inactivity). Thryduulf (talk) 08:51, 2 October 2024 (UTC)[reply]
It's hard to imagine any other scenario, besides this particular one, that the "In the case of removal due to inactivity" clause would be there for. (Or, equivalently, "if they are removed for inactivity" from the original RFC.) Since you can only get resysopped on request if you lost the bit for inactivity or by resigning. —Cryptic 12:13, 2 October 2024 (UTC)[reply]
There are two scenarios in which you can get the bit back by asking:
After removal due to inactivity

After removal due to resignation (this scenario)

The five-year clause explicitly only applies to the first scenario, and the 2019 RFC you linked did not reach a consensus to apply it to the second one too (in fact there was actually slightly more opposition than support). Thryduulf (talk) 12:26, 2 October 2024 (UTC)[reply]
Yes. I was responding to JSS's statement above that policy hadn't ever anticipated this scenario (that is, a former administrator who'd resigned, either over five years ago, or merely while their last logged action was over five years ago), despite it being worded for no other imaginable reason than to anticipate it - both in the current version of policy and in its original proposal. (Maybe we can track down that Beeblebrox guy who made the proposal and ask him.) —Cryptic 12:38, 2 October 2024 (UTC)[reply]

Ah I see. I missed the In the case of removal due to inactivity part. My brain didn't expect it to be there or something and paid attention only to the bold. Carry on :) –Novem Linguae (talk) 01:28, 2 October 2024 (UTC)[reply]

well this is good news! Floquenbeam (talk) 01:14, 2 October 2024 (UTC)[reply]

Welcome back Crisco! There's a 24 hour pause on resysops these days, ~~and nearly 21 hours of that still to run. But~~ I'm sure DYK will be glad of your return. Ϣere SpielChequers 12:35, 2 October 2024 (UTC)[reply]

Thanks both! No worries about the pause; I saw that at WP:RESYSOP as well, and I know that I've left the mop in the closet long enough to gather tons of cobwebs. — Chris Woodrich (talk) 12:49, 2 October 2024 (UTC)[reply]

@WereSpielChequers: Huh? It's been over 24 hours since the resysop request was posted ... it was posted yesterday. I was expecting to do my regular changes to the former admins pages tonight ... Graham87 (talk) 12:58, 2 October 2024 (UTC)[reply]

Indeed, I seem to have lost a day here. Careless of me. Bit flipped now. Ϣere SpielChequers 13:27, 2 October 2024 (UTC)[reply]

Done

Rights restored. Welcome back! Ϣere SpielChequers 13:27, 2 October 2024 (UTC)[reply]

Thank you! — Chris Woodrich (talk) 13:29, 2 October 2024 (UTC)[reply]