Steward requests/Global permissions

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by MarcoAurelio (talk | contribs) at 09:12, 8 September 2010 (→‎Global rollback for Quentinv57: fix). 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, though only stewards may use {{yes}} or {{no}} templates.
Cross-wiki requests
Meta-Wiki requests


Requests for global rollback permissions

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 Quentinv57

The following request is closed. Please do not modify it. No further edits should be made to this discussion.

It should make countervandalism easier. Thanks -- Quentinv57 16:30, 26 August 2010 (UTC)[reply]


  • Closed - I see community support here to promote Quentinv57 to the global rollback usergroup. Notwithstanding the objections raised should be taken into consideration and, as all members in this group Quentinv57 is adviced to use the tool with care and in obvious cases of vandalism and/or spam only. --dferg ☎ talk 09:12, 8 September 2010 (UTC)[reply]

Requests for global sysop permissions

<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>

Opt out for Amharic Wikipedia

Status:    In progress

I am bureaucrat on Amharic wikipedia. Please remove Amharic wikipedia from "global sysops enabled". There was no need for us to "opt in" to begin with. Our local admins, who all understand Amharic, have everything under control. One of the requirements for sysop actions on that wiki is familiarity with, fluency and literacy in the Amharic alphabet and language. Otherwise, we may have "global sysops" barging in gung-ho and doing things they do not really understand, as has already happened today. Thank you kindly, Codex Sinaiticus 06:34, 16 August 2010 (UTC)[reply]

Global sysop for Hoo man

I'm active in the SWMT and it would be quit useful to have the global sysop flag, because a significant amount of the vandalism I come over are useless new pages. Further it would be fine to be able to ban users myself, so I do not have to call for stewards that often.

Of course I already read the global sysop page and I have a link to meta on all my user pages, so users can contact me if necessary. Furthermore, I wont do anything if I'm not a 100% sure whether it's vandalism or not.

I know how to use the sysop tools from the administration of private wikis. - Hoo man 13:25, 24 August 2010 (UTC)[reply]

  • Do you have any significant experience with the sysop tool on wmf wikis? Have you been sysop somewhere already? -Barras 13:29, 24 August 2010 (UTC)[reply]
    Only on strategywiki, but I know the policys quite well and I think that I haven't done (if any) much wrong marking pages for deletion using dellieplagiat or requesting urgent blocks from stewards - Hoo man 13:36, 24 August 2010 (UTC)[reply]
  • Comment: You're a very active SWMT member, and I've seen only good work from you in that area. However, you don't seem to have much experience with the sysop tools in Wikimedia projects? Unless I'm missing something, you only have sysop tools in strategywiki, where you've made a total of 1 block and 0 deletions.[1] It would be a good idea to have some prior experience with the tools before applying for global rights. Jafeluv 13:35, 24 August 2010 (UTC)[reply]
    Are you talking about technical experience or community related things? - Hoo man 13:44, 24 August 2010 (UTC)[reply]
    (Sorry for the late response, somehow I missed your follow-up question.) I was thinking more about technical experience, since GS aren't really part of the local community anyway, but both aspects have some importance. Jafeluv 06:46, 26 August 2010 (UTC)[reply]
    That technical experience should be given. The only functions I'm really going to use frequently are block and delete. And I've already used block and delete on strategywiki and the private wikis. Further I'm usually able to understand technical things quite fast - Hoo man 11:49, 26 August 2010 (UTC)[reply]
  • Comment Comment I think you should begin as sysop on a local wiki, because it's important to know how the technical actions are considered by other users. If you was already local sysop I would have fully supported you, because you make very good cross wiki work. This is just a comment, I don't oppose you become global sysop even without the local experience. --Hercule 13:16, 26 August 2010 (UTC)[reply]
    Thats definitely right, but I don't see a chance for me to get a local sysop on a content project, soon. The only WMF wiki, where a local sysop would be useful for me would be enwiki and I have far to less edits for that. - Hoo man 16:20, 26 August 2010 (UTC)[reply]
  • Comment I guess this is as good a time as any to have this come up. Does the granting of global sysop first require that the candidate is an admin on an active project somewhere, or can a trusted, knowledgeable and active crosswiki candidate be considered qualified as well? Obviously global sysop must only be granted to people who have earned trust and shown they have the knowledge needed to use such a tool. I don't really know what to think in this case. I'd like to think that Hoo man has the clue to be a good admin, and I know the xwiki experience is there, but should someone's first experience of active adminhood be as a global sysop? IDK? fr33kman t - c 03:04, 2 September 2010 (UTC)[reply]
    I think making prior adminship somewhere else a requirement could easily give the wrong impression as to what the "job" is about. Global sysop is not the same as administrator. Global sysop is a much more limited a role. An administrator has to deal with content-issues, whereas a global sysop is explicitly not allowed to get involved. Under no circumstances would I want to give rise to the idea that one would have to get experience in all the duties of an administrator first, since as global sysop the person will get into trouble should that same experience be applied. Seb az86556 03:41, 2 September 2010 (UTC)[reply]
    I agree. The only experience should be the evidence of what a person already did (did they tag articles correctly? Did they rollback just blatant vandalism? etc.) since that's the kind of actions they'll be performing without a second opinion, sometimes. So, I think we should evaluate Hoo man based on their past performance, rather than their future potential. -- Mentifisto 15:59, 4 September 2010 (UTC)[reply]

