Wikipedia:Bureaucrats' noticeboard

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

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	12
Approved BRFAs	0

Requests for adminship and bureaucratship update

No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)

It is 11:58:59 on May 23, 2024, according to the server's time and date.

Barely active bureaucrats

Is it me or are there a fair few bureaucrats who only appear for these (incredibly rare) duties, and otherwise spend their time barely being active at all? I shouldn't expect to see a username I've never seen before participating in closing a contentious RfA, and given the damage an inactive-then-compromised 'crat could do... doesn't bear thinking about! I feel further tweaks to the activity requirements are needed, however I expect a certain amount of backlash that an increase would be pointless given how little they have the opportunity to do — perhaps then the question should be Bureaucrats: do we even need them? — TNT (talk • she/her) 16:48, 3 May 2022 (UTC)

There aren't a lot of "duties" for a 'crat. They basically consist of participating on this noticeboard, removing admin status when requested to do so through the proper channels, closing RFAs and RFBs, and weighing in on 'crat chats. That's pretty much it since renaming became global. Other than that, we participate to varying degrees as editors on Wikipedia, just like any other editor. It may be, however, that I'm missing the core point of your concern. If so, please elaborate. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 16:54, 3 May 2022 (UTC)

@Nihonjoe: you forgot granting bot flag . —usernamekiran (talk) 15:58, 4 May 2022 (UTC)

No one said I had a perfect memory. I hardly ever do anything with bots, so that's why I forgot it. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:14, 4 May 2022 (UTC)

I'd expect to see them active elsewhere though, much like our administrators :) maybe we don't need bureaucrats here any more? — TNT (talk • she/her) 17:03, 3 May 2022 (UTC)

The resolution of that RFA would have been a lot more interesting without bureaucrats. ScottishFinnishRadish (talk) 17:12, 3 May 2022 (UTC)

@TheresNoTime: You're welcome to start an RFC if you think that's a good course to take. A good community discussion will make the determination. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:20, 3 May 2022 (UTC)

The scope for undetected bureaucratic abuse is far less than the scope for administrative abuse. Granting and removing administrative permissions is far harder to do under-the-radar. Given that the bureaucratic activity requirements have been synched up with the administrative ones, it feels unnecessary to increase the bureaucratic ones out of sync. As for the idea that bureaucrats are unnecessary themselves, while I have pointed out issues with their representation, unless we move away from the consensus model and towards a hard voting system à la Committee elections, I would be far more comfortable with the results being determined by English Wikipedia community members than the stewards. Sdrqaz (talk) 17:09, 3 May 2022 (UTC)

• I don't think anyone has a problem with barely-active bureaucrats performing straightforward, uncontroversial tasks, which presumably make up the majority of the workload. I don't speak for TNT, obviously, but I think their concern (which I share) has to do with bureaucrats' roles in highly contentious decisions like Tamzin's recent RfA. These require subjective interpretation of community norms and assumptions. To take a pointed but concrete example, if the most apposite touchstone a 'crat can come up with is the Great Userbox War of Aught-Six, it's fair to conclude that they're out of touch with the site and community as it currently exists, and to question their qualifications to participate in these sorts of discussions. MastCell ^Talk 17:12, 3 May 2022 (UTC)

  I was not too impressed to see the userbox war (whose outcome I remember a bit differently) mentioned but not the fact that community consensus on userbox deletions has gone back and forth quite a bit since then. —Kusma (talk) 18:06, 3 May 2022 (UTC)

• If someone is going to talk about User:UninvitedCompany in a fairly specific way, the least we can do is ping them. Dennis Brown - 2¢ 17:15, 3 May 2022 (UTC)

  Meh. He's a person who has edited four times this year. Expand discussion, @Bureaucrats: . SN54129 17:34, 3 May 2022 (UTC)

  That seems unnecessarily dismissive. He's still a person. Reaper Eternal (talk) 17:54, 3 May 2022 (UTC)

  Edited in lighted of your sensibilities, Reverend. SN54129 18:10, 3 May 2022 (UTC)

• Regarding "I'd expect to see them active elsewhere though", my first instinct would be to suggest that we ask active, clueful editors of more recent vintage to join the 'crat pool to balance out us old farts. There wouldn't be a lot for them to do on a daily basis, of course, but having the input of newer editors on the occasions where input is needed would be a good thing, I think. 28bytes (talk) 17:46, 3 May 2022 (UTC)

  I was about to post something similar myself. Obviously, we want bureaucrats to be experienced, but if there are concerns, we have plenty of newer editors who might be willing. Reaper Eternal (talk) 17:52, 3 May 2022 (UTC)

  The candidate pool of admins from the last 5 years isn't very large, though, and given that they became admins after self-noms and RfBs went out of fashion, they may need to be nominated by someone else, for example a bureaucrat. —Kusma (talk) 17:57, 3 May 2022 (UTC)

  Looks like 4 of the last 7 RfB's were self-noms. They are quite rare obviously so the stats are hard to extrapolate from. — xaosflux ^Talk 18:21, 3 May 2022 (UTC)

On a practical level, we have almost no tasks to do after renames were moved to the global level. If it weren't for security purposes (having an extra level of authorization to turn on bot/admin flags), I think we should remove the userright entirely and either fold cratship into adminship completely, or simply make all the currently active admins crats. But I know I'm probably a minority when it comes to that opinion.

In terms of this particular issue, I think the best way to deal with barely active admins and crats is to have more active admins and crats, not police the ones who aren't active enough out. We're long overdue for a streak of RFBs. It would be especially helpful to have crats who started editing later, not so much of a matter of them being more "in touch," but because they edit out of a different frame than those of us who started in the naughts. But running an RFB solely for the purpose of closing RFAs seems like a crummy situation for everyone. Maybe it's RFB that we can use to experiment changes for RFA.

