On Commons, {{GFDL|migration=not-eligible}} can be produced by using {{subst:Bild-GFDL-Neu}}.

I sometimes find free files which have been mistagged as unfree on enwiki, mainly textlogos. New text needs to be written for the file information page, but it's often more convenient to only produce a fixed file information page for Commons (and leave the source wiki's text unchanged) than to first clean up the text on enwiki and then clean it up a second time on Commons. Therefore, I'd like if there is a way to upload such files anyway, provided that you edit the text of the file information page.

In T135801, @MZMcBride may have mixed up two different bugs.

Is something being done to fix this? This is a very annoying bug, and it seems to affect a few files everyday. It goes away if you purge the file with forcelinkupdate using the API, or if you edit the page. See for example https://en.wikipedia.org/w/api.php?action=query&pageids=50604305&prop=categories|links|templates|images&format=xml:

<api batchcomplete=""><query><pages><page _idx="50604305" pageid="50604305" ns="6" title="File:Athlone Institute of Technology Logo Circa 2015.png"/></pages></query></api>

No files, no templates, no categories, nothing. But if you check https://en.wikipedia.org/wiki/File:Athlone_Institute_of_Technology_Logo_Circa_2015.png, you can see that the file has two templates, "Non-free use rationale 2" and "Non-free logo" (which in turn call a few other templates), four categories (added by the templates), two images (added by the second template) and one external link.

In T73064#2001109, @Krenair wrote:

• ... now we have two As? The username field is supposed to be unique according to tables.sql.

This may also happen even if you do not implement user renames in Quarry. Consider the following situation:

• A and B both have SUL accounts. A has a Quarry account, but B has no Quarry account.
• A renames to C. C (previously A) remains Quarry user A because Quarry doesn't rename users.
• B renames to A.
• A (previously B) logs in to Quarry for the first time. Since A (previously B) hasn't logged in before, Quarry creates an account for A (previously B) under his current user name, A.

Now there are two "User:A" on Quarry.

Could someone link to some example files? Perhaps there's commonalities that could be identified by looking closer at the file.

I've seen uploads of lots of non-free films and music on Commons. Would it be enough to block film and music uploads through Wikipedia Zero? Or would it be an option to restrict film and music uploads to members of a specific user group? Most files on Commons are pictures, so I don't think that a restriction on film & music uploads would affect a lot of users.

In T124225#1949704, @JEumerus wrote:

If detection of non-free images is a concern, https://en.wikipedia.org/wiki/Category:All_non-free_media is a category that is set up (not sure if required by policy, but in practice always observed to my understanding) to list all non-free media on enwiki.

This is split up in two categories on jawiki: Images containing outdoor artworks and Images in the public domain in Japan but not in the United States. There is a common parent category, Images which can't be used freely, but the images themselves appear in the two subcategories.

In T124225#1956950, @Tgr wrote:

In T124225#1956908, @Deskana wrote:

That's debatable. Using a non-free image as a lead image on an article is perfectly permissible, both in terms of policy and legally.

Legally yes, policy-wise probably no (minimal use).

For example, non-free logos are used as lead images in lots of articles about organisations. This is currently permitted under enwiki's EDP.

In T124225#1984039, @Seraphimblade wrote:

I share the view that this is a cause for concern. On en.wp, the nonfree content criteria are very clear that nonfree images can't be used solely for decoration, and may be displayed only in an article. Not on templates, special pages, interface pages, etc., only in an article.

There are a few exemptions: a few maintenance categories are allowed to contain non-free files without a nogallery tag. For the same reason, it is probably acceptable to show non-free images in Special:ListFiles and Special:NewFiles, but Special:Gather/id/22108/Asterix seems totally unnecessary.

In T120867#1876447, @matmarex wrote:

There were 178 cases where someone had indeed downloaded an image from English Wikipedia and uploaded it right back in via cross-wiki upload to Commons. Note that this is English Wikipedia only (hadn't checked other wikis), and the uploads aren't necessarily copyvios (it just checks for duplicates). Out of 40 000 cross-wiki uploads, probably 10 000 of them deleted, I think this is minuscule.

Users may have uploaded Wikipedia thumbnails too. I have seen cases where users have taken a file from xxwiki and uploaded it for use on yywiki using this tool or other tools.

Suggested solution: Automatically create and attach a local account if an account exists globally when importing pages. This would also have the side-effect that the user's global userpage is displayed on the local wiki, which I suppose is useful.

If the files are reviewed on the server side, then the first edit must also be marked with a special tag which can't be faked. It is possible to fake upload log summaries and file information page content. An alternative solution for the upload wizard is to mark the file as 'unreviewed' and insert a {{flickrreview}} template with no parameters, asking for bot review.

Various common licences state that you must include any copyright notices when using a work.

In T37707#1226959, @Legoktm wrote:

\o/ https://lists.wikimedia.org/pipermail/wikimedia-l/2015-April/077623.html nearly all the renames are done, but this bug should stay open until $wgCentralAuthStrict = true on the cluster.

Note that I didn't search for all pages with this problem, so there may be more pages with the same problem.

Isn't this simply a dupe of T75788?