Wikipedia:Bureaucrats' noticeboard

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
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.

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 all of them keep an eye on the time remaining on these discussions. Thank you for your patience.

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

Crat tasks
RfAs 3
RfBs 0
Overdue RfBs 0
Overdue RfAs 0
Approved BRFAs 0
Requests for adminship and bureaucratshipupdate
RfA candidate S O N S % Status Ending (UTC) Time left Dups? Report
Femke 56 1 0 98 Open 08:42, 18 August 2022 6 days, 17 hours no report
Shushugah 47 37 14 56 Open 18:25, 16 August 2022 5 days, 3 hours no report
DatGuy 119 13 7 90 Open 16:59, 15 August 2022 4 days, 1 hour no report
It is 14:59:42 on August 11, 2022, according to the server's time and date.
Bureaucrat tasks:
Assigning bot status (talk)
Requests for adminship (talk)
Inactive administrators (talk)
Inactive bureaucrats (talk)
Bureaucrats' noticeboard archives:


Hello, Bs,

I was just looking over a former admin's account where they had lapsed into inactivity some years ago and was wondering if you had a rough estimate for how many current admins will lose their privileges due to the Village Pump RfC earlier this year. I know that it is only August and a lot of things can happen over the next four months but assuming that things continue on as usual, do you expect Wikipedia to lose dozens of admins due to not meeting the new standards of activity? Or hundreds? Of course, I'm not looking for an exact answer, which won't be known until January, just a hint at the scale of the change brought on by this RfC. And, also, I realize that many deactivated admins could return to reestablish their privileges in 2023 after resuming a more substantial level of activity on the project.

Thanks for any clue you can offer! Liz Read! Talk! 21:29, 7 August 2022 (UTC)Reply[reply]

Hi Liz! I know there was a table Worm That Turned put together that offers some insight into that. It was last updated in March but I would imagine it would still give a rough idea of what to expect. 28bytes (talk) 23:31, 7 August 2022 (UTC)Reply[reply]
And some stats that WTT added into the RfC suggested that for 100 edits/year for a 3 year period, 396 administrators would be affected and 67 others warned. The RfC closed with the line drawn at 100 edits/year for a 5 year period, so it's going to be around that order of magnitude. So hundreds. Stephen 00:12, 8 August 2022 (UTC)Reply[reply]
Many of these have had no admin actions in the last 5 years, so the actual impact to the project is pretty much zero. Losing 400 admins that don't actually do anything adminy is more of a push than a loss. They can still edit, although many don't do much of that anymore. Dennis Brown - 00:19, 8 August 2022 (UTC)Reply[reply]
(After edit conflict) For a little perspective, there are about 400 admins who have not made a single logged admin action so far this calendar year. Having 400 admins desysopped at the end of the year is not likely to have much effect on admin activity. - Donald Albury 00:22, 8 August 2022 (UTC)Reply[reply]
I have been playing with my table every so often, but I didn't want to edit the one that was part of the RfC, so I created a admin activity update table, which I update every so often. It's not 100% accurate, as it doesn't handle non-standard usernames and I haven't taken into account recent sysops / desysops, but your welcome to look there to get a feel for how many individuals were originally going to disappear who have now returned sufficiently to activity. That said, Cryptic's Quarry (below) would likely be a much easier way of seeing the data.
Either way, to give an idea of the uptake - We were looking at desysopping about 200 admins, we're down to about 180 now. I agree that when the date is looming, we'll probably get a little mad rush from a handful more, so I'm expecting around 150. WormTT(talk) 07:45, 8 August 2022 (UTC)Reply[reply]
Currently down to 180 still on track to be desysopped once this is effective.
I'm betting that those on the lower end of that query are least likely to be desysopped. If they've been averaging just one or two edits per year for that long just to avoid being desysopped under criterion (1), it strains credulity that they won't suddenly make just enough to game criterion (2) too. —Cryptic 00:51, 8 August 2022 (UTC)Reply[reply]
Maybe some of those will actually come back and get active, which would be a good thing. We need admin, we just don't need editors who are admin in name only. Dennis Brown - 02:14, 8 August 2022 (UTC)Reply[reply]
(edit conflict) From what I've seen the announcement of the new rule change in April did cause several previously-inactive admins to (at least temporarily) return to activity. * Pppery * it has begun... 02:26, 8 August 2022 (UTC)Reply[reply]
I agree with Dennis Brown. It would be wonderful if some of these inactive administrators decided to return to an active role. But inactive administrators have the same impact as inactive former administrators on the administrative work load, which is no impact at all. Cullen328 (talk) 02:25, 8 August 2022 (UTC)Reply[reply]
If past experience was that once an admin became inactive they almost never returned then I'd agree that how we treat currently inactive admins would make little or no impact on the workload. But my experience is that some admins do come back after gaps that sometimes run for years, and given our RFA problems, I think we should be trying to be more open to people who take sabbaticals from this site. Currently inactive admins make no contribution to the current admin workload, but given past experience it is would be safe to assume that currently inactive admins will make important contributions to the admin workload of five, ten and fifteen years time. ϢereSpielChequers 18:36, 9 August 2022 (UTC)Reply[reply]
As it stands, a former admin who was desysopped for inactivity may ask for the bit back, if it has been less than two years since their last edit and less than five years since their last logged admin action. So, if I am interpreting the criteria correctly, a former admin who had performed a logged admin action shortly before being desysopped, and edited WP at least once a year thereafter, could request the bit back up to five years after losing it for inactivity. I think it was clear in the RfC resulting in the change to the criteria for desysopping for inactivity that there were concerns about inactive admins losing touch with the current norms and expectations for admins. I'm not sure the community meant to allow up to 5 years for a return. - Donald Albury 19:41, 9 August 2022 (UTC)Reply[reply]
An interesting loophole, but do keep in mind that bureaucrats must be convinced the admin in question will make an effort to return to activity. Someone making a logged action, being desysopped, and popping back up again four years (and five edits) later to "get the bit back" will likely be turned down. On the other hand, for an admin who stays active and makes hundreds of edits after being desysopped, I would not have an issue restoring their perms.
After all, an admin that voluntarily relinquishes their perms can get it back within 5 years; I do not see this as being much different. Primefac (talk) 20:21, 9 August 2022 (UTC)Reply[reply]
I did say "may ask". :) I have this wild idea. Could we change If an editor has had at least two years of uninterrupted inactivity (no edits) between the removal of the admin tools and the re-request, regardless of the reason for removal, the editor will need to instead request through the WP:RFA process. to If an editor has made fewer tham 100 edits over the previous 60 months prior to the re-request, regardless of the reason for removal, the editor will need to instead request through the WP:RFA process. I realize this would be instruction creep, but I think it would make the process for returning the admin bit more in line with the intent of the RfC. - Donald Albury 21:53, 9 August 2022 (UTC)Reply[reply]
Do any of the current lists check for deleted contributions as well, or will that have to be dealt with manually? With years-old contributions in question I can certainly imagine cases in which admins start out passing the requirement and later appear not to be meeting it.Dekimasuよ! 14:46, 11 August 2022 (UTC)Reply[reply]
@Dekimasu the current inactivity process accounts for this, but it is manual. — xaosflux Talk 14:51, 11 August 2022 (UTC)Reply[reply]

