Commons:Requests and votes

^{Translate this page}

Shortcuts

• COM:VOTE
• COM:RAV

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

• Oversighter: Commons:Oversighters/Requests
• Checkuser: Commons:Checkusers/Requests
• Bureaucrat: Commons:Bureaucrats/Requests
• Administrator: Commons:Administrators/Requests
• License reviewer: Commons:License review/Requests
• Bot: Commons:Bots/Requests

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

How to comment and vote

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  Support votes or  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

watch

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

watch

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

watch

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

watch

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.

Requests for license reviewer rights

This is a closed request for license reviewer status. Do not make edits to it.

Requests for permission to run a bot

watch

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.

FlickypediaBackfillrBot (talk · contribs)

Operator: Alexwlchan (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions), working for the Flickr Foundation

Bot's tasks for which permission is being sought:

• Improving structured data for Flickr photos which have been uploaded to Wikimedia Commons, e.g. adding creator, license metadata.
• Adding the new ‎Flickr photo ID (P12120) property to all files, to make it easier for other tools to work with Flickr photos

Automatic or manually assisted: unsupervised

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

Maximum edit rate (e.g. edits per minute): tbc, probably 5–10 edits per second

Bot flag requested: (Y/N): Y

Programming language(s): Python

Discussion

• Please don't make manual edits with the bot account. Please make few test edits. --Krd 14:31, 1 November 2023 (UTC)

Interesting proposal. I made one edit to Commons:Flickypedia/Data Modeling, otherwise this looks good. Curious how you will handle conflicting existing SDC claims? --Schlurcher (talk) 17:53, 1 November 2023 (UTC)

Good question! My general approach with these things is to be extremely conservative – imo the V1 bot should be purely additive, and any conflicts should be flagged for manual inspection.

Then a couple of things might happen:

1. The existing SDC looks wrong, so I make a manual edit from my account to fix it. e.g. I’ve already been looking at the use of source of file (P7482) for Flickr photos in the SDC snapshots, and I found ~200 cases where the URL points to the Flickr URL’s profile (/photos/{username}) rather than the photo itself (/photos/{username}/{photo_id}). Those got dropped on a queue and I’ve been gradually tidying them up by hand – opening the files in question and making a manual edit from my account to point to the more specific URL.
3. The existing SDC looks right, so I work out why the bot is disagreeing. Is it a bug in my code, have I interpreted the data mapping wrong, is the data mapping at odds with the community approach to SDC, is the bot missing some bit of info on the Flickr photo. But the bot won't do anything on its own.

There might also be cases where the existing SDC is wrong in large numbers and we'd want to write an automated fix, but that's somewhat risky and I’d want to be extremely careful before doing that. Two possible examples spring to mind:

