September 2011

edit

Problems with Commons Helper Helper?

edit

Commons Helper helper (Krimpet/CH2.js) does not seem to be working for me. Is it working for anyone else? What the easiest way to move images to Commons? – Quadell (talk) 20:38, 14 August 2011 (UTC)Reply

P.S. I asked the script's author here, but have not yet received a reply. – Quadell (talk) 14:22, 17 August 2011 (UTC)Reply
It didn't work for me either. What is the other option? Download the image and then upload it to commons? Ryan Vesey Review me! 14:24, 17 August 2011 (UTC)Reply
It doesn't work. Also, if you don't want to download it, get an TUSC account. Remember that you don't need to keep it when you download it and uploaded it. ~~Ebe123~~ talkContribs 20:53, 17 August 2011 (UTC)Reply
I have a TUSC account. What works best for me is to use the tiny Copy to Commons via CommonsHelper link at the bottom of the {{Move to Commons}} template (e.g. at File:Angelfish belonging to Mitternacht90.JPG). – Quadell (talk) 23:24, 17 August 2011 (UTC)Reply
I attempted to use commonshelper, but it didn't work. Ryan Vesey Review me! 23:28, 17 August 2011 (UTC)Reply
The revamped instructions give a link to CommonsHelper 2, and also states that both of them have high rates of failure. You are not alone Ryan. Sven Manguard Wha? 04:18, 18 August 2011 (UTC)Reply
Ahh, yes I have had problems with CommonsHelper, not Commons Helper Helper. Here is my specific problem, when attempting to move the image, it took me to the normal upload form. At the form, it still asked for me to upload the file (which I did not have). Does it work if you click the link to use its successor? Ryan Vesey Review me! 22:05, 18 August 2011 (UTC)Reply

list

edit

Questions:

  • So eventually we will list the actual image filenames in the list parameter under our names at Wikipedia:WikiProject Images and Media/Commons/Drive Sep 2011/Logs?
  • If I copy the image to commons and then delete the one here, I only list it once, as "Moved to commons", not as "Deleted", right?
  • What's the "Deleted" entry for, then?
  • If I determine that an image should not be moved to commons, but may be a copyvio, and I list it at WP:PUF, should I list that here or not?

Thanks! – Quadell (talk) 11:29, 17 August 2011 (UTC)Reply

Yes.
Actually, you may list the image as deleted and moved if you deleted the file, and you could get the clean-up admin barnstar.
Deleted... It would be for if you delete the moved image from someone else.
Don't list the images that you nominated for deletion during this drive.
~~Ebe123~~ talkContribs 20:31, 17 August 2011 (UTC)Reply

Lot of work

edit

This whole thing seems like a lot of work to me. Moving images to Commons takes time because the tools are so buggy and slow, but to participate in the drive you also need to record each one, and review one-in-ten of other users' moves? I know it is the only way to really be sure that barnstars are awarded properly, but I just question how productive this whole thing will be (note that I like backlog drives and I think images should be moved to Commons... in fact, I move them frequently. I just don't think that the two will go well together). –Drilnoth (T/C) 21:15, 17 August 2011 (UTC)Reply

You do not have to review others peoples moves if you don't want to. Also, you may do the old-fashioned way of manually uploading. If you think that this is hard, I would say that wikifying is hard, and compared to my other drive (for WP:ABANDONED), its a piece of cake. ~~Ebe123~~ talkContribs 21:25, 17 August 2011 (UTC)Reply

Sign Up?

edit

Where do you sigh up for this? --Guerillero | My Talk 22:00, 18 August 2011 (UTC)Reply

Wikipedia:WikiProject Images and Media/Commons/Drive Sep 2011/Logs Ryan Vesey Review me! 22:07, 18 August 2011 (UTC)Reply
There's instructions at Wikipedia:WikiProject Images and Media/Commons/Drive Sep 2011/Logs. ~~Ebe123~~ talkContribs 11:10, 19 August 2011 (UTC)Reply

A short How-To, made for the September drive

edit

I have created an short "How To" guide for participating in the drive. It's located at User:Quadell/MoveToCommons guide. I hope it is helpful. – Quadell (talk) 23:00, 18 August 2011 (UTC)Reply

For your reviewing procedure, pretty good! Just remember that if things go wrong with an editor for any reason relevant, you may levy a penalty too. So, are you going to accept the As and Bs but not the Cs and Fs? For now, I will put your instructions on the main drive page. ~~Ebe123~~ talkContribs 10:27, 19 August 2011 (UTC)Reply
Yeah, someone else told me he didn't think the "letter grade" system was a good one, so I'm rethinking how I intend to review. I'll update that page when I figure it out. – Quadell (talk) 11:22, 19 August 2011 (UTC)Reply
I would just make it, if it is moved to commons and formatted correctly it counts. If it is not formatted correctly, not moved to commons, or not in the public domain there is a penalty. Speaking of penalties, you can actually become blocked if you continually move non-free content to commons. Ryan Vesey Review me! 13:31, 19 August 2011 (UTC)Reply
We would bar them from moving to commons before that happens. Quadell, if another sysop blocks a user for moving non-free to commons, bar them, and if they didn't get any notices about moving non-free, I think that un-blocking but with a warning would be good. ~~Ebe123~~ talkContribs 20:23, 19 August 2011 (UTC)Reply

Signpost

edit

This drive will be mentioned in the WikiProject page of The Signpost of 22 August 2011. Publishing is soon. ~~Ebe123~~ (+) talk
Contribs
22:23, 22 August 2011 (UTC)Reply

Published. ~~Ebe123~~ (+) talk
Contribs
10:36, 23 August 2011 (UTC)Reply

Pages

edit

So for the progress bars, there needs to be an initial number of pages. I will not be able to start it so this is what I would a reviewer (or whoever) to do; its at 00:00, 1 September 2011 (UTC), remove the "Drive has not started yet" tag, and put the number of files for the initial at Wikipedia:WikiProject Images and Media/Commons/Drive Sep 2011/Logs/Progress. There are notes for where to put the number. Also, if the number is too high, a reviewer may change it. ~~Ebe123~~ (+) talk
Contribs
10:36, 23 August 2011 (UTC)Reply

logs

edit

How do you mark things on the logs page? Jay8g (talk) 00:45, 27 August 2011 (UTC)Reply

So, you go here (your log section) and there's
# {{Moved to commons}}
# {{Moved to commons}}
# {{Working}}
# {{Deleted-image}}

. You add [[:File:<file>]] after

# {{Moved to commons}}

.

Sorry if it isn't a good explaination, I am not that good at explaining how to edit. ~~Ebe123~~ (+) talk
Contribs
13:03, 28 August 2011 (UTC)Reply

Thanks! I (think) I understand now. Jay8g Hi!- I am... -What I do... WASH- BRIDGE- WPWA - MFIC- WPIM 21:57, 28 August 2011 (UTC)Reply

Template:Backlog status

edit

I've made Category:Copy to Wikimedia Commons the focus of the month! Hopefully that will help bring more attention to this project. –Drilnoth (T/C) 14:58, 1 September 2011 (UTC)Reply

Thanks, Drilnoth! – Quadell (talk) 15:07, 1 September 2011 (UTC)Reply
I put of lots of publicity. At the community portal, 2 signposts, and more. ~~Ebe123~~ (+) talk
Contribs
16:13, 1 September 2011 (UTC)Reply

Template to contact uploader

edit

Can we have a template to contact an uploader to ask them for more information on a photo? Sometimes there are no pages linked to an image and it has no description. So, we can't transfer it and we also might not know what to re-name it (if necessary) and also what categories to put it under. A standardized talk page template to address these issues would be a great help. Thanks. --SMasters (talk) 15:50, 1 September 2011 (UTC)Reply

You are free to make one. ~~Ebe123~~ (+) talk
Contribs
16:13, 1 September 2011 (UTC)Reply
I frequently ask uploaders, but I found I get better responses when I don't use a template. – Quadell (talk) 16:43, 1 September 2011 (UTC)Reply

For all

edit

I have been seeing some things, here, one thing is that {{deleted-image}} is wrongly used. It is to say that you deleted that image, and its supposed to be stand-alone, not with moved. If you delete an image, put # {{deleted-image}} [[:<file you deleted>]], not after # {{Moved to commons}} [[:File:<name of file>]] and another user's log. Also, "8 acceptable, 1 unacceptable", reviewers should subtract the number of unacceptable files (and penalties) from the total files list and tell the user.

I hope its of help, ~~Ebe123~~ (+) talk
Contribs
16:13, 1 September 2011 (UTC)Reply

Uping the awards

edit

So, I realize that 10 images isn't hard at all so I propose uping the awards by 10 images. ~~Ebe123~~ (+) talk
Contribs
23:11, 2 September 2011 (UTC)Reply

Sure, why not? –Drilnoth (T/C) 23:27, 2 September 2011 (UTC)Reply
I've retouched the awards again. The current version satisfies my OCD, while not really moving the bar for any one star. Rounding to the nearest 5 is a good thing. Sven Manguard Wha? 14:57, 3 September 2011 (UTC)Reply

Drilnoth and F8 deletions and space

edit

Drilnoth has just under a hundred F8 deletions from the course of this drive, and it's only the fourth day. Since F8 deletions are routine, non-controvertial, and not in need of review, does anyone have any objections to just marking Drilnoth down for getting an Admin Barnstar at the end of the drive and then flushing the deletions from his list sheet (or at the very least, letting him know he dosen't have to keep listing them)? I only ask because the only real reason we track those is for the barnstar, which he's earned literally three times over already, and the deletion line items are taking up a lot of space. (Note that we might have to do this with other admins in the future as well).

Sven Manguard Wha? 16:27, 4 September 2011 (UTC)Reply

I am tempted to give him the star now --Guerillero | My Talk 18:02, 4 September 2011 (UTC)Reply
I'd be happy to remove the deletions from the list and just put a mark at the top of the list saying "Plus at least X deletions" for recordkeeping purposes. –Drilnoth (T/C) 14:27, 5 September 2011 (UTC)Reply
That works. :D Keep up the good work! Sven Manguard Wha? 03:41, 6 September 2011 (UTC)Reply
I've done something similar. I've done hundreds of deletion, but I only list 39 (for barnstar purposes, with a little leeway). – Quadell (talk) 16:38, 7 September 2011 (UTC)Reply

Question/s

edit

I have come across a number of logos of companies, organizations, etc., who are obviously copyright material and not free. Do we remove the bot tags? As a big part of this drive is to reduce the amount of images in the Category:Copy to Wikimedia Commons, and by removing the tag we achieve this, do we list these down to be counted? And do we need to put any other tags on the page, such as "keep local"? Thanks. – SMasters (talk) 14:14, 6 September 2011 (UTC)Reply

Here are some ways you can deal with these situations.
  1. If an image is tagged as free, but is certainly non-free, you can retag the image and add a rationale for each valid use.
  2. If an image is tagged as free, but is certainly non-free, you can list in at WP:FFD or WP:PUF.
  3. If an image is free here, but not suitable for commons, tag as keep local.
In all these cases you would want to remove the "Move to Commons" template. This will reduce the backlog. But it won't be listed in the logs here. – Quadell (talk) 14:31, 6 September 2011 (UTC)Reply
Yeah, Fastily and I knew this would happen at least a few times with the bot taggings. The bots are not smart enough to know if a user botched the licensing, so when a user blows through the wizard without looking and uses all the defaults, a whole lot of non-free things get credited as 'own work' and get tagged PD-self, GFDL self, or CC-BY-SA-3.0 self, depending on what year it was uploaded (and therefore which licence the wizard was using as a default). The bots look at license templates, they can't really tell if something has the correct template or not. Sorry about that, but then again, that's the entire reason that the bots dump to a subcategory instead of the main category.So yeah, Quadell's advice is sound here. Sven Manguard Wha? 15:53, 7 September 2011 (UTC)Reply
Smart?! Bots arn't smart at all and they cannot be intelligent. ~~Ebe123~~ (+) talk
Contribs
22:01, 8 September 2011 (UTC)Reply

As to the issue of counting them... I suppose the final decision lies with Ebe123, but I would say this: If it's free, but licensed wrong, fix it during transfer and count it as a transfer. If it's non-free and you relicense it and give it a proper FUR, then count it (we'd need a list template for relicensing so that it's tracked/reviewed separately). FurMe is a godsend, and when I combine all the time it has saved me it's probably in the dozen hours range, but it still takes a good deal of knowledge and effort to use, so it's worth counting. If all you're doing is listing it at FfD or sticking a Keep Local tag on it, I'd say don't count those. While valuable, it'd throw the competition element out of whack. Fastily, Drilnoth, and I have all, on separate occasions, listed over 100 files at FfD in one day (and yes, they were all deserving of deletion). That's my thoughts, at least. Sven Manguard Wha? 16:05, 7 September 2011 (UTC)Reply

I agree with Sven for the processes. ~~Ebe123~~ (+) talk
Contribs
21:59, 8 September 2011 (UTC)Reply

SMasters, a lot of company logos are simple enough to be PD; see {{PD-ineligible}}. I'm guessing you're already familiar with that, but just thought I'd mention it. There are a lot of iffy ones out there though, where it can be hard to tell if it passes the threshold of originality or not. –Drilnoth (T/C) 23:35, 8 September 2011 (UTC)Reply

Cross post

edit

There is a discussion is going on in the /Progress page about the Tertiary goal, now at -50%. Sven Manguard Wha? 18:16, 10 September 2011 (UTC)Reply

Drive

edit

I am organizing the next drive, which will be for november. You may already join. Its at Wikipedia:WikiProject Images and Media/Commons/Drive Nov 2011. It is under construction. ~~Ebe123~~ (+) talk
Contribs
12:07, 11 September 2011 (UTC)Reply

I suppose I can do a little bit for the November drive, although I tend to be of the philosophy that backlogs should be spaced out a bit more. There are a dozen or so backlogs in the file namespace, and I like to spread out my work among them. If we do go by the every other month format though, I'll probably be up for the January backlog (and by then, I'll be back in the States, where my internet will be faster, stronger, and less prone to random outages.) Sven Manguard Wha? 04:47, 13 September 2011 (UTC)Reply
I suggest that you guys should advertise it on Community Portal. Very few people were aware of the drive until it was being mentioned in the SignPost. OhanaUnitedTalk page 02:23, 14 September 2011 (UTC)Reply
Yeah, Drilnoth already said that. ~~Ebe123~~ (+) talk
Contribs
10:37, 14 September 2011 (UTC)Reply

Question from Vivekananda De

edit

Sorry about my previous mistake on the discussion page of the "Wikipedia talk:WikiProject Images and Media/Commons/Drive Sep 2011/Logs".. I m a newcomer so I might be a constant bugger. Q:How do you rename a photo in wiki media commons after you have uploaded it ?-Vivekananda De 04:05, 15 September 2011 (UTC)Reply

You can't move files without either the 'filemover' user right on Commons or the 'file mover' user right on Wikipedia. You can ask people to move things for you using the rename template. On Commons, it is {{rename|New name here (leave out the "File:", but do include the extention (.jpg, .png, etc.)|Reason for the new name}}. So it might look like {{rename|Rabbit with Pancake.png|Old name is not descriptive}}. Put that on the file description page at Commons and someone will do the rename for you. Sven Manguard Wha? 15:40, 14 September 2011 (UTC)Reply
If you're using CommonsHelper, you can also rename the file during the move. –Drilnoth (T/C) 12:35, 15 September 2011 (UTC)Reply

