Commons:Requests and votes

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Shortcut
COM:VOTE
This project page in other languages:

This is the requests and votes page, a centralized place where you can keep track of ongoing user requests, and where you can comment and leave your vote. Any user is welcome to comment on these requests, and any logged in user is welcome to vote.

When requesting rights that do not need the support of the community (e.g. filemover) please go to Commons:Requests for rights!

How and where to apply for additional user rights on Commons[edit]

All applications made on the above pages are automatically transcluded onto this page.

How to comment and vote[edit]

Any logged-in user is welcome to vote and to comment on the requests below. Votes from unregistered users are not counted, but comments may still be made. If the nomination is successful, a bureaucrat will grant the relevant rights. However, the closing bureaucrat has discretion in judging community consensus, and the decision will not necessarily be based on the raw numbers. Among other things, the closing bureaucrat may take into account the strength of any arguments presented and the experience and knowledge of the commenting users. For example, the comments and votes of users who have zero or few contributions on Commons may at the bureaucrat's discretion be discounted.

It is preferable if you give reasons both for Symbol support vote.svg Support votes or Symbol oppose vote.svg Oppose ones as this will help the closing bureaucrat in their decision. Greater weight is given to argument, with supporting evidence if needed, than to a simple vote.

Purge the cache. Use the edit link below to edit the transcluded page.

Requests for Oversight rights[edit]

When complete, pages listed here should be archived to Commons:Oversighters/Archive.

  • Please read Commons:Oversighters before voting here. Any logged in user may vote, although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for CheckUser rights[edit]

When complete, pages listed here should be archived to Commons:Checkusers/Archive.

  • Please read Commons:Checkusers before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for bureaucratship[edit]

When complete, pages listed here should be archived to Commons:Bureaucrats/Archive.

  • Please read Commons:Bureaucrats before posting or voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.

Requests for adminship[edit]

When complete, pages listed here should be archived to Commons:Administrators/Archive.

  • Please read Commons:Administrators before voting here. Any logged in user may vote although those who have few or no previous edits may not be fully counted.

No current requests.


Requests for license reviewer rights[edit]

No current requests.

Requests for permission to run a bot[edit]

Before making a bot request, please read the new version of the Commons:Bots page. Read Commons:Bots#Information on bots and make sure you have added the required details to the bot's page. A good example can be found here.

When complete, pages listed here should be archived to Commons:Bots/Archive.

Any user may comment on the merits of the request to run a bot. Please give reasons, as that makes it easier for the closing bureaucrat. Read Commons:Bots before commenting.

Legobot 3 (talk · contribs)[edit]

Operator: Legoktm (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Importing election tabular data (example)

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): Multiple "one time runs", as needed

Maximum edit rate (e.g. edits per minute): 6

Programming language(s): Python

I've been working on importing election tabular data to Commons for use on English Wikipedia articles. I manually imported 2012-2016 for California, and am now at a level where I would like to bulk import the rest of the data. I'm going to be starting with the MIT Election Lab data (CC-0 licensed). The initial import will create roughly 1000 pages (20 elections times 50 states), and I plan to import additional election data as I find sources and we have templates adapted and ready for use (someone has already asked me about extending this to Canadian elections). Legoktm (talk) 07:17, 13 November 2018 (UTC)

Discussion[edit]

  • Please make a test run. --EugeneZelenko (talk) 14:56, 13 November 2018 (UTC)
    Done, I had it create 10 pages and then stop. Spot-checking the California data, it looks correct. Legoktm (talk) 07:27, 14 November 2018 (UTC)
    Looks OK for me, but it'll be good idea to mention source in edit summaries. --EugeneZelenko (talk) 14:53, 14 November 2018 (UTC)
    Ok, how about Importing election tabular data from MIT Election Lab? Legoktm (talk) 21:36, 14 November 2018 (UTC)
    URL will be better. --EugeneZelenko (talk) 14:30, 15 November 2018 (UTC)
    Alright, now it's Importing election tabular data from MIT Election Lab (https://doi.org/10.7910/DVN/IG0UN2). Legoktm (talk) 03:59, 17 November 2018 (UTC)

Krdbot 4 (talk · contribs)[edit]

