Wikipedia:Bureaucrats' noticeboard: Difference between revisions

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 5 days may be automatically archived by Lowercase sigmabot III.

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	1
RfBs	0
Overdue RfBs	0
Overdue RfAs	0
BRFAs	9
Approved BRFAs	0

Requests for adminship and bureaucratship update

RfA candidate	S	O	N	S %	Status	Ending (UTC)	Time left	Dups?	Report
Worm That Turned	209	2	3	99	Open	09:47, 18 November 2024	4 days, 21 hours	no	report

It is 11:58:26 on November 13, 2024, according to the server's time and date.

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. UninvitedCompany 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]

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]

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 (about two hours prior to the bans' implementation). -★- 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]

Going to echo this as well. This is a very cryptic block, which seems very hard to tie to any public behaviour. Headbomb {t · c · p · b} 19:01, 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. GiantSnowman 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]
• T&S: training and simulation? Very confused. Talk English please. DrKay (talk) 18:53, 10 June 2019 (UTC)[reply]
  • DrKay, T&S means Trust and Safety. funplussmart (talk) 18:54, 10 June 2019 (UTC)[reply]
  • m:T&S. Killiondude (talk) 18:55, 10 June 2019 (UTC)[reply]
• A big ‘ole whiskey tango from me too. –xeno^talk 19:03, 10 June 2019 (UTC)[reply]
• I've put a note on meta:User talk:JEissfeldt (WMF), I believe that is the place for a wiki-talkpage-request. Jo-Jo Eumerus (talk, contributions) 19:05, 10 June 2019 (UTC)[reply]
• (moved from an) Holy shit, what? That’s insane. It appears that their admin rights have also been removed... can only wmf restore the rights, or will fram have to go through an rfa?💵Money💵emoji💵^💸 19:06, 10 June 2019 (UTC)[reply]

  Neither; this is a WP:OFFICE action so we can't overturn it. Per my comments above, I can't even imagine the circumstances in which this is legitimate, since if it were genuinely something so problematic he needed to be banned instantly without discussion, it would be something warranting a global rather than a local ban, and permanent rather than time-limited. ‑ Iridescent 19:09, 10 June 2019 (UTC)[reply]

• "HELLO? IS THIS THING WORKING???" Explanation required. The Rambling Man (talk) 19:13, 10 June 2019 (UTC)[reply]
• I sent a note to the WMF email address listed on User:Fram and asked for an explanation. I would suggest that perhaps other people might want to do the same. I imagine that T&S has valid reasons, but I believe that some sort of summary explanation to the community, at a minimum, is called for in this case. UninvitedCompany 19:15, 10 June 2019 (UTC)[reply]
  • So have I. --Floquenbeam (talk) 19:20, 10 June 2019 (UTC)[reply]
    • Seems like we are in good company as well. Probably better to wait now for any reply. Jo-Jo Eumerus (talk, contributions) 19:23, 10 June 2019 (UTC)[reply]
• Uh, yeah. Explanation required, please WMF. The fact he's only been banned from en.wiki and not globally locked suggests it's regarding something that's happened regarding this wiki. So, we're waiting. Black Kite (talk) 19:22, 10 June 2019 (UTC)[reply]

  In the absence of any explanation, the cynic in me guesses that at some point in the next 12 months the WMF are going to reattempt to introduce the forced integration of either Wikidata, VisualEditor or Superprotect, and are trying to pre-emptively nobble the most vocal critic of forced changes to the interface. ‑ Iridescent 19:25, 10 June 2019 (UTC)[reply]

  @Iridescent: The cynic in you has some evidence in its favor ... . * Pppery * _{it has begun...} 19:41, 10 June 2019 (UTC)[reply]

  This is worth quoting in full: This priority will focus on deeper evolutions to the core product — integrating content from Commons, Wikidata, Wikisource and other projects into Wikipedia. This will be accompanied by rich authoring tools and content creation mechanisms for editors that build upon new capabilities in AI-based content generation, structured data, and rich media to augment the article format with new, dynamic knowledge experiences. New form factors will come to life here as the outcomes of earlier experimentation. We will showcase these developments in a launch for Wikipedia’s 20th birthday in 2021. Nice of them to ask if we wanted this, isn't it? ‑ Iridescent 19:46, 10 June 2019 (UTC)[reply]

