This page hosts requests for global permissions. To make a request, read the relevant policy (global rollback, global sysop, global rename, …) and make a request below. Explain why membership is needed for that group, and detail prior experience or qualifications.
This is not a vote and any active Wikimedia editor may participate in the discussion.
Global rollback and global interface editor requests require no fewer than 5 days of discussion while abuse filter helper and maintainer requests require no fewer than 7 days. Global renamer and global sysop requests require no fewer than 2 weeks of discussion. For requests that are unlikely to pass under any circumstances, they may be closed by a steward without further discussion (after a reasonable amount of input).
Please note that Global rollbackers discussions are not votes. Comments must present specific points in favor of or against a user's approval.
Instructions for making a request
Before requesting, make sure that:
You have sufficient activity to meet the requirements to be allocated the global rollback flag
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable.
=== Global rollback for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = global <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
::''Not ending before {{subst:#time:j F Y H:i|+5 days}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than 5 days (other than requests that are unlikely to pass under any circumstances, no other exceptions are allowed, no matter how obvious the result may seem). This is not a vote, and all input is welcome. Stewards will determine whether consensus exists; when doing so it is likely that the weight given to the input of those involved in cross-wiki work will be most influential.
You are logged in on this wiki, and the account is part of your global account;
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable. If you previously requested that right, please add a link to the previous discussion(s).
=== Global sysop for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = global <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
:''Not ending before {{subst:#time:j F Y H:i|+2 week}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than two weeks (no exceptions are allowed no matter how obvious the result may seem). This is not a vote, and all input is welcome. Stewards will determine whether consensus exists; when doing so it is likely that the weight given to the input of those involved in cross-wiki work will be most influential. Please note: Since 2019 all global sysops are required to have two-factor authentication (2FA) enabled.
When you give someone global rename rights, please add them to the list of global renamers and ask them to subscribe to the global renamers' mailing list.
You are logged in on this wiki, and the account is part of your global account;
You have considered the addition of a user language box to your user page
To make a request
Copy the template below to the bottom of this section and explain of why you need the access and why you're suitable. If you previously requested that right, please add a link to the previous discussion(s).
=== Global rename for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!-- don't change this line -->
|domain = meta.wikimedia <!-- don't change this line -->
|user name = {{subst:REVISIONUSER}} <!-- don't change this line unless you're nominating another user -->
}}
:''Not ending before {{subst:#time:j F Y H:i|+2 week}} UTC''
The request will be approved if consensus to do so exists after a period of consideration of no less than two weeks (no exceptions are allowed no matter how obvious the result may seem). While all input is welcome, there is a hard 80% support requirement for this role as per the global renamer policy.
Your request might be rejected if you don't follow the instructions. Please review Global IP block exemption. You may request Global IP block exemption via stewardswikimedia.org if you can not edit this page.
Please note: Global IP block exemption does NOT make one immune to locally-created blocks of any sort, only global blocks.
If you want to edit the Chinese Wikipedia, usually global IP block exemptions will not help you. Please see this instruction to request a local IP block exemption.
Instructions for making a request
Before requesting global IP block exemption, make sure that:
You are logged in on this wiki, and the account is part of your global account;
To request global IP block exemption
Copy the template below to the bottom of this section and explain why you need the access and why you're suitable. If needed, link to relevant discussions.
=== Global IP block exempt for {{subst:u|{{subst:REVISIONUSER}}}} ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = {{subst:REVISIONUSER}}
}}
<Add an explanation here>, thanks, --~~~~
The request will be approved if there is demonstrated need for the permission, such as bypassing a global block from someone who is not the intended target.
Your request might be rejected if you don't follow the instructions.
Instructions for making a request
Before requesting additional global permissions, make sure that:
You are logged in on this wiki;
No specific section on this page exists for the permission you want to request;
To request additional global permissions
Copy the template below to the bottom of this section and explain what kind of access you need and why. If needed, link to relevant discussions. If you hold, or have previously held, the right and are asking for either a renewal or revival of that right, please add a link to the previous discussion.
=== <Add requested permission here> for [[User:Foo|Foo]] ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = Username
|discussion=
}}
<Add an explanation here>, thanks, --~~~~
The request will be approved if consensus to do so exists after a short period of consideration. A steward will review the request.
Global API high limit requestors for CampWiz[edit]
This bot is a part of the tool CampWiz which assists organizers of various edit-a-thon to host, manage campaign, evaluate submissions, publish results (As of now, about 30 campaigns are hosted and 9500+ articles were submitted through this tool). One of its sibling tool helps organizers to generate a list of articles which are not present on their wiki based on topic (As of now, 233k+articles in 150+ lists were harvested). One of our main targets was to reduce the security issue and liability along with privacy issue. As such, this tool uses a single bot account to interact with mediawiki which eliminates the need of storing the user's access token on the server. This bot mainly interacts with mediawiki API using two of the following cases:
FnF List Generator: When determining the missing articles, it uses the categories (in enwiki) to get through its members. It has to go through all of the category members and needs to check whether they are missing in selected language or not. There the performance of this tool heavily depend of each batch size. apihighlimits would allow the performance to improve drastically. Therefore, it needs this right on enwiki.
CampWiz: This tool allows the campaign to have a restriction based on the contributions of the submitter. That is, it can also determine how many bytes + words the submitter added during the campaign period. This is done via retrieving all the revisions during that period and performing calculations. If we get this right on each of the language the tool deals with, the overall speed of submission scrutiny would increase significantly. This needs the right globally.
So, after considering both of the scenerio, I think it would be appropriate to have global apihighlimits flag on this account. (For additional information, this bot has bot flag in several wiki for some write operation. But this global apihighlimits would be used for read operations only). Thanks, --Nokib Sarkar (talk) 19:18, 17 April 2024 (UTC)[reply]
Support As a lead for Wiki Loves Folklore international project these tools have been revolutionary for our Feminism and Folklore writing campaign that ran on Wikipedia and is in Jury phase now. We have plans to open-source this tool for other wiki campaigns also only after intensive testing and confidence for which this userright is requested. Thank you. Tiven2240 (talk) 04:31, 18 April 2024 (UTC)[reply]
Support As a lead for Wiki Loves Folklore international project these tools have been revolutionary for our Feminism and Folklore writing campaign that ran on Wikipedia and is in Jury phase now. We have plans to open-source this tool for other wiki campaigns also only after intensive testing and confidence for which this userright is requested. Thank you. Tiven2240 (talk) 04:31, 18 April 2024 (UTC)
Strong support.~aanzx ✉ © 12:02, 21 April 2024 (UTC)