Pagesize

edit

Currently, the log page is 466,107 bytes long. Updated 09:47, 28 November 2024 (UTC). The page is very hard to edit. ~~Ebe123~~ (+) talk
Contribs
13:19, 17 September 2011 (UTC)Reply

Really? I'm not having any trouble editing it. Try editing specific sections rather than the whole page, if you aren't already. –Drilnoth (T/C) 21:48, 17 September 2011 (UTC)Reply
For reviewing CGs files, its hard. I don't edit the hole page. ~~Ebe123~~ (+) talk
Contribs
12:19, 18 September 2011 (UTC)Reply
It takes a long time to save changes. I'm not sure if there's a way to fix that, though. – Quadell (talk) 13:00, 18 September 2011 (UTC)Reply
I thought it was on my end (Great Firewall). What should we do about it? Sven Manguard Wha? 13:38, 18 September 2011 (UTC)Reply
Just put common good and quadell's log in there own subpages since common good and quadell is about 1/3 of the page. ~~Ebe123~~ (+) talk
Contribs
18:56, 18 September 2011 (UTC)Reply

Congrats!

edit

Hi there everyone. Sorry I had to disappear for a while. I just wanted to stop in and congratulate everyone who participated in this drive. We did a great job, double our initial goal, and took a sizable chunk out of the backlog. Everyone who chipped in deserves a pat on the back, especially our two quadruple digit superstars. Sven Manguard Wha? 15:05, 30 September 2011 (UTC)Reply

We are awarding soon. ~~Ebe123~~ (+) talk
Contribs
20:22, 30 September 2011 (UTC)Reply

January 2012

edit

Interwiki moves

edit

A poll:
Should we accept files moved from other wikis?

  • Pro: The global backlog would decrease and can get users more moved files;
  • Con: This drive was made at en.wikipedia and for the moving of local images.

I would like to know how to go. ~~Ebe123~~ (+) talk
Contribs
22:10, 3 October 2011 (UTC)Reply

Wow, good question. I can see both sides, but I think I would vote to limit our drive to files moved from en.wiki, at least for now. For one thing, it would be easier for reviewers to review the moves if they're all from one place. Also, there are many more files here, currently, than we are likely to finish in a one-month drive. If we ever got to the point that there were only 2000 or so files left, then we would definitely want to expand the scope. I'm sure we'll get there eventually! – Quadell (talk) 12:30, 4 October 2011 (UTC)Reply
  Pro Sure. Interwiki dupes are a serious problem (I regularly work on) because deletions due to copyright problems in the source wiki will not be noticed at en.wikipedia. (other common problems with those files are: misattributions, wrong licenses, lack of translations and missing benefit from improved versions (e.g. removal of watermarks))
Moving a file from xy.wikiwhatever.org to Wikimedia Commons resulting in the deletion of an exact duplicate or scaled-down version at en.wikipedia should be counted as a valid transfer. -- Common Good (talk) 17:15, 4 October 2011 (UTC)Reply
Mostly what Quadell said, I personally think we should focus on removing the enwiki backlog first. On a second note, do you know when the awards will be given? The drive status is marked as 'Closed and awarded', but I have yet to receive any shinies :) If you want a hand dishing them out then I'd be more than happy to help as well, just drop me a line. Thanks, Acather96 (talk) 17:40, 4 October 2011 (UTC)Reply
Quadell, you may do the honours! ~~Ebe123~~ (+) talk
Contribs
19:28, 4 October 2011 (UTC)Reply
Ebe123, you could just re-add the awards which you removed from Acather96's user talk page rather than making another user repeat themselves. Acather96, check the revision history of your talk page for the awards. –Drilnoth (T/C) 21:03, 4 October 2011 (UTC)Reply
If you didn't see, I re-added them. Look at the talk page. ~~Ebe123~~ (+) talk
Contribs
09:40, 5 October 2011 (UTC)Reply
Thank-you :) Acather96 (talk) 07:21, 8 October 2011 (UTC)Reply
  • If the situation is as Common Good described, where moving a file elsewhere fixes a problem or otherwise aids English Wikipedia's files, then why not give credit. Besides, the amount of effort it takes to do these would limit it to a relatively small number of instances, and they'd be done by people that know what they're doing. On the other hand, our priority should not change, we have two massive backlogs to poach. Sven Manguard Wha? 11:33, 18 October 2011 (UTC)Reply

Two questions on reviewers/reviewing

edit

Why are we limiting the number of reviewers?

edit

I disagree with this edit by Ebe123. Last time around, most of the reviews were done by Quadell, Ebe123, Drilnoth, and I, with a few of the people that signed up to review not actually doing any reviewing, but that aside, I don't see why we should cap the reviews like that. At the very least, if Drilnoth wants in on reviewing, he should be allowed right on in. I'd like to hear Ebe123's reasoning though, before I ask if there's consensus one way or the other. Sven Manguard Wha? 11:29, 18 October 2011 (UTC)Reply

I was accepting other reviewers, such as Guerillero (talk · contribs). Also, the wording was not supposed to be definitive. ~~Ebe123~~ (+) talk
Contribs
 • 21:25, 19 October 2011 (UTC)Reply

I can review stuff, if you want. I won't add my name to that list, 'coz it says it's full. Chzz  ►  19:26, 24 November 2011 (UTC)Reply

No, no Chzz, you may join the reviewers. ~~Ebe123~~ → report on my contribs. 23:18, 25 November 2011 (UTC)Reply
We also need some more admin reviewers. ~~Ebe123~~ → report on my contribs. 23:18, 25 November 2011 (UTC)Reply
I've added myself as an admin reviewer, so we're up to 3 now. I'm going to be fairly busy in January, though, so no guarantees on how active a reviewer I'll be. --Philosopher Let us reason together. 04:42, 3 December 2011 (UTC)Reply
Never mind - RL is taking up most of my "wiki-time" at the moment.  :( --Philosopher Let us reason together. 06:48, 24 January 2012 (UTC)Reply

Should we do less or no reviews for experienced movers?

edit

By the end of the drive, no one was really reviewing 1 in 10 of Common Good or Quadell's submissions. They were in the thousands, and besides one minor mistake from Common Good, there weren't any errors in their work. To me, that means that 1 in 25 or 1 in 50 would be more sensible spot check figures for those users. It's just a waste of time to check over the work of people that just do things right every time, and in high volume. I'd also support raising the ratio to 1 in 25 for Acather96, Drilnoth, Ebe123, Michael Barera, and SMasters, all of whom churned out large numbers, and who had essentially smooth sailing throughout the drive. Also Guerillero, who had lower numbers, but who had no flagged transfers, and who I've worked with before and can vouch for. Essentially what I'm saying is that reviewers should be concentrating on users that are new to the drives, or have had problems in previous drives, and giving only a small amount of their time over to checking people that have proven that they can do it right consistently. Thoughts? Sven Manguard Wha? 11:29, 18 October 2011 (UTC)Reply

Lets review all users equally and fairly, as at least 10% reviewed. But I support 25% for all though, since this is no GoCE, the pages are in masse, over 3,000 pages, not 1,000 as GoCE. I was tring to review Common Good's transfers, but for like quality control, but for Quadell, I couldn't since he deletes after. I asked Drilnoth to do them, but he refused as useless since Quadell hasen't done anything wrong. ~~Ebe123~~ (+) talk
Contribs
 • 21:25, 19 October 2011 (UTC)Reply
Common good was batting 99.99% with only one error in 3000+ transfers. I do not intend to do 300 reviews for him, and even 120 reviews for him seems a bit much. Sven Manguard Wha? 05:08, 20 October 2011 (UTC)Reply
If you look close enough, you may see a pattern with his transfers. He transfers almost identical pages that's in a series. I reviewed like that, and the error was found as a surprise really. But now, I think 25% should be reviewed. As I said, "We are no GOCE". So do you want to start a "Requests for less reviews" on the main drive page where users could request 25% or 50%? Where some reviewers may accept or deny? ~~Ebe123~~ (+) talk
Contribs
 • 19:48, 20 October 2011 (UTC)Reply
Not really. By now I've worked with all of the people currently listed as reviewers and have reached the conclusion that they are intelligent people capable of making reasonable personal judgements. I see no reason to overly formalize it. I'll be doing 1 in 25 for the people I listed above, and 1 in 10 for the ones I didn't list, at least until enough reviews are in that I decide to bump them up to the 1 in 25 list. That's my personal decision, and other reviewers are free to do what they think is best. The way I see it, if it were not for the drives, none of these transfers would have been reviewed anyways, so I'm not going to get overly worried about the whole thing. Sven Manguard Wha? 14:42, 21 October 2011 (UTC)Reply
Lets just bump it to 25% for all. ~~Ebe123~~ (+) talk
Contribs
 • 19:59, 21 October 2011 (UTC)Reply

Priority List for January 2012 Drive

edit

I have been asked to create a list of files tagged with {{Copy to Wikimedia Commons}} containing at least one link to the mainspace so that participants in the upcoming drive can focus their efforts on a certain set of images. However, given the creation of a new transfer to commons tool, For the Common Good, which uses categories to fetch lists of files, I'd like to propose that we use a temporary template (e.g. Template:January 2012 Move to Commons Drive Priorty Candinate) and associated category (Category:January 2012 Move to Commons Drive Priorty Candinates) to flag mainspace-linked media files. The template could look something like this:

If there is consensus that this would be useful, I'll create the template and its category above and have my bot perform the appropriate taggings. This has to be done soon though, and a BRFA must be filed in this time, granted that the drive is only a few days away from starting. Also, please note that all remaining instances of this template will be removed at the conclusion of the drive. -FASTILY (TALK) 21:11, 26 December 2011 (UTC)Reply

.replace (/\{\{January 2012 Move to Commons Drive Priority Candidate[^}]*\}\}\n*/g, "")
~~Ebe123~~ → report on my contribs. 21:51, 26 December 2011 (UTC)Reply
This template may be useful - but in the new version of the FtCG it is possible to load lists of files Bulwersator (talk) 12:31, 27 December 2011 (UTC)Reply
Put in the User:Fastily/MXD page and you're on your way. Pretty much no need for anything. ~~Ebe123~~ → report on my contribs. 13:09, 27 December 2011 (UTC)Reply
Well never mind then, problem solved! I'll have my bot update that page more frequently. -FASTILY (TALK) 22:44, 27 December 2011 (UTC)Reply
I personally think using a category would be better, because categories are dynamic: if many people are using the same text file to feed FtCG, they will be faced with tons of "This file does not exist" errors as they load files that have already been transferred. So my advice would be: to preserve your sanity, use a category. — This, that, and the other (talk) 06:50, 28 December 2011 (UTC)Reply
  BRFA filed -FASTILY (TALK) 07:24, 28 December 2011 (UTC):Reply
A whole bunch of edits by Fbot turned up in my watchlist. It's not clear from the edit summary and template box what is supposed to happen next (should someone confirm that they are eligible?). I moved a couple of files using CommonsHelper, but I find it too tedious (CommonsHelper works like one out of two times). FYI, I'm the creater of these images and I confirm that they can be transfered: File:Erythemal action spectrum.svg‎, File:Prism-compressor.svg‎, File:CPA compressor.svg‎, File:Cpa stretcher.svg‎, File:THz pulse spectrum.png‎, File:THz pulse.png‎, File:Light through prism.jpg‎, File:Pulseshaper quadratic phase rb.svg‎, File:Pulseshaper quadratic phase br.svg‎. Han-Kwang (t) 15:47, 31 December 2011 (UTC)Reply
For the Common Good is way better. And tagging with priority was probably missed change to advertise drive in the edit summaries Bulwersator (talk) 15:56, 31 December 2011 (UTC)Reply
I see. However, I don't use Windows, which For the Common Good requires, so I'll leave it at that. Han-Kwang (t) 16:06, 31 December 2011 (UTC)Reply
The fact that it is known that they can be moved should be enough; now someone will come around to moving them at some point. One thing that I prefer with Commons Helper is that it attempts to guess categories. It often picks completely wrong categories, but it speeds up my searching for categories a bit. On the other hand, For the Common Good speeds up other things. --Stefan2 (talk) 17:47, 31 December 2011 (UTC)Reply
You can see from my edit history that it took me about one hour to move six files, including download/upload (direct upload was unreliable), adding cats, and repairing broken templates on commons. If you have a 500k backlog, I think you have to wonder whether the 23 man-years of work (assuming 5 minutes per move) wouldn't be better used in fixing broken links, correcting bad grammar on actual article pages rather than on moving pictures that are already used in articles. Han-Kwang (t) 11:18, 1 January 2012 (UTC)Reply
It results in categorized pictures usable by other language editions (it is extremely confusing for newbies to discover pictures working on enwiki and showing red text in their home wikipedia - BTW it is the worst effect of fair use) Bulwersator (talk) 18:54, 1 January 2012 (UTC)Reply
(unindent) Categorization is probably the hardest part, but the rest of the process can be fully automated, provided that you get community consensus that this is too tedious to do manually. If you do it at the database level on the Wikimedia servers, you can even preserve the original image uploader via global accounts. Use a bot to tag images with suitable license terms (like Fbot does) AND include a deadline: "this image will be automatically transfered in one month, unless this tag is removed". Start with the ones that can be categorized automatically and that do not have template issues.
By the way, I'm not always so happy about the way images are transfered. My username disappears from the upload log, and sometimes, source data for plots and images is deleted [1] or very difficult to find [2].
Han-Kwang (t) 19:47, 1 January 2012 (UTC)Reply
"this image will be automatically transfered in one month, unless this tag is removed" - transferring thousands of files with copyright problems to Commons will results in massive deletion, what will result in deleting also fixable files (and backlog will move in the different place rather than disappear) Bulwersator (talk) 21:08, 1 January 2012 (UTC)Reply
Besides, when I used For the Common Good a few hours ago, it took approximately 1-2 minutes per file moved, including categorisation and reformatting. --Stefan2 (talk) 03:01, 2 January 2012 (UTC)Reply

Twinkle Change

edit

I requested a while ago that Twinkle removes {{mtc}} (and related templates) as part of it's CSD function when F8 is the reason. This has now been implemented here and will, according to the commiter, "the tag {{move to Commons}} and most of its redirects are now automatically removed in the XFD (FFD and PUF), CSD, and DI modules." (here. For those using CommonsHelper + Twinkle to do the drive, I hope this helps :) - Rich(MTCD)T|C|E-Mail 10:40, 30 December 2011 (UTC)Reply

My bot actually does this periodically, but meh, this doesn't hurt. -FASTILY (TALK) 10:44, 30 December 2011 (UTC)Reply
People are using TW for tagging Moved To Commons? I haven't saw that in September. Also, how many runs will the bot have in January for untagging and adding priority? 1 day? ~~Ebe123~~ → report on my contribs. 13:05, 30 December 2011 (UTC)Reply

Working on one user at a time

edit

I think working on all the files uploaded by one user is a good way. For example User:Multichill/top self uploaders. I asked one user about some old maps and got this result User_talk:MGA73#Moving_files_to_Commons. The user suggest to delete 700+ files instead of moving them to Commons.

Perhaps getting a list of the top 10 uploaders in Category:Move to Commons Priority Candidates will give some good results? If one or more of the uploaders seems to be very good then hundreds or thousands of files can be moved with almost no checking and if the user on the other hand turns out to be really "bad" then we can tag a lot of files for deletion. --MGA73 (talk) 23:01, 30 December 2011 (UTC)Reply

