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!
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.
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.
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.
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.
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.
I'm not going to be wordy. I was a Commons Administrator for 12 years, from 2006 to 2018, when I lost the status because of inactivity. Much of that was my career and slowly growing apart from the Wikimedia projects in general. But in the last couple of years I've increased my involvement in the projects, helping when I've found the time. And I managed to bring myself to Wikimania this year in Katowice, reacquainting myself with the community and meeting a huge number of new people.
I was satisfied with just being a contributor and reviewer, however, I understand there is a huge backlog of things that need to be done, and I felt compelled to ask for the administrator rights again so I can better help with tasks here.
Weak oppose All due respect for your work, but IMHO flag should be granted also with regard of more recent activity... but as for Commons namespace (most relevant for admin work) unfortunately I see far less than 100 edits of yours in the last two years, and why should I presume it would be so much more in future? Sorry --A.Savin08:44, 25 September 2024 (UTC)[reply]
This isnt english wikipedia as per COM:DEADMINAdministrators who have lost admin rights through inactivity but who expect to become active again may re-apply through the regular process. there is no inquisition required for admins returning after inactivity. The specified requirement is that they expect to become active. Gnangarra09:40, 26 September 2024 (UTC)[reply]
Reason: I am quite familiarized with the license review process and its intricacies. I understand the importance of reviewing licenses to make sure Commons has as much content as we can while keeping away media that was incorrectly tagged as CC at its source. I'm happy to help with the license review backlog we currently have. --Rkieferbaum (talk) 14:42, 22 September 2024 (UTC)[reply]
Scheduled to end: 14:42, 24 September 2024 (UTC) (the earliest)
Before commenting on this, I'd like to ask you some Question. @Rkieferbaum, You come across the following files that need to be reviewed - Please give reasons as to why you would accept/decline each of the following:
@Tanbiruzzaman: hi there and thanks for your question. Here are my impressions:
1. Reject. Although the YouTube channel seems to be legitimate, the audio track (composition and execution) are presumably copyrighted and there's no indication of a release. Stills from the video would be acceptable.
2. Reject. CC license listed on Flickr is NC and therefore cannot be used bere.
3. Reject. CC license is ND, cannot be used here. Furthermore, the photograph is arguably derivative of the newspaper, so I might reject it (or at least seek a consensus before accepting it) even if the license listed on Flickr was OK.
4. Tricky one, but I'd also reject it (or at least put it up for discussion). The license on Flickr is acceptable and the account seems to be legitimate, but FOP in the USA doesn't cover sculptures. I see no indication that the artist released his copyright for such reproductions under said license. There seems to be a large number of photographs featuring artwork from the Burning Man up on Commons, though, including a few from this photographer, but I couldn't find a discussion about this around here that results in this type of photograph being acceptable.
5. Reject. The YouTube channel seems legitimate but this video is basically a slideshow of several pictures taken from all over the internet, and none of the ones I searched are free.
Question Hello, thank you for applying and offering to help. Since you have less than 2,500 edits since 2016, can you please talk more about how you became "familiarized with the license review process and its intricacies" .. as in what surprising things did you come across that might not be obvious to a user who does not have any interest in license review? Thank you. // sikander { talk } 🦖 00:21, 23 September 2024 (UTC)[reply]
@Sikander: hi there and thanks for your question. Maybe I'd start with the reply I gave above: I feel like all five examples might be considered acceptable by a user that's not familiarized with this subject, since all of them are stated to be licensed under CC. However, to my understanding, none of them should be accepted for the reasons I listed. Another example that comes to mind, which I've encountered multiple times, is when a YouTube channel or a TV network licenses their content under CC. Within a program, an image that is not free is used for some reason. Someone then uploads the video and uses a frame displaying the non-free content, arguing, even in good faith, that the TV network made that content available under an acceptable license. In such cases, it might be reasonable to interpret that whatever the network actually owns is indeed usable under CC, while still assuming that their use of non-free content did not release that content unless there's robust indication that it did. Please let me know if this answers your question. I'm happy to go into further detail. Cheers. Rkieferbaum (talk) 02:41, 23 September 2024 (UTC)[reply]
Reason: Hello! I have been an active Wikimedia Commons member since the summer of 2021 and I primarily specialize in Russian and post-Soviet topics. Since February of this year, I have had the flag of an auto-patrolled participant, and since July 22 - a file renamer. Over the years, I have uploaded thousands of files from many Russian and post-Soviet sites distributed under free licenses, as well as hundreds of my own photographs. I plan to mainly specialize in checking licenses for files primarily from post-Soviet sites, as well as videos from YouTube channels of the corresponding countries. --MasterRus21thCentury (talk) 19:41, 23 September 2024 (UTC)[reply]
Scheduled to end: 19:41, 25 September 2024 (UTC) (the earliest)
Reason: I’d like to express my interest to become a reviewer. I’ve been on here since November 2022 and have contributed my own pictures, mainly focusing on South Korean content. I would help with the backlog of reviews. I hope to help out when needed. Thank you for considering my application!--Hiyyihjaleh727 (talk) 11:01, 26 September 2024 (UTC)[reply]
Scheduled to end: 11:01, 28 September 2024 (UTC) (the earliest)
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.
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.
Bot's tasks for which permission is being sought: upload images, update their description and structured data
Automatic or manually assisted: automatically triggered, when upload happens on OsmAPP.org
Edit type(e.g. Continuous, daily, one time run): when user uploads an image on OsmAPP.org
Maximum edit rate (e.g. edits per minute): 20 ?
Bot flag requested:(Y/N):Yes No - IP exemption is enough
Programming language(s): TypeScript
Note:
I am creating an open-source app for browsing OpenStreetMap – the OsmAPP – and currently I am developing an upload tool, which lets OSM users add images to any map features and link them together.
I already requested last year, but the development took longer, Wiki API is quite challenging to work with. :)
Although, I have a big issue now – the OsmAPP.org is hosted at Vercel Platform, which is unfortunately completely blocked from accessing Wiki APIs. I asked Wikimedia Stewards if it is possible to be unblocked, but they said the only option is to flag OsmappBot with the "bot flag". So can I ask for the flag for this reason, please?edit: no need for Bot Flag, IPBE is working good. See discussion below.
I welcome any ideas or recommendations how to make this upload process more useful for Wiki-projects. After the OsmappBot is unblocked and I have a working demo, I will submit it also to Village Pump.
I had the same issue. Resolved it by requesting the IP Exception right, not the Bot right. Would that help?. These uploads should appear on recent changes, so I would like to consider other options that bot right. --Schlurcher (talk) 10:59, 22 September 2024 (UTC)[reply]
Thanks. We manage to make a test run from our production server and all works fine 🎉 Can you please grant a permanent IPBE?
I uploaded few images from my app - see the bot's contrib page. Since this is not an import, but real-time upload on behalf of OSM user, any change I make to the bot will only affect future uploads.
Should I completely finish the UI in the OsmAPP, or could I talk at the Village Pump first? eg. is the current images enough to asses usefullness for the wiki project, or should people be able to upload images themselves? Thx. Zbytovsky (talk) 09:55, 25 September 2024 (UTC)[reply]
Bot's tasks for which permission is being sought: File description cleanup and categorization for files uploaded with Reworkhelper tool. Per this request
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):
Bot flag requested:(Y/N): N (the bot already has a bot flag )
@Krd, I believe consistency and ease of navigating files uploaded with a specific tool. It's easier to find all uploads by a specific tool because of Category:Files by upload tool and the way the tools therein utilize the category. But that's not possible/much more difficult to do if the tool puts its name just in the file description, the way this tool does. – Ammarpad (talk) 17:26, 17 September 2024 (UTC)[reply]
Automatic or manually assisted: Manually assisted. The bot follows "divide and conquer" tactics. Since it seems to be impossible to apply one solutions to > 300,000 media files lacking an infobox template, it will work on sets of files, usually defined by same author / creator (assuming that those files share sufficient similarities). The bot will be run multiple times on that set of files in different modes. First, analyze the file page content and try to categorize each of its components, without modifying and content on Commons. This step will be repeated (manually) as often as needed to adapt the categorization patterns, until a pattern set that fits for all file pages of the current set has been found. Now, a "dry-run" ("simulation") generates an overview over the "planned" modifications (see txt and SQLite analysis and simulation results for Category:Media missing infobox template (maps t1)). Only if this simulation result seems acceptable, the bot will run in "doit" mode to apply the "proposed" edits.
Edit type(e.g. Continuous, daily, one time run): Multiple times a week, but not daily.
Maximum edit rate (e.g. edits per minute): Maybe 5-6 per Minute?
Sorry, took some time for me to understand the problem - bot will reach autoconfirmed status on Sep 10, allowing SDC modifications. Once autoconfirmed, I will continue with test runs. Fl.schmitt (talk) 18:21, 8 September 2024 (UTC)[reply]
@EugeneZelenko: yes, but I think this is better than removing parts of the original description. Removed parts are lost completely, for example using "artist" for the original uploader (which is IMO a nice, sympathetic way of referencing a person). That's an individual trait of the original description that's worth keeping. People shouldn't have to crawl the page history for this. The bot's general approach is to keep the original file description as intact as possible. Its main task is identifying SDC-relevant data, adding SDC and add {{Information}} for a uniform appearance. Keeping the original description is also some sort of "safety net" against the loss of relevant and important information about the file. Fl.schmitt (talk) 15:32, 11 September 2024 (UTC)[reply]
An example of edits is this. The bot is aimed to assist replacing names of some parameters in the templates {{Japanc}}, {{Japanp}}, {{Aichic}}, etc which I am testing now. Affected files are not too many, but neither few, and by limiting edits within certain categories, it will be unlikely to give harm to unrelated files. --トトト (talk) 12:59, 30 August 2024 (UTC)[reply]
I have tested with my account. And all the necessary edits related to the parameter name changes of {{Japanc}} and {{Japanp}} are completed for now. So I have tried another task today, adding region:JP_scale:5000 to geodata of files from Japan. This was innitially tried from Tototobot (talk·contribs) account, but an error message occured and the task was terminated unexpectedly at PAWS. Perhaps was it because of antispam filter? So I did it on my own account. --トトト (talk) 23:38, 2 September 2024 (UTC)[reply]
Hi @EugeneZelenko: No - this is something I've planned for the future. That being said, would it be OK to have the message displayed in English with a link for the user to view the message on other languages in a central Meta-Wiki page? And can this be done later (i.e, after the bot starts running here)? Leaderboard (talk) 16:15, 22 August 2024 (UTC)[reply]
I think this shouldn't be done. We don't make much use of temporary user rights at Commons, and I don't remember even a single case where rights expired without the user noticing it but leading to disruption. If a temporary right expires, it will be extended on request, and it makes no difference if renewal happens before of after it expires. If there are precedents which suggest different, please advise. --Krd07:36, 29 August 2024 (UTC)[reply]
Hi @Krd: , my experience (at least on Meta) is a bit different - I've seen cases like metawiki:Talk:Steward_requests/Global_permissions/2024#Question happen which was what motivated me to write this bot. Now Commons might be a bit different on that respect, but in my opinion, I see this as a "no loss" situation and while yes the user can renew the rights after expiry, the point is to avoid this disruption entirely especially if it's a right that requires some sort of discussion. Worst case the user ignores the notification. And Commons does appear to make use of temp rights, at least from the user rights log (covering rights such as primarily IPBE, account creator and trials for rights such as autopatroller).
(Note that if the decision is to not approve this bot which I understand, Commons will be placed in the bot's opt-out list which means that no user can opt-in and the bot will be disabled entirely on the wiki. Users can easily opt-out from the bot however if they want) Leaderboard (talk) 09:02, 29 August 2024 (UTC)[reply]
I think worst case is that by the notifications users may request renewal for rights they actually don't need, just because they can. But, I'm just providing feedback and will make any decision here. Krd06:26, 30 August 2024 (UTC)[reply]
"users may request renewal for rights they actually don't need" - can happen even without a reminder, right? I do appreciate your feedback in any case BTW - this helps when thinking about it for other wikis as well. Leaderboard (talk) 06:37, 30 August 2024 (UTC)[reply]
It can happen anyway, but per my experience the reminders will significantly raise the number of cases. If you look at Commons:Administrators/Inactivity section, the part of users who signed for keeping their right and still was inactive half a year later, has always been significant, and just dropped a bit in the last few years, Krd02:04, 2 September 2024 (UTC)[reply]
Bot's tasks for which permission is being sought: add the following structured data statement and qualifier to the file page of a new upload that is detected as a logo by this tool.
Automatic or manually assisted: automatic, supervised
Edit type(e.g. Continuous, daily, one time run): continuous
Maximum edit rate (e.g. edits per minute): it depends on the amount of image uploads and on the amount of images detected as a logo. Hard to tell for now
Wouldn't it be better to add them with a separate property? While I'm in favor of adding more such ways to identify images, I don't think it mixes well with other statements. This was attempted and finally discarded with "depicts" statement a while back. Please make sure these statements can also be searched with Special:Search. Enhancing999 (talk) 14:53, 1 August 2024 (UTC)[reply]
Is this bot going to be used as "act once on new uploads", "act once on all existing files", "potentially act more than once on the same file", or what? Unless it only acts exactly once on any given file, what is to prevent it getting into an edit war if its edit is reverted or otherwise changed? - Jmabel ! talk18:11, 1 August 2024 (UTC)[reply]
Good. Is there any chance that the bot could also look at the wikitext for {{Own work}} and add a maintenance category (call it Category:Own work logo to checked) if it appears to be a logo and is claimed as "own work"? We see that combination a lot, and it is almost never true. And possibly something similar for a logo + any CC license, because that's usually false as well: we very rarely get a license for any logo that is above the threshold of originality. - Jmabel ! talk15:15, 12 August 2024 (UTC)[reply]
I agree that the ability to search for logos plus own work and/or CC licenses would make a lot of sense. I think this is something we can do by querying structured data. For instance, we can already run a query like this to look for own work files with CC BY-SA 4.0. As soon as the proposed logo statements get added, we can then insert a wdt:P31 wd:Q1886349 constraint in the query. MFossati (WMF) (talk) 09:50, 14 August 2024 (UTC)[reply]
Comment As requested by the rules, we've test-run the bot on 100 uploads randomly sampled from uploads made between Aug 21 and today, and here are the results:
4 medias were deleted beforehand, so no edit
1 media was skipped (maximum retries attempted due to maxlag without success), so no edit
It appears each file is edited twice. Is that for technical reason, or can the edits be combined in any way? Krd17:36, 30 August 2024 (UTC)[reply]
Great point, Krd! It made me realize that the current code first adds the claim, then adds the qualifier, thus producing two edits. I've just tried that we can do the other way around. So - yes - we can indeed combine them into a single edit. I've updated the code accordingly. Thanks a lot, this is really helpful. MFossati (WMF) (talk) 14:16, 9 September 2024 (UTC)[reply]
@Enhancing999 Sorry for the long answer, but I felt the need to clarify some things about the request.
We need to start somewhere to see if the experiment is of some value to the moderators. This is an experiment within the first quarter OKR work for FY24/25 (WE2.3.1). We don't think a new property would work, especially because the property proposal request would likely be considered too specific in scope to be accepted by the Wikidata community, not without reasons.
We can quickly and easily use an existing property, and see if it’s valuable. If not, we will rollback as quickly and easily. The property instance of (P31) seems like the best fit, because we think it’s specific and meaningful. More importantly, the property is indexed, thus enabling search queries both in Special:Search and in Special:MediaSearch. Furthermore, qualifiers are also indexed, so it will be possible for moderators to find media classified as a logo by this bot. You can either use a search query (example with Special:Search, example with Special:MediaSearch) or a SPARQL one to achieve it.
If detecting and tagging incoming logos does not help with easier logo moderation, then our plan is to rollback our own edits at the end of the experiment. If it does help, then we’re planning to investigate other ways to store and query such data, as we are considering other experiments in the near future as suggested by the community. Sannita (WMF) (talk) 15:09, 9 September 2024 (UTC)[reply]
Wikidata easily creates properties that are just meant to be used for Commons. This shouldn't take much time and compared to working speed of WMF (It's seven weeks since you asked for input), this shouldn't be an issue. Nothing prevents you for indexing this property as well.
If you think a separate property wont work, it means that ultimately this wouldn't work using instance of (P31) either. I think such implementations need more attention than once every month.
Given the massive community backlash WMF got from an ill-prepared, hastily implement, not community feedback driven, likely costly previous experiment mixing machine contribution with our highly valued volunteer contributors, I think it's good to take good care this time, especially as a simple way was suggested already seven weeks ago. ∞∞ Enhancing999 (talk) 15:43, 9 September 2024 (UTC)[reply]
There are likely few false positive in the first test set as it's still followed, but last time, it became problematic when person at WMF developing it moved on to something else.
Based on past experience, I guess you know what happens afterwards: you will have to wait 7 weeks for an acknowledgment, then you will be told to ask for a change in the next wishlist, and, even if everybody agrees with it, you will have to wait for the next annual plan to have it scheduled. Possibly somebody will then throw it out entirely, because they don't know how to fix it.
In any case, the idea is to classify also images where there is a lower confidence in the automatism so review is necessary.
Using two different properties allows users to easily switch between volunteer assessment and machine assessment, focus on volunteer assessment while excluding machine assessment if they happen to agree. ∞∞ Enhancing999 (talk) 11:12, 13 September 2024 (UTC)[reply]
I agree that most of them are some kind of symbols or graphics, but I'd guess a third of them would not be put under Category:Logos, so "instance of logo" doesn't make much sense then. Am I mistaken? Krd14:16, 13 September 2024 (UTC)[reply]
It really depends what the logo people want to do with it. Today it's "logos", but it could be just any image type or topic. The confidence level of the classification can also evolve or be changed. ∞∞ Enhancing999 (talk) 14:29, 13 September 2024 (UTC)[reply]
Come to think of it, maybe the statement with the new property should be qualified with the confidence level (for the classification of the image) and the program version being used (if not available, the current date). ∞∞ Enhancing999 (talk) 09:08, 17 September 2024 (UTC)[reply]
You can't distinguish them any more when someone thinks they are correct and also adds a P31. Or would they have to remove the qualifiers? And no, looking at individual files and/or edits is definitely not a solution. Please make sure the results can be view by querying both with search and on SDC portal (hopefully eventually open). ∞∞ Enhancing999 (talk) 09:16, 21 September 2024 (UTC)[reply]
It's better to use a separate property and qualify that with the program version being used. A year or two later, one will otherwise have a hard time which version of the bot considered what by which threshold. I suggest we create to properties:
What is the commitment of WMF to maintain this going forward? How much time will you spend maintaining it in the next months each week? Or will it be discontinued after a month? ∞∞ Enhancing999 (talk) 09:23, 21 September 2024 (UTC)[reply]
We are committed to maintaining this bot for as long as it needs to be. As already mentioned, this is one of our priorities for the year, and definitely won’t be dropped after one month. On the other hand - after careful consideration with the team - we won’t be pursuing the path of creating new Wikidata properties, nor adding the confidence score as structured data, as part of this work of identifying and providing a way for easier moderation of logos.
While we agree that probabilistic statements supported by confidence scores are a very relevant topic, to the best of our knowledge no available Wikidata property can express so yet, and we see the need for a cross-community broad discussion that is outside of this experiment’s scope. If no consensus is reached on this bot request, the alternative is that we periodically release lists of potential logos to be considered (this time with confidence score), like we recently did. Sannita (WMF) (talk) 13:42, 25 September 2024 (UTC)[reply]
Looks like a great way to reduce mod/admin maintenance workload and reduce the number of copyvios on WMC. Please extend it or create similar bots to also detect other copyvios as proposed here or similar. Thanks for developing it, it seems very useful! --Prototyperspective (talk) 11:37, 21 September 2024 (UTC)[reply]