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 (with rare exceptions, 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.
Requests for 2 Factor Auth tester permissions
Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions.
Testing this service may result in the loss of your access and is not recommended for inexperienced users.
Instructions for making a request
Before requesting 2FA tester global permissions, make sure that:
Copy the template below to the bottom of this section and INDICATE you have read the Help page.
If the request page is currently protected, please file as an edit request on the talk page.
=== 2FA Tester 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 no reason not to grant one. A steward will review the request.
Requests for other global permissions
Please be sure to follow the instructions below:
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.
Hello all. After thinking about it for a while, I'm applying for the abusefilter-maintainer group. I often monitor the AbuseFilter dashboard on logstash, and there are many filters out there that are either terribly slow, or simply broken. In the past, I've sometimes left maintenance requests at the local village pumps, but some issues have never been fixed, and new ones continue to emerge. As an AF-maintainer I would make these fixes myself, as long as the functionality of the filters wouldn't change; example fixes are checking for divisions by zero and optimizing regexps. FTR, I'm already an abusefilter-helper (since 2018). Thanks, --Daimona Eaytoy (talk) 11:41, 10 April 2022 (UTC)[reply]
Support per the above users affirming the requestor's clear competency if not proficiency. As well, I would just add that I was impressed with the requestor's quick response to Base's question on whether the global permission is needed over, say, a local permission, and to the requestor's diplomatic skills. Dmehus (talk) 16:32, 10 April 2022 (UTC)[reply]
Strong support Since he's an AF developer there is no doubt that his contribution will be very useful for the maintenance of all projects. I personally thought he already had the ability to modify filters on all projects. Imho the flag can be assigned for the maximum foreseen by the policy (1 year)! Thanks for volunteering :) --Superpes15 (talk) 17:06, 10 April 2022 (UTC)[reply]
@Xaosflux: All fixes would be purely technical, and regexps would only be optimized if they make the filter too slow (so that it appears on the profiling dashboard on logstash), or prevent its execution entirely due to reaching the backtracking limit. That said, I would check case by case how impacting a certain change could be. Sometimes, there's essentially a single way to fix something (e.g. in the enwiki examples, you need to check whether an array element exists, and there aren't many ways to do that), in which case I'd be comfortable making the change myself. I personally know how important readability and maintainability are with filters and code in general, but I also know that sometimes it all boils down to personal preference. I would certainly try to rewrite the code as best as I can so that others can still read it and explain the changes in the "Notes" section. Also, if I feel that my changes may impact readability I'd leave a message to the village pump instead of making the change. However, I wouldn't do that when I'm sufficiently confident about my changes, just because someone could find my code less readable because they have different preferences (that is, unless those preferences can be inferred by reading the filter itself). --Daimona Eaytoy (talk) 15:11, 11 April 2022 (UTC)[reply]
Support obviously technically competent for this, and I am not concerned that updates would create any purposeful editor-facing effects. Please do take care in leaving notes (generally in the filter notes) about changes introduced when there are local maintainers. It can be easy to annoy others with things that seem technically irrelevant (e.g. indentation spaces) or that may be in place for some sort of reason (some sort of "or %string" chain vs a "contains" expression) if there is any local resistance it is rarely worth arguing over. Most local abusefilter editors should warmly accept your expertise! — xaosfluxTalk17:13, 11 April 2022 (UTC)[reply]