I think it's often easier to move files from the same category or article, since they will often have similar Commons categories (meaning less category searching). For that reason, I typically pick some random image, and then move all images used in the same article(s) as that random image. Of course, if the uploader is the same, it could mean that the categories also are similar. --Stefan2 (talk) 13:20, 31 December 2011 (UTC)Reply

For the Common Good

edit

Version 1.0.1.1 of For the Common Good, the new Commons transfer tool, is available. I suggest all users of previous versions update to this version, because it automatically checks for new versions - if a bug is found or a change is needed during the MtC drive, then users of the tool can be efficiently notified of the available update.

The consensus appears to be that participants should concentrate on Category:Move to Commons Priority Candidates (it should not be exhausted, since it contains 143,806 files as I write this!). — This, that, and the other (talk) 01:25, 31 December 2011 (UTC)Reply

Bot tagging update

edit

I just wanted to make sure everyone was on the same page with how these massive categories are forming. A while back, Fastily coded a bot task that tagged files with licenses that were part of a (now depreciated) whitelist for transfer. All of the PD-USGov licenses (there were 100), as well as PD-self, GFDL-self, and the CC-self family, were on that list. Because of the size of the task bot Fastily's Fbot and my Svenbot worked the task. Fastily and I decided to freeze the tagging because it was kind of demoralizing to be working on reducing the number of files during the drive while the bot was adding 100 files for every one we handled.

The priority candidates list is a Fbot task; every file tagged for transfer that is used in the mainspace at least once is part of that list.

Now, I'm telling you all of this because I think you all should know that the actual size of both of those categories, if we set Fbot (and perhaps Svenbot) loose on the task again, will be double what it is now. The depreciation of the whitelist means that every file that is part of the free media megacateory and does not contain elements from the blacklist will be eligible for transfer. It's a very large category, and a majority of the items there will be transferrable.

Note that Fbot makes sure that bot the transfer tags and the priority tags are kept up to date, but periodically running tasks that remove no longer valid tags.

Should you all decide that it's better to just let the bots loose and get the final number, it is doable, just let us know. If we don't hear from you, we won't start it up again until after the current backlog has been drained significantly. Sven Manguard Wha? 13:45, 31 December 2011 (UTC)Reply

I think it would be better if people see how the total backlog number goes down during the January drive, so I suggest that the bots don't add new {{Move to Commons}} tags until the drive has ended. The backlog is already too big: there is not enough time to move all of the currently tagged images anyway. I'm also wondering: is it really useful to tag images as being movable to Commons if they already are in Category:All free media? Instead of searching the Move to Commons category, you could just search for images to move in the All free media category. --Stefan2 (talk) 14:01, 31 December 2011 (UTC)Reply
Template:Keep local (file may be inside Category:All free media but moved), file may be in Category:All free media and listed on the WP:PUF and other funny problems (see http://toolserver.org/~magnus/catscan_rewrite.php?ns[0]=1&ns[6]=1&templates_yes=PD-US%0D%0ADo+not+move+to+Commons&ext_image_data=1&doit=1 as example) Bulwersator (talk) 14:14, 31 December 2011 (UTC)Reply
  • I think that the tagging all files and creating The Biggest Backlog Ever is not bad - as it will show real size of backlog. Also jump from 10,000 to 500,000 (after transferring around 200,000 files) is also likely to be demoralizing Bulwersator (talk) 14:14, 31 December 2011 (UTC)Reply
    • But it should be done before and/or after drive Bulwersator (talk) 14:32, 31 December 2011 (UTC)Reply
      • At least not during the drive, please. If people look at statistics and see that the backlog was doubled during the drive, people would think that the drive was a huge failure while the true answer is that it's just a result of adding tags to places where tags previously were missing. I don't oppose running the bot today or in February. Please just keep it switched off in January. --Stefan2 (talk) 15:22, 31 December 2011 (UTC)Reply
  • As I noted it on the progress page, the goal may change, and that's if there are more files in the bot-assessed category, so set it loose for getting the category over with. ~~Ebe123~~ → report on my contribs. 20:10, 31 December 2011 (UTC)Reply

File names

edit

Can we please, please, please, PLEASE make sure that files have CLEAR, INFORMATIVE, UNAMBIGUOUS NAMES before moving them to Commons? Can we make sure that the names give a good idea of what the image actually is, in terms that do not require reading the uploader's mind? Can we make sure that the filename is not short and cryptic? Can we make sure that the names are such that the files they won't be confused with similarly-named-but-hugely-different files? Can we make sure that the names are distinct enough that there is no risk of them being re-used by someone else for a completely different purpose, thereby screwing up multiple articles and license releases?

Remember, we're not using MS-DOS. We can use filenames that are longer than eight characters.

RENAMING HINT: If the image is not used in an article, you should go back and check what other edits the uploader was making around that time, so that you have an idea of the purpose for which it was uploaded. If no article is found, then it's probably in the user's deleted contributions. If you don't have access to the deleted contributions by reason of not being an admin, then you shouldn't be renaming that image, much less moving it to Commons.

If you move badly-named images to Commons without making any effort to rename them or to find out what the hell they are... well, you should be ashamed of yourself. Bad Wikipedian. Bad. Go sit in the corner. DS (talk) 15:13, 31 December 2011 (UTC)Reply

Your renaming "hint" is bad as there is the image renaming policy and not that many files do get put in a article. Deleted contributions are for other things, such as logging inappropriate edits, such as page creation vandalism. The reviewers will make sure that there is a good name for each file. ~~Ebe123~~ → report on my contribs. 20:04, 31 December 2011 (UTC)Reply
If the reviewers did make sure that each image had a good name, I wouldn't have to make this request. DS (talk) 00:38, 1 January 2012 (UTC)Reply
The last paragraph is demeaning, as treating us like dogs. This is pretty bad advice, and you're begging us. You may always apply for FM at commons. Here are the things we (should) check (I check them all but if deleted, I just check number 1 to 8 and not mark as good as I do not have the file on enwiki):
  1. Image name
  2. Source
  3. Author
  4. Licence
  5. Permission
  6. Description
  7. Bot-checked
  8. Category
  9. Same file and licencing here and at commons.
The hole point of "reviewers" that I made was to detect copyright violations (bolded)
~~Ebe123~~ → report on my contribs. 13:21, 1 January 2012 (UTC)Reply

DS is right. With 200,000 files to choose from, we shouldn't be moving over files that no one has any clue as to what they are. It's not the reviewer's job to mandate that file names be informative, but Commons is a dysfunctional and understaffed project as it is, simply dumping our project's junk files on them without any attempt to filter it is irresponsible. Sven Manguard Wha? 21:32, 1 January 2012 (UTC)Reply

There is not necessarily an error if the licence differs. I moved an image listed as fair use here because I found out that it was published without a copyright notice -- and I only fixed the licence at Commons. But I guess it makes sense in most cases. --Stefan2 (talk) 22:59, 1 January 2012 (UTC)Reply
I moved one and changed the licence because it was just 2 coloured triangles. The 9th is for a bad licensing change, not changing because it isn't fair use, or changing to "too simple", but other things. ~~Ebe123~~ → report on my contribs. 23:30, 1 January 2012 (UTC)Reply

This is why the category Category:Move to Commons Priority Candidates exists: these images all have at least one use in an article, and it is possible to write a good description/give a better file name for most of them, if they don't already have these things. — This, that, and the other (talk) 04:16, 3 January 2012 (UTC)Reply

"[Please prioritize the human tagged files]"

edit

Why? Is see no reason to do this and it may encourage useless manual tagging. Bulwersator (talk) 18:51, 1 January 2012 (UTC)Reply

Don't know why either, and encourage the removal of the notes. ~~Ebe123~~ → report on my contribs. 19:35, 1 January 2012 (UTC)Reply
Okay, remove it then. My thinking is that files tagged manually are more likely to be accurate in that they are ready for tagging, and that it'd be good to get that backlog down to a smaller size because it's easier to envision kicking 13,500 files than it is 200,000 of them. Sven Manguard Wha? 21:27, 1 January 2012 (UTC)Reply

Priority candidates in certain category

edit

Thanks to catscan and "Move to Commons Priority Candidates" category it is trivial to generate list of priority images in certain category. Examples:

In Category:Public domain images ineligible for copyright: http://toolserver.org/~magnus/catscan_rewrite.php?depth=111&categories=Public+domain+images+ineligible+for+copyright%0D%0AMove+to+Commons+Priority+Candidates&ns[0]=1&ns[6]=1&ext_image_data=1&doit=1

In Category:NASA images: http://toolserver.org/~magnus/catscan_rewrite.php?depth=111&categories=NASA+images%0D%0AMove+to+Commons+Priority+Candidates&ns[0]=1&ns[6]=1&ext_image_data=1&doit=1

Bulwersator (talk) 21:16, 1 January 2012 (UTC)Reply

Fbot could tag them. ~~Ebe123~~ → report on my contribs. 23:02, 1 January 2012 (UTC)Reply

New Bot request

edit

I suggest that we get a bot to generate the user listings. It is hard to keep adding them and if you're using FtCG, it's a nightmare to remove the timestamp, the repetition, and adding the template. ~~Ebe123~~ → report on my contribs. 23:02, 1 January 2012 (UTC)Reply

Well, I can remove the timestamp from FtCG if you want - you're the one who asked me to add it!! I'm happy to fix the repetition, which is a bug. I personally don't see the point of the {{moved to commons}} template - it's either moved to Commons or deleted, so why not separate the log into two sections, under two headers ("Moved to Commons" and "Deleted")? — This, that, and the other (talk) 04:14, 3 January 2012 (UTC)Reply
My log is copy-pasted from FtCG, under single "Moved to Commons" header Bulwersator (talk) 11:32, 3 January 2012 (UTC)Reply
I just edit the log in Vi to get a better format. "Replace all" is fast and simple. --Stefan2 (talk) 20:36, 9 January 2012 (UTC)Reply

Robert Delaunay

edit

Please copy this file: http://en.wikipedia.org/wiki/File:Delaunay-Windows.jpg of Delaunay, which is now public domain, to commons. The mentioning of the Estate of Robert Delaunay works to be protected until 2031 seems to be copyfraud. Greetings -- Alinea (talk) 10:45, 3 January 2012 (UTC)Reply

1941 + 70 = 2011 + 1 = 2012. Have a look at Commons, http://commons.wikimedia.org/wiki/Category:Robert_Delaunay?uselang=de there is already a lot of files of Delaunay. This one is missing ... -- Alinea (talk) 11:43, 3 January 2012 (UTC)Reply
  Facepalm Bulwersator (talk) 18:17, 3 January 2012 (UTC)Reply
  Done -- Common Good (talk) 18:04, 3 January 2012 (UTC)Reply

Search trick of the day

edit

You may have noticed that incategory:"Move to Commons Priority Candidates" doesn't work for searching for images, since files are only in that category through transclusion. I found another way though: look for priority=true as part of the search term. For example, to find priority images about Chicago to move, select Multimedia (or File), then do the search:

Chicago priority=true

I don't know if all the bots involved in the drive are using the same format, but searching like that seem to be feeding me at least a few interesting candidates so far. --Closeapple (talk) 13:06, 4 January 2012 (UTC)Reply

Thank you! I've been looking for a way to do that for an hour. Scillystuff (talk) 22:06, 5 January 2012 (UTC)Reply

BTW: Is there another way to exclude files on Commons from the search results? --Leyo 23:05, 5 January 2012 (UTC)Reply

With the normal Wikipedia search box, not for the first few hours after a move; the search index is not in real time. Now, if {{Copy to Wikimedia Commons}} was removed once {{NowCommons}} was placed (or Svenbot fixed it), then after a day or so the problem will take care of itself for that file, because priority=true will disappear from the index. If a file has happened to hang around long enough with both tags that it got indexed that way, you could skip those also by adding -(NowCommons OR "Now_Commons") I believe:
"New York" priority=true -(NowCommons OR "Now_Commons")
The "OR" has to be in upper-case. Hope this helps. --Closeapple (talk) 09:34, 15 January 2012 (UTC)Reply
Thank you. What is meant is how to avoid Commons pages be found, not local images that were moved to Commons but not yet deleted locally. --Leyo 14:14, 15 January 2012 (UTC)Reply
In theory, Commons files would never have "priority=true" in their page texts, so a Wikipedia search should never bring up a file that has been deleted from Wikipedia (and exists only on Commons) for more than a day or so. That being said: I noticed that Commons might look for "priority" and "true" separately. So maybe the searches should have quotes around the phrase "priority=true", like this:
Chicago "priority=true"
France river "priority=true"
"New York" "priority=true" -(NowCommons OR "Now_Commons")
Hope this helps. --Closeapple (talk) 13:18, 16 January 2012 (UTC)Reply
I was looking for a general method on how to avoid Commons images being found, i.e. without the “priority=true” thing (that is a good trick, but not what I wanted to know here). Sorry for the lack of clarity. --Leyo 14:47, 16 January 2012 (UTC)Reply

Files in Category:Move to Commons Priority Candidates that are already on Commons

edit

Moved from User talk:Fastily
Hi Fastily. What about checking Category:Move to Commons Priority Candidates for files that are already on Commons? File:Glasgow Anniesland (Scottish Parliament constituency).svg for example was already there before being tagged by your bot. --Leyo 23:10, 2 January 2012 (UTC)Reply

That's User:MGA73bot job. As it stands, once MGA73's bot tags a file with {{Now commons}}, my bot removes {{Copy to Wikimedia Commons}}. Unfortunately, the Java framework I use does not have the ability to check if a duplicate of a file exists on Commons. While I can think of a number of extremely crude hacks to possibly remedy this issue, they'll at best be >50% accurate :\ Sorry. -FASTILY Happy 2012!! 07:29, 3 January 2012 (UTC)Reply
OK. It's just a matter of fact that if I decide to have another admin double check a transfer a made, it takes up to several weeks until NowCommons is added by a bot (if not added by me). In de.wikipedia, it usually only takes a few hours. --Leyo 09:09, 3 January 2012 (UTC)Reply
Wow... My own job :-) I started tagging after User:BotMultichill stopped tagged the files. My plan was only to do it from time to time because it makes toolserver beg for mercy :-D Later "tag_nowcommons.py" was changed and it made the bot tag files that should not be tagged (files with a keep local and pages where the file is on Commons and page on en-wiki is only a description etc.). After a long time of doing nothing i tried to make a query on toolserver but the query was so big it failed. However, I found a work around that included manual work. So that is why my bot does not tag the files sooner.
I thought that as long as there is plenty of files with a NowCommons then it is not a big problem that files were not tagged. But I see the problem with the current Move to Commons Drive. So we should find a better solution. I will do a few tests to see if I can find a solution. Perhaps we can copy the bot from de-wiki? --MGA73 (talk) 16:18, 3 January 2012 (UTC)Reply
The bot on de.wikipedia is RevoBot. It does not tag NoCommons files. In order to respond quickly the bot watches the uploads by File Upload Bot (Magnus Manske). --Leyo 16:30, 3 January 2012 (UTC)Reply
Thank you for the information. Files can be moved to Commons by other bots so watching the uploads of ^bot is not enough. But it is a good start.
I did some manual work and started my bot. But we need a better solution if we want the bot to act faster. If Fastily keeps the "ugly" files away from Category:Move to Commons Priority Candidates I could ask my bot to work on that category more often untill we find a solution for all files on en-wiki. --MGA73 (talk) 17:46, 3 January 2012 (UTC)Reply

