- 1 Re Category:Yosemite National Park - too crowed - see notice at top of category
- 2 re Category:Yosemite National Park - reason for moving image in the notice at the top of the category - please read and compy
- 3 File:Moran2.jpg
- 4 Important message for file movers
- 5 Google Code-In 2019 is coming - please mentor some documentation tasks!
Re Category:Yosemite National Park - too crowed - see notice at top of category
I only moved it because [[:Category:Yosemite National Park] shouldn't have images added directly to it. See notice at the top of the category.
This category has become too crowded. It should list very few images directly. Files should be moved to subcategories where appropriate. New subcategories can be created. Some files need to be moved elsewhere. Search for more categories: fulltext, Main Page, topics, meta categories. Please remove or replace this tag afterwards.
re Category:Yosemite National Park - reason for moving image in the notice at the top of the category - please read and compy
- I think you may be interpreting the notice too strictly. We shouldn't be violating Commons guidelines in order to empty out the category. Namely:
- Commons:Category says that every image in Commons needs to be in a category: your edit to File:Tuolumne Muir Gorge.jpg left it out of any categories.
- Commons:Category says that images should be categorized with "where" they were taken. Your edit to File:Granite Yosemite P1160483.jpg removed that information
- Notice that the notice at the top of the categories suggests creating new subcategories. If you find that Category:Yosemite National Park is too crowded, then create new geographical subcategories (like Category:Bishop Pass is to Category:Kings Canyon National Park, and reclassify the images into the subcategories. Don't simply remove the super-category and leave nothing in its place. — hike395 (talk) 20:29, 15 March 2015 (UTC)
File:Moran2.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.
Important message for file movers
A community discussion has been closed where the consensus was to grant all file movers the
suppressredirect user right. This will allow file movers to not leave behind a redirect when moving files and instead automatically have the original file name deleted. Policy never requires you to suppress the redirect, suppression of redirects is entirely optional.
Possible acceptable uses of this ability:
- To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
- To perform file name swaps.
- When the original file name contains vandalism. (File renaming criterion #5)
Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect. If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.
The malicious or reckless breaking of file links via the
suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right. This message serves as both a notice that you have this right and as an official warning. Questions regarding this right should be directed to administrators. --Majora (talk) 21:35, 7 November 2019 (UTC)
Google Code-In 2019 is coming - please mentor some documentation tasks!
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 firstname.lastname@example.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 email@example.com.