On a personal note, I have to say that I found it really nice to see familiar faces in this particular chat like UninvitedCompany and Warofdreams, both of whom I looked up to when I started editing. They've seen and experienced much. But maybe that's just the ex-Esperanza, metapedian me speaking. bibliomaniac15 18:26, 3 May 2022 (UTC)

Hi there. The first paragraph is spot-on: we should just eliminate the bureaucrat role entirely, it's no longer needed and there's already an extra level of authorization in stewards. I truly don't understand how your second paragraph then suggests that we're overdue for a streak of RFBs when we just determined that the role is no longer necessary. --MZMcBride (talk) 19:04, 3 May 2022 (UTC)

If the bureaucrat role were eliminated, I imagine that it would be up to stewards to add and remove administrator flags and administrators to adjust bot flags. Who would determine consensus at RfA? Would any experienced editor be able to close a discussion? Jake Wartenberg (talk) 19:51, 3 May 2022 (UTC)

Indeed — stewards are, in fact, entirely suited to this role as they are bound by policy to enact valid community consensus. A RfA/RfB would therefore be treated like any other consensus building discussion — TNT (talk • she/her) 20:28, 3 May 2022 (UTC)

@MZMcBride: I meant that I would consider what I wrote in my first paragraph to be the best course of action, but because I don't think that would ever happen, what I wrote in my second paragraph would be my next best course of action. Sorry for making that ambiguous; they weren't meant to be connected thoughts per se. And to respond to Salvidrim! below, I have absolutely zero desire to become an arbitrator; that would be an immediate resignation from me. bibliomaniac15 03:20, 4 May 2022 (UTC)

Ahh, understood, thanks. I think it's a bit overly pessimistic to say we couldn't ever get rid of the role, but you may well be right. This place is certainly horribly intransigent at times. :-) --MZMcBride (talk) 05:24, 4 May 2022 (UTC)

IMHO it's a lot harder to have/retain competency for the full range of admin tasks than for the full range of bureaucrat tasks. So inactivity by a crat is far less likely to cause competency issues and mis-actions than inactivity by an admin. Sincerely, North8000 (talk) 18:43, 3 May 2022 (UTC)

Are there any admins who are competent in the full range of admin tasks, and have been so constantly for years? The important thing is to notice whether you are competent or not, there's always the option of simply not using your tools in areas you're not currently competent for. —Kusma (talk) 18:57, 3 May 2022 (UTC)

I'll go out on a limb and say: nope. The range is very wide. — xaosflux ^Talk 19:01, 3 May 2022 (UTC)

Agree, the full range is too much to ask for and so "full" was an overstatement on my part. And admins usually stick to areas that they know. But to put my point more bluntly, it's not difficult to remain competent crat and so I think inactivity is less of an issue to worry about. And longevity buttresses trust, which is very important. North8000 (talk) 19:15, 3 May 2022 (UTC)

• From the recent RFC, starting in January 2023, 'crats will have the same new editing activity requirements as admins - so some of this topic may get resolved then one way or the other (hopefully by less active editors becoming more active!) — xaosflux ^Talk 19:00, 3 May 2022 (UTC)
• Pinging Warofdreams since they have also been mentioned. Dennis Brown - 2¢ 19:54, 3 May 2022 (UTC)
• Shall I be a little more direct? If bureaucrats aren't significantly active on actually improving the encyclopedia, whether that be through editing or administrative duties, they should resign. Black Kite (talk) 19:59, 3 May 2022 (UTC)
• Thank you, returning bureaucrats. While I respect disquiet that decisions get made/contributed to by people who are no longer very active, I think it's important to start from the right place: to those bureaucrats who no longer spend much time on Wikipedia, but made time to review a tricky RFA and engage in discussion, thank you for your time. With that out of the way, I actually don't think there is a problem here. The fundamentals of judging consensus have not changed much in the past 15 years, any more than the five pillars. Meaningful changes in interpretation, like shifts in target percentages, requirements for bureaucrat chats, etc. have been clearly established via RFCs and I see no evidence any of our bureaucrats are ignoring them. And if some bureaucrat used a prehistoric example during the chat, so what? To the extent it would be problematic or not really applicable, I am sure some other bureaucrat in the chat would raise that. To be sure, I don't necessarily fully agree with every point every bureaucrat ever makes, but that's immaterial. I continue to have trust that when they deliberate, bringing their range of long-standing and recent experience to the table, they tend to get it right. Martinp (talk) 22:16, 3 May 2022 (UTC)
• Ugh, I have a lot to say and maybe I'll find time to type it all out some day, but as someone who was vocally skeptical of UninvitedCompany's and Avaraham's rationales I don't see any issues that need resolved. Some people agree with their method for assessing consensus, and there were a hundred people opposed to the RfA who I'm sure had justifications for a no consensus finding. They deserve to have their ideas represented among crats. Similarly, a diversity of views strengthens everyones' arguments. Without UC's or Avi's opinions I wouldn't have bothered to spend the time writing a detailed analysis because it would be a waste of time; when the question is legitimacy of process though, we want strong and detailed analyses. If there is fault (dubious) it's not in their tenure or activity because other crats of similar activity and tenure came to opposite conclusions. It's worth remembering that they were selected by the community at particular points in time for their judgment, and having institutional wisdom from various points in our history helps prevent us from making mistakes already seen in the past. To the degree that there is a problem with the crat corps, I agree with others that it's a younger cohort of editors who lacks representation within it. I think the solution isn't older crats but a need to promote more. — Wug·a·po·des​ 23:55, 3 May 2022 (UTC)
• Not going to speak for my fellow bureaucrats, but while it doesn't look as though I'm very active (under 50 edits so far this year), I am watching BN and RfA every day and read what's going on. Yes, it would certainly be helpful from the community's perspective if I were a little more active overall but I ensure my knowledge of the positions I hold is as up to date as much as possible (I did forget about not removing autopatrolled from successful admin candidates, but was reminded and will remember that in future). Acalamari 01:36, 4 May 2022 (UTC)
• Personally, I'm quite happy with how the 'crat team conducted itself in my RfA. If anything, I'd favor approaches that give more power to the 'crat team (enhanced discretion in clerking, preapproval of questions, stuff like that) than ones that lay fault with the group that gets brought in to make sense of the chaos. -- Tamzin^{[cetacean needed]} (she/they) 02:11, 4 May 2022 (UTC)
• I guess I count as a fairly active crat, though I had to recuse from that crat chat. We have just changed the rules so that in the longterm inactive crats get decratted. I think it is a good thing if we have uninvolved crats making close calls in crat chats, and crats who have been little involved in recent years but come back for a crat chat may well have more detachment from the individuals involved in current RFAs. That said we have problems in the crat group, a lack of new blood and a gender ratio that last time I looked could be as few as one crat in twenty (we've just had a crat chat on a female candidate for adminship, and I think I'm correct in saying that none of the crats who participated in either the RFA or the Cratchat are female as our only female crat was unavailable in those days). The solution to that is to encourage more candidates to run RFBs, especially it would be good to have some extra female crats. As for Crats not having enough to do, that's a direct result of us not having enough people running at RFA. Fix that problem and at least we have no shortage of crats to close RFAs. ϢereSpielChequers 09:57, 4 May 2022 (UTC)

  @WereSpielChequers: Not that it makes a huge difference as to your broader point, but Useight lists their gender on their userpage as androgynous. -- Tamzin^{[cetacean needed]} (she/they) 10:01, 4 May 2022 (UTC)

  The picture isn't much better for former bureaucrats: may have overlooked someone, but I think the list is just Angela and Secretlondon? —Kusma (talk) 10:32, 4 May 2022 (UTC)

  When Jimmy appointed the first batch of crats it wasn't very unbalanced, it has been a while since I looked, but I think most of the first nine were male but he did include both Angela and SecretLondon. Subsequent elected Crats have I believe been overwhelming male, but I had missed Useight when I looked through all of them a couple of years ago, and there are also some where I don't know their gender. ϢereSpielChequers 14:35, 4 May 2022 (UTC)