There are currently 229 files tagged both as Priority Candidates and NowCommons. --Leyo 20:35, 4 January 2012 (UTC)Reply

Please note that I will be fixing Twinkle soon so that it removes {{copy to Commons}} from a file page when applying {{now Commons}}, {{keep local}}, or {{do not copy to Commons}}. That should assist in keeping this number down. — This, that, and the other (talk) 06:20, 5 January 2012 (UTC)Reply
Why Template:Keep local? It may be added to file that can be copied to commons Bulwersator (talk) 07:37, 5 January 2012 (UTC)Reply
In addition, in many cases there is simply no reason for keeping a local copy of these files. --Leyo 21:31, 5 January 2012 (UTC)Reply
I agree that "Keep local" is often added without a good reason. But I suggest that the discussion of that is taken later. The "anti Commons users" are often active in discussions about the template and the "pro Commons users" are often not there when it is being discussed so the result is always "kept".
I fixed most of the 229 images mentioned above yesterday but new files keep showing up so we need a bot to run over those files often or we need more admins to delete the files. --MGA73 (talk) 17:57, 8 January 2012 (UTC)Reply
While I do think that files incorrectly tagged with anti-Commons tags should be moved to Commons, I feel that it would be more efficient to move other files first. The files originating from the anti-Commons users may result in long and angry conversations, taking a lot of time to process. --Stefan2 (talk) 20:49, 9 January 2012 (UTC)Reply
Instead of deleting the files you can just remove the NowCommons and add "|File:New name.jpg" to the keep local template. That will save the discussion about deletion for later. --MGA73 (talk) 06:59, 10 January 2012 (UTC)Reply

Next Drive

edit

As this drive progresses, it's time to decide for our next drive. So I will be getting it ready for March. Some changes will be that the main goal will most probably be in the Priority category, and if it's not cleared out, it will be the bot-assessed category as it is over 3 times the size. We will also expand the awards for deletion and talking about deletions, the higher deletion awards will be given for deleting other users files, as the current sysops are only deleting their files (most of the time). Please feel free to raise your comments. ~~Ebe123~~ → report on my contribs. 01:16, 5 January 2012 (UTC)Reply

I'll start tomorrow. ~~Ebe123~~ → report on my contribs. 01:24, 5 January 2012 (UTC)Reply
Next drive? With this speed all the files will be moved this time :-D --MGA73 (talk) 17:49, 8 January 2012 (UTC)Reply

I would recommend giving priority to those files in the situation discussed in #Already in use in WP:fr — that is:

  1. First, files that exist on English Wikipedia and don't exist on Commons, and are already redlinked with an identical filename on another Wikipedia/Wikimedia project; such files would be in immediate use when transferred.
  2. Second, files that exist on English Wikipedia and other Wikipedias/projects as copies, but are not on Commons yet.
  3. Third, the current priority (files that are in use on English Wikipedia, indicating that they may become useful quickly on other projects).

For contest purposes, if one wanted to get complicated: a score could be assigned based on the number of redlinks that would be solved by transfer, number of different projects that merging removed duplication on, etc. --Closeapple (talk) 20:31, 17 January 2012 (UTC)Reply

If someone makes a list of those files, I would be happy to help with processing them. I have created a list of files on English and Japanese Wikipedias which are suffering from the EXIF rotation problem and am currently processing those, since it is another urgent category. --Stefan2 (talk) 21:38, 17 January 2012 (UTC)Reply

Deletions

edit

For admins: You may always delete files from other users, and the backlog for deletions are from over 4 days ago. You may also go join Guerillero's F8 deletions efforts. ~~Ebe123~~ → report on my contribs. 01:16, 5 January 2012 (UTC)Reply

Thanks for pointing that out Ebe123 --Guerillero | My Talk 02:43, 5 January 2012 (UTC)Reply
Double the work load for the poor old admins ;-)  Ronhjones  (Talk) 20:21, 5 January 2012 (UTC)Reply
I actually was planning on a "test-sysop" here to help... But as it's not implemented yet (or approved by consensus), I couldn't exempt if I went through a RfA (I do not want to) ~~Ebe123~~ → report on my contribs. 20:28, 5 January 2012 (UTC)Reply
Just link to the log here. I am flexible. --Guerillero | My Talk 22:06, 5 January 2012 (UTC)Reply
It will be there for the next drive. ~~Ebe123~~ → report on my contribs. 23:46, 5 January 2012 (UTC)Reply
I don't plan on retracting the offer until there isn't a 500+ file backlog --Guerillero | My Talk 05:57, 6 January 2012 (UTC)Reply
We need more admins to delete files. I deleted almost 2.000 files since January 1 but the number of files pending deletion is still growing... --MGA73 (talk) 17:46, 8 January 2012 (UTC)Reply

Manual or automatic logs?

edit

I might be confused. I'm not seeing my edits come up in Wikipedia:WikiProject Images and Media/Commons/Drives/Jan 2012/Logs, even after 48 hours after adding the initial template. Does a bot take care of filling in our moves, or do we have to edit it ourselves using the comments the template dropped in? --Closeapple (talk) 08:35, 5 January 2012 (UTC)Reply

Progress?

edit

251,638 - 249,380 = 2258. But according to "progress" table backlog was reduced by 479 files. Why? Bulwersator (talk) 22:31, 5 January 2012 (UTC)Reply

Addressed now. Sven Manguard Wha? 01:54, 7 January 2012 (UTC)Reply
During next drive we should show "real" backlog, rather than "manual tagged only" Bulwersator (talk) 08:48, 7 January 2012 (UTC)Reply
Agreed. It was a function of the fact that we were tracking the wrong thing from the start. Next backlog, we should do three lists (manual, bot, and both) and one graph showing all the lines. Mind you the graph is going to be tricky, as we'll be doing 200 files a day in a category with 200,000 items... Sven Manguard Wha? 15:04, 7 January 2012 (UTC)Reply
I'll add the bot and total next drive. ~~Ebe123~~ → report on my contribs. 12:53, 8 January 2012 (UTC)Reply

New CH!

edit

With permission from Magnus, I went ahead and created a new version of CommonsHelper on my Wikimedia Labs instance, it's ALOT quicker then the old one. For those who are not using FtCG, check it out Here! - Rich(MTCD)T|C|E-Mail 08:51, 6 January 2012 (UTC)Reply

Are there any differences apart from the performance? --Leyo 10:14, 6 January 2012 (UTC)Reply
Nope, the script itself is the same, the only things different are 1. Some wording has been changed, such as the "There seems to be a problem" message after uploading ok is gone 2. A different bot does the uploading (Found Here) and 3. It's a lot quicker - 92.40.253.97 (talk) 14:14, 6 January 2012 (UTC)Reply
Would you have the possibility to implement any improvements by request? --Leyo 01:51, 7 January 2012 (UTC)Reply
My biggest beef with the file upload bots is that they all put the transfer information into the Template:Information template. This can make things pretty confusing, and in some cases incorrect. There needs to be something like the line FTCG puts in, or my "Template:English Wikipedia to Commons Transfer Documentation" to separate everything out. Sven Manguard Wha? 02:22, 7 January 2012 (UTC)Reply
@Leyo - Sure, although as I'm no coder, it may be delayed.
@Sven: I don't know, any suggestions?
Rich(MTCD)T|C|E-Mail 19:01, 7 January 2012 (UTC)Reply
Yes. Take all of the information about the transfer which is currently put into the Template:Information form, and put it all in the "Original upload log" section, above the original upload data that gets stuck in now. It dosen't need to be fancy, just functional. Sven Manguard Wha? 19:22, 7 January 2012 (UTC)Reply
@:Rich: Where can we put the requests? Here? I have a small one: It is possible that the file description pages would not start with an empty line?
@Sven: If you add importScript('User:Magog the Ogre/cleanup.js'); to your common.js, you can do the cleanup much quicker. I am sorry, but I am not happy with commons:Template:English Wikipedia to Commons Transfer Documentation. As seen in this example, it puts too much weight on who made the transfer and when. This information, however, is way less important than who is the author and what is the original source. The transfer-related information is not relevant to the average user (I do not refer to a logged-in Wikipedia or Commons user, but a person surfing in the internet), so it is sufficient to have it in the history. --Leyo 19:59, 7 January 2012 (UTC)Reply
@Leyo: Here or my talk page. I'll see what I can do —Preceding undated comment added 12:24, 9 January 2012 (UTC).Reply

File lists by topic

edit

What I am missing here on en.wikipedia is the possibility to get file lists by topic (files used in articles of a certain topic). This could either be done by category trees or by WikiProject banner templates transcluded in talk pages. On de.wikipedia, the former possibilty is available (example file list; bot currently under maintenance).
The advantage of file lists by topic is that project participants could focus on areas they are knowledgeable in, including legal aspects (e.g. freedom of panorama in different countries). Is anyone able to generate such lists? --Leyo 13:39, 6 January 2012 (UTC)Reply

Go http://toolserver.org/~daniel/WikiSense/CategoryIntersect.php, and fill it out. ~~Ebe123~~ → report on my contribs. 20:33, 6 January 2012 (UTC)Reply
How? Please note that I am not looking for files in a category tree, but files in articles in a category tree. --Leyo 01:49, 7 January 2012 (UTC)Reply
The trouble is that images here, have typically been uncategorised. Which makes it impossible to lump together like images. If you remember, Leyo, I spent almost every April evening last year adding {{pd-chem}} to several thousand chemical structures - which is relatively easy, as one can usually spot a structure in the thumbnails at category:all free media - it's just the vast size of that category that makes it take so long. Perhaps a bot to run every free image through Wikisense?  Ronhjones  (Talk) 16:20, 7 January 2012 (UTC)Reply

@Ron: I know that local images are generally uncategorized. That is why I am asking for another, generally applicable (not just for chemical structures) method. There is a bot for cattree approach exists on de.wikipedia, but the bot owner is too busy to offer the service on other wikipedias. In brief, it works as follows:

  1. Generate a list of all articles in a given cattree.
  2. Generate a list of all local images in these articles.
  3. Exclude fair use material (everything that cannot be moved to Commons).
  4. Write the file list to a page, preferentially formatted as a gallery.

Is there someone who is able to do this (or something similar)? Otherwise we post post a request at WP:BOTREQ. --Leyo 17:01, 7 January 2012 (UTC)Reply

The solution I've found to the categorisation problem is to take a random file eligible for Commons and then checking all articles using the same image or all other images uploaded by the same user, since they may have similar categories. It saves some time searching for categories. --Stefan2 (talk) 18:05, 8 January 2012 (UTC)Reply
The purpose of my suggestion is that if a user get an image list of his topic, he is more knowledgeable in terms of law (image eligible for Commons) and categorization. The gains would be a higher efficiency and a lower error rate. In my case, I could move and categorize images e.g. from Switzerland more efficiently, because i am pretty familiar with the country-specific freedom of panorama and the categorization system on Commons. --Leyo 00:12, 10 January 2012 (UTC)Reply

New uploads

edit

split from above as request
The other sad thing I notice is that editors still continue to upload free images to en-wiki - I tagged a load the other night with my "move to commons" script.  Ronhjones  (Talk) 16:20, 7 January 2012 (UTC)Reply

Yes, that is a problem. It would take one person about two hours to move a given day's uploads to commons (guesstimate on time, factoring in ease of FTCG), the issue is that until someone does that, we're going to get things coming in faster than we can get them shipped out. People just don't read the notices advising things be sent to Commons. Sven Manguard Wha? 16:35, 7 January 2012 (UTC)Reply
Let's discuss the problem of local uploads in another thread please. --Leyo 17:01, 7 January 2012 (UTC)Thread splitReply
The solution to the problem with local uploads to English Wikipedia might be to post a notice at the uploaders' talk pages when their images are moved to Commons. This practice is used on Japanese Wikipedia where you are asked to add {{subst:コモンズへの移動通知|local file name|Commons file name}}--~~~~ at the bottom of the upoader's talk page. If people get notices about this, they might realise that they should upload their images to Commons instead. Commons moving tools could easily add this tag automatically so that it won't waste any time for the Commons mover. --Stefan2 (talk) 18:05, 8 January 2012 (UTC)Reply
Maybe bigger than this group - could it not be engineered to switch an uploader to commons, once he has picked a "free media" category. Wouldn't trap all, as some cannot even be asked to provide any description or license... :-(  Ronhjones  (Talk) 22:16, 8 January 2012 (UTC)Reply
In order to upload something to Commons, you need to be logged in there. It seems that many users haven't activated SUL, and even if it is activated, there might be an SUL conflict on Commons. Commons seems to have the strictest usurpation rules of all of Wikimedia (0 edits on Commons, no not yet usurped accounts on any other Wikimedia project), so it isn't really easy for users to complete SUL either. But if Special:Upload can check whether you are logged in on Commons or not, maybe your suggestion would be possible. --Stefan2 (talk) 12:04, 9 January 2012 (UTC)Reply

It seems that not all top uploaders have been made aware of Commons using {{un-c}}. Maybe we should do that. --Leyo 08:26, 9 January 2012 (UTC)Reply

Maybe the moving tools could just notify all uploaders automatically by putting that template on their talk pages when moving a file. It would spam the mass uploaders' talk pages quite a lot, though. --Stefan2 (talk) 12:04, 9 January 2012 (UTC)Reply
Could be tweaked - if you upload to commons and don't add any category, then you get a big message by a bot some time later - if you repeat the action it just adds the new page to the list it just made - example here - http://commons.wikimedia.org/wiki/User_talk:Ronhjones/Archive_1#Tip:_Categorizing_images_5. A similar system would make multiple notifications much smaller and compact.  Ronhjones  (Talk) 21:24, 9 January 2012 (UTC)Reply
That's one of my bots. You can find the source code here. I hate to get the same message twice so I implemented this. The trick is that the bot leaves a hidden tracker (<!-- Uncategorized notification -->) which can be use later to find the end of the list. It shouldn't be too hard to reuse this code to create a bot to notify all uploaders who appear at User:Multichill/Free uploads. Multichill (talk) 22:15, 9 January 2012 (UTC)Reply
Yes, a bot which notifies users on upload would be wonderful. Not only would they be notified, but they would also be notified earlier than if they aren't notified until image moving time. --Stefan2 (talk) 00:14, 10 January 2012 (UTC)Reply

MtC files sorted by page views

edit

Here is something simple, but helpful I hope, I threw together: User:Quibik/MtC top files by view counts. This provides at least some prioritization in the set of more than 100,000 files. —Quibik (talk) 05:21, 8 January 2012 (UTC)Reply