1. License versions. Flickr photos use CC 2.0 licenses, so that's what the bot will write into the SDC. But what if it finds a Wiki Commons file which links to the 4.0 version of the CC license? That sounds like an easy candidate for a fix buuuut I think there are Flickr users who leave descriptions on their photos saying "I license this as CC 4.0". A human copying their photo across would notice that; the bot might not. So in this case the bot would likely leave it as-is to avoid deleting info.
3. Date granularity. Flickr has different levels of granularity for "date taken". Most photos are DDMMYY, but there are some which are MMYY or YY or "Circa YY". If there are lots of cases where there's an imprecise data but the SDC claims it's a full DDMMYY, we might consider automating that. (It's pretty obvious when this has happened – Flickr always returns a full timestamp from its API, but it sets all the unknown values to 0/1. So a YYYY becomes taken="1950-01-01 00:00:00" takengranularity="6".) The bot could be written to fix these. But I don't know if that's a widespread issue in practice.

If/when the bot does start editing existing SDC claims, I'll make sure we document those with examples – and if there are cases that seem contentious, I'll bring them back for community discussion before actually implementing them. Alexwlchan (talk) 08:13, 2 November 2023 (UTC)

👍 I’ll probably get to making some test edits early next week, and I’ll link them here for inspection when they’re done. Alexwlchan (talk) 07:46, 2 November 2023 (UTC)

• I left some comments about the data model at Commons_talk:Flickypedia/Data_Modeling#Some_feedback_based_on_User:GeographBot. Where can we find the source code? The bot I mentioned is at https://github.com/multichill/toollabs/blob/master/bot/commons/geograph_uploader.py . Multichill (talk) 20:52, 16 November 2023 (UTC)

MappeComuniBot (talk · contribs)

Operator: Sette-quattro (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

Tasks: Upload up-to-date maps of Italian municipalities. There are about 8000 municipalities, boundaries are updated yearly by the national statistical agency. Here is an example of image that will be uploaded, the description will be automatically updated for each municipality: [1]

Bot's tasks for which permission is being sought: upload several images automatically

Automatic or manually assisted: automatic supervised (through OpenRefine)

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

Maximum edit rate (e.g. edits per minute): I don't know the edit rate allowed using the new OpenRefine function for uploading images. As fast as it can, i suppose.

Bot flag requested: (Y/N): Y

Programming language(s): used through OpenRefine Batch Uploading https://www.youtube.com/watch?v=sc6aNNmsNCI

Sette-quattro (talk) 16:03, 20 October 2023 (UTC)

Discussion

• Please make test run. --EugeneZelenko (talk) 15:34, 22 October 2023 (UTC)

Done a test run Sette-quattro (talk) 21:10, 1 November 2023 (UTC)

Looks OK for me, but please fix space in Category: Maps of municipalities of the province of Monza and Brianza. Will be good idea to create templates for legend and data source. --EugeneZelenko (talk) 15:01, 3 November 2023 (UTC)

Ok, I will create the two templates. Thank you and best regards. Sette-quattro (talk) 09:16, 8 November 2023 (UTC)

GlaMainBot (talk · contribs)

Operator: Beao (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

Bot's tasks for which permission is being sought: I've automated lossless crops for Category:Images from the German Federal Archive with borders and need permission to start uploading the results.

Automatic or manually assisted: Manually assisted to start.

Edit type (e.g. Continuous, daily, one time run): One time run for uploads, otherwise daily for my listing of User:GlaMainBot/Most_used_images_for_cleanup

Maximum edit rate (e.g. edits per minute): At most ten uploads per minute.

Bot flag requested: (Y/N): Y

Programming language(s): TypeScript (using mwn)

Beao 07:49, 23 September 2023 (UTC)

Discussion

Just to clarify: Is this to upload as a new version, or to overwrite? If the latter, is there a consensus to do so? I see that those borders include photo credits to the individual photographers, and these are from a respected archive, so I'd just want to make sure that there is agreement that this is desired; I've seen similar situations go either way. Clearly more useful in Wikipedia articles without the borders, but it's not clear to me that we don't want also to host a version with the credit line on the image. - Jmabel ! talk 23:58, 1 October 2023 (UTC)

My thought is to overwrite. I've not seen any written consensus on the matter, but in practice that's what has been done for years in this category. I think that implies a silent consensus, considering these captions have been digitally added by the archive and provide no additional information not already in the description. Beao (talk) 08:36, 2 October 2023 (UTC)

Please make some example edits. Krd 17:06, 6 October 2023 (UTC)

All right, here are three examples:

File:Bundesarchiv Bild 137-068842, Sonderzug der Einwandererzentralstelle.jpg

File:Bundesarchiv Bild 137-068843, Sonderzug der Einwandererzentralstelle.jpg

File:Bundesarchiv Bild 137-068852, Sonderzug der Einwandererzentralstelle.jpg Beao (talk) 10:55, 7 October 2023 (UTC)

Looks good to me. Krd 13:49, 11 October 2023 (UTC)

Any more information or discussion needed? Beao (talk) 12:22, 14 October 2023 (UTC)

[2] Why is this updated so often? Krd 03:04, 19 October 2023 (UTC)

The "Images with watermarks" category is very big, so the retrieval of file usage statistics is batched to a fixed number of images every hour to avoid performance spikes, and I update the gallery after every batch. Is updating gallery pages too often problematic? I could do it less often (I'm thinking if images are not removed from the category), and also avoid doing it when nothing changes. Beao (talk) 15:53, 20 October 2023 (UTC)

Please at least don't update when nothing significant changes. Krd 07:42, 21 October 2023 (UTC)

I've updated the code to update only on changes now! Beao (talk) 09:01, 24 October 2023 (UTC)

I appears to me that there are still too many edits or the statistics pages. (Or is there any relevant work done on these maintenance categories?) Krd 14:31, 10 November 2023 (UTC)

Requests for comment

Centralized discussion
Does the PDART license apply to textile works? (15 November 2023) Does this image contain "love hearts"? (17 August 2023) Overhaul of categories by period (5 December 2022) Version of Saudi flag to use (11 July 2022) Concern regarding revocability of KOGL licenses (22 December 2021) Should deleting content from your own talk page be forbidden? (11 November 2021) Revise the COM:FOP Sweden section (1 February 2021) Change technical name of LRs to license-reviewer from image-reviewer(2 November 2023) User talk:湯崩正海#Image Tagging File:青島ビール放尿動画事件.jpgとUser talk:湯崩正海#File:青島ビール放尿動画事件.jpgで議論しています。皆様のご意見を募集しています。是非、ご参加ください。(2 November 2023)
Template: View   ■ Discuss    ■ Edit   ■ Watch