Requests for global editinterface 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 global editinterface permissions, 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 editinterface permissions
Copy the template below to the bottom of this section and explain why you need the access. If needed, link to relevant discussions.
=== Global editinterface for [[user:Foo|Foo]] ===
{{sr-request
 |status    = <!--don't change this line-->
 |domain    = global<!--don't change this line-->
 |user name = 
 |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.


None currently

Requests for global IP block exemption

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 Global IP block exemption
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 [[user:Foo|Foo]] ===
{{sr-request
 |status    = <!--don't change this line-->
 |domain    = global<!--don't change this line-->
 |user name = 
 |discussion=
}}
<Add an explanation here>, thanks, --~~~~

The request will be approved if consensus to do so exists after a short period of consideration (typically 5 days). 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 IP block exempt for Fridae'sDoom

Following my return to activity I was affected by IP blocks at home and at school, primarily on Commons Wiki (now blocked at my school under the categories Open/Mixed Content & Reference) enwikt, enwiki, simplewiki, enwikisource and some zhwikis. This is quite annoying considering I've only just been active cross-wiki-wise and requesting Gloval IP block exemption seems like a sensible thing to do thanks, --Fridae'sDoom 04:14, 5 September 2010 (UTC)[reply]

Addendum: The blocks are long-term school hardblocks so I can't create an account etc. I can edit but my laptop requires me to logon to WMF projects each time I logon to a different network despite the fact I've saved my login. Fridae'sDoom 04:18, 5 September 2010 (UTC)[reply]

  • Note: Hello Fridae'sDoom. The 'global-ipblock-exempt' flag will protect you from being targeted by globally blocked IP addresses only, not locally blocked ones (this permission currently does nothing with local hardblocks). That said if the IP addresses/IP ranges that are causing you problems are locally blocked you'll need to request local IP block exemption flag. Thank you, --dferg ☎ talk 11:33, 5 September 2010 (UTC)[reply]
    Oh, well I was wondering if I am eligible for this flag since I am somewhat active cross-wiki. Fridae'sDoom 06:09, 6 September 2010 (UTC)[reply]
    Actually, if the school machines are shared-use, it'd be preferable for you to not use any accounts with substantial permissions on them. We all forget, at times, and do things like forget to log out after doing some work, or we're in a rush. If you're going to use shared-use machines, I'd really highly suggest making a second account for use on those. Kylu 06:18, 6 September 2010 (UTC)[reply]
    (ec) FD, no one's talking about your cross-wiki activity. The point is, if your school IPs are not globally blocked but only locally blocked, this flag will not do anything. sonia 06:24, 6 September 2010 (UTC)[reply]

See also