Do you mind if we strike out ones that we've done or notice are done? (With the understanding that you might regenerate the list and lose the strike-outs, of course.) Also, is it easy to regenerate once a bunch of the files are deleted or no longer tagged? --Closeapple (talk) 10:30, 8 January 2012 (UTC)Reply
That would be ok by me, I'm just not too sure how practical it would be to make many small edits to a ~200 kB sized page. I can regenerate it pretty much instantly, if desired. —Quibik (talk) 11:34, 8 January 2012 (UTC)Reply
Here's an idea for an alternative way: as it would be expected that the images in that list are moved sequentially, a subpage (like User:Quibik/MtC top files by view counts/index) could be created that stores the number of top images that are done or "taken" at the moment. It would be transcluded on top of the list in a noticeable manner, with an "edit" button next to it. Now, if someone decides to move any images on that list he/she could increase the index number by the amount he/she vouches to do before starting to do them. How does this sound? —Quibik (talk) 12:01, 8 January 2012 (UTC)Reply
Or I could just make the list shorter, say 1,000 files, and refresh it more often. It wouldn't have the benefit of preventing editors from trying to work on a same image simultaneously, though, like my previous suggestion would. —Quibik (talk) 12:08, 8 January 2012 (UTC)Reply
Just regenerating the list would work for me: I pick out the files that interest me or look quick, and look at the number just as a rough guide of how important it is to do it sooner, rather than just doing the list starting at the top. It's been 2 days since an update, and I only came across 1 file I was planning on moving that someone else got to first, so I haven't even bothered striking out things as I mentioned. Maybe there isn't as much risk of picking already-moved files yet as I expected there to be. --Closeapple (talk) 08:06, 10 January 2012 (UTC)Reply

GIF to PNG

edit

If I see a (non-animated) GIF file eligible for Commons, but I convert it to PNG before I upload it to Commons should I still add it to the log? The reason I ask: Since the Commons transfer process is really download+upload+delete anyway no matter whether a bot or a user does it, and GIFs are deprecated and generally lack metadata (so there's nothing to lose in the conversion), it seems silly to not let the upload land on Commons as a PNG instead of a GIF with {{BadGIF}} already applied, since I already have command on my computer to do it. (I'd then nominate it for normal file-for-deletion on en.wiki, since speedy on en.wiki explicitly excludes file format changes.) I see 228 GIFs out of 5000 files in User:Quibik/MtC top files by view counts, for example. --Closeapple (talk) 08:24, 10 January 2012 (UTC)Reply

Have a look at the concerns expressed at commons:Template talk:Convert to PNG. --Leyo 08:49, 10 January 2012 (UTC)Reply
My understanding of the argument for converting .gif to .png is this: Pro: PNG compresses better. Con: PNG is a much larger file. If that's really all it is, then by all means convert them. Wikipedia's devs have told us several times that we should not worry about server space in our decision making. Of course it goes without saying that if you change the format, it necessetates a change to the file name (Example.gif --> Example.png), so you're going to have to make sure that the pages that use the file all use the new name. Thankfully we have Fbot task 10 now, which might be able to help. Sven Manguard Wha? 15:36, 10 January 2012 (UTC)Reply

Already in use in WP:fr

edit

Hello, sorry if it's not the correct place to talk. Somes articles on WP:fr are translated from WP:en and files in the scope of your project are already in use there. (in red). I don't know how to highlight this kind of priority.
For exemple :

not yet flag by the projet

candidate to be flag by the project ?

- Drongou (talk) 00:20, 12 January 2012 (UTC)Reply

I think that the lack of a flag is just random chance, because of Fbot not getting to that file before the Commons drive started on January 1. The French translated articles indirectly must have the same priority as English: Because the French articles were translated from English, each image also appears in an English article. Fbot (which sets the priority flag) does not seem to care how many articles use a file: Fbot only cares whether it is used on at least 1 article. File:Gujarat patola.jpg and File:Liu Jin Li Curler.jpg are also in use in the English articles; it seems to me that both files should be flagged, and that Fbot just didn't get to them. (Fbot has temporarily stopped flagging files, so that users can see progress in the statistics during the January drive.) --Closeapple (talk) 08:44, 12 January 2012 (UTC)Reply

A question for anyone familiar with Wikipedia statistics: Are there recent logs or statistics about the 404s (page names that were requested but that don't exist) on Wikipedia projects? If we can correlate 404s with filenames, we might be able to discover which English files are the most "redlinked" on other projects, and therefore are important to move to Commons. --Closeapple (talk) 08:44, 12 January 2012 (UTC)Reply

Images uploaded to multiple projects

edit

There is a category in de.wikipedia that lists local copies of files initially uploaded to en.wikipedia. These files might also be of intested for other Wikipedias. Similar categories might be created here. --Leyo 10:02, 12 January 2012 (UTC)Reply

Didn't User:MGA73 operate a bot to check if an image appears on both English Wikipedia and Commons without having a {{NowCommons}} template? It might be useful to use that bot code to create a bot which adds interwiki links if a picture appears on several Wikimedia projects so that all images in use on several projects are identified. I assume that finding an identical image on e.g. French Wikipedia isn't more complex than finding an identical image on Commons; it's just the tagging which gets a different syntax. Some time ago, I came across a user who uploaded many of his images locally to the English, German and Italian Wikipedias and it would be nice to be able to tag the images as {{NowCommons}} on all three projects at the same time. --Stefan2 (talk) 11:13, 12 January 2012 (UTC)Reply

It is tag_nowcommons.py :-) --MGA73 (talk) 16:31, 15 January 2012 (UTC)Reply
This one? --Stefan2 (talk) 18:19, 15 January 2012 (UTC)Reply

How to transfer a lot

edit

This procedure only works on files that are obviously own work. Don't use it if their is a hint of doubt.

  1. Install and configure Pywikipedia.
  2. Go to User:Multichill/top self uploaders and pick an easy gallery
  3. Check the images (make sure they're all own work) and remove any problematic images (not own works/derivative works/freedom of panorama seems to be the cause of most problems)
  4. Fire up the bot: python imagecopy_self.py -lang:en -autonomous -imagelinks:User:Multichill/top_self_uploaders/<username>
  5. Wait for the bot to finish (you can start with the next gallery if you like)
  6. Check the images at Commons

This way we can really make a difference. Multichill (talk) 16:27, 15 January 2012 (UTC)Reply

I think that the problem isn't that it takes time to find the images but that it takes a lot of time to clean up the data after a transfer. In many cases, the text on the file information page doesn't use the {{Information}} template but text stored in any other format, requiring a lot of reformatting. The file description page often contains texts such as "photo of the train station taken by the uploader seen from the west entrance" which needs to be split up in description, source and author. Often there are no categories either, so it is necessary to search for those too. Does your tool handle this in some efficient way? Besides, I suppose that it would require a bot account both here and on Commons (for uploading+NowCommons tagging) which I currently don't have. --Stefan2 (talk) 18:16, 15 January 2012 (UTC)Reply
I agree that checking and cleaning up takes time even if imagecopy_self.py has reduced that time. It is a big problem if information is lost during transfer and that often happens if the transfer is made by less experienced users (for example if they just add "From Wikipedia" or a username as source). It often takes more time to repair than it would have taken to make the transfer ourselves.
However, if all relevant text is added to the page on Commons I think it is still ok even if the text is not sorted into the right boxes or if categories are not added. We have perhaps 100 (?) users that can make a good transfer but only 20 (?) that is actually moving files. But we have 1.000 (?) users that could help categorize and rearrange the information on Commons. So I think that if someone wants to move files to Commons without adding categories etc. that is ok.
We should have 200 users to check files before move, 20 users to move the files and 2.000 users to cleanup after the move and if huge amounts of files with same problem is found the 2 users to do bot-cleanups. --MGA73 (talk) 08:35, 16 January 2012 (UTC)Reply
{{check categories}} is currently used on 246,081, {{uncategorized}} on 228,906 and {{BotMoveToCommons}} on 64,954 images. Please don't make the backlog at Commons worse than it already is. Along with checking for copyvios, cleaning up the image info should be the most important step of the whole process, I think. —Quibik (talk) 17:33, 16 January 2012 (UTC)Reply
I agree that it means more trouble if people upload images improperly. Yesterday, I ran into a number of cases where users had moved English Wikipedia thumbnails to Commons under the same file name, all without adding {{NowCommons}} and with incomplete sourcing. On the other hand, if we move files without cleaning them up properly, it makes backlogs at Commons worse. --Stefan2 (talk) 18:35, 16 January 2012 (UTC)Reply
Interesting comparison: en.wikipedia vs. de.wikipedia. ;-) --Leyo 19:01, 16 January 2012 (UTC)Reply
Why it is better to have the backlog on en-wiki? And the difference between Commons and en-wiki is that Commons try to categorize images where en-wiki don't. January is a "Move to Commons Drive" - February could be a "Clean up on Commons Drive" :-) --MGA73 (talk) 20:29, 16 January 2012 (UTC)Reply
Re: de-wiki contra en-wiki. I moved 100 images from de-wiki a few days ago so that de-wiki users can have something to work with and I can easily move a few thousand more ;-) --MGA73 (talk) 19:51, 21 January 2012 (UTC)Reply

Some of the files end up in this category. If someone needs a few minutes away from the mtc-drive they are welcome to have a look at the files in this category. It should be possible to empty the category with a lot of hard work. But it is sooooo boring to work on 800+ files but if 10 users fix a few files each day it should only take a few weeks to empty the category. --MGA73 (talk) 18:55, 20 January 2012 (UTC)Reply

 
Example of a logo copyrighted in the UK
Many of the files seem to be British logos which can't be deleted because of commons:COM:TOO#UK. It might be better to wait with those until commons:COM:Deletion requests/Two British logos has been closed, but I suspect that most if not all should be removed from Commons and that the licence template should be specified as {{PD-ineligible-USonly|the United Kingdom}}. They should not be marked as copyrighted (or get a fair use rationale) unless they are above the US threshold of originality, since those tags are (as far as I have understood) reserved to works copyrighted in the US. The fact that the Edge logo was determined to be copyrighted by a British court due to an "unusual" font being used for writing the letter E probably means that almost no British logos can go to Commons. --Stefan2 (talk) 00:17, 21 January 2012 (UTC)Reply
Yes I know that not all files can be deleted. But the template says "... Once this issue has been resolved, please retag it ..." and if it is not possible to resolve the issue then the solution is to remove the tag and add perhaps {{Do not move to Commons}} to inform other users that the image can't be moved. --MGA73 (talk) 19:10, 21 January 2012 (UTC)Reply
Just so it's clear what is being said here: In the case of commons:COM:Deletion requests/Two British logos, the problem is not that it's impossible to resolve, just that it hasn't been resolved quite yet; it's going to fall one way or the other. Now, the other files in Category:Wikipedia files moved to Wikimedia Commons which could not be deleted might be resolvable. (And really, all files are resolvable eventually: if all else fails, Commons:Commons:Project scope/Precautionary principle applies.) --Closeapple (talk) 09:57, 23 January 2012 (UTC)Reply
I agree. Everything can be resolved if there is time enough - in 200 years everything is PD-old :-) I was just trying to say that if it is not possible to resolve the problem in a few weeks then the template should be reemoved/replaced. If we remove what we can't fix it is easier to find what we can fix. --MGA73 (talk) 11:40, 23 January 2012 (UTC)Reply
I joined, but it is "we may keep it from changing into YA giant backlog" rather than "it should only take a few weeks to empty the category" Bulwersator (talk) 12:37, 23 January 2012 (UTC)Reply

Help with an image

edit
 
AW101 undergoing VH-71 testing near the Lockheed Martin facility in Owego, NY

I have volunteered to do the Good Article review of AgustaWestland AW101. I have checked all the images and most are properly licenced. There appears to be a minor issue with this one. I see a red warning banner saying This file was flagged for transfer by a bot. Please thoroughly review the copyright status of this file and ensure that it is actually eligible for transfer to commons

I would appreciate it if someone could do what has to be done and remove the red warning banner, or let me know where I should take the problem. Thanks; I'm not conversant with issues surrounding proper use of images. Dolphin (t) 02:21, 25 January 2012 (UTC)Reply

Short answer: You don't need to worry about it.
Long answer: A few months back, two bots, Fbot and Svenbot, tagged over 100,000 freely licensed files for transfer to Commons. Because it was a bot, rather than a human (who presumably would be able to tell if a file had a false claim of own work or other shenanigans) that tagged the file for transfer, the red message was added. All the red message is doing is telling the people doing the transfers to double check that a file legitimately should be transferred, which realistically is something that we need to do anyways.
Hope that helps. Sven Manguard Wha? 03:40, 25 January 2012 (UTC)Reply
It does help. Many thanks. Dolphin (t) 05:23, 25 January 2012 (UTC)Reply

Reflections on the drive, opinions on improvement needed

edit

Please see the thread Wikipedia:File namespace noticeboard/Archives/1#Reflections on the Transfer to Commons Drives. Sorry for the long, long chunk of text. Sven Manguard Wha? 02:28, 27 January 2012 (UTC)Reply

PR lingo detected?

edit

Greetings. Please look at this one: [3] and tell me if the description is not questionable: DDRdrive X1 - The drive for speed. This sounds suspiciously like a slogan similar to "XYZ Cameras - Picture your life [TM]". Wikipedia is NOT an advertising platform, and hopefully will never be. Opinions please. -andy 77.190.8.122 (talk) 21:35, 27 January 2012 (UTC)Reply

Yes, and you may change the description. Be bold. Change things without consulting. ~~Ebe123~~ → report on my contribs. 01:30, 29 January 2012 (UTC)Reply

Keep Local teamplate.

edit

While I was going through the guide guide for moving a file I felt that the keep local teamplate is not discussed.Lets say that a "keep local" teamplate exists alongwith "move to commons" teamplate(which also says its a priority candidate) then what should one do?For example see here.I overlooked the keep local teamplate and moved the file and added "NowCommons" tag to it as suggested by the guide because the file is a self work and it falls under attribution sharealike version 3.0.My question is that if a copy of file is kept then what is the need of moving the file.Again if somebody has uploaded a file and shares with "sharealike 3.0" then it means one does not have a problem with sharing a file on other projects.The whole concept of move to commons is to reduce space, but here a file (with keep local teamplate) is rather duplicated.Vivekananda De--tAlK 06:22, 29 January 2012 (UTC)Reply

Space is not the most important argument to move to Commons. Even if a file is deleted it is not "deleted deleted". It is just hidden from non-admins. However, once moved to Commons it can be used everywhere so instead of 5, 10 or 50 copies there will only be 2.
You can move files even if there is a Keep local. The template is only a request not to delete the local file if a copy is on Commons. If the file is totally useless you can nominate it for deletion but it is probably easier just to skip the file and we could have a discussion another time what to do with keep local-files. --MGA73 (talk) 09:32, 29 January 2012 (UTC)Reply

Finished

edit

The drive is now ended. The awards will be given out after some extra reviews, and you may come back for the march drive. Sign up there already! ~~Ebe123~~ → report on my contribs. 00:01, 1 February 2012 (UTC)Reply

It was good having over 50 users to tackle the biggest backlog in Wikipedia. Have a nice month and see you again soon! ~~Ebe123~~ → report on my contribs. 00:02, 1 February 2012 (UTC)Reply
This was a fun drive; I learned a lot about Commons participating. One suggestion for the next drive: it is a huge gap between 200 files moved and 1000 files moved. Interim prizes might encourage participants to keep going; I slowed down when I decided that there was no way I was going to be able to break 1000. Grondemar 00:08, 1 February 2012 (UTC)Reply
I'm sorry I got distracted and went off to other things --Guerillero | My Talk 02:15, 1 February 2012 (UTC)Reply
I'll be adding some (WikiCups) of different colo(u)rs. ~~Ebe123~~ → report on my contribs. 11:27, 1 February 2012 (UTC)Reply
One of the pics that was missed was File:Malcolm Wilson gravesite; Gate of Heaven Cemetery (Hawthorne, New York).jpg. Would anybody mind if I sent it in early before the proposed March 2012 drive? And while I'm at it, can I get a hidden category to identify the original uploader? I've uploaed too many other people's images to the commons that have been falsely identified as mine. ----DanTD (talk) 14:41, 5 February 2012 (UTC)Reply

