Steward requests/Global permissions: Difference between revisions

Add links
From Meta, a Wikimedia project coordination wiki
Browse history interactively
← Older editNewer edit →
Content deleted Content added
VisualWikitext
Line 87: Line 87:
*{{s}} [[User:Eurodyne|eurodyne]] ([[User talk:Eurodyne|talk]]) 05:44, 13 May 2017 (UTC)
*{{s}} [[User:Eurodyne|eurodyne]] ([[User talk:Eurodyne|talk]]) 05:44, 13 May 2017 (UTC)
{{TempSysop|12|2018|05|13||}} —[[User:MarcoAurelio|Marco]][[User talk:MarcoAurelio|Aurelio]] 09:07, 13 May 2017 (UTC)
{{TempSysop|12|2018|05|13||}} —[[User:MarcoAurelio|Marco]][[User talk:MarcoAurelio|Aurelio]] 09:07, 13 May 2017 (UTC)

=== Global editinterface for [[User:Nemo_bis|Nemo_bis]] ===
{{sr-request
|status = <!--don't change this line-->
|domain = global<!--don't change this line-->
|user name = Nemo_bis
|discussion= [[phabricator:T164242]] and related bag of bugs
}}
I offer to help users of a few hundreds wikis fix a few thousands of gadgets, listed by Krinkle at [[phabricator:T164242]]. A broken gadget is enough to make editing hard or impossible for its users, but the fix is often as simple as adding <nowiki>|dependencies=mediawiki.util</nowiki> to [[MediaWiki:Gadgets-definition]] (I have already developed and tested a process to do this quickly).

I have experience collaborating with hundreds of wikis on configuration changes and I've helped multiple wikis fix their JavaScript, but I think it's better to apply such small fixes directly, rather than chase (and annoy) local administrators, especially when there's an urgency because users are frustrated by bugs. I don't know whether I'll also engage in more complex changes: I prefer more experienced JavaScript developers to take care of these if possible (and if someone else took care of the immediate urgency I'd be more than happy!).

A term of 1 year should suffice for now; I'll request deflag if my interest ceases earlier. --[[User:Nemo_bis|Nemo]] 11:48, 14 May 2017 (UTC)


== See also ==<!-- DO NOT EDIT UNDER THIS LINE -->
== See also ==<!-- DO NOT EDIT UNDER THIS LINE -->

Revision as of 11:48, 14 May 2017

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

