Jump to content

Steward requests/Global permissions

From Meta, a Wikimedia project coordination wiki
(Redirected from SRIPBE)
Shortcut:
SRGP
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).

Quick navigation: Dynamic pages:
Cross-wiki requests
Meta-Wiki requests


Requests for global rollback permissions[edit]

Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions, and not doing so would reflect poorly on your suitability.
Please also review the Global rollback policy.
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.

Global rollback for SHB2000[edit]

Not ending before 22 June 2024 11:22 UTC

Hello, everyone. Although my x-wiki matrix is perhaps not the most extensive with my x-wiki work being somewhat sporadic, global rollback would greatly help assist from SWViewer and the restore tool (which is what I've been using), especially when dealing with x-wiki vandalism and LTAs. I'm an admin on the English Wikivoyage, English Wikibooks and Meta, and hold RB privileges on Commons, the English Wikipedia, Simple English Wikipedia and Wikidata. I realise my x-wiki activity is on the lower side of what's ideal, but I thought I'd give it a shot.

I've well and truly understood the global rollback policy, including the GR policy on the 7 wikis with additional local policies on global rollback. --SHB2000 (tc) 11:22, 17 June 2024 (UTC)[reply]

Requests for global sysop permissions[edit]

Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions, and not doing so would reflect poorly on your suitability.
Please also review the Global sysops policy.
Stewards
When you give someone global sysop rights, please list them on Users with global sysop access and ask them to subscribe to the global sysops mailing list.
Instructions for making a request

Before requesting, make sure that:

  1. You have a global account ;
  2. 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.

Requests for global rename permissions[edit]

Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions, and not doing so would reflect poorly on your suitability.
Please also review the global rename policy and the global renamers policy page.
Stewards
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.
Instructions for making a request

Before requesting, make sure that:

  1. You have a global account;
  2. You are logged in on this wiki, and the account is part of your global account;
  3. 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.

Requests for global IP block exemption[edit]

Please be sure to follow the instructions below:
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 stewards(_AT_)wikimedia.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.
Instructions for making a request

Before requesting global IP block exemption, make sure that:

  1. You have a global account ;
  2. 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.

Global IP Block Exempt for Двійка[edit]

Per UTRS #89351 --DeltaQuadBot (talk) 22:00, 1 June 2024 (UTC)[reply]

Global IP block exempt for Butcher2021[edit]

Editing from Wikipedia-hostile territory, thanks, --Butcher2021 (talk) 11:41, 4 June 2024 (UTC)[reply]

Global IP block exempt for Ternera[edit]

Hello, I would like to request global IP block exemption for my account. I've been doing cross-wiki anti-vandalism work and running into blocks on Wikivoyage projects in particular, saying my IP is blocked (this happens when I try to log into these projects to revert vandalism). My ISP uses CGNAT, so I may appear to have the same IP address as others and my IP may be flagged as spam in some cases. I already have IP block exemption on my home wiki, but it would be helpful to have it globally for the other small projects that I am effected by. Thanks, --Ternera (talk) 20:26, 10 June 2024 (UTC)[reply]

Hi, are you affected by a global block or are the blocks just regular local blocks? If it is the latter, global IP block exempt will not help you as it will only exempt you from global blocks. If you are affected by local blocks, you need to request a local IP block exemption. EPIC (talk) 20:31, 10 June 2024 (UTC)[reply]
I don't believe they are local blocks because I've had it happen fairly often.. I've definitely seen it on the Wikivoyage projects, but those are definitely not the only ones that I've been effected on - there are other small wiki projects where my IP is blocked. I have previously made a mobile hotspot from my phone to get around it. I would prefer to not use my phone's mobile data though. Ternera (talk) 21:09, 10 June 2024 (UTC)[reply]

Requests for 2 Factor Auth tester permissions[edit]

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:

  1. You are logged in on this wiki;
  2. You have read the help page about two-factor authentication and understand how it could lead to irrecoverable loss of access to your account ;
To request 2FA tester global permissions
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.

2FA Tester for Alanwill00[edit]

Hi, I have read the guide and I know and understand the risks and benefits of the feature. I would like request access to 2FA, thanks, --Alanwill00 (talk) 21:33, 17 June 2024 (UTC)[reply]

Requests for other global permissions[edit]

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:

  1. You are logged in on this wiki;
  2. 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 interface editor for U.T.[edit]

At the time of the request, dark mode has been rolled out on Wikimedia wikis. Meanwhile, many sites (especially on small wikis without local interface admins) are still using deprecated prettytable attribute in their local common.css. This is causing a severe issue: under dark mode, tables are displayed with white background, making the texts inside illegible. I connected with ԱշոտՏՆՂ before, and know how to deal with this issue (he has fixed it on hy:). This is why I'm requesting a temporary GIE access here: 2 weeks might be sufficient for this specific task. --U.T. 14:05, 14 June 2024 (UTC)[reply]

  • This seems like it needs a more detailed plan explained first. Do you have a report of what projects need work, and what the different work for each project would be? The GS's may be able to solve this if there is a plan. — xaosflux Talk 15:21, 14 June 2024 (UTC)[reply]
    Yes, there have been tools for this. Night mode checker reports where errors are occurring on dark mode and some useful details. Also, I can search prettytable with global search tool and find where it's still existing (especially in common.css). These are what I'm going to fix: one has to gain write access on these pages in MediaWiki namespace to carry out the plan above. However, this issue also occurs on some GS opted-out wikis, especially existing templates which has color attributes incompatible with dark mode. U.T. 16:00, 14 June 2024 (UTC)[reply]
    This seems to be too broad of a task, especially with you potentially targeting large projects with many interface admins; while the hywiki fix may have been to delete the entire element definition from that css, that may not be the best fix on every project. "Accessibility for Reading (Vector 2022)" is an opt-in beta feature, problem with are not something I'd consider "severe" enough to force changes on other projects yet. A discussion about problems with that beta software interacting with popular project configurations can be started at mw:Talk:Reading/Web/Accessibility for reading. — xaosflux Talk 20:06, 14 June 2024 (UTC)[reply]
  • Oppose Oppose It seems like a bad idea to give the global keys to the MediaWiki namespace to someone who is actively planning to make these changes on GS opted-out wikis. Opting out means just that, they don't want the global sysops, so why would they want a GIE to make these changes either? Just submit it as an edit request if it means that much to you, but the attitude being given off of somewhat of an ignorance of community consensus is alarming, especially for rights like GIE and GS. EggRoll97 (talk) 04:10, 17 June 2024 (UTC)[reply]
    As for me, I have clear plans for my actions. Also, I would certainly be very cautious: deeply I understand what would occur if I take reckless actions on these interface objects. Therefore, I vouch that I carry out the aforementioned tasks carefully. If only on GS opted-in wikis actions should be taken, then why we need a GIE user group enabled globally, without exceptions? U.T. 05:29, 17 June 2024 (UTC)[reply]
  • Oppose Oppose per EggRoll97. * Pppery * it has begun 04:56, 17 June 2024 (UTC)[reply]
  • Support Support - I am not opposed to this. Regarding Xaosflux's claim that a beta feature doesn't warrant GIE, I don't think that's true - it's an officially supported beta feature and I think that's OK. I find the "GS opt-out" argument to be odd, because why have the GIE group at all then? Leaderboard (talk) 05:19, 17 June 2024 (UTC)[reply]
    That comment is that I think the "severe issue" priority being claimed appears to be excessive. — xaosflux Talk 09:31, 17 June 2024 (UTC)[reply]
    See here for an example, which I mentioned to Jdlrobson as well. As it shows, texts in some tables (typically ones in "further down" sections) aren't readable. This is why I call it an issue somewhat "severe". We must consider about readability before arguing about what colors appear better on screens. U.T. 11:02, 17 June 2024 (UTC)[reply]
    I don't dispute the condition may appear; just that the impact is only to (a) logged in users, (a.1) who have opted in to a beta test, and (a.1.1) who have toggled on this view - a severe minority of people that may view a page. In your example of dawiki - that project has interface admins, who actively and recently have been seen maintaining their sitewide scripts example. They can already decide what the best way to update their project could be. Documenting proposed fixes communities could use and linking to said documentation from mw:Talk:Reading/Web/Accessibility for reading could certainly be useful and would be a good thing for you to do first regardless (as if you do end up making these changes to projects you are nor normally present on, being able to link your edit summary to details of the change would be helpful). — xaosflux Talk 13:19, 17 June 2024 (UTC)[reply]
    In my opinion, the fact that it's an officially supported beta (even if not a lot of people use it) does support the OP's case for interface-admin rights, given that they primarily plan to use it on smaller wikis - it's like an abuse filter maintainer updating scripts. I can understand the hesitance if this was some random user-written script though. In other words, I am not convinced we should be routing this user to others, though agree that documenting the fixes is a good idea in any case. Leaderboard (talk) 13:23, 17 June 2024 (UTC)[reply]
    If a software roll out is causing a severe problem there is a good argument that it should be rolled back until proper mitigation plans are developed, communicated, and executed. — xaosflux Talk 13:40, 17 June 2024 (UTC)[reply]
    In your sense, my action is part of mitigation. U.T. 13:42, 17 June 2024 (UTC)[reply]
    Could be, though execution is the 4th step of that, not the first. — xaosflux Talk 14:16, 17 June 2024 (UTC)[reply]
  • I don't have the technical expertise to comment on the merits of the request, but I do want to add that one of the purposes of this group is to give trusted users truly global interface editor access - the intended scope here is all wikis, not gs wikis, and even large projects like enwiki explicitly allow GEIs to edit within the scope of their rights. Previous successful requests have been made on the basis of implementing some changes across all wikis. That said, there should also be strong merits for the specific reason of the request, and I'll let others speak to that. – Ajraddatz (talk) 15:22, 17 June 2024 (UTC)[reply]

See also[edit]