When are the awards going to be given out? – Quadell (talk) 13:45, 23 February 2012 (UTC)Reply

Straw poll on the bot-tagged category

edit

Congratulations on knocking off over 20,000 files. That's an amazing number. While we still have everyone watching this page, I wanted to start a straw poll that I've been dreading starting. There are 233,000 files that are in the bot-transferred transfer category. When Fastily and I did the first run of Fbot and Svenbot taggings, we were somewhat selective with what templates were put onto the Whitelist. If we do another round of taggings, which we have tentatively planned for this coming month, we're going to drop the Whitelist in favor of tagging everything in Category:All free media (which has 372,000 files in it) that isn't also on the blacklist. That means that there are 139,000 files that could be eligible for getting added to the bot tagged list.

Before I contact Fastily and we start the bots again, I wanted to make sure that the community was okay with that. I estimate that we'll tag another 100,000 to 115,000 files if we run the program. The priority candidates task will be run immediately afterwards, so that both the bot tagged and the priority categories are up to date come the beginning of the March drive.

Should we

a) Run the bots this month (Upside: it'll be as current as possible, and we'll be able to tell if something is on the blacklist simply by the absence of a transfer tag. Donwside: demoralizing aspect of "congratulations on clearing 20,000 files, we're adding 5 times that to the to do list")
b) Do nothing (Upside: Not demoralizing. Downside: Once we clear the backlog, on track for 2013 or 2014, we'll have 139,000 more files to deal with, plus whatever else is uploaded over time. A rough estimate based on January 2012 levels is that we add 25,000 to 30,000 freely licensed files a year. That would mean that even if we clear what's tagged now, we might have up to 200,000 more files to deal with by the end of 2014, unless we can get people to stop uploading Commons eligible images here.)
c) Depreciate the bot tagged template entirely and remove all instances of it now in use (Upside: The bot-tagged system isn't really that much more efficient than just using All free media, and the edit count required is high. Downside: Makes it more likely that blacklisted items will be transferred, and it'll take 233,000 edits to remove the tags already done).

Other than that I personally don't see the 'remove all instances of it now in use' part of option c as being a worthwhile use of resources, I'm actually rather ambivalent on what is chosen here. I'm far more concerned that the transfers are done, and done correctly, than I am about how we reach that objective. Please note that if no one responds, Fastily and I will implement option A, which is the default per prior community discussions which I don't have on me but could dig up if I had to. Sven Manguard Wha? 04:02, 1 February 2012 (UTC)Reply

Straw poll comments

edit
I we need two different mtc-templates. One to add when the file has been checked and found ok by a (trusted) user and another we could add to get users to check the file. Today both good files and bad files end up in the same category because some users add a mtc even if the file is not ok.
So I think we should 1) remove the templates, 2) make them invisible or 3) change it to a "Please help review the file" (yellow background).
We should create a new template and a review script just like on the NowCommons template where you can mark the file as reviewed (green background + "This file was marked as eligible for transfer to Commons by User:MGA73) or failed (red background). We will soon learn if reviewers are good or if they make (too) many mistakes. And sorting the files in categories per reviewer would help.
Another option is to choose 1.000 files and add a special template to mark them with a "Please help to check and move this file to Commons - batch 1" and then we could see how long it would take us to work on all those files. When they are done we could tag 1.000 more (batch 2) etc. I think working on a category with 1.000 files is more fun than working on one with 300.000 files. --MGA73 (talk) 12:36, 1 February 2012 (UTC)Reply
That means we need 3 categories (+ relevant sub categories):
Files in the last category should be marked with a Puf, a Ffd etc. or the license should be changed. --MGA73 (talk) 12:45, 1 February 2012 (UTC)Reply
"One to add when the file has been checked and found ok by a (trusted) user" checking whatever user X is trusted is useless overhead Bulwersator (talk) 12:55, 1 February 2012 (UTC)Reply
I think that it is bad to have a lot of templates.
"Reviewed and found eligible": waste of time. It is more practical if trusted users move the files to Commons directly instead. The users will handle fewer images because of the extra time it takes, but it is better if images are transferred properly instead of being transferred improperly (as is often the case).
"Reviewed and found ineligible": unless they have {{non-free image}}, {{PD-US-1923-abroad}} or similar, they should probably be reported for deletion (PUF, no source et cetera). Clicking on a few buttons in Twinkle to add those templates would take about as much time as adding a "found ineligible" template, but the result would be better.
Bot tagging: useful since it can exclude problem tags. For example, {{PD-US-1923-abroad}} puts the image in Category:All free media, but the image is not necessarily free in the source country, making it ineligible for Commons.
I think that a bot should mark the remaining eligible files, but it doesn't matter if it is done now or later since there already are so many tagged files to move anyway.
I think that a more urgent task is to run a bot which tags {{ShadowsCommons}} since that is a more serious problem. In many cases, the problem is that someone has moved a thumbnail to Commons without tagging as {{NowCommons}} or that a file has been moved without {{NowCommons}} and then updated at either Wikipedia or Commons. Regardless of the reason, it is useful to identify all problem cases so that they can be sorted out. --Stefan2 (talk) 14:20, 1 February 2012 (UTC)Reply
And {{ShadowsCommons}} should be removed from files tagged as {{NowCommons}} with the same name Bulwersator (talk) 14:36, 1 February 2012 (UTC)Reply
Interesting observation which I wasn't going to bring up but might as well do now: The people that do good transfers, that know what they're doing, and that can be trusted to make correct judgements on files, they don't need the drives, they do transfers in small numbers on a regular basis. Part of the problem with the drives is that they bring in a lot of people that have never done transfers before and might not even be at all familiar with files or file copyright. Yes, some of them do good work, but many of them don't. The only reason that I support the idea of the drives in the first place is that the backlog is just too massive, and grows too fast, for anything else to work. Sven Manguard Wha? 15:29, 1 February 2012 (UTC)Reply
Note that it is more efficient to educate during drive (people want barnstars :) ) and it is possible to find new filemovers. I am completely uninterested in awards but I joined drive due to reviewing. It may be also a good idea to create place where somebody may request review of his/her transfers Bulwersator (talk) 15:46, 1 February 2012 (UTC)Reply
I assume that the deletion admins review all images before deleting them, so you would get a review anyway, but you might have to put the images on your watchlist to tell whether they are deleted or whether they get a {{Not moved to Commons}} template. The drives do seem to increase the number of transfers (Category:All Wikipedia files with the same name on Wikimedia Commons is much bigger than usual), but I'm not sure how often the transfers are problematic. --Stefan2 (talk) 16:19, 1 February 2012 (UTC)Reply
Before this drive nobody complained about leaving date field empty Bulwersator (talk) 16:22, 1 February 2012 (UTC)Reply
I'm pretty sure I've always complained about. An incomplete form is an incomplete form. Even a logical guesstimate is better than a blank space. (FTSOD, saying "Photographer not listed" when the photographer isn't listed is also better than leaving the author field blank.) The drive did, however, make the caring more obvious. Sven Manguard Wha? 21:46, 1 February 2012 (UTC)Reply
Maybe a drive to review files before we do a drive to move them. I was already doing my own thing before I came along here I was slowly working my along "All free media" (I'm still only up to "H"...)- see User_talk:Ronhjones/CSD_log/Archive_1, and I didn't view every image, just the ones in the thumbnails that looked like they might be suspect. If we could get enough volunteers maybe take a start letter each, and maybe a new template, with a script to add it!( I've made my own to add "move to commons" in one click).  Ronhjones  (Talk) 22:27, 1 February 2012 (UTC)Reply
Your CSD log makes my CSD log look tiny. Well done sir. I'll add that to the list of things to do when I have time.

Here's another idea. About 50-100 free use files are added each day. It'd be wonderful if we had someone go through the Multichill logs each day, look over the files, and then tag the non-free ones for deletion, notify users if they've given incomplete information, ask users to use Commons in the future, and transfer the free files over. That way we can stop the inflow. We'd work on the things we already have as well, too, of course. Sven Manguard Wha? 22:38, 1 February 2012 (UTC)Reply

I have already been checking User:Multichill/Free uploads every day for a week or two tagging many images. I examine suspicious-looking files in more detail by looking at the file information page and tag as something where appropriate. If the image is unlikely to be problematic, I don't inspect the file information page. It may also be a good idea to look at the raw Special:ListFiles since a lot of unfree media files are uploaded without fair use rationales. I have now also checked the latest daily update. --Stefan2 (talk) 00:20, 2 February 2012 (UTC)Reply
  • A. Best to work with the real backlog. Grondemar 03:39, 2 February 2012 (UTC)Reply
  • A. Its best to see/know the exact size of the humongous backlog that we have.But, I would also support User:MGA73 in his view of creating subcategories related to free and non-free files which would subsequently lead to a modular system of bunching of files.There is another part of the problem that we may be overlooking here.Almost 20 out of 78 participants in this drive moved <15 files.I can't predict the exact problem but I feel its due to the lack of understanding of the complexities of the copyright issue.Yes, it is possible for them to post a question in the talk-page and seek help but for a newcomer it is a overwhelming process.Rather if we subcategorize the files according to their licenses then the process can be streamlined.For example "Atrribution Sharealike License for self/other user uploaded photos", "Copyright pertaining to the images created by the US Govt. employee" etc.In doing so we can create separate guides for moving files in these categories.Like for the "US Govt. owned files" we should have links to the internet which show the usage of the file in a US govt. website (eg link for this file).We can also have coordinators/experts of this particular copyright who would be the go-to guy for any problems related to any problem.A newcomer can choose to move files from one subcategory whose copyright issue he/she can understand.Thus for a particular subcategory the process and guidelines of moving a file will be same.It will lead to faster elimination of non-free files.I might swayed away from addressing the main problem here but I believe these small improvements will go a long way in eliminating the backlog.Vivekananda De--tAlK 05:57, 2 February 2012 (UTC)Reply
  • I really can't see why on earth it should not be relevant if a file has been checked by a trusted user or not. If 100 files have been checked by trusted users I can move them to Commons in perhaps 5 minutes. And I can do it so no information have been lost.
If 100 files have been tagged by a user that has not checked properly I will have to check all files (again) and it will take more than 5 minutes.
It seems to me that "community efford" needs to be discussed. Why "demand" that all users do all steps? If a user does not know how to move files to Commons or do not want to go throug the trouble why should we not welcome their help reviewing files? I think that telling them to "If you do not want to move the file we don't need your help." is a bad idea.
I think it would be much more effective that we work together. Lets asume that User A is an expert in US copyright and can review a file in 30 seconds. User B has to spend 10 minutes to review the file. User A can move a file in 1 minute and User B can move a file in 30 seconds. In 1 hour they can move about 45 files if they check and move files themselves (A moves 40 files and B moves 5). If they work together they can move 120 files (A checks 120 and B moves 120 files). Is that not better???
If User A does not like to move files to Commons then User A will not join the mtc-project. And if User B gets sick of checking licenses because it takes so long time then User B will perhaps leave the mtc-project. So instead of moving 120 files 0 files will be moved.
And yes files that is not eligible should be tagged for deletion (or whatever). But sometimes users just ignore "bad" files instead of fixing the problem. For example if it is a photo of a statue and user is not sure if it is ok or not. Then they do not move it and they do not report it. They ignore it and let another user check. Who knows how many users checks the file before someone moves it or tags it for deletion? My point is that if it is not ok or "most likely not ok" then it should be taken care of. If user wants to fix the problem then fine by me. But unless we fix Twinkle we need two edits to do so. One to remove the "MTC" and one to tag for deletion. My guess is that if it was possible to mark as "not eligible" or "perhaps not eligible" then users would do so instead of ignoring the file.
I agree with Sven Manguard that it would be nice if files on Multichill's lists were checked every day. And if someone has checked the files then it should not take long to move the good files to Commons. So if Multichill added the uploads to separate subpages then the user who checked the files could mark the subpage with "files are checked" and then (s)he or another user could move the good files to Commons. --MGA73 (talk) 19:36, 2 February 2012 (UTC)Reply
And I once more agree with Sven Manguard that it is a problem that some users make bad transfers. I think that it is not transfering files that takes time. It is checking the files before the move. I think it would be better if it was only a small number of users that moved the files. Crappy transfers is probably also the reason why there is a F8 backlog. If all transfers were good then Twinkle could clear the backlog in a few minutes. --MGA73 (talk) 19:40, 2 February 2012 (UTC)Reply
I'm confused - Twinkle does remove the mtc when you add a speedy - check http://en.wikipedia.org/w/index.php?title=File%3AGleed.jpg&action=historysubmit&diff=474110284&oldid=468393446  Ronhjones  (Talk) 01:02, 3 February 2012 (UTC)Reply
Twinkle removes "move to Commons" for me when I add any kind of deletion tag (CSD, XFD, DI). --Stefan2 (talk) 01:15, 3 February 2012 (UTC)Reply
Good. --MGA73 (talk) 12:57, 3 February 2012 (UTC)Reply
Well, since there appears to be consensus for option A, I'll set Fbot loose on the category in a few hours, granted that there are no reasonable objections raised in the next few hours. Then back to my quiet break >.> -FASTILYs (TALK) 02:19, 3 February 2012 (UTC)Reply
Why not add it to the free license templates? Will that not do the same trick? One edit fixes thousand of files. --MGA73 (talk) 12:57, 3 February 2012 (UTC)Reply
A free licence might be combined with an unfree licence. For example, {{PD-old}} might be combined with {{Not-PD-US-URAA}}. If something free is combined with something unfree, images shouldn't have any {{Move to Commons}}. --Stefan2 (talk) 13:22, 3 February 2012 (UTC)Reply
"ad C: wtf, see Template:Do not move to Commons, backlog on Category:All Wikipedia files with the same name on Wikimedia Commons and file may be in All free media and in All non-free media (1692). Moreover file may be nominated for deletion. Bulwersator[odp] (talk) 12:07, 1 February 2012 (UTC)" - my comment on this page Bulwersator (talk) 14:21, 3 February 2012 (UTC)Reply
  • Yes I know that some files may not be eligible for Commons but the goal here seems to be quantity and not qualitiy. So we will have many files in the category that are not really eligible for Commons.
If we asume that 99,5 % of the files with a PD-self etc. are ok for Commons then why change the 99,5 % instead of just adding a "|mtc=no" on the 0,5 %?
And if Twinkle can remove the mtc when a file is nominated for deletion then why should it not be possible to tweak Twinkle to add the "|mtc=no"?
Or even better. When a file is in non-free media we should not use a ordinary free license. We should create a special license to add on for example statues and other copyrighted things. That way it is very simple to avoid that these files get a mtc added. And even better: It is possible too add a "|free_in=2020" if the file gets free in year 2020 and when that time comes the template could change the license from a non-free to a free. --MGA73 (talk) 14:13, 4 February 2012 (UTC)Reply
I don't like that only because I just know that it will be consistently by users that aren't a familiar with file copyright as we are, especially the date param.
The date param idea is a good one though. It should be done in a seperate, optional template though, so that only the users who know what they're doing will ever bother with it. Sven Manguard Wha? 17:08, 4 February 2012 (UTC)Reply
The object of the drive is not quantity, but quality. I've said that already to some transferers. ~~Ebe123~~ → report on my contribs. 00:25, 5 February 2012 (UTC)Reply
The reason I said that the goal was quantity instead of quality was that I suggested that we focused on tagging files that was truely eligible for Commons instead of tagging all files that had a free license. But that was rejected.
"tagging files that was truely eligible for Commons instead of tagging all files that had a free license" - we (=Fbot) are doing it Bulwersator (talk) 18:27, 5 February 2012 (UTC)Reply
Are you saying that all files tagged by Fbot are eligible for Commons? No derivative works tagged for example? No files taken from the Internet tagged with a PD-self? No files tagges with a PD-old without a valid source? --MGA73 (talk) 18:32, 5 February 2012 (UTC)Reply
Of course there is no reliable way to identify all copyvios and it is necessary to check file before transfer. But it is also true for files tagged by humans (files from Category:Copy to Wikimedia Commons ) Bulwersator (talk) 18:38, 5 February 2012 (UTC)Reply
True. And that is why I suggested that we introduced a review system like on Category:Wikipedia files reviewed on Wikimedia Commons. I bet that we will soon find out if some users tag a lot of files as "ok" even if they are unfree. Then we can tell users what to tag and what not to tag and hopefully they will learn. Should a few users never learn then we can add a notice/warning on the top of the users category that files need to be checked carefully before they are moved. And if users like Magog the Ogre marked files as eligible for Commons then I would not worry too much but just move them all. --MGA73 (talk) 18:47, 5 February 2012 (UTC)Reply
With "a million" files in the mtc-category I fear that many users will say "Oh no..." and give up. So I think it would be good to have some sort of focus category with a limited number of files. That could be files in use. Files related to a area (country or type). Files with a special license (example LOC-images). Ramdom images. Images users want to be moved (we could move all files in Category:Copy to Wikimedia Commons to Category:Copy to Wikimedia Commons (bot-assessed)‎) and tell users that if they want the file moved to Commons (and don't know how to do it themself) they can remove "|bot=Fbot" and then a user will move the file as soon as possible. --MGA73 (talk) 18:18, 5 February 2012 (UTC)Reply
We do have Category:Move to Commons Priority Candidates, it only has 140,000 files in it. Sven Manguard Wha? 22:02, 5 February 2012 (UTC)Reply
140.000 files it about 40 % of what is in Category:Copy to Wikimedia Commons (bot-assessed)‎. When I nominated 1.100+ files for deletion in one Ffd there was many users that complained and said it was way to much and when I send 50 files to Puf there was someone who asked me to take a break. I bet if I send 140.000 files to Ffd or Puf there will not be many users who will say "It is only 140.000 files..." :-)
And how many files was moved in the January drive? It was not even close to 140.000 files. If we are lucky it was 14.000 files or less than 10 %. So I still think it would be nice if we had a smaller focus so there is a realistic chance that we can empty the category in a few weeks. --MGA73 (talk) 18:45, 13 February 2012 (UTC)Reply
There was a net decrease of roughly 20,000 freely licensed files during January. Most of that was by transfer, some of that was by deletions, a tiny fraction was by untagging. Sven Manguard Wha? 23:28, 13 February 2012 (UTC)Reply
Better than I thought :-) Any way it seems that most of the users here think the system works ok and no need for adjustments are needed. So lets just end it here and see what happens. --MGA73 (talk) 22:07, 14 February 2012 (UTC)Reply

Log

edit

I boldly broke the log in half so I can save changes in a decent amount of time. cheers --Guerillero | My Talk 03:55, 2 February 2012 (UTC)Reply

I am far to busy to review any more files. --Guerillero | My Talk 23:52, 13 February 2012 (UTC)Reply

Moving and deleting

edit

Hi. I had uploaded this picture in 2007, which was already tagged for moving to Commons. However, I decided to upload a bigger version of the same pic, with better resolution (see here). How do we handle the deletion of the first one? Thief12 (talk) 20:37, 5 February 2012 (UTC)Reply

I deleted it as F8 like we delete other files on Commons. --MGA73 (talk) 21:04, 5 February 2012 (UTC)Reply
Thanks! Thief12 (talk) 22:17, 5 February 2012 (UTC)Reply

March 2012

edit

Images with source in other Wikipedia

edit

If an image was copied from another Wikipedia and then transferred to Commons, it is likely that the attribution is incorrect. Therefore, I suggest checking for duplicates in other Wikipedias. If an image was uploaded there earlier and in en.wikipedia, the local image should be tagged to alert users to transfer to file from its original source to Commons. Is there a bot that is able to do this task?
If this is not feasible, images with interwiki links and/or links to other Wikipedias in the source field might be tagged. --Leyo 15:35, 21 February 2012 (UTC)Reply

How is de:Kategorie:Datei:Identisch mit Kopie in anderem Projekt generated? Is there a bot which could be copied from German Wikipedia? It may also be an idea to move images currently listed in the German category. --Stefan2 (talk) 16:24, 21 February 2012 (UTC)Reply
There is no bot. This was a one-time action by a user. --Leyo 17:38, 21 February 2012 (UTC)Reply
I see. It would still be a good idea to fix the English/German dupes in those categories, though. But the main question remains. --Stefan2 (talk) 23:22, 21 February 2012 (UTC)Reply
I agree. These 502 files need to be transferred from en.wikipedia to Commons, whereas those 256 files should be transferred from de.wikipedia to Commons. Of course, it has to be verified if a file is eligible to be transferred at all. Me and other users have already handled many files. --Leyo 00:41, 22 February 2012 (UTC)Reply

Keep local once more

edit

Files with a {{Keep local}} keeps showing up here. This time I have a suggestion how to get them "away" from the categories we try to empty. You can comment on Category_talk:User-created_public_domain_images#Keep_local_files. --MGA73 (talk) 11:08, 23 February 2012 (UTC)Reply

Lets get users to upload free files to Commons

edit

The new Wikipedia:File Upload Wizard is being implemented. I suggest that everyone has a look and give their comments on how we can improve it to get more users to upload free files to Commons. --MGA73 (talk) 17:53, 24 February 2012 (UTC)Reply

Another idea to involve more users

edit

I think that perhaps users do not move files to Commons because it is "so hard" to get the tools working. So what if we did a little test and moved 1.000 files to Commons without checking if they are ok (other than they have a free license). Then users can join the project by checking the file is eligible for Commons:

  • If eligible they click bot-check on Commons, fix description, categories, whatever. Mark the file as reviewed on en-wiki.
  • If not eligible they add a speedy on Commons, fix the license on en-wiki or send it to puf/ffd.

That way they do not have to worry about using tools to move files.

We could ofcourse make it easier by selecting files with only one file in upload history so they do not have to worry about if older versions should be moved. We could also choose files with a PD-self or so they do not have to worry about GFDL license migration etc.

We would perhaps need a template to add on en-wiki to inform users and admins that the file is a part of the mtc drive and that they should not delete before file is checked. --MGA73 (talk) 10:38, 26 February 2012 (UTC)Reply

Will do. ~~Ebe123~~ → report 12:27, 26 February 2012 (UTC)Reply
I meant a new template telling that the file was moved without checking at all and not just a change of the NowCommons template :-D --MGA73 (talk) 10:33, 27 February 2012 (UTC)Reply
Well, I've done this at {{Now Commons (MtC drive)}}. ~~Ebe123~~ → report 00:11, 28 February 2012 (UTC)Reply
Thanks a million. I added some text and started a talk page with a little info. I think we need a link to a help page somewhere because these files may be checked by users that are not experts. --MGA73 (talk) 08:49, 28 February 2012 (UTC)Reply
  • Maybe we can change rules a bit to count files
    • Transferred in a correct way, file is on commons without cleanup templates on commons like BotMoveToCommons
    • Transfer from Category:Files moved from en.wikipedia to Commons requiring review was cleaned and BotMoveToCommons template was removed. This way it is not necessary to make mass blind move (that will certainly will include moving copyvios to commons), enwiki related backlog on commons will be reduced, may reduce number of "was moved to commons in a wrong way and deleted". Downside is that it will decrease backlog on commons rather on enwiki (but I think that it is not very important)
  • Bulwersator (talk) 10:24, 28 February 2012 (UTC)Reply
It would be very nice if BotMoveToCommons-files was checked but the problem with many of the "old" files on Commons is that the version on en-wiki is allready deleted so it is hard for non-admins to do something about those files.
But I see no reason why we can't do both things (or ten things). As long as there is not an unacceptable number of bad files moved. --MGA73 (talk) 11:32, 28 February 2012 (UTC)Reply
So we may link to backlog from 2012 Bulwersator (talk) 14:18, 28 February 2012 (UTC)Reply
Yep could do. There is a risk that user X moves a file to Commons and user Y removes the BotMoveToCommons template before user X does but I doubt we risk big fights if that should happen. So go ahead :-) --MGA73 (talk) 18:43, 28 February 2012 (UTC)Reply
In order to avoid problems where two different users clean up the same file concurrently, I suggest that we recommend people not to clean up files until at least an hour after the move. That would give the movers some time to do the cleanup. --Stefan2 (talk) 19:16, 28 February 2012 (UTC)Reply

I created Category:Wikipedia files on Wikimedia Commons - MtC drive unchecked file and put 10 random files in it. I picked some from Category:Move to Commons Priority Candidates. That way we can see if template works and we have a few files "to play with". --MGA73 (talk) 22:45, 28 February 2012 (UTC)Reply

And I now deleted / fixed the files I moved as a test. Template is no longer used... Project has been terminated. --MGA73 (talk) 20:28, 3 March 2012 (UTC)Reply

"The overall goal" category includes only human-tagged files, promoting moving files from this category may be a bad idea as it will encourage useless manual tagging of files with "move to commons" template Bulwersator (talk) 22:56, 26 February 2012 (UTC)Reply

I agree. Let's drop that goal altogether and make the "priority candidate" one the main goal. --Stefan2 (talk) 23:05, 26 February 2012 (UTC)Reply
I removed human-tagged files and moved "priority candidates" to top. Bulwersator (talk) 06:19, 27 February 2012 (UTC)Reply
I re-added Copy To Wikimedia Commons as it is a part too and I think we could eliminate the category in March. ~~Ebe123~~ → report 01:52, 29 February 2012 (UTC)Reply
Human added files may be added because someone thinks that it is important that the file is moved to Commons and others may be added "bot like" without thinking. So I suggest that we 1) change all excisting human tagged templates to "bot=human" (name indicate that it was originally tagged by a human) to get the files away from this category and into the same category as all the bot tagged files 2) add a notice on the template that if you want to request a file to be moved to commons then you remove the "bot=xxx" from the code. After that only files with high priority would end up in the category. --MGA73 (talk) 08:44, 29 February 2012 (UTC)Reply