Voluntary self-revocation of adminship (Graham Beards)[edit]

Graham Beards (t · c · del · cross-wiki · SUL · edit counter · pages created (xtools • sigma· non-automated edits · BLP edits · undos · rollbacks · logs (blocks • rights • moves) · rfar · spi) (assign permissions)(acc · ap · fm · mms · npr · pm · pcr · rb · te)

Dear Bureaucrats,

After 12 years, or thereabouts, as an admin, I would now like to relinquish the tools. I intend to remain an active editor.

My best regards. Graham Beards (talk) 15:56, 8 August 2022 (UTC)Reply[reply]

 Done with thanks for your prior service. If you need any of the flags from WP:PERM feel free to reply here, ping me, or post at PERM. Happy editing, — xaosflux Talk 16:05, 8 August 2022 (UTC)Reply[reply]
Job Done.png Job Done
Awarded to Graham Beards for good services as an admin, and for resigning the tools in a noble manner. SilkTork (talk) 18:08, 9 August 2022 (UTC)Reply[reply]

Request for question moderation[edit]

I do not believe Bison's question at Shushugah's RfA is appropriate and would ask that it be removed. Best, Barkeep49 (talk) 22:59, 9 August 2022 (UTC)Reply[reply]

While Shushugah answered the question, I nevertheless agree that its being asked was inappropriate. As such, I have removed it. Acalamari 23:20, 9 August 2022 (UTC)Reply[reply]

When will admin who are impacted by the new activity requirements be desysopped?[edit]

I had been presuming that they would get desysopped in January but Primefac has written that it's April. Can this be clarified? Best, Barkeep49 (talk) 11:46, 11 August 2022 (UTC)Reply[reply]

I was under the impression it would be January. I assume Primefac is under the impression that the notification cannot happen prior to January, but I see no reason this cannot happen. I'd expect the first set of talkpage notifications to go out next month, and the second set in December, leading to the desysops in January. (Going further - and reading the RfC, there wasn't a lot of discussion about the implementation date, but when asked, I specifically said "I don't think anyone believes going from 1-100 is a good thing, so giving them over 6 months to reach the activity level seemed fair and a reasonable sacrifice to get the proposal over the line". When I wrote the RfC, I intended (and thought it was clear) that the desysopping itself would come into force on 1st January, and notifications should work back from that date. WormTT(talk) 11:51, 11 August 2022 (UTC)Reply[reply]
Not that I am a crat, but my reread of the policy text suggests that the criteria comes into effect in January but the notifications went into effect immediately. In other words I agree with Worm. Best, Barkeep49 (talk) 11:59, 11 August 2022 (UTC)Reply[reply]
I wasn't supportive of the RFC (I wanted something more comprehensive) but Worm's reading of consensus is the same as mine. Dennis Brown - 12:15, 11 August 2022 (UTC)Reply[reply]
The discussion seems to support starting the actual removals in January next year, provided we are able to get the notifications going in 3 weeks from now. The first batch may need to be manual, as I don't think the bot will be ready (or is even being worked on yet). — xaosflux Talk 13:05, 11 August 2022 (UTC)Reply[reply]
Presumably by manual you mean MMS? Best, Barkeep49 (talk) 14:05, 11 August 2022 (UTC)Reply[reply]
@Barkeep49 MMS will be fine, as the new requirements are only for talk page. The list will need to be regenerated right before to make sure it is current. It's not a big job, just something to do. — xaosflux Talk 14:16, 11 August 2022 (UTC)Reply[reply]
Indeed both that the email requirement has been removed and that an MMS list will need to be generated nearly at the time of MMS send. Best, Barkeep49 (talk) 14:19, 11 August 2022 (UTC)Reply[reply]
I have no issue if I am in the minority with my interpretation of the close; I am operating under the interpretation that the new rules, including notification requirements, go into effect on 1 January 2023. If it is the consensus that only the activity requirements are triggered on that date, then clearly the notifications can go out earlier. Primefac (talk) 13:36, 11 August 2022 (UTC)Reply[reply]