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

This page has archives. Sections older than 5 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	16
Approved BRFAs	0

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

It is 13:10:55 on October 4, 2024, according to the server's time and date.

Od Mishehu (Level II desysopping)

The Arbitration Committee has adopted a motion desysopping Od Mishehu (talk · contribs · blocks · protections · deletions · page moves · rights · RfA). Would a bureaucrat please remove the permissions? For the Arbitration Committee, AGK ■ 16:46, 5 June 2019 (UTC)[reply]

Done. Useight (talk) 16:50, 5 June 2019 (UTC)[reply]

I note that the edit filter manager (EFM) permission was left in place and later removed by someone else. It seems to me that we should routinely remove other permissions that imply a high degree of trust in these sorts of situations, particularly permissions like EFM and interface administrator (IA) that are rarely granted to non-administrators. Perhaps there should be a policy on exactly what is left in place. Uninvited Company 18:14, 5 June 2019 (UTC)[reply]

@UninvitedCompany: the Interface Administrators Policy specifically calls for removal if -sysop for any reason. Feel free to update any procedural documentation on that one. — xaosflux ^Talk 18:31, 5 June 2019 (UTC)[reply]

@UninvitedCompany: (edit conflict) Note that Wikipedia:Interface administrators#Removal of permissions specifies, as circumstance 4, Upon removal of administrator access, for any reason. and that unlike EFM, only bureaucrats can remove IAdmin rights. However, WP:EFM specifies a process for removing the access of non-admins; following a desysopping, that process technically governs. Maybe it should be amended? DannyS712 (talk) 18:32, 5 June 2019 (UTC)[reply]

I've amended Wikipedia:Bureaucrats#Removal_of_permissions to specifically include IAdmin removal in the procedure. — xaosflux ^Talk 20:02, 5 June 2019 (UTC)[reply]

There are no “procedures” for removing rights assignable by sysops. If there is a good reason to be removed, they can be removed. Amorymeltzer has removed the permission, which in my view is appropriate. TonyBallioni (talk) 18:48, 5 June 2019 (UTC)[reply]

I'm pretty sure one or more previous discussion agreed that EFM rights are removed at the same time as sysop if EFM was self granted. They ought to normally keep it if they had it before sysop and reason for desysop doesn't itself merit EFM removal. Can't find the discussion though. -- KTC (talk) 20:11, 5 June 2019 (UTC)[reply]

This is a big part of why I did it. It had been self-granted a decade ago, only logged changes to their "personal test filter" for about two years, and, in my opinion as an administrator, the reasons given for the desysop and from a checkuser were more than sufficient to indicate lack of trust in the position. I may well have treated a different situation differently. At any rate, the policy at WP:EFM says that a request for discussion or removal of the user right may be made at the edit filter noticeboard (emphasis mine). ~ Amory (u • t • c) 20:51, 5 June 2019 (UTC)[reply]

Additionally the ArbCom clerks procedures (Wikipedia:Arbitration_Committee/Clerks/Procedures) do mention that additional notifications may have been warranted here. — xaosflux ^Talk 18:35, 5 June 2019 (UTC)[reply]

Though the section it appears in does seem to be not "in general" - @AGK: any thoughts on that? In any event, removal of EFM isn't a bureaucrat responsibility per se. — xaosflux ^Talk 18:37, 5 June 2019 (UTC)[reply]

@TonyBallioni: regarding the above as well, it looks like after this came up in the past the clerks procedure was not notify WP:EFN during ArbCom desysops, such that an administrator could review the situation and process removals if needed (assuming it was not already an arbcom remedy from a case). — xaosflux ^Talk 20:04, 5 June 2019 (UTC)[reply]

Yeah, I think that makes sense, but I don’t think we need a formal process if an admin who is competent at such things notices it at WT:ACN and actions it then. They can always request it back. TonyBallioni (talk) 20:20, 5 June 2019 (UTC)[reply]

@Xaosflux: Notifications were sent to Od Mishehu themselves and to WP:AN, which I think about covers it. If you were asking because I did not cross-post, it's because the new ArbClerkBot automatically syndicates an announcement. Which is a great help. AGK ■ 21:15, 5 June 2019 (UTC)[reply]

@AGK: I'm referring posting to WP:EFN when If the desysopped editor has self-granted edit filter manager rights, post a note to the edit filter noticeboard for review as listed on the clerk procedures. — xaosflux ^Talk 21:57, 5 June 2019 (UTC)[reply]

Will follow up on this at Wikipedia_talk:Arbitration_Committee/Clerks (as it's not really a 'crat matter). — xaosflux ^Talk 04:16, 6 June 2019 (UTC)[reply]

Wikipedia:Arbitration/Requests/Case/Rama closed

Per the final decision of the arbitration committee linked above, please remove the sysop bit from Rama (current rights · rights management · rights log (local) · rights log (global/meta) · block log).

For the Arbitration Committee, GoldenRing (talk) 13:58, 6 June 2019 (UTC)[reply]

Done — xaosflux ^Talk 13:59, 6 June 2019 (UTC)[reply]

Looks like Xeno beat me to the click. — xaosflux ^Talk 14:01, 6 June 2019 (UTC)[reply]

