Wikipedia:Requests/Permissions


Wikipedia Requests

Wikipedia Test-Wiki is for developers.

Please read this: This wiki does not exist for users to test out random nonsense on an exhaustive basis; it's here for developers to check that changes to the code aren't going to cripple the live sites. See also: WP:WWD and WP:NOT. Special:ListGroupRights details available usergroups and their rights.

As a result, administrator status is still not going to be given out to all and sundry. This isn't an arena for you to play with the tools, or mess about, nor is it somewhere you should be testing your bots, etc. - If you want a place that is for you to test out sysop tools, etc, try these sites.

Having said that, if you do need administrator status for a particular reason, request this status and ensure that your userpage here is linked to your home wiki project.

Requests for user rights

edit

After creating the subpage, come back here and transclude the page below ({{Wikipedia:Requests/Permissions/Example}}).

@Cactusisme: You don't have local import or sysop rights on a production wiki, is there anything in particular you will need import rights for, and if so, what will you need it for? Import is quite serious stuff and can mess up quite a bit if used incorrectly, even on a test wiki. EPIC (talk) 16:43, 4 July 2024 (UTC)[reply]
Template importing? Cactusisme (talk) 00:03, 5 July 2024 (UTC)[reply]
Could you be a little more specific; what will you need to import templates for? To test before using it in production? Otherwise I'm not sure what you will need it for as this is a not a wiki for testing rights but rather a wiki for developers to test their stuff before taking it to production to ensure that it's not going to break stuff. Like I mentioned, importupload is a cautious right and can mess up a lot if used incorrectly, even here on testwiki - while this is a testing wiki it is still part of the SUL cluster, and there is generally not much of a need to import things here since we're not on a real content wiki so I would like to know what you will need it for, also considering that you don't have local import rights anywhere. Now, I haven't really handled that many permissions requests here so I'm not the best person to talk but if another more experienced crat here wants to give their opinion (e.g. Xaosflux), that is of course appreciated. EPIC (talk) 01:37, 5 July 2024 (UTC)[reply]
  Oppose See the request immediately below this one. I also have trust concerns based on the user's CentralAuth. Dragoniez (talk) 10:17, 6 July 2024 (UTC)[reply]


The following request has been closed by Ameisenigel (talk) 09:16, 2 July 2024 (UTC) as   Not done.[reply]
Closing rationale: No local admin / importer rights in production wikis. Please use the tools that are listed on Wikipedia:Requests/Tools instead.
Have you tried these sites? Admin rights aren't generally given out to users who don't have them on any other wikis, and testwiki isn't a place to test admin tools. Even if this request will be (partially) approved, importer rights would suffice for your purposes. Dragoniez (talk) 16:48, 29 June 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by EPIC (talk) 18:28, 21 June 2024 (UTC) as   Done.[reply]
Closing rationale: Seems like a valid enough use case, granted for one month as requested.
  • Wüstenspringmaus (talk · contribs · logs), global contribs 18:07, 21 June 2024 (UTC)[reply]
  • Motive for request: I would like to test some new abuse filters that require admin access. I am currently a rollbacker, translation admin and property creator on Wikidata, also test on test.wikidata and active on a few other wikis.
  • Requested rights: Administrator (temporary, 1 month for now)
  • Comments:   Done for one month to begin as per request, should you have use for the rights in the future again, we can consider extending if all goes well. EPIC (talk) 18:28, 21 June 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by EPIC (talk) 09:20, 15 June 2024 (UTC) as   Done.[reply]
Closing rationale: Looks OK to me, valid rationale provided.
The following request has been closed, more comments are not accepted.


The following request has been closed by EPIC (talk) 18:38, 8 June 2024 (UTC) as   Not done.[reply]
Closing rationale: Page was user's first edit in SUL; also not specified what right is being requested, nor any reason for the request.
The following request has been closed, more comments are not accepted.


