User talk:Senator2029
|
Google Code-In 2019 is coming - please mentor some documentation tasks!
[edit]Hello,
Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.
I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!
From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.
If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.
Thank you!
--User:Martin Urbanec (talk) 22:04, 23 November 2019 (UTC)
|
Category:Unidentified_people_with_file_names_or_descriptions_in_Spanish has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you! |
Estopedist1 (talk) 10:02, 21 January 2020 (UTC)
Growth team updates #12
[edit]Welcome to the twelfth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
General news
[edit]- A training for mentors has been published. The training was first tried with the Czech community, and went well.
- Growth team features have been deployed to Hungarian, Ukrainian, and Armenian Wikipedias. If your community is enthusiastic about welcoming newcomers, we encourage you to contact us so that we can verify together whether your wiki is eligible. Then you can go through the checklist to start the process of configuring the features.
Productive edits from newcomer tasks
[edit]We deployed the basic workflow for newcomer tasks to our target wikis on November 20, and the early results are exciting.
Graph captions (top to bottom):
■ Copyedits
■ Add links
■ Expand article
■ Add reference
■ Advanced edits
- About 1.5% of newcomers who visit their homepage complete the workflow and save a suggested edit. So far, this has amounted to over 450 edits, on all wikis, coming from both desktop and mobile users.
- When we look at the edits that newcomers make, we see that they are largely positive! We are pleased to see that this feature does not appear to encourage vandals.
- 75% of the edits are productive and unreverted.
- 95% of the edits appear to be in good faith.
- Most of the edits include copyedits and adding links, with some newcomers also adding content and references. Copyedits are suggested most strongly.
- Click here to learn more specifics about the results so far.
Topic matching deployed
[edit]The results from our user tests showed us that newcomers are likely to do more suggested edits if they can choose articles related to a topic that they're interested in, such as "science", "music", or "sports".
- On January 21, we deployed topic matching on our pilot wikis. Newcomers are now using it. We expect it to cause more newcomers to try suggested edits, and to keep making more of them.
- In the coming weeks, we will be making improvements to the accuracy of the algorithm used to topic matching, which is part of the ORES project.
Next steps for newcomer tasks
[edit]
Because we are seeing positive results from newcomer tasks, the Growth team plans to concentrate our efforts on improving the workflow and encouraging more newcomers to use it.
- Guidance: next, we will be using the help panel to provide guidance to newcomers as they do suggested edits, and to prompt them to do another edit after completing their first one. In user tests for this feature, demo videos were one of the favorite features, and we will think about how these might be added.
- Starting the workflow: only about 20% of newcomer who visit their homepage begin the newcomer tasks workflow. We are going to be trying out different layouts of the homepage to encourage more newcomers to try newcomer tasks.
- Additional task types: we are researching methods to recommend more specific tasks to newcomers, such as specific links to add, or images that could be added to articles from Commons.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:40, 4 February 2020 (UTC)
|
File:Zabbix logo.png has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
2001:41D0:602:9CC:0:0:0:0 10:09, 11 March 2020 (UTC)
Xu Jiaqi
[edit]Hi, may I know which “Tistory” page is allowed to be reused? I have seen many other “tistory” images that were accepted but instead the ones i uploaded was not. How do I know which images are allowed to reuse? Thanks! Woaahh (talk) 09:10, 18 March 2020 (UTC)
CfD: College athletics programs
[edit]Hi, I have started a discussion to rename a large collection of categories, one or more of which you may have created or edited. Please see the discussion thread at Commons:Categories for discussion/2020/04/College athletics programs for details. Thanks, IagoQnsi (talk) 04:39, 24 April 2020 (UTC)
SVG (Scalable Vector Graphics)
[edit]In other languages (translate this)
|
|---|
|
|
|
 Thank you for uploading some images!