User:Fram banned for 1 year by WMF office

Please note admin User:Fram has been banned for 1 year as per Office action policy by User:WMFOffice.Pharaoh of the Wizards (talk) 17:56, 10 June 2019 (UTC)[reply]

What the hell? There had better be a damn good explanation; Fram is arguably the best admin in Wikipedia's history, and while I can imagine problems so bad they warrant an emergency WP:OFFICE ban without discussion, I find it hard to imagine problems that are simultaneously so bad they warrant an emergency ban without discussion but simultaneously so unproblematic that the ban will auto-expire in a year. ‑ Iridescent 18:01, 10 June 2019 (UTC)[reply]

And also only applicable to enwiki, meaning Fram can communicate on other wikis. I note that the WMF only recently gave themselves the power to do partial bans/temporary bans.. Galobtter (pingó mió) 18:09, 10 June 2019 (UTC)[reply]

Galobtter - Any clue about whether Fram's ban is the first exercise in implementing these or have other editors been subject to these P-bans, earlier? ∯WBG^converse 18:43, 10 June 2019 (UTC)[reply]

Winged Blades of Godric, first on enwiki at least per User:WMFOffice contributions, I checked de wiki and found some more de:Special:Contributions/WMFOffice; the timing of those dewiki bans suggests the policy was put into place to ban those two people. Galobtter (pingó mió) 18:47, 10 June 2019 (UTC)[reply]

@Winged Blades of Godric: It is not. The first WMF partial bans were done in German Wikipedia. The earliest that I know of is Judith Wahr in February. Policy regarding partial bans were added around the same time. -★- PlyrStar93 _{→Message me. ←} 18:50, 10 June 2019 (UTC)[reply]

I'm with you on this. Fram and I have butted heads a time or two (I think?) but I just am trying to wrap my mind around a decision like this with no real explanation. I understand the nature of WMFOffice blocks but I would think that anything egregious enough for an emergency decision like this would have had some indication prior to it happening, like a community discussion about bad behavior or abuse of tools which would reveal PII (os, cu), but Fram was neither of those. I can't seem to think of a single thing that would warrant such unilateral action that could also result in only a one year ban (as opposed to indefinite, if that makes sense) and so narrowly focused on one local project. Praxidicae (talk) 18:06, 10 June 2019 (UTC)[reply]

Yes, saying "email us" is not sufficient explanation for banning a well-known veteran editor and admin like this.-- Pawnkingthree (talk) 18:10, 10 June 2019 (UTC)[reply]

Per Iri. It's also so unproblematic that he's not banned on any other WMF projects?! Banning from en.wiki only seems like something ArbCom gets to do, not WMF. And I see he's already been desysopped by WMF, instead of locally, too. If there are privacy issues involved, I certainly don't need to know what's going on, but I do want ArbCom informed of what is going on and get their public assurance that they agree with the action, and this isn't bullshit. They even preemptively removed talk page access. --Floquenbeam (talk) 18:11, 10 June 2019 (UTC)[reply]

User:Whatamidoing (WMF), I know you're heartily sick of my pinging you, but if ever there was a situation that needed an explanation from Commmunity Relations, this is it. ‑ Iridescent 18:13, 10 June 2019 (UTC)[reply]

This is T&S business and I am not sure if Community Relations knows better. — regards, Revi 18:14, 10 June 2019 (UTC)[reply]

Which goes back to my original point: if it's egregious enough (T&S) to warrant a unilateral decision like that, why only a year? Praxidicae (talk) 18:15, 10 June 2019 (UTC)[reply]

(edit conflict) If it's a T&S issue, then why is he still trusted on every other project, and why is it simultaneously so urgent it needs to be done instantly without discussion, but so unproblematic it expires after a year? "We're the WMF, we can do what we like" may be technically true, but the WMF only exists on the back of our work; absent some kind of explanation this looks like a clear-cut case of overreach. As Floq says, if there's an issue here that can't be discussed publicly then fine, but given the history of questionable decisions by the WMF I'm not buying it unless and until I see a statement from Arbcom that they're aware of the circumstances and concur with the actions taken. ‑ Iridescent 18:20, 10 June 2019 (UTC)[reply]

I've asked ArbCom to comment at WT:AC/N. --Floquenbeam (talk) 18:26, 10 June 2019 (UTC)[reply]

WTF? Echo everything that Iri says. ∯WBG^converse 18:25, 10 June 2019 (UTC)[reply]
As above. I am not Fram's biggest fan (the feeling is more than mutual, don't worry) but when I saw this in my watchlist it was an actual spoken 'WTF' moment. We need a good explanation, quickly. Giant Snowman 18:50, 10 June 2019 (UTC)[reply]
Office has full-protected Fram's TP in the midst of this discussion; it is hard to believe they do not know it's going on, but certainly easier to believe that they feel they can ignore it. 2A02:C7F:BE76:B700:C9AE:AA89:159B:8D17 (talk) 18:52, 10 June 2019 (UTC)[reply]
Like everyone else, I simply fail to understand why the Foundation would ban a good-standing admin for no apparent reason. funplussmart (talk) 18:52, 10 June 2019 (UTC)[reply]