Meta:Requests for adminship
Most requests should be listed here for at least seven days; bureaucrats should only close after the minimum time foreseen in the relevant policy. Discussions are not closed early. Adminship will be granted by a support ratio of at least 75%. If a request hasn't been addressed by a bureaucrat after a lengthy period of time, please leave a note at Requests for help from a sysop or bureaucrat. Requests may be extended, or put on hold by bureaucrats, pending decision or finding of consensus.
Requests for temporary adminship and bot requests may be less formal and often go for a shorter duration if consensus becomes clear after only a few days of discussion.
All editors with an account on Meta, at least one active account on any Wikimedia project, and a link between the two, may participate in any request and give their opinion of the candidate. However, more active Meta editors' opinions may be given additional weight in controversial cases.
See below for information on prerequisites on submitting a request, and how to add a nomination.
Information
Note that this page is for access on Meta only. See the permission request to stewards page for adminship/deadminship requests on other projects.
Regular adminship
- Before requesting admin access, please check the policy for requesting adminship.
- Use the box below, insert your username:
- Place a request on this page, by transcluding the subpage, for example
{{Meta:Requests for adminship/Username}}
. Please put the newest request on the top. Bear in mind that even if you do meet the criteria above this does not mean that the community will automatically approve a request. - Please note, past administrators who have given up their rights must meet all criteria at the time of the new request. There is no separate process for reinstating past administrators.
Please note: Ill-considered nominations for adminship can be draining and deflating to both the community and the candidate. Any successful candidate will need to be able to demonstrate sufficient experience within the Wikimedia community, in addition to a familiarity with Meta-Wiki. If a candidate is not already a local administrator or holder of advanced permissions on a Wikimedia content project, they are less likely to pass a request for adminship here at Meta-Wiki.
Bureaucratship
Add your request below under the bureaucratship section. Please note:
- Only active administrators can become bureaucrats, and only after at least 6 months of regular adminship.
- User is endorsed by two current bureaucrats after they nominate themselves here.
If you fail any of these requirements, you will not be assigned the bureaucrat flag. For more information see the Meta bureaucrat page.
Other access
For these types of access, create a subpage just as you would for regular adminship and add it to the appropriate section of this page.
- Interface adminship: Please read the Meta interface administrator page. The WMF requires two-factor authentication for this access.
- Limited adminship: If you need sysop access for a particular reason (such as ability to edit protected pages), you may request limited adminship on Meta. If granted, the user understands that they will only be allowed to use the tools for the tasks they were approved, and not doing so will be grounds for immediate removal. Temporary sysop access will normally be valid for one month unless requested and granted otherwise.
- Bot: Please read the bot policy. This wiki allows global bots and automatic approval of certain types of bots; for other bots, add your request below under the bot section, in the same way as an admin request.
- CheckUser: please read the CheckUser policy and add your request below under the checkuser section, in the same way as an admin request.
- Oversight: please read the Oversight policy and add your request below under the oversight section, in the same way as an admin request.
- Translation administrator: please read Meta translation administrator page and Meta’s page about translate extension. No fixed time limit for these requests is defined, and there are no particular requirements; if you provide a valid reason and demonstrate that you know and understand how to prepare pages for translation, your request will most likely be granted.
- CentralNotice administrator: Meta Central notice administrator page grant access to manage and edit banner campaigns. Because of the potentially huge impact of banners on the wikis, this should be granted carefully and sparingly. The WMF requires two-factor authentication for this access.
For these types of access, just ask on Meta request for help from a sysop or bureaucrat page:
- MassMessage senders: please read about MassMessages, and provide a clear reason for requesting access. Specify whether you need it temporarily or permanently.
- Uploaders
- Patrollers
Requests for global renamer permissions are handled at global permission requests to stewards page.
WMF Office Staff and Contractors
- If you are an WMF Official or Contractor and need rights on Meta-Wiki to perform your duties the process is different. Please have a look at the WMF staff userrights policy on Office wiki[restricted access] and follow the procedure described there. If in doubt, please contact Trust and Safety; or send an email to ca
wikimedia
org.(source)
Requests for regular adminship
Requests for limited adminship
- Kizule (talk • contribs • deleted user contributions • logs • block log • abuse log • CentralAuth • stalktoy) Bureaucrats: user rights management.
Not ending before 19:50, 22 May 2025 (UTC)
I'm requesting temporary administrator rights to manage machine translations for the Serbian language and conduct a general cleanup of Serbian translations. I'll need them just for a period of 3-7 days, no longer.
These administrator rights will solely be used for deleting unfixable translations, those not worth updating, or fully machine-generated ones. This is for this specific purpose, and nothing more.
I'm currently doing this on translatewiki.net as well, I'm a regular administrator on Serbian Wikipedia, therefore, I have enough experience.
Thank you so much for your understanding and consideration! Kizule (talk) 19:50, 15 May 2025 (UTC)
- About how many of these pages are there?
- Can you provide some examples of different types of these pages.
- Thank you, — xaosflux Talk 22:08, 15 May 2025 (UTC)
Requests for interface adminship
Requests for bureaucratship
Requests for CheckUser access
- "Meta:Requests for checkuser" redirects here. To request checkuser information, see Meta:Requests for CheckUser information.
Requests for Oversight access
- "Meta:Requests for oversight" redirects here. To request oversighting, see Meta:Oversighters#Requests.
Requests for translation adminship
Requests for CentralNotice adminship
Requests for bot flags
- DreamRimmer bot (talk • contribs • deleted user contributions • logs • block log • abuse log • CentralAuth • stalktoy) Bureaucrats: user rights management.
I have been manually archiving processed requests on Steward requests/Permissions for the past 15–16 months, and I now want to use a bot to automate the process. Manual archiving is a tedious and time-consuming task, and processed requests often remain on the page for several days. I propose archiving handled requests if the last response is at least 15 hours old. Please let me know if you have any questions or suggestions. – DreamRimmer ◆ 14:21, 11 May 2025 (UTC)
Support, definitely has the required technical skills. I'm extremely astonished to see that SRP archiving was manual till now; so thanks for voluteering and helping out so far. – Svārtava (tɕ) 18:48, 11 May 2025 (UTC)
Support ToadetteEdit (talk) 19:49, 11 May 2025 (UTC)
- To clarify, I raised this issue back in November about the archiving issue, and I an really glad that this is getting resolved :) ToadetteEdit (talk) 07:51, 12 May 2025 (UTC)
Support--A09|(pogovor) 20:41, 11 May 2025 (UTC)
- I definitely support using a bot to archive the page, but does it have to be a flagged bot? Given the traffic at that page, I think running the bot once a day should be enough; and two or three edits per 24 hours (one to the main page and one or two edits to archive pages) shouldn’t flood the recent changes. (By the way, why did you choose a timeout of 15 hours? I’m okay with it, I’m just curious, as it’s not a “round” number.) —Tacsipacsi (talk) 22:45, 11 May 2025 (UTC)
- I don't think the bot flag is really needed since there probably won't be many edits, but I will leave that for the crats to decide. As for the 15-hour timeout, I think that's a reasonable amount of time for users to check back and for others to respond, but I am open to suggestions from the stewards if they feel the requests should stay a bit longer. – DreamRimmer ◆ 00:37, 12 May 2025 (UTC)
- I would keep it at 48 hours, as users occasionally need to respond after closure (eg adding 2FA). Leaderboard (talk) 04:47, 12 May 2025 (UTC)
- +1 to that. ToadetteEdit (talk) 07:54, 12 May 2025 (UTC)
- I also support 48 hours. – Svārtava (tɕ) 11:59, 12 May 2025 (UTC)
- I would keep it at 48 hours, as users occasionally need to respond after closure (eg adding 2FA). Leaderboard (talk) 04:47, 12 May 2025 (UTC)
- I don't think the bot flag is really needed since there probably won't be many edits, but I will leave that for the crats to decide. As for the 15-hour timeout, I think that's a reasonable amount of time for users to check back and for others to respond, but I am open to suggestions from the stewards if they feel the requests should stay a bit longer. – DreamRimmer ◆ 00:37, 12 May 2025 (UTC)
Support —MERULEH 22:59, 11 May 2025 (UTC)
Strong support no-brainer request and reason. //shb (t • c) 00:01, 12 May 2025 (UTC)
Strong support --Galahad (sasageyo!)(esvoy) 00:07, 12 May 2025 (UTC)
- Support, but if I recall correctly, SRP processing used to be automatic. What happened then? Leaderboard (talk) 04:46, 12 May 2025 (UTC)
- JarBot handled archiving until December 2022, but it was stopped after its operator, جار الله, was banned by the WMF. MajavahBot tried to take over, but was stopped due to the different archiving structure, which required completely different functionality from what it used on other SR pages. Since December 2022, archiving has been done manually. – DreamRimmer ◆ 05:40, 12 May 2025 (UTC)
- Couldn't JarBot's code be used, or was that closed-source? Leaderboard (talk) 14:37, 13 May 2025 (UTC)
- @Leaderboard: It was closed-source, and their Toolforge tool was eventually deleted because the WMF ban was global and applied across all WMF platforms. I will make my code open-source so that others can use it in my absence. – DreamRimmer ◆ 15:31, 13 May 2025 (UTC)
- But if it run on Toolforge, didn't their bot had to be open-source as per the WMCS terms of service? (I'm aware this is getting off-topic, so feel free to continue on my talk page or elsewhere) Leaderboard (talk) 11:01, 14 May 2025 (UTC)
- I was not around when Jarbot was active, but based on my experience with Toolforge, there is no requirement to link the source code on-wiki. Some Toolforge users do not share their source code publicly and also restrict access to their files on the Toolforge server. These tools are still considered open source and comply with WMCS terms of service because Toolforge admins can access them. – DreamRimmer ◆ 14:24, 15 May 2025 (UTC)
- But if it run on Toolforge, didn't their bot had to be open-source as per the WMCS terms of service? (I'm aware this is getting off-topic, so feel free to continue on my talk page or elsewhere) Leaderboard (talk) 11:01, 14 May 2025 (UTC)
- @Leaderboard: It was closed-source, and their Toolforge tool was eventually deleted because the WMF ban was global and applied across all WMF platforms. I will make my code open-source so that others can use it in my absence. – DreamRimmer ◆ 15:31, 13 May 2025 (UTC)
- Couldn't JarBot's code be used, or was that closed-source? Leaderboard (talk) 14:37, 13 May 2025 (UTC)
- JarBot handled archiving until December 2022, but it was stopped after its operator, جار الله, was banned by the WMF. MajavahBot tried to take over, but was stopped due to the different archiving structure, which required completely different functionality from what it used on other SR pages. Since December 2022, archiving has been done manually. – DreamRimmer ◆ 05:40, 12 May 2025 (UTC)
Strong support Obviously. Jianhui67 talk★contribs 04:47, 12 May 2025 (UTC)
Support 48 hours.--Cactus🌵 spiky ouch 10:24, 12 May 2025 (UTC)
Support Heh, I did notice you had to manually archive SRP the other day and was surprised to see it has been manually archived for the last 2.5 years. Support of course - ideally the bot would be the same for all steward request pages, but that doesn't matter that much. --Ferien (talk) 16:49, 12 May 2025 (UTC)
Support --V0lkanic (talk) 16:51, 12 May 2025 (UTC)
Support Trusted users and DreamRimmer is already very technical experienced editor and already working on various task with her bots on enwiki. --Warm Regards, Abhimanyu7 talk 07:34, 13 May 2025 (UTC)
- Just noting that I have started the bot for trial runs so we can see how it performs. It is set to archive requests that are 48 hours old. – DreamRimmer ◆ 16:46, 13 May 2025 (UTC)
Support--Turkmen talk 07:34, 14 May 2025 (UTC)
Support – Phương Linh (T · C · CA · L · B) 11:10, 14 May 2025 (UTC)
Support A lot of other wikis have bots that function similarly so I'm surprised that we don't have one to automatically archive some of the highest traffic pages here.-FusionSub (talk) 14:13, 14 May 2025 (UTC)
See also
- Current administrators
- Current removal discussions
- Previous confirmation discussions (obsolete)
- Index of requests and proposals
- Information on user groups
- Meta–steward relationship
General requests for: help from a Meta sysop or bureaucrat · deletion (speedy deletions: local · multilingual) · URL blacklisting · new languages · interwiki map
Personal requests for: username changes · permissions (global) · bot status · adminship on Meta · CheckUser information (local) · local administrator help
Cooperation requests for: comments (local) (global) · translation