reviewing

edit

I would do an extreme review instead of moving any images. The last drive showed me that I don't want to move any images any longer (independent of drives). Regards, mabdul 09:37, 29 February 2012 (UTC)Reply

There is still a batch of images that need to be reviewed --Guerillero | My Talk 00:16, 1 March 2012 (UTC)Reply

Next drive

edit

Hi, so about FtCG, please download the file for the MtC drive on atlight.github.com. About CommonsHelper, the tag will be replaced soon. So uploads on other wikis will not count, as we are in the 300,000 files. I think that we will be able to break down the 10,000 files, and eliminating the old Copy to Wikimedia Commons category. ~~Ebe123~~ → report 11:43, 29 February 2012 (UTC)Reply

So I just got a note about this new drive and I wondered what happened with the closing of the previous one. What's the status of that one? Multichill (talk) 12:07, 29 February 2012 (UTC)Reply
Someone moved so many files that they did not manage to review them before the next one started... ;-) --MGA73 (talk) 18:39, 29 February 2012 (UTC)Reply
That was one raeson for no mass-uploaders, but I will be saying that a lot of your images will be rejected, as you did not remove BotMoveToCommons before the end of the crime. ~~Ebe123~~ → report 20:30, 29 February 2012 (UTC)Reply
You guys are pathetic. I'm sorry I wasted time on this project. Multichill (talk) 20:53, 29 February 2012 (UTC)Reply
Sorry for the typo, I meant "drive". ~~Ebe123~~ → report 00:10, 1 March 2012 (UTC)Reply
Seriously Ebe123? Fantastic job there. If this is how you're going to run the drive, I'm not going to help you run people away. Sven Manguard Wha? 02:23, 1 March 2012 (UTC)Reply

Reboot the drive?

edit

While it was most certainly not my intention (all I wanted was for him to apologize to Multichill), Ebe123 has resigned from this drive and has stated his intention not to run future drives. That leaves this drive up in limbo.

It is clear to me that the organizational aspects of the drive, doing reviews, tracking moves, awarding barnstars, even menotring new transferers, were failing even before this. With Ebe123 gone, I don't think it's likely that this situation will do anything but deteriorate.

Therefore I am proposing that we reorganize this drive into a much more casual affair. I propose the following:

  • The drive be made into a perpetual drive, much like WP:GBD has become. This would mean that instead of monthly organizational pages, there would be one organizational page. There would be one sign up sheet, which doesn't expire. It will include a separate section for people willing to offer advice, much like the first drive back in late 2011 had.
  • Under the new drive, reporting your transfers will be optional. People that choose to record their transfers, either using the FTCG recorder or by hand, will create a subpage in their userspace to publish their records. They will then link to those subpages on the Users that don't wish to log won't have to.
    • Rather than awarding barnstars on a monthly basis, they will be cumulative. At say 50, 100, 250, 500, 1000, etc. transfers a different barnstar is awarded. It can be awarded by anyone. Obviously, since only people who log their transfers would get milestone based barnstars (otherwise how would we know), but that dosen't stop people from handing them out on their own anyways to whomever they want.
    • The leaderboard would be opt-in only. If you want to add yourself, you can do so. It'll have a slot for them to indicate when they started.
      • Both of these above changes are based on the observation that some people stopped doing transferrs because they thought they'd never catch up with the leaderboard toppers; making it informal and opt-in and milestone based is designed to stave off the discouragement factor.
  • There will be no formal reviewers/reviewing under this system, because reviewing just didn't get done in a reasonable amount of time before. This dosen't stop people from checking on how others are doing, it just deinstitutionalizes the process.
  • The most important thing is that the transfers are done right (right being defined as all of the sourcing/authorship/descriptive information makes the transfer, and that the transferred file is allowable on Commons). What format this is done in, whether it's by human or by bot, and what tools are used doesn't matter.
  • The drive will have no formal leadership. I will help set it up, but I neither want nor have the energy to try and keep control over it.

Thoughts? Sven Manguard Wha? 20:11, 2 March 2012 (UTC)Reply

What exactly happened here? Is what was posted above the full issue or is there more to it than that? As someone who very much enjoyed moving files during the last drive, I am very disappointed to discover this right before I was going to start on this drive. This is especially bad happening right at the start of a drive, after a massive talk page mailing, when the cleanup for the last drive still isn't complete.
I really don't think that the right time to be discussing changes to any drive is in the middle of it. We should either continue this drive per what was set up before we started, or else close it. If we do decide to close the March drive, we should decide quickly so that editors don't feel that their time is wasted and elect not to participate in future drives from this project.
Also, we really need to come up with a plan to finish the review of the January drive. It is not acceptable to draw off editor resources with promises of rewards only to never provide them. Grondemar 00:54, 4 March 2012 (UTC)Reply

Best as I can tell, the sequance of events was as follows:

  1. Multichill asks what happened to the closing of the January drive.
  2. Ebe123 states that many of Multichill's transfers will be rejected because they still had the BotMoveToCommons template on their Commons page.
  3. Multichill leaves the drives, obsensibally over that comment.
  4. I publicly withdraw from the drives until Ebe123 rectifies the situation with Multichill.
  5. Ebe123 leaves the drives, rather than try to rectify the situation with Multichill.
  6. I post the above thread.