Did you know that Wikimedia Commons recommends the SVG (Scalable Vector Graphics) format for certain types of images? Scalable Vector Graphics are designed to look appropriate at any scale, and SVG images are easier to modify and translate, helping Wikimedia to distribute knowledge to all of the world. A lot of modern programs support SVG export. If you encountered problems or have questions, don't hesitate to ask me, a member of the Graphic Lab, or the Graphics village pump. Uploading images in SVG format isn't mandatory, but it would help. (To avoid any misunderstandings, please don't just put raster images into an SVG container as embedded raster.) Thanks, and happy editing!
|
--EugeneZelenko (talk) 15:54, 16 May 2020 (UTC)
Growth team newsletter #13
[edit]Welcome to the thirteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Join the conversation: structured tasks
[edit]
We are looking for community input on a new project to make it easy for newcomers to make real article edits.
In our previous newsletter, we talked about the productive edits coming from the newcomer tasks feature. Those good results have continued: about 900 newcomers made over 5,000 suggested edits so far. We've learned that newcomers are interested in receiving suggested edits.
Now, we are thinking about how to supply them a feed of easy edits that will help more of them be successful quickly. We have a new idea called "structured tasks". This would aim to break down edits into steps that are easy for newcomers and easy on mobile devices.
In the past, certain kinds of editing tasks have been structured. For instance, adding categories through HotCat. Now, we are thinking about how to structure the editing of articles. The goal is to allow newcomers can make large content additions, especially from their mobile devices.
Please visit the project page and respond to the discussion questions listed on the talk page. You are welcome to show this project to others in your community. You can help by translating the materials to your language so that more voices can join in. We will be having this conversation until June 18.
Expanding to more wikis
[edit]We have expanded to six new wikis, and are looking for more interested communities.
In the last two months, we deployed Growth features to six new wikis: Ukrainian, Serbian, Hungarian, Armenian, and Basque Wikipedias, and French Wiktionary. Newcomers from these wikis have already contributed over 600 edits through Growth features.
We want to expand to more wikis in the coming months, and we are looking for interested communities. French Wikipedia already agreed and will be the next one to join the experiment. We will contact several other wikis in the coming weeks to offer them to participate.
Do you think the Growth Team features would be a good addition to your wiki? Please see this translatable summary of Growth features. You can share with your communities and start a discussion. Then, please contact us to begin the process!
Other updates
[edit]
Work continues on improving newcomer tasks and the homepage.
- In March, we deployed an upgrade to the topic matching in newcomer tasks. The current version offers 39 different topics using new ORES models.
- In April, we completed an A/B test of two homepage configurations. We learned that more newcomers will attempt suggested edits if the module is made more prominent. We are implementing those learnings in our next test. See the full results here.
- We are currently working on guidance for newcomer tasks. It will use the help panel to guide newcomers through completing easy edits.
- Our next step is to create new configurations of the homepage. The goal is to encourage more newcomers to begin doing suggested edits.
As usual, we are still welcoming your feedback and questions about our features. Please contact us on the project talk page!
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
14:30, 18 May 2020 (UTC)
Deletion of images
[edit]Hei, Answering to your message about my attempts to start deletion processes in Commons. I have been trying to delete some files I uploaded and that are not being used and are very unlikely to because they are no longer relevant: [1] and [2] However, I have failed to put the correct tag on them.
I would appreciate if you can show me the correct way to do this.
Thanks! --Kaklen (talk) 10:29, 8 June 2020 (UTC)
|
|
File:Chaturbate logo.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
轻语者 (talk) 14:23, 15 July 2020 (UTC)
Growth team newsletter 14
[edit]Welcome to the fourteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Success with guidance
[edit]
We deployed the "Guidance" feature on June 15.
This feature uses the help panel to explain what to do after selecting a suggested edit. For instance, if a newcomer selects a copyedit task, they are guided on what sorts of errors to look for. They can see examples of how to rewrite the text. You can try this feature on test.wikipedia.org. First enable the homepage and the help panel in your preferences there.
Since we launched "Guidance", the data we collected show good results (see image). Now, we see more users completing suggested edits than before Guidance was deployed.
Structured tasks
[edit]
Structured tasks is a project that aims to break down editing workflows into a series of steps. We hope newcomers can accomplish these tasks easily.
In the previous newsletter, we asked for feedback from community members on the idea. We had a good discussion in six languages with 35 community members (summary here). We have now posted new design mockups. We hope community members can check the mockups out and react to them (in any language). They are posted along with some of the main questions we are thinking about as we continue to refine our plans.
Other technical updates
[edit]_of_newcomer_homepage_2020-04-09.png)
- We are currently working on Variants C and D (adjacent image) of the homepage. The goal is to increase the number of newcomers who start the newcomer tasks workflow. This is the team's main project at the moment.
- We've made it easier to hide the help panel when not needed. [3]
- The welcome survey has a new question for people who created their account: language skills. The goal is to find out how many newcomers know multiple languages, so that we can learn whether it is a good idea to integrate Content Translation as a newcomer task. To make room for this question, we removed one that is not being used. [4]
Community outreach
[edit]- We continue to engage with more communities. We recently deployed the Growth features to Persian, Hebrew, and Russian Wikipedias. Learn more about getting the features.
- If your community is having a remote event, and you are interested in hearing from the Growth team, please contact us! We have already participated to two community events online:
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
09:33, 7 September 2020 (UTC)
Deleted content
[edit]
- use in any work, regardless of content
- creation of derivative works
- commercial use
- free distribution
See Commons:Licensing for the copyright policy on Wikimedia Commons, and Commons:Image casebook for some specific examples. Some other Wikimedia projects have different licensing policies. For example, the English Wikipedia allows fair use of sounds and photographs. This is not the case on Wikimedia Commons; "fair use" materials are not acceptable here.
Please make sure that you only upload educational content you have created yourself, those which are out of copyright, or those for which you have the required permission for the work to be used in all the ways described above. Please note that derivative works of copyrighted material are also considered copyrighted. Again, please read through Commons:Licensing, which is quite crucial, to understanding how Wikimedia Commons works. Thanks for your contribution, and please do leave me a message if you have further questions.Yours sincerely, - FitIndia Talk ✉ 08:09, 9 September 2020 (UTC)
Notification about possible deletion
[edit]|
|
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.
If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Affected:
Yours sincerely, Jonteemil (talk) 14:28, 29 September 2020 (UTC)
Growth team updates #15
[edit]Welcome to the fifteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Variants C and D deployed
[edit]
Variants C and D are two new arrangements of the newcomer homepage. We hope they will increase the number of users using suggested edits. They both make suggested edits the clear place where newcomers should get started on the page. They have some differences in their workflows, because we want to test which design is better. We deployed these variants on October 19; half of newcomers get each variant. After about 5 weeks, we will analyze the data from the tests. The goal is to determine which variant is helping more newcomers to make more suggested edits. We will identify the better variant and then use it with all newcomers.
Structured tasks: add a link
[edit]As we discussed in previous newsletters, the team is working on our first "structured task": the "add a link" task. After community discussion on design ideas, we ran user tests on the mobile designs. We decided on the design concept we want to use moving forward: Concept A. We're now engineering the backend for this feature. Next, we will be running user tests for desktop designs.
Learn more about the findings.
Community news
[edit]- We recently deployed the Growth features to Polish, Portuguese, Swedish and Turkish Wikipedias. 18 wikis now have Growth features. Learn more about getting the features.
- Have you recently checked if all interface messages are translated for your language?
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
10:10, 1 November 2020 (UTC)
Growth team updates #16
[edit]Welcome to the sixteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Growth features show impact
[edit]Newcomer task experiments results
The team recently published our analysis of the impact of newcomer tasks. We are happy to announce that we found that the Growth features, and particularly newcomer tasks, lead to increased editing from newcomers.
In November 2019, the Growth team added the "newcomer tasks" feature to the newcomer homepage. After six months, we collected data from Arabic, Vietnamese, Czech, and Korean Wikipedias. We analyzed the overall impact of the Growth features, including newcomer tasks.
This analysis finds that the Growth features lead to increases in:
- the probability that newcomers make their first article edit (+11.6%)
- the probability that they are retained as editors
- the number of edits they make during their first couple of weeks on the wiki (+22%)
We also find that the quality of their edits, as measured by revert rate, is comparable to that of a control group.
-
The number of suggested edits completed by each wiki each week, going from December 2019 to November 2020, with a line for the total. -
The number of distinct users completing suggested edits by each wiki each week, going from December 2019 to November 2020.
.png){kind=link}
![[1]](https://commons.wikimedia.org/wiki/File:Alianzas.PNG){kind=link}
![[2]](https://commons.wikimedia.org/wiki/File:Feuc2012.png){kind=link}
Because of these results, we think all Wikipedias should consider implementing these features. Learn more about how to get them.
You can find more details about this experiment on the report page. Please post any feedback or questions on the talk page
General metrics
As of November 2020, across all wikis where the features have been deployed:
- more than 5,000 newcomers have made more than 40,000 edits using Newcomer tasks.
- more than 14,000 questions have been sent to volunteer mentors by more than 11,000 users.
- more than 2,000 questions have been asked on help desks by more than 1,500 users.
Learn more about Growth results here, and please post any feedback or questions on the talk page.
Variants C and D
[edit]Variants C and D are two new arrangements of the newcomer homepage. We deployed them in October. After six weeks of these variants being deployed, we can see that they have led to increased interactions with newcomer tasks. Next, we will determine which variant is best and use that for all newcomers.
News for mentors
[edit]Mentors are volunteers ready to help newcomers in their first steps. Newcomers can contact them using the mentorship module on their homepage.
A separate list for workshops hosts
During workshops organized by education programs through the communities, workshops hosts like to mentor people they train on wiki. Several wikis requested to have a way to claim their mentees without having other newcomers being randomly being assigned to them. To address this need, a separate list can be created on wiki, for mentors that wish to claim mentees, but prefer not to have random mentees being assigned to them. Learn more about this feature.
Claiming multiple mentees at once
Mentors can use Special:ClaimMentee to claim a newcomer as their mentee. The feature now allows mentors to claim multiple newcomers at once.
Community news
[edit]The help panel allows people to post a message to the local help desk while editing. Previously, the tool always posted messages to the bottom of help desks. Wikis are now able to configure it to display new messages at the top of the help desk page. T261714
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
14:22, 7 December 2020 (UTC)
Vandalism warning
[edit]
— Jeff G. ツ please ping or talk to me 21:37, 16 December 2020 (UTC)
.png&action=edit&redlink=1){kind=link}
 |
File:Shah & Anchor (blue).png has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that.
The file you added has been deleted. If you have written permission from the copyright holder, please have them send us a free license release via COM:VRT. If you believe that the deletion was not in accordance with policy, you may request undeletion. (It is not necessary to request undeletion if using VRT; the file will be automatically restored at the conclusion of the process.)
|
Glorious 93 (talk) 08:42, 8 February 2021 (UTC)
.png){kind=link}
Growth team newsletter #17
[edit]
Welcome to the seventeenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Structured tasks
[edit]Add a link: the team is continuing to engineer on our first "structured task", which will break down the workflow of adding wikilinks to articles, and assist newcomers with an algorithm to identify words and phrases that could be made into links.
Add an image: even as we build our first structured task, we have been thinking about the next one. "Add an image" is a structured task in which newcomers would be recommended images from Wikimedia Commons to add to unillustrated articles. This is an ambitious idea with many details to consider. We have already learned a lot from community members, and we encourage everyone to look at the project page and join the discussion.
Moving forward: more wikis to get the features
[edit]Last November, our team published the analysis of the impact of newcomer tasks. We announced that we found that the Growth features, and particularly newcomer tasks, lead to increased editing from newcomers. Because of these results, we believe all Wikipedias should implement these features.
We have started to contact more wikis to deploy the features, including Wikipedias of all sizes. Bengali Wikipedia recently began using Growth features, and Danish, Thai, Indonesian, and Romanian Wikipedias will be coming soon. Please contact us if you have questions regarding deployment.
We are looking for translators who can help by translating the interface. Translating is done on Translatewiki.net (it requires a different account that your Wikimedia one). Communities that already have the Growth features being deployed are invited to check on the translations. Access translations here.
Variant testing
[edit]As mentioned in our previous newsletter, we ran a test of two variants of the newcomer homepage, meant to find a version that increases users completing suggested edits. We have completed the experiment, and learned that one of the variants leads to more edits on desktop while the other leads to more edits on mobile. Therefore, we will deploy the strongest variants for each platform to all newcomers.
News for mentors
[edit]Mentor dashboard: we have interviewed mentors from several communities as we plan a mentor dashboard feature, which would help mentors track the progress of their mentees. We encourage all mentors to share their thoughts on tools that would help them.
Magic word for mentors: it is now possible to use a magic word, {{#mentor}}, to display the name of a given newcomer's mentor. This can be used on welcome messages, userboxes, etc.
Help panel questions going to mentors: in most wikis, newcomers using the help panel ask questions to the help desk. On Czech Wikipedia, we have experimented with sending these questions to mentors instead. This simplifies the newcomer experience, and only led to a increase in mentorship questions of about 30%. We tried this in Arabic, Bengali, French and Vietnamese Wikipedias, and we are making it the default experience.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
16:03, 3 March 2021 (UTC)
Notification about possible deletion
[edit]|
|
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.
If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Bidgee (talk) 02:19, 7 March 2021 (UTC)
Pointless move of uncategorized Geograph uploads
[edit]Edits like this one are pointless. The file is uncategorized and doesn't have any categories to review. Please undo these edits because this way we loose track of files that need attention. Multichill (talk) 15:32, 4 April 2021 (UTC)
Growth Newsletter #18
[edit]Welcome to the eighteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in mid-size Wikimedia projects.
Structured tasks
[edit]
"Add a link" is now being tested in production and is nearing release on our four pilot wikis (Arabic, Czech, Vietnamese, and Bengali Wikipedias). We'll be doing final tests this week and next week, and then plan to deploy to the four wikis either during May 24 week, or May 31 week. After two weeks, we will analyze the initial data to identify any problems or trends. We expect that this feature will engage new kinds of newcomers in easy and successful edits. If things are going well after four weeks, we'll progressively deploy it to the wikis with Growth features.
News for mentors
[edit]
- We are currently working on a Mentor dashboard. This special page aims to help mentors be more proactive and be more successful at their role. The first iteration will include a table that shows an overview of the mentors current mentees, a module with their own settings, and a module that will allow them to store their best replies to their mentees questions.
- We've conducted our quarterly audit on Growth's four pilot wikis to see the activity of mentors. It appears that the vast majority of mentors are active.
Community configuration
[edit]
We are working on project to allow communities to manage the configuration of the Growth features on their own. In the past, communities have needed to work directly with the Growth team to set up and alter the features. We plan to put this capability in the hands of administrators, through an easy-to-use form, so that the features can be easily tailored to fit the needs of each community. While we developed it initially for Growth features, we think this approach could have uses in other features as well. We'll be trying this on our pilot wikis in the coming weeks, and then we'll bring it to all Growth wikis soon after. We hope you check out the project page and add any of your thoughts to the talk page.
Scaling
[edit]- Growth features are now available on 35 wikis. Here is the list of the most recent ones: Romanian Wikipedia, Danish Wikipedia, Thai Wikipedia, Indonesian Wikipedia, Croatian Wikipedia, Albanian Wikipedia, Esperanto Wikipedia, Hindi Wikipedia, Norwegian Bokmål Wikipedia, Japanese Wikipedia, Telugu Wikipedia, Spanish Wikipedia, Simple English Wikipedia, Malay Wikipedia, Tamil Wikipedia, Greek Wikipedia, Catalan Wikipedia.
- A new group of Wikipedias has been defined for the deployment of Growth features. Please contact us if you have questions about the deployment process, or if your community likes to get the features in advance.
- After discussion with the English Wikipedia community, the Growth features will be tested on a small percentage of new accounts. At the moment, registered users can test the features by turning them on in their preferences.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
15:23, 17 May 2021 (UTC)
We need your feedback!
[edit]Hello. Apologies if this message is not in your native language: please feel free to respond in the language of your choice. Thank you!
I am writing to you because we are looking for feedback for a new Wikimedia Foundation project, Structured Data Across Wikimedia (SDAW). SDAW is a grant-funded programme that will explore ways to structure content on wikitext pages in a way that will be machine-recognizable and -relatable, in order to make reading, editing, and searching easier and more accessible across projects and on the Internet. We are now focusing on designing and building image suggestion features for experienced users.
We have some questions to ask you about your experience with uploading images here on Wikimedia Commons and then adding them to Wikipedia. You can answer these questions on a specific feedback page on Mediawiki, where we will gather feedback. As I said, these questions are in English, but your answers do not need to be in English! You can also answer in your own language, if you feel more comfortable.
Once the collecting of feedback will be over, we will sum it up and share with you a summary, along with updated mocks that will incorporate your inputs.
Also, if you want to keep in touch with us or you want to know more about the project, you can subscribe to our newsletter.
Hope to hear from you soon! -- Sannita (WMF) (talk to me!) 09:56, 2 August 2021 (UTC)
|
|
File:Banco di Napoli Logo.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
— Racconish 💬 09:14, 22 August 2021 (UTC)
|
|
File:Deutsche Verkehrswacht logo.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Edgar Moebius (talk) 13:48, 24 August 2021 (UTC)
Code issues in User:Senator2029/common.js
[edit]Hi Senator2029, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.
Curious about the reason? Possibly not but I will tell you anyway:
- You edited User:Senator2029/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
- Though, that change appears to introduce 4 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
- To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
- ISSUE:
line 39 character 9: Expected '}' to match '{' from line 38 and instead saw '{'. - Evidence:{ - ISSUE:
line 40 character 9: Expected ']' to match '[' from line 38 and instead saw 'label'. - Evidence:'label': 'Logo', - ISSUE:
line 40 character 16: Missing semicolon. - Evidence:'label': 'Logo', - ISSUE:
line 40 character 16: Expected '(end)' and instead saw ':'. - Evidence:'label': 'Logo',
Your CommonsMaintenanceBot (talk) at 23:51, 27 August 2021 (UTC).
Code issues in User:Senator2029/common.js
[edit]Hi Senator2029, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.
Curious about the reason? Possibly not but I will tell you anyway:
- You edited User:Senator2029/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
- Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
- To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
- ERROR: Cannot parse
line 39 column 3: Unexpected token {
Your CommonsMaintenanceBot (talk) at 23:51, 27 August 2021 (UTC).
|
|
File:CSR974logo.gif has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
mattbr 06:47, 17 February 2022 (UTC)
Why you create valid codes?
[edit]??????? With reupload. --SamsonBVB (talk) 21:32, 28 June 2022 (UTC)
Category move
[edit]When you start a thing, would be kind to complete it. -- Blackcat 
18:34, 15 August 2022 (UTC)
Descriptions and Categories
[edit]Hello, good afternoon from Philippines; User talk:RamaGaspar asked us from the Barasoian Church laity to help in descriptions and categories on Museum; Fr. Vicente "Jay" B. Lina, Jr. (parish priest of St. Elizabeth of Hungary Parish (Est. 1859) Bagong Bayan (Sta. Isabel), Malolos City) is the Curator of Barasoain Church (ecclesiastical) Museum while Fr. Domingo Meneses "Memeng" Sanlonga is incumbent parish priest succeding Rev. Fr. Dario V. Cabral. Parish Priests from 31 August 1859 Fr. Francisco Arriola to 1989 Msgr. Moises Andrade Msgr. Jose Aguilan, Jr. Msgr. Filemon Capiral Msgr. Angelito Santiago). The historical and cultural treasures of the Malolos Congress are now on display in this museum. Unfortunately, most of these treasures were donated by pious readers since 1859, and very few images could be reasonably described with more precise categories rather than general. One reason or maybe the best, is that the donors desired to be anonymous. Second, most of the images are very rare, oldest and command at least 10,00 dollars. Hence, the donors would not want their treasures to be subject of theft or robbery if they divulge the specifics. For example a retired priest donated all his vestments and chose to be anonymous. Hence it took us time to meticulously add descriptions and Categories; it is very typical for Church museums in the Philippines to fail to place name plates or descriptions. hence our predicament, Sincerely 122.2.111.134 09:24, 3 September 2022 (UTC).
- In addition, we added descriptions and categories on several photos per User contributions for 122.2.111.134 Cheeers 122.2.111.134 09:28, 3 September 2022 (UTC).
|
|
File:DMEXCO logo.png has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Trade (talk) 22:50, 4 October 2022 (UTC)
Short question
[edit]Hi!
You added some SVG Development info on File:DNA chemical structure nl.svg, including the number of errors in the source code. What are these errors exactly and how are they calculated? TheBartgry (talk) 13:52, 9 December 2022 (UTC)
Category fixes
[edit]Hello, I noticed you took care of the categories of a couple of my uploads. I appreciate your help, but I must ask you not to add categories localizing them in Italy: many of my pictures are indeed taken in Italy and when possible I use categories localized as accurately as possible, but when I don't it is because either:
- they are from another country that I prefer not to disclose, or
- I was allowed to take them in private places under the condition that I do not disclose their location.
The changes you did are not a big problem of course, and I already fixed the ones that needed to, I just wished to inform you about that. --CosyCobra (talk) 00:10, 26 December 2022 (UTC)
 | Category:SM-J701M is considered to fulfill the criteria for speedy deletion and has been marked on its page. The following reason has been specified:
If you believe the content does not meet the criteria for speedy deletion, you may replace the speedy deletion tag with a regular deletion request (if the content has not been deleted) or request undeletion (if the content has already been deleted). |
R'n'B (talk) 15:02, 31 December 2022 (UTC)
Notification about possible deletion
[edit]|
|
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.
If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Affected:
Yours sincerely, JWilz12345 (Talk|Contrib's.) 23:37, 28 July 2023 (UTC)
|
|
Category:Files_from_Flickr_(uncategorized_2020) has been listed at Commons:Categories for discussion so that the community can discuss ways in which it should be changed. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this category, please note that the fact that it has been proposed for discussion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. If the category is up for deletion because it has been superseded, consider the notion that although the category may be deleted, your hard work (which we all greatly appreciate) lives on in the new category. In all cases, please do not take the category discussion personally. It is never intended as such. Thank you! |
A1Cafel (talk) 08:39, 19 September 2023 (UTC)
|
|
File:Eugene Volokh.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
—holly {chat} 21:35, 27 December 2023 (UTC)
|
|
Template:Original uploader own has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this template, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. |
ZandDev (talk) 09:10, 7 January 2024 (UTC)
Source of derivative work is not properly indicated: File:Yavapai-Apache logo.jpg
[edit]
|
| This file may be deleted. |
A file that you have uploaded to Wikimedia Commons, File:Yavapai-Apache logo.jpg, is a derivative work, containing an "image within an image". Examples of such works would include a photograph of a sculpture, a scan of a magazine cover, or a map that has been altered from the original. In each of these cases, the rights of the creator of the original must be considered, as well as those of the creator of the derivative work.
While the description page states who made this derivative work, it currently doesn't specify who created the original work, so the overall copyright status is unclear. If you did not create the original work depicted in this image, you will need to specify the owner of the copyright. Please edit the file description and add the missing information, or the file may be deleted. If you created the original content yourself, enter this information as the source. If someone else created the content, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you! |
Hello, I've flagged this file because I have been unable to find a source to confirm its copyright status. If you have any information to help verify it is freely licensed, please edit the file accordingly. Thanks! Yours sincerely, Intervex (talk) 04:05, 1 December 2024 (UTC)
|
|
File:WDRB 2018 Logo.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