Shortcut:
SRGR
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 (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.

Requests for global sysop permissions

Shortcut:
SRGS
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 IP block exemption

Shortcut:
SRIPBE
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 SlitherSnakeSempter

Status:    Not done

I for some reason am routinely caught up in global blocks. I don't know why as I have never edited anonymously in a disruptive manner at all. Therefore, I am requesting GIPBE to get around this strange problem. I am currently most active at EN Wikipedia, but this will expand in the future. SlitherSnakeSempter (talk) 19:57, 10 May 2017 (UTC)[reply]

Not done Taking into account your socking history. Ruslik (talk) 12:22, 12 May 2017 (UTC)[reply]

Requests for global rename permissions

Steward requests/Global permissions/Global renamers

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:

  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 editinterface for Nirmos

Status:    Not done

There is now widespread JavaScript breakage across WMF projects, as can be seen at en:Wikipedia:Village pump (technical)#Old script-pocalypse. This is because phab:T122755 was recently resolved, which removed variables that had previously been deprecated. What I'd like to do is:

  1. Update sitewide JS and gadgets so that projects are no longer in script error
  2. Prepare for the next removal (phab:T35837, phab:T72470) so that that removal won't be as painful as this one was

Nirmos (talk) 00:08, 2 May 2017 (UTC)[reply]

  • I am not sure that breakdowns are so widespread. In fact, many scripts on many wikis have already been updated. Ruslik (talk) 18:24, 2 May 2017 (UTC)[reply]
  • For the record, there have been 3 previous (unsuccessful) requests for this permission in the past: [1], [2], [3]. --Vogone (talk) 19:58, 2 May 2017 (UTC)[reply]
  • I am still not convinced by the rationale, and the three failed requests are worrying. --Rschen7754 01:30, 3 May 2017 (UTC)[reply]
    • JavaScript does not currently work on a large number of projects. How is that rationale not good enough? Nirmos (talk) 02:12, 3 May 2017 (UTC)[reply]
      • How many of those wiki's javascript can be fixed by updating the code and/or removing local versions of the code and replacing them with versions on mediawikiwiki or metawiki? --TerraCodes (talk) 02:19, 3 May 2017 (UTC)[reply]
        • I'm not sure I understand the question, but to be perfectly clear, I do not intend to replace local versions of scripts with mw.loader.load calls to other projects, nor do I intend to do any kind of copy-pasting between projects. That's not what this is about and I think that would require a lot more discussion. What I intend to do is very simple adjustments, like replacing addPortletLink with mw.util.addPortletLink, wrapping code that depends on certain ResourceLoader modules with mw.loader.using, declaring missing dependencies on MediaWiki:Gadgets-definition. That sort of thing. Does that answer your question, TerraCodes? Nirmos (talk) 02:59, 3 May 2017 (UTC)[reply]
          • Yes, it does. Thanks --03:57, 3 May 2017 (UTC)
      • "JavaScript does not currently work on a large number of projects" is misleading, because you are implying that all scripts are broken on a large number of projects. That is false. Again I have to Oppose Oppose this sort of doomsday-style justification to get a very powerful right. I have never been convinced of the user's willingness to tread lightly on big wikis which don't like outsiders coming in and editing their scripts either. --Rschen7754 05:54, 3 May 2017 (UTC)[reply]
        • No, it's not misleading. All scripts do not have to generate an error for JavaScript to be down on a site. An error in one gadget – or even in a gadget definition – is enough to stop all other JavaScript from executing. Nirmos (talk) 19:38, 3 May 2017 (UTC)[reply]
          • It indeed is not misleading and Nirmos is describing the situation accurately (and this is once more an example of how most other users have NO clue how Javascript works on this site). Additionally this botdetection is reporting 440 site wide running script pages that are likely to have a problem, some of those don't even compile. And that excludes any mistakes in gadgets and widely used user scripts, which will also cause highly variant failures that can be very confusing to users. —TheDJ (talk • contribs) 11:45, 5 May 2017 (UTC)[reply]
  • Oppose Oppose Per Majora's comments on previous requests. --TerraCodes (talk) 04:01, 3 May 2017 (UTC)[reply]
  • JavaScript is fully broken for all or many users on hundreds of wikis and there are thousands of pages to update, see also phabricator:T164242#3230381. I'd support (temporary) global editinterface for anyone able to help, but the candidate didn't provide information showing experience in the field. --Nemo 08:17, 3 May 2017 (UTC)[reply]
    • Nemo: Ignoring all the work I have done on svwiki, you can see what other projects I have updated on my user page. You are most welcome to look at my contributions on those projects and judge for yourself. Nirmos (talk) 19:41, 3 May 2017 (UTC)[reply]
  • Support Support On it.wiki we are experiencing a lot of problems because of this. We desperately urge skilled peoples being able to fix our broken scripts ASAP. --Roberto Segnali all'Indiano 16:53, 3 May 2017 (UTC)[reply]
    @Roberto Mura: itwiki could always add temporary/limited adminship if desired. — xaosflux Talk 05:10, 8 May 2017 (UTC)[reply]
  • Support Support Nirmos is very experienced and has proven to be competent through his work on svwiki and a lot of other wikis. We can not ignore the fact that many wikis are experiencing difficult problems with JavaScript. If a user like Nirmos wants to help solve these problems, I think the community should be happy about it and assign him the permissions. Frisko (talk) 12:13, 4 May 2017 (UTC)[reply]
  • Support, Nirmos is trusted, and helping hands are always needed. Stryn (talk) 12:31, 4 May 2017 (UTC)[reply]
  • I'm not exactly familiar with Nirmos' his/her Javascript skills in detail since we only just met, but judging from recent contributions it seems decent enough. The user has also been active long enough that a basic level of trust to not abuse his privileges seems in place. The problem is that most of the sites are not moving on the front of keeping their javascript up to date enough to prevent serious user facing problems. Basically everything below en.wp, de.wp and Commons is likely to be a sorry affair, simply because they lack qualified JS developers who are able to take care of / prevent problems. These sites mostly just copy paste from other sites what works and never follow up. Therefor in principal I support this request. However I would caution Nirmos to take his actions slow, to diligently provide edit summaries (more than on a homewiki) and to make use of a tool like tool tourbot where appropriate. —TheDJ (talk • contribs) 11:45, 5 May 2017 (UTC)[reply]
  • Oppose Oppose per most of the rationales on the last 3 requests - the attitudes expressed in these leaves me concerned that local communities interests will not be the top priority. — xaosflux Talk 05:10, 8 May 2017 (UTC)[reply]
  • Oppose Oppose per above. --Steinsplitter (talk) 13:08, 10 May 2017 (UTC)[reply]
  • Oppose Oppose Per above. —Alvaro Molina (✉ - ✔) 06:57, 11 May 2017 (UTC)[reply]
  • Oppose Oppose Per above --Rumelio () 13:54, 11 May 2017 (UTC)[reply]
Not done This request is obviously going nowhere like the previous ones. Ruslik (talk) 12:48, 13 May 2017 (UTC)[reply]

Global editinterface for Petrb

Status:    Done

Hi, I had this permission twice or more, but it was always automatically removed after some time, I would like to have it again, because it helps me maintain Huggle and its configuration pages and templates, which are all over Wikimedia projects, and often protected, thanks. --Petrb (talk) 18:19, 8 May 2017 (UTC)[reply]

Done Granted for 1 year to expire on 2018-05-13. —MarcoAurelio 09:07, 13 May 2017 (UTC)[reply]

Global editinterface for Nemo_bis

Status:    In progress

I offer to help users of a few hundreds wikis fix a few thousands of gadgets, listed by Krinkle at phabricator:T164242. A broken gadget is enough to make editing hard or impossible for its users, but the fix is often as simple as adding |dependencies=mediawiki.util to MediaWiki:Gadgets-definition (I have already developed and tested a process to do this quickly).

I have experience collaborating with hundreds of wikis on configuration changes and I've helped multiple wikis fix their JavaScript, but I think it's better to apply such small fixes directly, rather than chase (and annoy) local administrators, especially when there's an urgency because users are frustrated by bugs. I don't know whether I'll also engage in more complex changes: I prefer more experienced JavaScript developers to take care of these if possible (and if someone else took care of the immediate urgency I'd be more than happy!).

A term of 1 year should suffice for now; I'll request deflag if my interest ceases earlier. --Nemo 11:48, 14 May 2017 (UTC)[reply]

See also

Cooperation requests for: comments (local) (global) · translation

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global_permissions&oldid=16759068"