• I'd rather see significantly higher activity expectations for 'crats over and above that required for administrators. I'd go for at least 100 edits per year, with evidence of closing at least two consensus-based processes during each year. The latter could include closing AN/ANI threads, closing deletion discussions, closing RFCs, as well as closing RFAs. I do have genuine concerns that our least active 'crats have lost touch with the current community, and that their analysis of consensus is out of step with community norms. (And in response to the thread below, no, I don't think the role should go to arbitrators or functionaries. Yes, we generally have more current understanding of consensus and would meet activity requirements, but RFA consensus analysis is a long way from what our elected/appointed roles are.) Risker (talk) 17:00, 5 May 2022 (UTC)

Testing the waters: shift Bureaucrat to Arbitrators?

This seems like it would solve every single problem raised here.

• Closing RfAs is either uncontroversial (could even be done by arbclerk, with arb flipping the bit on?), or requires a 'crat chat, which is already almost equivalent to Arbs discussing a motion
• Desysoppings are already either at the request of Arbs, or routine for inactivity
• Arbs are not a lifetime appointment, they were recently elected and have the highest level of trust.
• This would not require technical changes (just make Arbs 'crat on top of CU/OS) and could be done with relatively small changes to how policies are currently interpreted and applied.
• I get that we may not be keen to add to the burden of Arbs but this seems like a very small burden, as someone has said above, 5 crat chats since 2016 is hardly onerous.

Just throwing the idea out there. Ben · Salvidrim! ✉ 21:14, 3 May 2022 (UTC)

There is a section of the community that thinks there should be a division between those user sets. While I am not in that set, I am also not in the set of people who want to be a crat. :) Izno (talk) 21:40, 3 May 2022 (UTC)

Goodness no! Bin the right, shift it back to the stewards 😅 — TNT (talk • she/her) 21:44, 3 May 2022 (UTC)

I'd oppose that; we should keep local control of the interfaceadmin right. While having it handed out by stewards would be better than giving the power to the WMF (remember superprotect?) I would rather have this as a local community responsibility instead of something done externally. —Kusma (talk) 21:53, 3 May 2022 (UTC)

(unlike global interface admin then..?) — TNT (talk • she/her) 21:55, 3 May 2022 (UTC)

Out of all the groups I'd support merging the 'bureaucrat' usergroup to if consensus emerges to eliminate it, stewards are about last. I don't think we should give up local governance. Merge it to 'sysop' if needed, and even that isn't a particularly good choice. Reaper Eternal (talk) 21:59, 3 May 2022 (UTC)

Interesting. Why the mistrust of a user group who are policy bound to enact valid local consensus..? (nb. I'm not suggesting stewards judge the consensus for what its worth.. that I agree should remain local, just merely "flipping the bits") — TNT (talk • she/her) 22:02, 3 May 2022 (UTC)

Any answer other than "because they are outsiders to the enwiki clique" is tripe. Ben · Salvidrim! ✉ 22:05, 3 May 2022 (UTC)

Enacting local consensus requires that one first understands how local consensus works. I wouldn't expect a random volunteer from another wiki to understand our processes in depth, however experienced and well-intentioned, any more than I'd know how to close a discussion on the French, German, Russian or Chinese Wikipedias.  — Amakuru (talk) 22:08, 3 May 2022 (UTC)

You may have missed my addition above, apologies — I'm not suggesting stewards judge the consensus for what its worth.. that I agree should remain local, just merely "flipping the bits" — TNT (talk • she/her) 22:10, 3 May 2022 (UTC)

I think you might be mistaking what I'm saying, TheresNoTime—sorry about the confusion and let me explain myself better. :) I don't distrust stewards. I simply think that, given stewards are ultimately beholden to the WMF (and we've all seen multiple times what a mess the WMF make when they stomp around), they should not be in charge of granting and revoking sysop on larger projects like enwiki. That should be left to trusted members on these projects who are elected by the local project, aka bureaucrats. Ultimately, this is why I don't think we should remove 'bureaucrat' even though their task list is ridiculously small. Does this make more sense? Reaper Eternal (talk) 22:58, 3 May 2022 (UTC)

Well I say all of this with my steward hat firmly away, and with mild trepidation: I personally disagree that we the stewards are beholden to the WMF any more than you are as a checkuser. But assuming we were, and assuming the WMF wanted to make a mess, there's no technical barrier to me a steward granting/revoking sysop here. The maintenance of local bureaucrats doesn't stop that from happening. — TNT (talk • she/her) 23:19, 3 May 2022 (UTC)

I'm working on a similar but distinct idea. Best, Barkeep49 (talk) 21:55, 3 May 2022 (UTC)

What barkeep has outlined is a good way to get the conversion rolling because it has an end date and creates a situation where something happens in the case of deadlock. I see a few paths forward from there. The functionaries as the crats is a possible outcome that some people would have some feelings about. Another would be finding more things for the crats to do so that more people would run for crat and diversify the pool of users. Crats are very much of an era. A third is to tap the global resource of the Stewards. Guerillero ^{Parlez Moi} 22:36, 3 May 2022 (UTC)

While evolution and simplification is always good, why not reach a consensus on a better solution first, rather than resolve to blow up the bureaucrat user group first without knowing what we're migrating to? And if we can't find a better solution (i.e. Guerillero's "deadlock"), maybe the status quo is good enough. Martinp (talk) 23:00, 3 May 2022 (UTC)

Thanks to Guerillero's comment above and some feedback I received off wiki, I have been able to hone in on what I am trying to do. The core idea of my proposal is to say that the status quo is not working. That the role and/or responsibilities of crat needs to be reimagined. The RfC establishes that consensus. But all too often on Wikipedia we can have that consensus that the status quo is not good enough but can't reach enough of a consensus on any given plan because the minority who don't think there needs to be change still think that and are joined by enough who dislike something about an alternative to block change - especially a problem given that our mode of consensus means we require more than a simple majority in cases like this. By having a meaningful deadline, I think it actually becomes more likely that we'd reach consensus on a better solution because "do nothing" doesn't actually end at nothing. Best, Barkeep49 (talk) 23:13, 3 May 2022 (UTC)

I think I can write a book about all the problems with changing our existing CUOS process to be the crats; will wait if there is an RFC to expend that time. — xaosflux ^Talk 23:24, 3 May 2022 (UTC)

@Xaosflux I'm wondering if you might be willing to write a chapter (maybe the introduction) about the problems you foresee? Salvidrim posting his similar idea meant I went public with mine a little earlier than I had planned but I had planned to seek out your feedback specifically before moving forward with any kind of proposal. Also just for clarity, we wouldn't be changing our existing CUOS processes to be the crats, we'd be letting the CUOS people do the crat processes. Best, Barkeep49 (talk) 00:34, 4 May 2022 (UTC)

• @Barkeep49: I suppose my biggest concern is that CUOS's are not managed by the community. CUOS's are also not accountable to the community, they serve at the pleasure of arbcom (barring a situation where WMF steps in to remove one). The CUOS selections are about the least transparent process we have, using a secret review process. CUOS's can be arbitrarily added or removed for any reason anytime the smallest quorom of arbs can be bothered to show up and vote on a motion by a 50%+1 margin. I'm far more in favor of the community taking back the CUOS management process from arbcom, leaving arbcom to be more focused on dispute resolution and less on investigations. — xaosflux ^Talk 01:12, 4 May 2022 (UTC)

Personally, I feel it would be better to first have a discussion to determine if there is a consensus that there is a problem with the status quo, and what specifically is the problem. I don't think a discussion setting a time limit on revising a role is warranted until there is agreement on a problem statement. isaacl (talk) 23:39, 3 May 2022 (UTC)

As you've written about, isaac, Wiki decision making can mean that there is a consensus of a group of people who agree that there is a problem and what it is. But there might only be a majority who agree on a particular solution and so the status quo - a status quo that has no consensus - remains. Numerically, and in simplified form, this can look like 75% of people editors on what the problem is with Group A having 55% of editors who agree on the problem and the solution, Group B having 20% who agree on the problem but not the solution, and Group C has 25% who don't like any solution because they genuinely don't believe there's a problem in the first place. There's some incentive for Groups A & B to come together but not any real incentive for C, other than respect for project consensus, again not because they're being bad actors but because they're honestly doing what they think is right for the wiki. Further, this all tends to happen in a single round - there's no mechanism to iterate proposals because if a proposal like this is rejected it generally stays rejected for at least 18 months. Trying to find a method people can live with to solve this dynamic and to allow for a better implementation of a consensus proposal is what I was proposing here. Best, Barkeep49 (talk) 00:45, 4 May 2022 (UTC)

Yes, I understood your intent. But until we've found the 75% of editors who agree on a problem statement, I don't think a deadline on revising or eliminating the bureaucrat role is needed. isaacl (talk) 00:58, 4 May 2022 (UTC)

I'm glad I'm not the only one to have that thought today. -- Tavix ^(talk) 22:42, 3 May 2022 (UTC)

I feel like having ArbCom be both the body removing and granting sysop would create some weirdness. If arbcom desysops an admin and they run for adminship, and that goes to a "cratchat", we could have the same arbs who voted desysop having to decide if there's a consensus for promotion. I could see this being seen as problematic especially if the ArbCom decision is one the community mostly disagreed with. Some separation of powers seems reasonable to me. Galobtter (pingó mió) 23:24, 3 May 2022 (UTC)

If ArbCom desyops an admin, they it has the right to re-sysop the admin. That is because it can modify any of its decisions. Hawkeye7 (discuss) 01:38, 4 May 2022 (UTC)

Although I agree with the overall thread that bureaucrats overall seem somewhat unrepresentative of the overall community for crat chats and such. Galobtter (pingó mió) 23:26, 3 May 2022 (UTC)

That'd be a shame. I've enjoyed 'crat work. But what will be, will be, I suppose. 28bytes (talk) 23:25, 3 May 2022 (UTC)

I think of low activity bureaucrats as a feature rather than a bug. Having a group that is trusted to assess consensus, and not very involved with wiki-politics and drama is good. They can take a high level view without having their judgement affected by community drama. ScottishFinnishRadish (talk) 00:06, 4 May 2022 (UTC)

The selection criteria for crats, arbs, and functionaries are all different and I don't think conflating them is the best idea. Crats need 85% support (right? I can't be bothered to look it up) and are selected based on their ability to read consensus. Arbs need 50-60% support and are selected for their dispute resolution abilities. Functionaries (besides arbs) are not elected by the community at all, but are instead selected by the committee based on feedback from stakeholders including the community. I worry that combining crat with any of them means the selection criteria for the others will change in a way that may not necessarily be beneficial. There are people who would be good checkusers but not helpful in a crat chat, and the reverse. That's a trade-off I'd need to think more about. — Wug·a·po·des​ 00:10, 4 May 2022 (UTC)

• Wugapodes is spot on. We just had a contentious RFA that was on the edge, and the Crat system worked perfectly. And now people want to use that success as a reason to change it. People bitch when Crats don't participate, then bitch when they do. Frankly, I can see why any Crat could have seen the consensus either way, which is why the Crat chat uses a consensus. It worked. It's all about trust and nothing that took place shook my faith in the Crats. The candidate approves of the Crats behavior, in fact (see above). If someone didn't like the !votes of the Crats, perhaps they should run and see if they can get 85% support to become a Crat, then they can participate in the next Crat chat. Replacing someone with 85% approval with someone with 50%+ approval (or no approval at all) is a step down in trust, not up. Dennis Brown - 2¢ 03:40, 4 May 2022 (UTC)
• Yeah I don't recall things like ability to read consensus or communication skills coming up in CUOS selections. Quite possibly many CUOS have those also, but they were given those tools for other reasons (technical proficiency, investigation skills, etc.) – Joe (talk) 07:14, 4 May 2022 (UTC)

• Well, this discussion really has accelerated since it started. I guess a lot of folks watchlist WP:BN. It seems like this is a discussion about major changes that is moving a little fast. But maybe folks are just throwing their ideas out there. Nothing will change outside of a majority vote on an RfC. Liz ^{Read! Talk!} 03:47, 4 May 2022 (UTC)

Oh, a mere 85%? How hath the mighty fallen, It was over 90% in my day! And we walked uphill, both ways, in the snow, barefoot, with our soles strewn with broken glass for traction, and we were grateful. Just setting the record straight :). Now seriously, regarding the suggestion of 'ceding the role of the 'crat to the stewards', I'd like to share my opinion. Similar to a few others here, I've seen a LOT of Wikimedia in my younger days. At one point I was simultaneously an admin/crat/CU/OS on Enwiki, an admin/OS on Commons, an admin on Meta, a steward, a member of OTRS, and served on the WMF Ombudsman committee. I gave almost all of those tools back years ago as the way my career developed, I no longer had the necessary time required to devote myself to all those duties. But in that decade or so, I've seen how consensus is built on different projects, and it is (or at least was) clearly not the same across projects. This was especially difficult on Commons, where the its flavor and mores are fundamentally different than on EnWiki. Meta was more neutral. Also, in my time as a steward, while the plurality may have been EnWiki based, there was not a stigma, but an assumption that Enwiki was the 800lb gorilla and what flies here would not fly on DeWiki or JaWiki for example. There was an extra burden on us EnWiki stewrads to make sure we remained aware of that and respected the local culture. I think that EnWikipedians passion, and the evolved method of consensus finding—from the glacial pace of some RfCs to the frenetic pace of the RfX, is special and that in the cases where consensus is not clear, and some body needs to be tasked to help ascertain, that body should be made up of native Enwikipedians. I am in no way shape or form implying that the stewards aren't trustworthy, G-d forbid, or even that they wouldn't do their best to respect the EnWiki culture. They most certainly would. And they perform admirably. But that is the best option for projects without the critical mass needed to have a native body. Enwiki does have that critical mass. So I do not think ceding that role to the stewards is a good idea. Thank you. -- Avi (talk) 07:32, 4 May 2022 (UTC)

I prefer barely active bureaucrats who have caused no issues at all over active CUs / OSs / Stewards / WMF persons who think it is wise to change their userpage during this RfA to a polemic anti-Trump page, to then go and harass the main cause of the RfA opposes on their user talk page to get them to withdraw their oppose. A steward who seems only interested in stirring up things around this RfA instead of cooling down the situation is a strong argument against giving stewards any role in this process. Fram (talk) 08:06, 4 May 2022 (UTC)

@Fram: I appreciate being called out. I had let emotion speak over sense, and have apologised. For what its worth, I personally would not be permitted to act as a steward on any permission changes here per policy — TNT (talk • she/her) 14:27, 5 May 2022 (UTC)

Thank you. Fram (talk) 14:45, 5 May 2022 (UTC)

• Responses to issues raised:

1) On the issue of barely active Crats: that has already been addressed, though has yet to kick in.
2) On the issue of Stewards replacing Crats: Stewards have not been elected here, those that can operate here are not active here, and would not be as familiar with EnWiki consensus as they would for their home Wiki. Concerns that people have about EnWiki Crats would be multiplied if switching to Stewards.
3) On the issue of replacing Crats by Arbs. That is a different election process for a different purpose. On the whole I feel that someone who is an Arb could do the Crat role and vice versa, though the community may be more cautious when voting for a Crat than when voting for an Arb, because of the nature of the Crat role.