• Actually, if the WMF office knew anything, they knew this would blow up. So waiting is inappropriate really, they should have already been in a position to respond immediately to this. The Rambling Man (talk) 19:26, 10 June 2019 (UTC)[reply]

•  Bureaucrat note: (and response to User:Money emoji) While it is useful to have a notice here about this action, there isn't really anything for 'crats to do right now. The WMF Office action indicates a 1 year prohibition on administrator access at this time that we would not override. Per the administrator policy, former administrators may re-request adminship subsequent to voluntary removal. As Fram's sysop access removal is not recorded as "voluntary", the way I see it is that a new RfA, after the prohibition period, would be the path to regaining admin access (outside of another WMF Office action). — xaosflux ^Talk 19:29, 10 June 2019 (UTC)[reply]
• At ths point I don't even care about the reasoning but there is no way that the WMF can claim this is preventative. If it's so bad that WMF had to act in what appears to be a local matter, why is there no concern about this a year from now? Why, if whatever happened is so bad, is there no concern about ill intent on the hundreds of other projects Fram could edit? I'm not suggesting Fram be indeffed but I think some transparency from WMF is needed here, the optics are very bad and no matter which way I connect the dots on this, it seems extremely punitive. Praxidicae (talk) 19:30, 10 June 2019 (UTC)[reply]

• Yeah,a big whiskey tango foxtrot from me as well. What the hell are they playing at? Reyk _YO! 19:41, 10 June 2019 (UTC)[reply]
• Could this have been self-requested? I can't imagine T&S saying yes, but you never know. In any case, piling on here. An explanation is required. Without one, people will assume the worst, either about Fram, or the WMF. I'm ashamed to admit my mind already went to same place as Iridescent's. Suffusion of Yellow (talk) 19:48, 10 June 2019 (UTC)[reply]

  Speculation can take us anywhere of course. Keep in mind there could be additional T&S terms that we are unaware of (such as a speculative "may not hold admin or above access on any project for a year") - functionally, enwiki is the only project where advanced access provisioned, so may have been the only one where rights modifications was warranted. — xaosflux ^Talk 19:51, 10 June 2019 (UTC)[reply]

• Add me to the list of those who said "WTF" out loud after seeing this. The scope of the ban is baffling, too; if Fram has violated the terms of use, why only a year, and why only the English Wikipedia? If they haven't, then why a ban at all? Also, the WMF is doubtless aware that Fram was an admin with a long an prolific history of productive editing. Any office action against them was always going to be controversial; so why wait to post a statement at all? I see that the de.wiki bans were also to a single wikimedia project; but I haven't enough German to find any subsequent discussion. Vanamonde (Talk) 19:52, 10 June 2019 (UTC)[reply]
• WTF???? I wasn't aware of any misconduct from Fram that warranted this. I'm eager to know what prompted this ban.—CYBERPOWER (Chat) 20:01, 10 June 2019 (UTC)[reply]

• Early betting at Wikipediocracy is that this is preliminary to some sort of centralized imposition of either Superprotect or Flow or Visual Editor, Fram being one of the most outspoken critics of WMF technological incompetence and bureaucratic overreach -- not that there is much room for debate about that at this point. I share the views expressed above: we need answers. Carrite (talk) 20:04, 10 June 2019 (UTC)[reply]

  Which is clearly way outside any "office actions". That's called "repression" where I come from, should it be in any sense true. The Rambling Man (talk) 20:11, 10 June 2019 (UTC)[reply]