The following request has been closed by -- Xaosflux (foo/bar) talk 13:43, 4 June 2024 (UTC) as   Not done.[reply]
Closing rationale: This is not ready for open testing.
  • Stang (talk · contribs · logs)
  • Motive for request: To test securepoll running on local wiki per T335201. The Chinese Wikipedia community has a strong interest to use securepoll locally for sysop election, this permission will be really helpful. As securepoll-view-voter-pii is not included, there's no need to worry about NDA related stuff. Maybe this should be done on metawiki, but whatever. Stang 16:07, 1 June 2024 (UTC)[reply]
  • Requested rights: electionadmin
  • Comments:
  • Special:CentralAuth/Stang for convenience. Support. —Justin (koavf)TCM 19:57, 1 June 2024 (UTC)[reply]
  • According to Special:ListGroupRights this right cannot be granted by local users. If a bureaucrat approves this request the right would have to be granted by a steward. --Ameisenigel (talk) 07:24, 2 June 2024 (UTC)[reply]
  • I just noticed that you already have regular administrator rights and they include securepoll-create-poll. I guess you should already be able to create polls. --Ameisenigel (talk) 07:56, 2 June 2024 (UTC)[reply]
    • @Ameisenigel: The reason for this request is that some part of securepoll extension is hard-coded, and you can't do something unless having this group applied to your account. Like, um, you could not add yourself to the "Admin" section on the "create vote" form, there will be an error said "Somebody" is not a member of the electionadmin group. Stang 10:17, 2 June 2024 (UTC)[reply]
  • @Xaosflux: Could you please have a look at this one? Thanks. Stang 05:32, 3 June 2024 (UTC)[reply]
  • @Tim Starling (WMF): is this available for community testing again? I know there was some significant problems at one point. (please @mention me on reply). -- Xaosflux (bar/foo) talk 08:56, 3 June 2024 (UTC)[reply]
    Alternatively, @Martin Urbanec: do you know if all of the underlying issues for this were resolved? (There were many tickets, including phab:T290808). -- Xaosflux (foo/bar) talk 13:06, 3 June 2024 (UTC)[reply]
  • @Stang: so I did a test, and securepoll does still collect and make available private checkuser-like information on anyone who votes in these, unless the poll is explicitly configured to not collect this, however that is something that the voter would have a very hard time knowing before participating. -- Xaosflux (foo/bar) talk 22:38, 3 June 2024 (UTC)[reply]
    So that's likely going to result in this being a   Not done for this request, as you would be gaining checkuser access via this method. -- Xaosflux (bar/foo) talk 23:33, 3 June 2024 (UTC)[reply]
    @Xaosflux: It's true that securepoll does collect pii, but based on my knowledge such information is not accessible to user without a permission called securepoll-view-voter-pii. From the groupright assignment at votewiki, there's two kinds of user group related to securepoll: "electcomm" can create and manage the vote, but they could not see pii; while "electionadmin" can see pii. My request here does not include the permission to see pii, that is not included in the user group here. Stang 01:45, 4 June 2024 (UTC)[reply]
    @Stang I literally just created a poll in the last 24 hours and tested this, the pii is still there. While "securepoll-view-voter-pii" is not listed as configured in the group, it is still available. So more work is needed before this could be extended. A steward could make a poll if something needs to be tested from the voter-side. -- Xaosflux (bar/foo) talk 09:38, 4 June 2024 (UTC)[reply]
    @Xaosflux: Got it, pretty sad to hear this, there's still a lot of work to do with securepoll. Please close this request. Stang 10:52, 4 June 2024 (UTC)[reply]
  Not done due to NDA issues that need upstream work. -- Xaosflux (foo/bar) talk 13:43, 4 June 2024 (UTC)[reply]


The following request has been closed, more comments are not accepted.

.