Additionally, the community (and ArbCom itself) have over the years been reducing the role and function of ArbCom, something I fully support. Ideally we should get to the stage where the community feels confident in dealing with all disputes, and all the legal aspects of ArbCom are dealt with by the professionals who should be dealing with it (with a nod toward those who have worked in ArbCom to get WMF to accept some of their responsibilities in this area). It would be against the spirit of what has been happening to actually increase ArbCom roles.

4) On the issue of CUOS taking over the Crat role, they have not been elected for the role, and are either given those rights as Arbs, or are given those rights by ArbCom, albeit with some feedback from the community, so haven't been directly approved by the community to become Crats.
5) On the issue of there being little for Crats to do, I find I am pinged to a Crat discussion more frequently than I had anticipated. Such discussions are not logged as Crat activity, but are still part of the Crat role. Someone asking to be resysopped may result in a discussion with the decision not to resysop, for example. However, yes, it's not a work heavy role; but I'm not seeing why that is a disadvantage to it being a distinct role. I'm in favour of unbundling advanced roles rather than squeezing more together. Let individuals decide which tools/roles they wish to use to help the project.
6) Barkeep mentions in his Crat proposal that Crat appointments are few, and that there hasn't been one for a while. While I feel that there are enough active Crats to do the work in a reasonable responsive manner, this may not always be the case for one reason or another, so looking into how we can keep a sufficient number of active Crats in the role is something I'd be interested in.