• Every block needs to be given a reasonable explanation. Without an explanation, we cannot know if a block is valid or not. This entire situation is suspect until an explanation is given. ―Susmuffin ^Talk 20:07, 10 June 2019 (UTC)[reply]
• Since it doesnt appear anyone has asked the question: Has anyone asked Fram? I am sure at least one of the admins and/or arbcom has had off-wiki correspondence with them at some point. While obviously asking the subject of a ban for their version of events has its own drawbacks, in absence of any other information.... Only in death does duty end (talk) 20:08, 10 June 2019 (UTC)[reply]

  Yes, no reply. The Rambling Man (talk) 20:10, 10 June 2019 (UTC)[reply]

  I've already asked on Commons (where he's not banned) if he wants to make any public statement, and offered to cut-and-paste it across if he does. Technically that would be proxying for a banned editor, but I very much doubt the WMF wants the shit mountain banning Fram and me in the same week would cause. ‑ Iridescent 20:11, 10 June 2019 (UTC)[reply]

  I'll do it, then no harm no foul if TRM gets permanently banned. The Rambling Man (talk) 20:13, 10 June 2019 (UTC)[reply]

  Well I pinged him before you posted this and offered same. I have no fucks to give and lets see if he likes me more ;) In more seriousness, I am concerned that the WMF has enacted a wiki-specific limited-time ban, which indicates two things: Firstly its a local en-wp issue, possibly linked to a specific ENWP individual editor, and secondly that its punishment not a genuine concern for safety. If it was, you would just ban someone permanently, and from all wikimedia projects. Only in death does duty end (talk) 20:14, 10 June 2019 (UTC)[reply]

  To expand a little on the above: I want the WMF to ban editors permanently if there is a *safety* issue. I dont want them interfering in local wikis because someone got their feelings hurt. If they want to do that, they can do the rest of the work policing the userbase too. Only in death does duty end (talk) 20:18, 10 June 2019 (UTC)[reply]

• (edit conflict) So what, are they repressing people with no explanation now? What did they violate? SemiHypercube 20:12, 10 June 2019 (UTC)[reply]

  SemiHypercube, disappearing people without explanation is accepted practice at Wikipedia in extreme circumstances; there are sometimes good reasons we want someone gone and don't want to discuss it publicly for their own privacy's sake. What's unique here is that the WMF are saying that Fram is untrustworthy here, but trustworthy on every other WMF project, and will become trustworthy here in exactly 365 days' time, both of which are confusing to say the least. ‑ Iridescent 20:16, 10 June 2019 (UTC)[reply]

  Not to mention that "disappearing" someone like Fram is going to cause a shitstorm, unlike the Great Purge, where you just purged those causing the shitstorm too. I'm afraid to say, and Arbcom may now ban me forever, but this looks like incompetence of the highest order by WMF. The Rambling Man (talk) 20:30, 10 June 2019 (UTC)[reply]

• People I trust say this is warranted, but I do object that this was communicated to stewards and not the local ArbCom. Most en.wiki users don’t even know what a steward is, and the local arb with the least support here has more voters for them than even the most popular steward. Stewards do great work and I trust them and have a good working relationship with them, but local only blocks should be disclosed to the local ArbCom, not a global user group that is mostly behind the scenes on en.wiki. This action was guaranteed to get local pushback, and having users who were trusted locally be able to explain it. I’m someone who has a good relationship with the WMF and stewards, and as I said, from what I’ve been told by sensible people this was justified, but if I was trying to think of a better way to make the WMF intentionally look bad on their biggest project, I couldn’t. TonyBallioni (talk) 20:14, 10 June 2019 (UTC)[reply]

  I can not recall a single instance an explanation was given in the case of WMF ban (and being active on Commons, I have seen them a lot). I do not expect this situation to be different.--Ymblanter (talk) 20:18, 10 June 2019 (UTC)[reply]

  Stewards are informed the reason for every WMF ban, including this one. They can’t say what it is, but considering that this was such an extraordinary event, letting the local group that would be most comparable know the reason would have been the very least that could have been done. Then an arb could say “We’ve seen why and it’s warranted.” TonyBallioni (talk) 20:21, 10 June 2019 (UTC)[reply]

  TonyBallioni, given that it only affects en-wiki it must relate to en-wiki. I no longer have Magic Oversight Goggles, but can see nothing remotely problematic in Fram's contributions or deleted contributions in the past month; is there anything in the contributions of Fram (or User:EngFram, who the WMF have also ejected) that raises the slightest concern? (You obviously don't need to specify.) ‑ Iridescent 20:25, 10 June 2019 (UTC)[reply]

  Iridescent, I don’t see any recent suppressed contributions that raise red flags. I don’t know any more than anyone else other than “Yes, this was intentional, and yes, it looks valid” from people who are generally sensible. Of the WMF departments, T&S is usually one of the most sensible. My objection here is that I know they’re pretty sensible because I’ve worked with them in the past on other things and trust them. Most en.wiki users don’t know that T&S is any different than [insert pet bad idea from the WMF here] and so communicating with the local ArbCom so at least some name recognition here could say they know why. TonyBallioni (talk) 20:40, 10 June 2019 (UTC)[reply]

