Steward requests/Global permissions

Add links
From Meta, a Wikimedia project coordination wiki
< Steward requests
This is an archived version of this page, as edited by 99of9 (talk | contribs) at 04:58, 10 July 2012 (→‎Global editinterface for 99of9: thanks). It may differ significantly from the current version.
Shortcut:
SRGP
This page hosts requests for global permissions. To make a request, read the relevant policy (global rollback, global sysop) 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 requests generally require no less than 5 days of discussion, while global sysop discussions last no less than 2 weeks.
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 (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.

Requests for global sysop permissions

Shortcut:
SRGS
<translate>

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 [[<tvar name="T:GS">Template:List of global sysops</tvar>|Users with global sysop access]] and ask them to subscribe to the [[<tvar name="2">mail:global-sysops</tvar>|global sysops mailing list]].</translate>
<translate> Instructions for making a request</translate>

<translate> 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).</translate>
=== 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''

<translate> 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.</translate>

Requests for global editinterface permissions

Steward requests/Global permissions/GEI-Header

Global editinterface for 99of9

Status:    Done

I am requesting these permissions because I've recently noticed that the sidebars of most other-language wikipedias are not fully translated into English, and vice-versa. These require creating simple language subpages of sidebar terms, and will not be controversial or dangerous. I do not intend to edit .js or .css files (I do have some experience at that, but it is not required for this issue). My first attempt at this was to request that it be done by a local community, but even those editors able to discuss in English do not necessarily have the administrative tools or knowhow to implement the required changes, and are usually focused on improving content in the language of the wiki itself. I imagine this will be even more difficult in smaller communities. Thus if you are willing to allow it, I would like to create the translations myself. (I only speak English, so will seek native guidance before putting translations into other languages on the en-wiki sidebar). Regarding community trust: I am a bureaucrat on Commons, and long-term editor on en-wiki. I am in good standing and free from controversy on all projects (clean block logs and no known disputes). Thanks, --99of9 (talk) 02:49, 25 June 2012 (UTC)[reply]