On the whole, other than looking into how we can get more Crats (an annual election?), I feel that the status quo works, and I suspect there are fewer complaints about Crat actions than about actions performed in other roles. SilkTork (talk) 10:23, 4 May 2022 (UTC)

Regarding the #4, with a couple personal powers/privileges exceptions, when you vote for an arb are safe knowing they can't just go make huge policy impacting decisions without convincing at least a few other committee members to go along with them. If we went this route would need to determine if the standard for quorums would be required here. — xaosflux ^Talk 13:00, 4 May 2022 (UTC)

I don’t get what problem is being solved here. Assessing consensus (crats) is not the same as deciding as a committee by fiat on intractable behavioural issues (arbitrators). I don’t see any issue with the current crat corps. They might have a low workload but that’s not a problem, there’s no evidence of security compromises or unauthorised promotions, and I think all opinions expressed in the recent crat chat were legitimate, reasonable, and made in good faith. I think it’s a slippery slope to decide you don’t like how someone whose consensus-ascertaining judgement is trusted reasoned in a particular case => radical change is needed. ProcrastinatingReader (talk) 10:29, 4 May 2022 (UTC)

Have to agree with Proc above, I believe the process worked, and we will be aligning 'crat requirements to admins from January of '23 which should bring them in line with community expectations. Also, have to add that dissenting 'crat viewpoints can be treated as reductions of community minority viewpoints, it is plausible (as with any argument) to find logical flaws or subjective disagreement within the same but they exist nonetheless. --qedk (t 愛 c) 11:31, 4 May 2022 (UTC)