Pretty sure WMF has never made a unilateral decision on a local matter that resulted in a long term editor and sysop being removed for local issues either. So...Praxidicae (talk) 20:21, 10 June 2019 (UTC)[reply]

• This might sound a bit like conspiracy theory nonsense but has anyone checked to see if WMFOffice is compromised? Ivanvector (^Talk/_Edits) 20:22, 10 June 2019 (UTC)[reply]

  Ivanvector, I was thinking something similar but that seems unlikely, as stewards have indicated that the ban was justified, and the wmfoffice account doesn't seem compromised, based on its edits. 💵Money💵emoji💵^💸 20:39, 10 June 2019 (UTC)[reply]

• I've emailed them - I suggest everyone do the same to push some weight on that route. There are actions that could warrant this - but they'd have to be confident it was Fram not a compromised account. That normally requires a bit of time consideration. Which let's us ask...why such a dramatic sudden action . ARBCOM can handle off-wiki information, so that's even fewer possible actions that could lead to this. We should also ask ARBCOM to discuss it at their monthly chat - I suspect several requests from us would have more impact. Nosebagbear (talk) 20:29, 10 June 2019 (UTC)[reply]

  Yes yes, I emailed them hours ago. Nothing at all, of course. I do wonder how much thought went into this on behalf of WMF. Perhaps the UK government have paid them to create some kind distraction from Brexit? It's probably the only rational explanation. The Rambling Man (talk) 20:33, 10 June 2019 (UTC)[reply]