Operator: Krd (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Tagging files with {{OTRS received}}, i.e. {{subst:OR|TICKETNUMBER}}, for all open OTRS permissions tickets where the affected files names are machine readable.

Test edit: Special:Diff/324998478

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): continuous

Maximum edit rate (e.g. edits per minute): perhaps 50 per day

Bot flag requested: (Y/N): N

Programming language(s): Perl

The code will parse all open tickets in the permissions hierarchy and look for possible file names in the subject and body of the first article. If file names are detected, and the files currently contain any issue like {{OTRS received}}, {{No permission since}}, {{No license since}}, {{Delete}} or {{Copyvio}}, it will add {{OTRS received}} accordingly to delay the deletion process. Additional details are open to discussion. --Krd 14:49, 22 October 2018 (UTC)

Discussion[edit]

  • Good idea. Hopefully it will avoid deletion of some files with a valid permission. --Yann (talk) 01:16, 23 October 2018 (UTC)
  • @Krd: I also think it is a good idea. It may benefit from some of the recent discussions at MediaWiki talk:Gadget-PermissionOTRS.js, like expanding notifications in DRs to include use of OTRS received. Also, you may want to add "|user=Krdbot".   — Jeff G. please ping or talk to me 06:31, 23 October 2018 (UTC)
  • Please remove Bot: from edit summaries. --EugeneZelenko (talk) 14:44, 23 October 2018 (UTC)
    • @EugeneZelenko: Generally we ask users to add "Bot:" to the edit summary (as per standard practice). Please elaborate. --Steinsplitter (talk) 10:45, 24 October 2018 (UTC)
      I think user's (bot's) name is enough. --EugeneZelenko (talk) 13:30, 24 October 2018 (UTC)
      • @EugeneZelenko: Hm... OK. The test edit looks fine, i think this should be approved as soon as possible, it will reduce a lot of work for volunteers and the task seems uncontroversial. --Steinsplitter (talk) 14:39, 24 October 2018 (UTC)
  • The bot task is good idea. I have some concerns with the template used or, to be precise, the text in the template. Both the German and English content of the template contain: the message was not sufficient to confirm permission for this file.. Per the description of the bot tasks, the bot will not perform a qualitative assessment. Thus, it the template used should be more in line of an OTRS ticket was received but not reviewed yet --Schlurcher (talk) 15:04, 23 October 2018 (UTC)
To answer my own question: please consider to add |reason=processing to the template --Schlurcher (talk) 15:08, 23 October 2018 (UTC)
Perhaps a new reason of "queued" would be better.   — Jeff G. please ping or talk to me 15:13, 23 October 2018 (UTC)

Ijonbot (talk · contribs)[edit]

Operator: Ijon (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Iterating over Category:Images from Wiki Loves Monuments 2018 in Ukraine and ensuring Jewish heritage photos are properly categorizing, according to whether they are nationally-recognized monuments or only special-nomination objects, according to this page] on Ukrainian Wikipedia.

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): One time run.

Maximum edit rate (e.g. edits per minute): 50

Bot flag requested: (Y/N): Y

Programming language(s): Ruby

Ijon (talk) 14:13, 6 October 2018 (UTC)

Discussion[edit]

  • Please use Help:Gadget-HotCat-style edit summaries. --EugeneZelenko (talk) 14:18, 7 October 2018 (UTC)
    • Could you clarify what exactly you'd like to see? Explicitly name all the categories affected (the bot makes multiple cat changes in a single edit)? Or do you just mean to add a link to the bot page from the edit summary? Ijon (talk) 14:49, 7 October 2018 (UTC)
      I meant list of categories affected. Task description could be shorter. --EugeneZelenko (talk) 13:39, 8 October 2018 (UTC)
      @Ijon: ?--Krd 10:38, 24 October 2018 (UTC)
      @Ijon: Could you please give some feedback? Thank you. --Krd 11:31, 12 November 2018 (UTC)
      Hello, sorry for the delay. I have made the changes requested. One can examine the source code (in Ruby) if one wishes. Thanks! Ijon (talk) 17:43, 12 November 2018 (UTC)

Requests for comment[edit]

Centralized discussion

Template: View • Discuss  • Edit • Watch