I can recall only a couple of glaring 'crat. errors (IMO) in the 15 years I've been here. Let sleeping dogs lie. Leaky caldron (talk) 14:49, 4 May 2022 (UTC)

I think 'crats are an important soft power base in the community. They have almost no real power in the community (unlike Arbs or CheckUsers) and their deliberations are all public. When you add to that the extremely high threshold of trust it takes to become one, you end up with a group of people who are selected for their reasonableness. They're the most apolitical grouping of people with advanced permissions.

I would love more diversity in the group. But I'm not a fan of removing them. Guettarda (talk) 16:38, 4 May 2022 (UTC)

• Way back in the before times I ran at RFB, and one of the reasons it failed was that several users felt I was too controversial to be a 'crat. @Worm That Turned: even explicitly said he did not support me as a 'crat but would support me as an arbitrator, and you know what, in the end I agreed with that, they are two very different jobs requiring different skill sets. I don't know if he'll poke his head in here, but @Keegan: was around when the role was created, and he told me that the dev who came up with the role deliberately came up with the most boring and unappealing name they could think of for the role, so nobody would imagine it was some sexy new user right that would be exciting to be involved with. So, while I totally support the new activity standards, I really think moving the role over to Arbs is an awful idea. On top of my already stated reasons, the committee has more than enough on its plate already. I was actually just commenting the other day to my wife that I was glad the latest dramastorm was clearly not our issue to deal with and somebody else could take the heat for a change. Beeblebrox (talk) 17:13, 4 May 2022 (UTC)

  @Beeblebrox: Unless you know something I don't about their account history, Keegan's first edit was in October 2005, as also implied by their user page, well after the bureaucrat role was created in February 2004. Perhaps you were thinking of a different person? In any case, you're right about the origin of the name ... see Wikipedia:Village pump/Archive W#Apparent new "bureaucrat" access. While checking through related history, I found a now-amusing comment at Wikipedia talk:Bureaucrats/Archive 1#desysop ability about bureaucrats getting the ability to desysop users (which they didn't have until many years later): "I don't think the asymmetry is necessarily a bad thing. It ought to be easier to make sysops than unmake them since that is a far rarer occurrence." How times have changed! Graham87 07:50, 5 May 2022 (UTC)

  Maybe he just heard about it second hand. It was an in-person conversation a decade ago in a subway station so it's possible I got the details wrong. Beeblebrox (talk) 16:28, 5 May 2022 (UTC)

