(Go: >> BACK << -|- >> HOME <<)
Jump to content

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 Matanya (talk | contribs) at 21:58, 25 January 2014 (→‎Global exemption to CAPTCHA for NigelSoft). 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.
Successful global rollback requests require no fewer than 5 days of discussion, while successful global sysop discussions require no fewer 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>

Global sysop for JurgenNL

Status:    In progress

Hello, I would like to request for GS. I'm a GR and active in the Small Wiki Monitoring Team. I have experience with the sysop tool as being a sysop on nlwiki since March 2013 and as sysop on Commons since a couple of weeks. This tool would help me to delete vandalism, spam pages, block spambots and persistent vandals, who do not listen to warnings. You can find me on IRC at the Freenode network in several channels. Now I have to ask other global sysops or stewards, but it would be much easier when I can do it by myself. JurgenNL (talk) 15:27, 16 January 2014 (UTC)[reply]

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="1">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>

Requests for other global permissions

<translate>

Please be sure to follow the instructions below:

Your request might be rejected if you don't follow the instructions.</translate>
<translate> Instructions for making a request</translate>

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

<translate> The request will be approved if consensus to do so exists after a short period of consideration. A steward will review the request.</translate>

Global exemption to CAPTCHA for Wakkie1379

Status:    Done

This user is helping me to integrate / add the translations being done as part of the medical collaboration with Translators Without Borders [1]. Wondering if they can get CAPTCHA exemption to make their work easier. So far this project has translated around 3 million words of text and is working in about 60 languages. We have local Wikipedians helping in some languages but not others. We of course would love to have more people join us. But till than. Many thanks Doc James (talk · contribs · email) 20:36, 9 January 2014 (UTC)[reply]

Regardless of the merits of this request, I don't think we could act without the target user being involved. However, on the specific merit, I am highly doubtful that we should grant such a permission to a user with 132 edits globally. Snowolf How can I help? 21:00, 9 January 2014 (UTC)[reply]
Sure will get them to post here. CAPTCHA makes working across many wikis a pain. Doc James (talk · contribs · email) 21:01, 9 January 2014 (UTC)[reply]
The CAPCHA entry is slowing me down significantly. I'm working on posting material that is in many languages thus an exemption would be nice.Wakkie1379 (talk) 22:53, 9 January 2014 (UTC)[reply]
There no requirements for this permission except that it is necessary for a particular work and the user is unlikely to misuse it. Ruslik (talk) 19:08, 10 January 2014 (UTC)[reply]
I agree with Ruslik0 here. CAPTCHAs are there to prevent spambots from editing, not humans who voluntarily help out on small wikis. Vogone talk 19:41, 10 January 2014 (UTC)[reply]
There's a need for it. Why not? Ajraddatz (Talk) 02:06, 13 January 2014 (UTC)[reply]
Agreed. CAPTCHA is used to determine whether a user is actually a (spam)bot or a human. In this case, CAPTCHAs are slowing someone down. Why not grant this? PiRSquared17 (talk) 02:24, 13 January 2014 (UTC)[reply]
Agreed too. CATCHAs are there to capture and block bots that perform massive edits wthout controling what they do and without other ways to block them. A refular user, once it is known that it is not a bot, is not a bot, and thus does not need the CATCHA, even if that user made "only" 320 edits (the bots that CAPTCAs are attempting to block are those that have performed many more edits).
Ideally the CATCHA feature should be automatically disabled on all user accounts that have already succeeded the test : this includes logged-on user-accounts for at least one month, and IPs for at most 24 hours, possibly less for some known ranges of IPs used by proxies from mobile ISPs or free wifi hotspots or any open proxy not honoring the "Via"/""For" mechanism to properly detect and separate their distinct users, and open proxies that provide no way to manage their list of users and responsively regulate their outgoing traffic with a locally enforced charter and a known point of contact to reach the admins of the proxy in case of problems).

For example we can accept anonymous user connecting to Wikimedia from TOR. The IP belongs to the TOR range, but these connecting IPs should have a temporary anonymous session id that will work for 24 hours. As long as this session identifier is used for that time, the CAPTCHA will be presented only once to that session (the TOR session identifier should remain in private-data logs, eve n if we expose the IP of the TOR node). The captcha can be passed once by a regular user to create a regular Wikimedia account and then use it to be logged on. Logged on users do not need to succeed later the CAPTCHA sent to TOR users, and the association of that logged on user to TOR should also remain private-data (just like the history list of IPs for the TOR nodes used by that user, it is as much private as other IPs for normal users).

So do not remove CAPCHAs but tune them so that they do not reappear excessively to the same user account or IP. CAPTCHAs are not the proper tools to efectively block real abusers. verdy_p (talk) 04:37, 14 January 2014 (UTC)[reply]

Done --MF-W 13:49, 15 January 2014 (UTC)[reply]

Global exemption to CAPTCHA for NigelSoft

Status:    Done

I often asked to enter CAPTCHA when editing other wiki programs (such as Wikivoyage, Wikibooks, etc.), sorry for my poor English, thanks, --Nigel 04:12, 17 January 2014 (UTC)[reply]

Done Matanya (talk) 21:58, 25 January 2014 (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=7228686"