Comment Comment I kinda don't understand why it is important/necessary to translate the navigation sidebar into English. The only links that needs translation (that I can think of) is probably Village Pump and Community portal, but usually there will either be a redirect or interwiki link. If there isn't one, creating a redirect is much simpler. Other links should usually be content-related, and does not matter to those who can't speak the language imho. Bencmq (talk) 05:04, 25 June 2012 (UTC)[reply]
Comment Comment Interwiki assumes that the visitor is coming from their home language wiki? I wasn't, I was just browsing around some other language wikis, and wanted to know what I was clicking on. For example, if I was at the nl-wiki main page, and wanted to see their featured content page, I'd find it easier to click "Featured content" than "Etalage". Anyway, the way it is properly done is by translating the Mediawiki sidebar, so even if it's simpler to do something different, I'm offering to do the harder but interface-improving thing. I'm not saying it's super-important, but it would have helped me, and I'd like to do it to help others. --99of9 (talk) 05:41, 25 June 2012 (UTC)[reply]
Comment Comment P.S. I notice that zh-wiki is very well translated (into English at least), and uses the exact method I'm suggesting (e.g. here). --99of9 (talk) 05:51, 25 June 2012 (UTC)[reply]
Although the fact that they redirect the main page to "Home page" isn't very helpful as the interwikis on "Home page" take you to the articles of those names instead of the other projects' main pages! QU TalkQu 10:36, 26 June 2012 (UTC)[reply]
Oh yes, that's a bit unusual, I didn't notice those interwikis! --99of9 (talk) 10:28, 27 June 2012 (UTC)[reply]
Comment Comment for what it's worth 99of9 is highly trusted by me after working with them for some years on Commons. --Herby talk thyme 09:34, 25 June 2012 (UTC)[reply]
Comment Comment I've noticed the same issue and agree that adding translations would be helpful for crosswiki people that aren't necessarily fluent in the wiki's language. English translations would be a good start, although I wonder whether it would be possible to automatically make use of the large number of multi-language translations that already exist on Translatewiki. Jafeluv (talk) 09:56, 25 June 2012 (UTC)[reply]
Can you see an easy way? --99of9 (talk) 00:22, 26 June 2012 (UTC)[reply]
Not sure how it goes exactly, but... taking nl:MediaWiki/Vind een artikel as an example, wouldn't it be possible to add a translation to translatewiki:MediaWiki:Vind een artikel/en so that the English text comes automatically from Translatewiki? That way multiple wikis could also use the same translations in case needed. Also, that way anyone registered to Translatewiki could add translations to other languages (as opposed to just a few people with admin/editinterface rights). In any case, someone more familiar with Translatewiki should probably confirm how the system really works. Jafeluv (talk) 09:39, 26 June 2012 (UTC)[reply]
New translations can only be added by updating the Messages file via git. Furthermore English interface message names (like "Find an article") should be used, so that they could be easily used on different wikis and are easier to handle. But still I think that's how it should be done, local interface messages aren't the way to go. - Hoo man (talk) 22:55, 1 July 2012 (UTC)[reply]
That sounds like a very general solution, but also an enormous barrier to entry. I'd guess that the developers have better things to do with their time than add messages. Assuming I'm not yet up for learning git / mediawiki_source, how long is this likely to sit on the backburner? Maybe my efforts would eventually be replaced, but if that timespan is long, then I still think it would be worth improving the interface immediately. Alternately, if a developer is willing to do it, what do they need from me - a list of English terms that should be translated? Their mediawiki codenames on en-wiki? In what format? --99of9 (talk) 04:32, 2 July 2012 (UTC)[reply]
Thanks for the insight, Hoo. I guess one way how this could procees is this: when a project has a custom sidebar entry (e.g. "Vind een artikel"), you could change the sidebar to point to a local MediaWiki: message which has some appropriate general name (eg. MediaWiki:Findanarticle). Then you could create MediaWiki:Findanarticle with "Vind een artikel", and a translation, e.g. MediaWiki:Findanarticle/en with "Find an article". The created MediaWiki: message names could be listed on a centralized page. Afterwards the whole list of new messages could be posted to Bugzilla and developers could add them to the interface whenever, enabling other users to continue translating the messages on Translatewiki. Would that work? For the record, I also Support Support giving 99of9 the rights for this purpose. If my proposal is considered overkill compared to the benefit gained, I have no problem with adding the English versions by using the simpler method described in the nom. Jafeluv (talk) 10:11, 2 July 2012 (UTC)[reply]
@99of9: I missed your request of here, but if you tell me what I have to add to those pages I'm happy to help. :) I Support Support this request btw. Trijnsteltalk 16:05, 25 June 2012 (UTC)[reply]
Never mind. I created the five pages: nl:MediaWiki:Vind een artikel/en, nl:MediaWiki:Today/en, nl:MediaWiki:Etalage/en, nl:MediaWiki:Snelcursus/en, nl:MediaWiki:Kladblok/en. I hope I used the correct translation so a double check of another Dutch admin (Mathonius?) would be appreciated (got his permission, thnx). Trijnsteltalk 16:24, 25 June 2012 (UTC)[reply]
Thanks Trijnstel, they look perfect. One down, hundreds to go :). Thanks for your support. --99of9 (talk) 00:22, 26 June 2012 (UTC)[reply]
Comment Comment What about all those users who have set neither the local default nor English as their interface language? Will it be useful to them too? Otherwise it seems to me that one of the other solutions (e.g. including twn.net) that have been mentioned above might be better than just charging one user with only fixing the things for English. --MF-W 00:44, 3 July 2012 (UTC)[reply]
  • Support. Even if it only affects a couple of people, 99of9 is willing to volunteer his time making it happen. I see absolutely no reason to turn him away, since this would obviously useful to those who use it. Ajraddatz (Talk) 16:32, 4 July 2012 (UTC)[reply]
  • Oppose. Unless you'll do this for all languages into all languages. Seb az86556 (talk) 16:45, 4 July 2012 (UTC)[reply]
    Comment CommentOh? Let us set someone up for a fall 700 wikis * 100+ languages = ???? edits. You'd would like it done by Christmas too? How about being realistic and maybe working on a reasonable goal of setting up the explanatory pages and the framework for all languages so local admins can do it by following some simple instructions. Maybe even investigating if we can have some export/import files, etc. so that others can assist among those who have the rights? — billinghurst sDrewth 11:10, 9 July 2012 (UTC)[reply]
  • Support --Katarighe (Talk) 18:20, 4 July 2012 (UTC)[reply]
    Done The consensus is that it should be granted for the purpose of creating /en subpages of the sidebar interface messages. Following our customary practice the permission is granted for one year until 9 July 2013 with the possibility of renewal. Ruslik (talk) 13:11, 9 July 2012 (UTC)[reply]

Global editinterface for Jack Phoenix

Status:    In progress

Hi.

I would like global editinterface user right to ensure that CSS and JS code on WMF wikis meets the MediaWiki coding standards, which ensure that best practises are followed and no subtle bugs can slip in.

For example, even the English Wikipedia's MediaWiki:Common.js page isn't fully in accordance with the coding conventions; deprecated wgGlobals are used instead of mw.config.get( 'wgSomeGlobal' ) and indentation/spacing isn't consistent. This is quite remarkable, given that the English Wikipedia is the biggest Wikipedia there is and it has a large and active administrator community, of which many people know JS (and CSS too). I'm convinced that the situation isn't necessarily as good as the English Wikipedia's on all other WMF-hosted wikis; some of which may have only very few or no active administrators.

I've been a MediaWiki developer since 2008 and I've written and contributed to plenty of extensions. In addition to that, I've been a Countervandalism Network staff member since late 2007 and ShoutWiki staff member since its foundation.

In the light of all of the above, I dare to claim that I'm pretty familiar with CSS, JS and the associated standards and best practises. If you allow, I would like to make use of these skills in order to improve Wikimedia's wikis. --Jack Phoenix (Contact) 18:17, 9 July 2012 (UTC)[reply]

Requests for new wiki importer permissions

Steward requests/Global permissions/NWI-Header

Requests for global IP block exemption

Shortcut:
SRIPBE
<translate>

Please be sure to follow the instructions below:

Your request might be rejected if you don't follow the instructions. Please review [[<tvar name="GIBE">Global IP block exemption</tvar>|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.</translate>
<translate> Instructions for making a request</translate>

<translate> 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.</translate>
=== 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}}
}}
<translate><!--T:6-->
<Add an explanation here>, thanks</translate>, --~~~~

<translate> 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.</translate>

See also


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

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