It does not matter at this point what the action was as WMF acted only in a local capacity and not the global capacity that they should act under. There is no action as far as I'm concerned that would warrant WMF Office involvement in just a local project, this is black and white in my opinion and if Fram's behavior (or non-behavior, considering we don't know what has happened) was a problem only for the English Wikipedia, it should have been dealt with by measures that are in place on the English Wikipedia and not by a WMF employee/global group acting as a rogue arbcom. Praxidicae (talk) 20:31, 10 June 2019 (UTC)[reply]

From WP:OFFICE, the WMF have the right to ban from a single project on the grounds of Repeated misconduct within a single Foundation-supported project, with considerable impact either on that project overall or on individual contributors who are active in that project., but that seems unlikely here, and if there were some kind of misconduct going on, if it were at the level the WMF needed to intervene I'd expect the ban to be permanent. ‑ Iridescent 20:37, 10 June 2019 (UTC)[reply]

Ditto, see my comments above. If T&S have to be involved, why are they doing time-limited bans? Thats how ENWP deals with serial problem users. If its a T&S issue they should either not be involved in day-to-day misbehaviour or should be enacting permanent bans. Time-limited either indicates its punishment or that its not an issue that rises to T&S level. Only in death does duty end (talk) 20:44, 10 June 2019 (UTC)[reply]

• So, are we technically prevented from unblocking? Tiderolls 20:36, 10 June 2019 (UTC)[reply]

  Not in a software sense, but the WMF will insta-desysop anyone who overturns them. ‑ Iridescent 20:38, 10 June 2019 (UTC)[reply]

  Then they need to get their collective asses in gear before someone does something regrettable. Tiderolls 20:43, 10 June 2019 (UTC)[reply]

  Not really. I agree that the shroud of darkness around this matter is regrettable (they haven't even gone to the extent of telling us "we can't tell you anything" yet...), but as long as we sit on the WMF's servers then we as a community are ultimately powerless to do anything about this. We can ask the question, but if we don't like the answer then our only options are to (a) keep quiet and toe the line, or (b) fork the whole encyclopedia under CC licence on to a new set of servers... (and if Wikivoyage vs Wikitravel is anything to go by, such an exercise would probably not end up a success).  — Amakuru (talk) 20:49, 10 June 2019 (UTC)[reply]

  Was that fork borne of a constitutional crisis? –xeno^talk 20:53, 10 June 2019 (UTC)[reply]

  Actually, Wikivoyage was a fork of Wikitravel, not the other way around. (See Wikitravel#Community fork in 2012). * Pppery * _{it has begun...} 20:58, 10 June 2019 (UTC)[reply]

  @Amakuru: - there is one other step we've seen before. In the wake of the Superprotect saga, and the failure of the Community board members to act, all three were replaced. But before we get that far, and waiting on T&S' "we can't tell you anything for your own good" - perhaps we reach out both to community liasions and to our board members? Nosebagbear (talk) 20:57, 10 June 2019 (UTC)[reply]

  Indeed, if a sufficient number of admins agree this should be reversed, WMF will be committing suicide to act against them. This will go to the press (I can guarantee that given questions I've received offwiki) and WMF will look stoopids. The Rambling Man (talk) 20:55, 10 June 2019 (UTC)[reply]

• Does anyone know of any T&S team members who would be responsive to the community? Surely one of them has to be a reasonable human being that we can actually communicate with? I find it hard to believe that "Trust" & Safety has no problem (further) decimating community relations without any attempt at damage control. Then again, WMF never fails to disappoint in these situations. ~Swarm~ ^{sting} 20:51, 10 June 2019 (UTC)[reply]

  The whole lot of them are listed here (you need to scroll down to reach T&S); pick one you think looks trustworthy. ‑ Iridescent 20:55, 10 June 2019 (UTC)[reply]

  40% of the T&S team don't trust us to let us know what they look like. Enough said. The Rambling Man (talk) 20:57, 10 June 2019 (UTC)[reply]

(edit conflict) Dear members of the English Wikipedia community,

We have been approached by several volunteers with questions concerning the recent Office Action, the time-limited partial Foundation ban of User:Fram covering your project. As we saw similar questions also being asked in your discussions around the project, including here, we thought it is most accessible to interested community members to provide clarifications publicly here:

• What made the Foundation take action at all and why at this specific time?
  • As described on the Metapage about Office actions, we investigate the need for an office action either upon receipt of complaints from the community, or as required by law. In this case we acted on complaints from the community.
  • All office actions are only taken after a thorough investigation, and extensive review by staff. This process usually takes about four weeks.
  • Office actions are covering individuals and not just individual user accounts. Therefore, the measure covers more than one user account in this case.
• Who made the complaint to the Foundation?
  • The Foundation always aims to be as transparent as possible with office actions. However, as outlined in the general information section of the office actions page, we also prioritize the safety of involved parties and legal compliance. Therefore, we do not disclose who submitted community complaints.
• Why did the Foundation only ban for a year?
  • As part of the Improving Trust and Safety processes program, less intrusive office actions were introduced. Those options include time-limited and partial (project-specific) bans to address serious concerns that are, however, temporary or project-specific in nature. For example, if a user has been problematic on one project in particular while contributing without concerns to another community wiki, this can now be addressed in a more targeted way than a full Foundation global ban.
• Why did the Foundation de-sysop? Does this mean that Fram will not be an administrator when his ban ends in 2020?
  • The removal of administrator access is intended as enforcement of the temporary partial Foundation ban placed on Fram. It is the community’s decision what to do with Fram’s administrator access upon the expiration of the Office Action ban.
• What kind of appeal is possible against this office action?
  • As a this time-limited Foundation ban is an outcome of a regular office action investigation, it is governed by the same rules already familiar from Foundation global bans: it does not offer an opportunity to appeal.

As the team carrying out office action investigations, Trust and Safety starts cases from the position that it is up to volunteers to decide for themselves how they spend their free time within the frame of the Terms of Use and the local community’s rules provided for in section 10 of them. The Terms of Use do not distinguish whether a user participates by creating and curating content, building tools and gadgets for peers doing so, helping out as a functionary handling admin, checkuser or oversight tools or in other forms. However, on occasion community members submit evidence strongly indicating cases where local communities consistently struggle to uphold not just their own autonomous rules but the Terms of Use, too. We will continue to consider these rare cases brought to our attention under the framework of the office actions policy. Best regards, WMFOffice (talk) 20:58, 10 June 2019 (UTC)[reply]