• Every point initially raised in favor of this seems like it would be made unambiguously worse if arbitrators (or functionaries) were filling the job, except for the bit about bureaucratship being a lifetime appointment. And even if we wanted that, we'd be better off by imposing term limits or requiring reconfirmation RfBs; while those have always gotten rejected for admins as a whole due to the sheer volume of them required, it's manageable for 20 crats. —Cryptic 17:25, 4 May 2022 (UTC)

  @Cryptic A "simple" periodic reconfirmation for stewards (latest: meta:Stewards/Confirm/2022) is usually low drama. — xaosflux ^Talk 22:47, 4 May 2022 (UTC)

• Crats should be elected for five year terms. Levivich 03:21, 5 May 2022 (UTC)

  I would back 4-year or 5-year terms Nosebagbear (talk) 10:55, 12 May 2022 (UTC)

I don't think I agree with the removal of the bureaucrat role, but feel the agree side of neutral on whether improvements are needed for the crat role. To address proposals as to where the rights would go if it was removed:

1. With regards to ArbCom and it's clerks, I would add to what has been said above:
   • While arbitrators are trusted members of the community and I think I would support any current arbitrator for the crat role if they went for RfB, their primary focus is around dispute resolution. The extra time needed to do crat tasks decreases the time they have to spend on dispute resolution, and increases the requirements for the role which could potentially exclude some otherwise great candidates that maybe don't have enough experience in determining consensus in large discussions.
   • Both as an arbcom clerk and community member, I strongly oppose arbcom clerks filling in for the crat role. Our role is can be summed up as being a helping hand for the arbitrators for on-wiki matters. While we do perform clerking actions on our own initiative, major clerking actions from my experience always are checked over by an arbitrator which ultimately means an arbcom clerk would be asking a arb as to whether to give or not give the sysop rights in a RfA discussion.
2. CU/OS taking this on is something I would also oppose as a member of both groups. In a similar vein to the arbitrators it's not what we are appointed to do.
3. Although I disagree with handing the role to stewards, what I would say in opposition has already been said by SilkTork so I won't restate it. Dreamy Jazz ^{talk to me | my contributions} 00:26, 13 May 2022 (UTC)

Inactive administrators and alternate accounts

Sorry if this has already been discussed somewhere else - I happened to notice at WP:Inactive administrators that Nyttend (talk · contribs) was on there with his last edit given as May 3, 2021. But he has a declared alternate account - Nyttend backup (talk · contribs) - that has edits as of July 7, 2021. Should his de-admin date be moved to August 1? --B (talk) 13:33, 4 May 2022 (UTC)

I don't think so. The admin bit is tied to just one account, and, in my opinion, that is the only account that should count in determining admin activity. Donald Albury 13:46, 4 May 2022 (UTC)

Not a 'crat, but given the precedent of WP:USEIGHT, it would be weird for a different rule to apply to Nyttend. Writ Keeper ⚇♔ 13:50, 4 May 2022 (UTC)

Indeed, I don't agree that the admin bit is tied to an account, it's tied to a person. Hence users may not have two admin accounts (save for bots), and why we've moved the bit from one account to another in certain circumstances in the past. I do agree that the deadmin date should be moved. Worm^TT(talk) 14:01, 4 May 2022 (UTC)

I delisted it for now, the bot will keep putting it back each month. In practive, it is really no big deal if it did get done, since if they really are not inactive they could just log on and ask for it back. — xaosflux ^Talk 14:30, 4 May 2022 (UTC)

I'm not certain, but I feel like I remember someone telling me that an exception was written into the bot a number of years ago when I was exclusively using an alt account. If that's the case, it could also be done for Nyttend (talk · contribs) if (s)he remains on an alt long enough that it gets tedious constantly manually delisting. Useight (talk) 15:19, 4 May 2022 (UTC)

I think that was the old bot, and frankly I think it was quite silly per the not a big deal comment I made above. — xaosflux ^Talk 15:33, 4 May 2022 (UTC)

Sounds good. Whatever works is great. Useight (talk) 15:41, 4 May 2022 (UTC)

"We've moved the bit from one account to another in certain circumstances in the past" Certain circumstances? Because you were scared! Can User:Darwinbish have the bishbit for a while now? bishzilla _ROARR!! pocket 17:30, 4 May 2022 (UTC).

Ah, yes, little 'Zilla was a Victim of Circumstance.... Wyrm That Turned (talk) 18:54, 4 May 2022 (UTC)

Your account was initially excluded when I developed the current bot, but that was removed before it went live. The bot can still exclude accounts if necessary. — JJMC89 (T·C) 02:26, 5 May 2022 (UTC)

It's probably not worth adding an exclusion for Nyttend, since this situation will only occur once more (the June list), and then Nyttend will be actually removable for inactivity in July, by which point everyone will likely have forgotten about this discussion. On the other hand, it would probably be worth manually excluding ProcseeBot, which has been inactive since November 2020 and has been manually removed from every month list since. That is, if you don't just desysop it, which is what I would do if I were a crat. * Pppery * _{it has begun...} 02:50, 5 May 2022 (UTC)

