Use this page for requests for :
- autopatrollers, uploaders or IP block exemption (which can be assigned by administrators)
- Promotion to sysop, translation admin, bureaucrat or anything not above (which can be assigned by bureaucrats)
- Requests for comment and other miscellaneous requests
Any new flagging to +sysop should have an associated subpage here, except for well-established developers, where a developer is someone who has had changes accepted to the MediaWiki core or a MediaWiki extension where the total number of changed lines in the relevant whitespace-insensitive diffs exceeds 100.
One thing to keep in mind is that unlike most Wikimedia sites, this site is controlled by the MediaWiki developers, not the other users in this community. Being a developer (someone with merge access who uses it to maintain code that runs on Wikimedia sites) automatically entitles you to at least administrator status, and a long-time developer won't find it hard to become a bureaucrat. If you're not a developer, you do have to give some good reason to get any privileges; you should not expect to ever be made a bureaucrat. Something like a third of administrators and a quarter of bureaucrats are non-developers, however, so it's not like you shouldn't bother asking.That said, there aren't really any formal policies on what's required: you just have to convince a bureaucrat. Use common sense―if you're trustworthy and your services are in need, there's no reason not to promote you to administrator at least, but don't ask for administrator without giving a concrete reason (unless you're a developer). Being personally known to a developer or having administrator or higher status on a major Wikimedia project are two ways to be deemed trustworthy.
Requests for permissionsEdit
- Archives: Autochecked user • Translation administrator • Administrator • Bureaucrat • Other user rights
Other requests and requests for commentsEdit
Proposal to remove long-term inactive bureaucrats and interface adminsEdit
- Related: Project:Requests/RfC/Removal of inactive sysops & Project:Requests/RfC/Removal of inactive sysops (2018)
- Current IA/'crat statistics: https://tools.wmflabs.org/meta/stewardry/mediawikiwiki?bureaucrat=1&interface-admin=1
|3||2017-11-05||I'm active again. Tim (SVG) 08:25, 25 May 2020 (UTC)|
From the previous 2 RfCs, it seems clear that admin rights can be held indefinitely. However, neither of them mentioned about the crat and IA flag which are fairly sensitive as both (in a way) can edit the site interface and I believe that they should be subject to the admin activity review.
- I propose the removal of the crat flag and IA flag if the user is inactive for more than 2 years and 1 year respectively. Affected users are listed above.
- To ensure that inactive crats and IAs will have their rights removed, I am also proposing a yearly review, probably in April?. Affected users will be notified on their talk page and emails (if possible) on April 1 and if there isn't any reply to keep the flag:
- crats: A request will be posted on meta to remove the flag a week later (April 8).
- IAs: A local request for a crat to remove the flag a week later (April 8)
- About to log off, but just a note: Stewardry is wrong. Remember the dot's last edit given is from before interface admins were a thing - used the permissions in august. MZMcBride last edited in December 2019, not 2007, and Midom last edited in 2010 (a while ago, yes, but after 2005). The chard above isn't an accurate list of who would be affected under the proposal. --DannyS712 (talk) 10:59, 23 February 2020 (UTC)
Does inactive mean "doesn't edit in general" or "doesn't have recent entries making use of their rights?" I ask because this wiki is fairly low-traffic in terms of rights requests, such that 1-3 crats largely handle every request for permissions. Just because I (or another crat) mostly handle that area doesn't necessarily mean the other crats are inactive. That being said, I am largely in support of a policy to remove rights from inactive accounts so long as we can get a good enough qualification of what activity means in the somewhat unique context of mediawiki.org. I know in the recent RfC about removing inactive sysops, it was brought up by @Legoktm: that some users are still very active on IRC, phabricator, gerrit, etc. I personally think that measuring off-wiki activity is not useful for whether or not on-wiki rights should be kept, because those users can still do everything they need to do on IRC, phabricator, gerrit, etc. without needing elevated privileges on-wiki. Should they wish to retain such privileges however, we need a process to alert the users in question on their talk pages so they can affirmatively say they'd like to hold onto it (if we define "activity" as "any edits" this would also flag them as active again). If they lose it and need it back in the future, I feel it would be pretty uncontroversial to re-grant such permissions. --Skizzerz 20:31, 24 February 2020 (UTC)
- @Skizzerz: I'd generally prefer going with total inactivity, no edits, no actions. To add on with removing inactive sysops, I'll also support in removing the inactive sysops (we have too many (212) here). Perhaps maybe have the same criteria as proposed above for crats (2 years)? Minorax (talk) 09:10, 25 February 2020 (UTC)
- Note, User:Amusso (WMF) more commonly edits as User:Hashar. Both User:Emufarmers and User:MZMcBride are still around (I see them on irc a lot) even if they don't have all that many actions here. I support them keeping their rights. Leaning to remove for the others, unless they write a comment saying they want to keep the rights. Also, have all these users in question been notified of this request? Bawolff (talk) 05:15, 27 February 2020 (UTC)
- @Bawolff: This is a proposal on the policy so there isn't a need to notify those mentioned above as their rights won't be immediately removed if this RFC passes. Minorax (talk) 05:24, 27 February 2020 (UTC)
I'm boggling at the table a bit. It has inaccurate data, but at least it's noted(???). And someone has already pointed out the plainly wrong last edit for my account, and someone else just shrugged it off. And it's a table of 11 users, not hundreds... baffling. I looked at Project:Requests just now and there's a single request that appears to have been declined. I believe local bureaucrats are no longer doing user renames, so I'm curious if there's some work I should be doing that's getting missed? --MZMcBride (talk) 02:11, 28 February 2020 (UTC)
- I've notified all except Emufarmers & MZMcBride since they know the RfC exists and already replied here. As for the staff account, I decided to not notify them. Minorax (talk) 04:08, 29 February 2020 (UTC)
- @Minorax: can you work on getting a more accurate table? While this request is aimed at setting a general activity policy in general, having an accurate representation of who it would impact would be nice to avoid confusion and angst. @MZMcBride: there's nothing you're missing, demand for local crats is incredibly low here. We may get like 2-3 new requests for permissions a month, and that's about it.
- The reason I'm in support of a general policy (i.e. a set of criteria that will be applied going forwards, not just narrowly scoped to the users in some table generated via questionable means) is that it reduces the wiki's attack surface in the event of a compromised account. Ideally, all crats and interface admins will have 2FA enabled, but not all sysops will. I know this particular RfC is scoped for just crats and interface admins, but it is something I'd like to extend to all privileged access (whether now or in the future). However, given the low amount of work here that privileged access is actually needed for (at least on the crat side), I also want the criteria for being "active" to not rely on requiring the use of such rights. It would not be fair to MZMcBride (for example) if they were to lose crat simply because someone else jumped in faster to handle those 2-3 permissions requests a month. In the same vein, I'd be fine with waiving any activity requirements for accounts with 2FA enabled, because the barrier to compromising such accounts is significantly higher. --Skizzerz 17:52, 29 February 2020 (UTC)