The reason I posted the above thread is that with no one doing any of the back end stuff for the January and with Ebe123 gone, it's clear that the back end stuff isn't working. My model is one that doesn't need the extensive back end that these drives do.

If you think it's best to close out the drives, go ahead and do that. In about three hours I go on Wikibreak, and I honestly have no idea when or in what capacity I'm coming back from that Wikibreak in. I can almost gaurentee now though that if the structure of the drives remains the same, I'm not going to have any part in them.

One final note, and then I really am done with the issue until at the very least when I come back from Wikibreak: You do not need drives, or drive based incentives, or logging, or reviewing, or any of this to do transfers. If the drives collapse, but you enjoy doing transfers, do them anyways. Sven Manguard Wha? 02:09, 4 March 2012 (UTC)Reply

File:Gamhar.jpg

edit

Does anyone know why CommonsHelper is unable to move this file to Commons? --Leyo 08:43, 23 March 2012 (UTC)Reply

Security reasons: the Commons Helpers (and many other file uploading tools) upload images in an insecure way which has been blocked. See Commons:COM:AN#CommonsHelper blocked?. --Stefan2 (talk) 12:39, 23 March 2012 (UTC)Reply
Thanks. I found it (rev:114429) out in the meantime, too. Let's hope, Magnus is able to fix it soon. --Leyo 14:17, 23 March 2012 (UTC)Reply
The original CommonsHelper has just been fixed. I don't know the status of the wmflabs version. --Leyo 17:29, 24 March 2012 (UTC)Reply

June 2012

edit

Future drives?

edit

According to the leaderboard about 200 files was moved as a part of this drive.

The rest of the progress of 5.000 file drop in Category:Copy to Wikimedia Commons (bot-assessed) was either deletions of files or moves made by users not a part of the drive or just moves not added on the leaderboard yet.

So perhaps we should ask some of the users that move files to Commons why they do not do it as a part of the drive. That could give information what to do involve more users.

We could also ask if they have any suggestions to make it easier to move files. --MGA73 (talk) 18:20, 1 April 2012 (UTC)Reply

I have moved a few files from Wikipedia to Commons during the past month, but I chose not to list any of them because of the this and this. From what I've understood, some other users made the same decision. --Stefan2 (talk) 21:03, 1 April 2012 (UTC)Reply
Yes that is probably one of the reasons. And now we are in april and january drive is not yet awarded.
I suggest that we stop counting and looking for all details. Multichill is in a category of his own. I think we should give him the biggest award we can find and. As for the rest of the users on the leaderbord probably I think that they also removed the botchecktemplate and cleaned up on Commons. It should be enough to check a few files from each user and if the first 20 checked files are ok then the rest is proably also ok. Then we should just give them an award matching what they listed on the leaderboard. If one or more files are not ok then we check 10-20 more and if they are all ok we give them an award etc. So only if a user made many bad transfers we should reduce the number listed on the leaderboard.
I suggest we do the same with april. We check a few and if they are ok we give an award. If not we check a few more etc.
Lets not waste weeks and months checking and counting. --MGA73 (talk) 12:02, 2 April 2012 (UTC)Reply
Yes, let's check 10 or 20 random files per user and assume that everything is fine if those 10 or 20 files are fine. If someone's list contains lots of red links, this would be an indication of errors. --Stefan2 (talk) 13:16, 2 April 2012 (UTC)Reply
I started working on Wikipedia:WikiProject Images and Media/Commons/Drives/Jan 2012/Logs/A-J and Wikipedia:WikiProject Images and Media/Commons/Drives/Jan 2012/Logs/K-Z. --MGA73 (talk) 17:52, 13 April 2012 (UTC)Reply
See #January drive awards below. --MGA73 (talk) 19:34, 15 April 2012 (UTC)Reply
I expect a lot of the reduction in the bot-assessed category has been caused by myself and many others working through Category:Wikipedia orphaned files, moving some to Commons and nominating many more for deletion. Cloudbound (talk) 20:10, 13 April 2012 (UTC)Reply
And getting junk deleted is just as good as getting files moved to Commons. But the way the system is now only transferred files count :-( --MGA73 (talk) 21:08, 13 April 2012 (UTC)Reply

January drive awards

edit

As listed above in #Future drives? I think we should give out the awards soon. I suggested barnstars on Wikipedia:WikiProject Images and Media/Commons/Drives/Jan 2012/Logs/A-J and Wikipedia:WikiProject Images and Media/Commons/Drives/Jan 2012/Logs/K-Z. I hope someone will help check the work I made on the 2 links above.

I suggest to award Order of the Superior Scribe of Wikipedia to Multichill for most transfers and to Bidgee for most transfers that was also also checked on Commons. The rest of the users on the leaderboard should have the Transfer to Commons Drive Leaderboard Barnstar.

I know it is not 100 % as originally planned but who says that the original plan is the only way to do it? And as you can read above not all are happy how it turned out.

I would really appriciate if someone could say "Yes I agree" so we can give the awards or if not then come with a suggestion what else to do. --MGA73 (talk) 19:34, 15 April 2012 (UTC)Reply

I agree that the awards should be given out, just as a thank you for helping. Thanks MGA73 for checking through all the uploads, not an easy task I'd expect. Perhaps all those who took part and successfully transferred at least one file could receive something like the Modest Barnstar? Cloudbound (talk) 20:12, 15 April 2012 (UTC)Reply
I did not check ALL uploads. I checked a sample of uploads to see how uploader cleaned up correctly after the transfer. In many cases other users had checked some of the files and in these cases I checked very few files. The users that moved more than 25 files generally did an ok job. Yes, sometimes things could have been better. And a few users (like Multichill) did not clean up after the transfer. I have also deleted thousand of files per F8 so I know many of the top file movers allready.
Ofcourse it takes more time to transfer files if you check all files carefully but even if users do not remove the bot check template it is still helpfull as long as they do not mass transfer copyvios. I have cleaned up thousand of files with my bot removing junk templates etc. And if deletings admins do a good job they check for copyvios before they delete. So I expect most of the files transferred to Commons are ok for Commons. What we still need are categories.
It would be ok to me if all users that participated got a small barnstar. --MGA73 (talk) 20:54, 15 April 2012 (UTC)Reply
It seems reasonable to divide by two if files were not properly cleaned up. I have checked your summaries for all users and confirmed that they correspond to the barnstars listed here. In some cases, you proposed a barnstar which formally would require a few more moves, but I guess it is fine in those cases. I suggest distribution of barnstars per your suggestion. People who do at least transfer free images and with an upload history are definitely preferable to people who transfer a thumbnail of an image under the wrong licence without crediting the original uploader or adding {{NowCommons}}, and I've found plenty of those improper transfers lately. It takes too much time to clean them up. --Stefan2 (talk) 14:36, 16 April 2012 (UTC)Reply
Yes. We should probably make sure that users that move less than 25 images do not have 100 % bad transfers before we give them a barnstar :-) --MGA73 (talk) 16:23, 16 April 2012 (UTC)Reply
  • Reviewer's Comment I gave up reviewing after a while. There was too big of a backlog for one person. All but two people did their transfers correctly from the reviews I did. I feel that it is safe to give out the stars. --Guerillero | My Talk 15:21, 17 April 2012 (UTC)Reply
Any objections to me awarding barnstars based on MGA73's assessments? Cloudbound (talk) 21:10, 26 April 2012 (UTC)Reply
No objections from me, with one exception: someone else should give you your own barnstar. --Stefan2 (talk) 21:54, 26 April 2012 (UTC)Reply
That goes without saying. Cloudbound (talk) 18:38, 27 April 2012 (UTC)Reply
I just awarded Cloudbound the The Commons Ambassador Barnstar. Please feel free to award the rest of the awards. --MGA73 (talk) 19:17, 27 April 2012 (UTC)Reply
Thanks MGA73. I've awarded the rest. Cloudbound (talk) 20:09, 27 April 2012 (UTC)Reply
Cool. Now the barnstars are out. What about the leaderboard awards? --MGA73 (talk) 08:15, 28 April 2012 (UTC)Reply
If you're happy with the standings as they are, I could award them too. Cloudbound (talk) 22:14, 28 April 2012 (UTC)Reply
The first place award is trivial: no one transferred nearly as many files as Multichill. Some users were to get reduced numbers, sometimes by dividing by two. Does this affect the leaderboard? --Stefan2 (talk) 23:06, 28 April 2012 (UTC)Reply
I suggested that Multichill get the first place for most files "moved" and Bidgee get the first place for most files "moved and checked". --MGA73 (talk) 14:29, 29 April 2012 (UTC)Reply
I just checked the leaderbord and the number of files uploaded. If we say that a file moved but not checked only count as ½ then Cloudbound would go out and ~~Ebe123~~ enter the leaderboard. So I would suggest that we award the 10 on the leaderboard + ~~Ebe123~~ --MGA73 (talk) 15:57, 29 April 2012 (UTC)Reply
I think I'll leave it for you all to decide for this. Cloudbound (talk) 18:28, 29 April 2012 (UTC)Reply
I think you deserve your Leaderbord Barnstar so I gave you one. Let's just award some more :-) --MGA73 (talk) 19:27, 29 April 2012 (UTC)Reply
Thanks. I thought I'd wait until everyone was sure about what to do, but if you like, I could award the rest? Cloudbound (talk) 19:29, 29 April 2012 (UTC)Reply
Discussion has been open for 2 weeks and no big "Stop wait..." so just go ahead :-) --MGA73 (talk) 19:36, 29 April 2012 (UTC)Reply
All done. Now for the next drive... Cloudbound (talk) 21:43, 29 April 2012 (UTC)Reply

Lists of free files updated again

edit

Hi. If any of you were using User:Multichill/top self uploaders or User:Multichill/Free uploads then have a look. They have been updated :-) Plenty of free files to move. Or copyvios to tag for deletion depending on how good the uploader knows copyright. --MGA73 (talk) 20:49, 29 April 2012 (UTC)Reply

Yes, wonderful! --Stefan2 (talk) 15:58, 1 May 2012 (UTC)Reply

Orphan files

edit

Perhaps the focus of another drive could be Category:Wikipedia orphaned files? At present there are 114,200 files - a collection of useful forgotten files, copyright violations and almost unuseable content. Sorting through it would be beneficial not just here but to the other language Wikipedias as well. Cloudbound (talk) 00:00, 12 May 2012 (UTC)Reply

Very good idea :-) On Commons I made a query for all files that had a specific "text" in the file name. If someone for example would like to work on trains then we could make a list of all files with "train" or "locomo" in the file name. Example of a list with specific words in the file name can be found here. The list can be improved. For example if we exclude files with the word training and we could also add words like rail etc. --MGA73 (talk) 13:11, 12 May 2012 (UTC)Reply
Oh... I forgot to fix the query only to work on orphan files but you'll get the idea :-D --MGA73 (talk) 13:13, 12 May 2012 (UTC)Reply
I'm just wondering if it wouldn't be better to focus on files which are currently in use. I've looked at files shadowing Commons lately, and I've found that in many cases the error is that someone has moved a file improperly, requiring users to spend a lot of time on correcting the errors. I would say that it takes more time to clean up after an incorrect move than to move a file myself, so I think that it would be better to start with files which are likely to attract users who might do an improper move in order to avoid such improper moves (and thereby save us some time when cleaning up files). Maybe start with heavily used files instead? --Stefan2 (talk) 13:45, 12 May 2012 (UTC)Reply
I think the best is to work on what you want to work on. If we decide that next drive is about X and you feel that something else was better then you will probably not work as much on the drive as you would if you thought it was a brilliant idea.
If we worked on all new files and checked source, author, license, description etc. and tagged all the files with problems and moved the good ones then there would be a good chance that uploader was still active to fix any problems and if we informed the uploader about Commons we might be able to persuade some uploaders to use Commons in the future. But like any other ideas is only good if we get enough users to work on it :-) --MGA73 (talk) 18:23, 12 May 2012 (UTC)Reply

CommonsHelper has been improved

edit

Hi! For those of you that uses CommonsHelper or helps check files that others have moved to Commons I can inform you that CH has been fixed so now it should add much less junk. It should no longer add templates like {{FULLROOTPAGENAME}}, {{Hidden}}, {{Max}}, {{Ns has subpages}}, {{Red}} and {{Template other}} etc... If you notice any problems or have ideas for other junk that could be avoided please tell so User:Magnus Manske can fix it. --MGA73 (talk) 05:55, 16 May 2012 (UTC)Reply

Orphan images

edit

We have 113,333 orphan/unused files in Category:Wikipedia orphaned files. Some are no longer usable, some are copyvios, some are "hidden treasures" and some could be usable if they get a better description.

I was thinking that perhaps it was a good idea to ask the uploaders of the files to have a look (with a bot). We could ask them something like:

"Hi! One or more of the files you uploaded are not in use. It would be a big help if you would have a look at the files to see if they are still usable.

  • If the file is no longer usable please nominate it for deletion with {{db-author}}.
  • If the file is usable please:
    • check and fix the description (remember to use links [[ ]] if possible)
    • check the source (if you are the photographer/creator please add "I took this photo" or similar and if you are not the photographer/creator please make sure there is a link to the webpage or another good source)
    • add the file to an article

Remember if the file can't be used on English Wikipedia it may still be usable elsewhere if the file is moved to Wikimedia Commons.

A list of the files can be seen below [list of the files]"

What do you think? --MGA73 (talk) 18:07, 5 June 2012 (UTC)Reply

Good idea.
What about adding a link to //toolserver.org/~revolus/afterUpload/?project=en.wikipedia.org&image=NAMEOFIMAGE to each image in the list in order to facilitate finding out the article(s) an image was used in past? --Leyo 19:25, 5 June 2012 (UTC)Reply
Hey that was a cool tip :-) --MGA73 (talk) 20:12, 5 June 2012 (UTC)Reply

Example of links:

--MGA73 (talk) 20:33, 5 June 2012 (UTC)Reply

Yes, it would be very practical to add a link to the Toolserver tool to {{orphan image}} so that articles can be located. Otherwise, it is often very hard to write a description for images. --Stefan2 (talk) 22:54, 6 June 2012 (UTC)Reply
Yeah adding the link to the template would be much easier than to add it to the lists. It would also save a lot of space. --MGA73 (talk) 06:39, 7 June 2012 (UTC)Reply
Just a note, MGA73 started a discussion about this on the template's talk page: Template talk:Orphan image#Add link to toolserver tool. Fantastic idea! -- ТимофейЛееСуда. 21:05, 7 June 2012 (UTC)Reply

Mark files as reviewed

edit

It has been suggested before but I made a post at Template_talk:Copy_to_Wikimedia_Commons#Make_human_review_possible about a change of the mtc-template so users can choose to mark it as reviewed. If a "good user" marks a file as ok someone can spot it and move it in no time. --MGA73 (talk) 19:46, 28 June 2012 (UTC)Reply

It is now possible to mark files as reviewed. I plan to keep an eye on the category Category:Copy to Wikimedia Commons reviewed by a human so that files that are reviewed are moved fast or "unreviewed" if user made a mistake. I hope users will use this review if the files are moved fast. You are all most welcome to help move the files fast. --MGA73 (talk) 21:48, 30 June 2012 (UTC)Reply