I'll cross-post that to WP:BOTN (discussion link). Primefac (talk) 07:21, 5 May 2022 (UTC)

For the bot thing, thanks Prime - let's follow up there (I added more to that one).

Not a "'crat comment" --- For admins that just refuse to log on, this is silly. They should just log on. If you have advanced privileges like admin and can make things easier for anyone else by bothering to do anything with your account once a year (right now), and you just won't - what is going on? — xaosflux ^Talk 09:43, 5 May 2022 (UTC)

I think we should count alternate accounts and excluding bots because alternate accounts are edit of the same user, but bots are run by scripts and sometimes bots can be operational when the owner are missing. We have a new policy about inactive admins (100 edits/5 years) Thingofme (talk) 12:04, 5 May 2022 (UTC)

It has always been exactly that, so no change is needed. Dennis Brown - 2¢ 01:15, 6 May 2022 (UTC)

"but bots are run by scripts and sometimes bots can be operational when the owner are missing" - that's very true - if I were to die, my bot might continue running for years until my wife figures out how to turn off the server that it's running on. ;) --B (talk) 10:45, 6 May 2022 (UTC)

It can be taken over to someone else before you dies... Thingofme (talk) 14:53, 6 May 2022 (UTC)

I guess, but regrettably we don't generally know the the hour or day that we will die. It just kinda happens. --B (talk) 20:58, 6 May 2022 (UTC)

Bot codes are generally stored on GitHub so maybe, no problems. The bot will be blocked and someone will use this bot. Thingofme (talk) 02:50, 7 May 2022 (UTC)

If sanctions apply to the person rather than just the account such as a user who was banned from politics would be banned on all their accounts, I fail to see why that shouldn't apply to good things as well. An edit from an alternative account should be counted for the purpose of inactivity. Crouch, Swale (talk) 19:10, 11 May 2022 (UTC)

Desysop User:ProcseeBot

Hello 'crats, following this proposal over at WP:BOTN, we're asking that this bot be desysoped as it is inactive and we have not heard back from the operator, User:Slakr. No action on the admin-operator is needed, and should the operator want to reactivate it while they are still an administrator a new note at WP:BOTN should be able to get that speedily handled. Best regards, — xaosflux ^Talk 19:21, 11 May 2022 (UTC)

 Done. 28bytes (talk) 19:28, 11 May 2022 (UTC)

Setting down tools for a while (Valereee)

Valereee (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'd like to request desysop for a bit. Trying to get my mojo back, hoping just feeling like I've nothing to do but research and write will help kickstart that! Thanks! valereee (talk) 13:04, 14 May 2022 (UTC)

 Done have a good break. — xaosflux ^Talk 13:12, 14 May 2022 (UTC)

Enjoy your time off, valereee! -- Tamzin^{[cetacean needed]} (she/they) 13:33, 14 May 2022 (UTC)

Thank you, Auntie Val. Having the mop has changed my relationship to pagespace too. We want you well and happy, and you are trusted no matter what role you choose to take on. BOLD is a good thing and we appreciate yours. BusterD (talk) 14:15, 14 May 2022 (UTC)

@EEng: nevermind that RFaR draft, we're too late. Levivich 14:30, 14 May 2022 (UTC)

Totally got out before it started to drizzle. valereee (talk) 15:31, 14 May 2022 (UTC)

Hope your "break" helps! I've BOLDly regranted all of your pre-sysop bits (extended-confirmed, NPR, PCR, rollback); give me a shout if there are any you didn't want back. GeneralNotability (talk) 15:14, 14 May 2022 (UTC)

Fine with having those tools, thanks, and sorry for the extra work! :D valereee (talk) 16:09, 14 May 2022 (UTC)

Thanks, I forgot to hit save on +ECP; certainly no objection to the others if she wants them! — xaosflux ^Talk 17:37, 14 May 2022 (UTC)

Would have been weird when I tried to move Ruthrauff & Ryan just now and discovered I couldn't, lol...it was actually a little weird to not have the option to move without leaving a redirect! This is actually going to be very interesting, it's been nearly three years! valereee (talk) 18:32, 14 May 2022 (UTC)

Do you want 'page mover' access added @Valereee? — xaosflux ^Talk 19:07, 14 May 2022 (UTC)

Actually that'd be great! I kind of hate leaving redirects behind unless there's a reason. Thanks! valereee (talk) 19:20, 14 May 2022 (UTC)

Shouldn't it be the other way around, where you should only suppress a redirect when there's a reason? Sdrqaz (talk) 19:39, 14 May 2022 (UTC)

@Sdrqaz, oh, clarification: it's when I'm moving from a user draft of my own that I want to suppress the redirect. I do almost all creation of articles in my own user space because I usually am not positive a subject is notable yet, and that gives me unlimited time to keep doing research. I've only had maybe a couple of times where someone had linked to one before I moved it (which is what I meant by a reason to leave it), so I usually just delete unless that's the case. valereee (talk) 19:51, 14 May 2022 (UTC)

 Done — xaosflux ^Talk 21:17, 14 May 2022 (UTC)

• Pinged here by Levivich (and no idea what you're talking about, L -- I've been AWOL for several days) and just want to say: Hey, Valereee, you're a cool gal. EEng 05:47, 16 May 2022 (UTC)

  Aw, you're making me blush valereee (talk) 19:54, 16 May 2022 (UTC)

Voluntary desysop request ( Sean Whitton)

Sean Whitton (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)}

Solely for the reason that I am not presently active, please desysop my account. Thanks. —Sean Whitton / 23:35, 18 May 2022 (UTC)

 Done have a good break. — xaosflux ^Talk 23:52, 18 May 2022 (UTC)