The following request has been closed by Martin Urbanec (talk) 08:44, 31 May 2024 (UTC) as   Done.[reply]
Closing rationale: Reasonable use-case. Granted sysop rather than interface-admin, as that is sufficient to create JSON pages in NS_MEDIAWIKI (if interface adminship is required at any point, it can be granted as well).
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (foo/bar) talk 13:45, 4 June 2024 (UTC) as   Done.[reply]
Closing rationale: Trusted user.
  • EPIC (talk · contribs · logs) 06:30, 21 May 2024 (UTC)[reply]
  • Motive for request: I'm testing some steward-related/blocking scripts, and I've already been doing some testing here, but since I'm planning to more actively test stuff related to administrative actions on this wiki I'd rather do it with local admin rights.
    I'm a sysop/bureaucrat at test2wiki as well as a steward and a sysop on some content wikis, so I think that might be enough here. EPIC (talk) 06:30, 21 May 2024 (UTC)[reply]
  • Requested rights: Administrator (+bureaucrat, see below EPIC (talk) 20:29, 21 May 2024 (UTC))[reply]
  • Comments:
    • Special:CentralAuth/EPIC. Support Globally trusted user with advanced permissions elsewhere. —Justin (koavf)TCM 06:48, 21 May 2024 (UTC)[reply]
    • Adding that if possible, I would also like to request bureaucrat rights, at least temporarily. Multiple of my tests here will require flagging and unflagging accounts, which will require bureaucrat rights. If help is also wanted in bureaucrat areas I'd also be willing to help out with that.
That said, you can consider granting the crat right for as much time as you feel comfortable with. If I remain regularly active here at testwiki I will consider placing another request to extend it when it has expired. EPIC (talk) 20:29, 21 May 2024 (UTC)[reply]
  Done +sysop, indef; +crat 1 year. -- Xaosflux (foo/bar) talk 13:45, 4 June 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (bar/foo) talk 13:58, 4 June 2024 (UTC) as   Done.[reply]
Closing rationale: Trusted xwiki admin
The following request has been closed, more comments are not accepted.

The following request has been closed by DannyS712 (talk) 03:56, 19 June 2024 (UTC) as   Not done.[reply]
Closing rationale: No support after a month
  • BilledMammal (talk · contribs · logs) 05:33, 17 May 2024 (UTC)[reply]
  • Motive for request: I'm developing updates for enwiki's rmCloser script, and I want to add functionality that allows admins to move a page over an existing page. However, I need admin rights to test this, as I would prefer to discover my mistakes before some unsuspecting admin deletes the main page.
  • Requested rights: Administrator
  • Comments:
  • Special:CentralAuth/BilledMammal for convenience. I have no objections, especially if it's temporary. User has no advanced permissions elsewhere but is also not blocked. Safe enough to try, I reckon. —Justin (koavf)TCM 05:57, 17 May 2024 (UTC)[reply]
      Oppose Object, not an admin on any project, and was very recently blocked on their homewiki for violation their project's arbitration committee restrictions. -- Xaosflux (foo/bar) talk 13:55, 4 June 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (bar/foo) talk 14:22, 30 April 2024 (UTC) as   Done.[reply]
Closing rationale: LGTM, sysop on other projects.
  • ArielGlenn (talk · contribs · logs) 03:18, 30 April 2024 (UTC)[reply]
  • Motive for request: For doublechecking that merged MW patches behave the way they should after deployment to test wikis; some of these patches require admin functionality to check them out. While testing in deployment-prep ought to be enough, well, let's just say that I'd rather have the ability to test here in addition.
  • Requested rights: Admin
  • Comments:
  Done don't break things, ya know :) -- Xaosflux (bar/foo) talk 14:19, 30 April 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (bar/foo) talk 12:42, 14 June 2024 (UTC) as   Done.[reply]
Closing rationale: per below
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (bar/foo) talk 14:21, 30 April 2024 (UTC) as   Done.[reply]
Closing rationale: See below.
  Done don't break stuff. -- Xaosflux (bar/foo) talk 20:41, 13 April 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (foo/bar) talk 14:21, 30 April 2024 (UTC) as   Done.[reply]
Closing rationale: See below.
+ Also, I would like to test some filters. When I test, I will set my filters to logging-only.
  Done added for 12 months. -- Xaosflux (foo/bar) talk 20:39, 13 April 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.

The following request has been closed by -- Xaosflux (foo/bar) talk 14:21, 30 April 2024 (UTC) as   Done.[reply]
Closing rationale: See below.
  Done -- Xaosflux (bar/foo) talk 20:37, 13 April 2024 (UTC)[reply]
The following request has been closed, more comments are not accepted.