From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search

Domain names and alternatives[edit]

Name Domain Suggested by Comment
NonFreeWiki Green Giant
FairUseWiki TeleComNasSprVen
FairMediaWiki Harrybrowne1986 Potential for confusion with MediaWiki?
CentralWiki Harrybrowne1986 Just like the way we have central wiki login, the same way.
OneWiki Harrybrowne1986
UnCommons GregRundlett and Rich Farmbrough Because it's like Commons but the opposite in legal terms. Their use should be uncommon. / とある白い猫

See also[edit]

People interested[edit]


  1. Green Giant, as proposer.
  2. PC-XT (talk) Centralized attention on fair-use files, with the goal of enforcing the different wikis' policies, within Wikimedia's policies makes sense to me.
  3. This idea has been floated a few times in the past. Thank you for putting a well written proposal together. John Vandenberg (talk) 14:08, 19 March 2014 (UTC)
  4. Strong support.--GZWDer (talk) 13:55, 2 April 2014 (UTC)
  5. Also express strong support for this idea. I think this is a well thought out idea that solves a very real problem. Zellfaze (talk) 18:46, 9 April 2014 (UTC)
  6. Strong support --Pierpao (talk) 17:36, 21 April 2014 (UTC)
  7. Symbol conditional support.svg Conditional support --Ricordisamoa 02:52, 30 April 2014 (UTC)
  8. Same as Ricordisamoa. --The4DGovernment (talk) 02:12, 4 May 2014 (UTC)
  9. Symbol conditional support.svg Conditional support --Harrybrowne1986 (talk) 13:27, 15 May 2014 (UTC)
  10. This is a brilliant idea. As a Thai Wikipedian, I believe that it is very helpful for small and medium-sized wiki projects. We have spent significant amount of time dealing with fair-use image issues. The issues are somewhat redundant and can be avoided by a centralised system. --Taweethaも (talk) 00:09, 3 June 2014 (UTC)
  11. Support Support I think that the idea is effective and efficient. It is a waste of time for Users to re-upload images just because they need to use it on a local wiki. In addition, it will maintain a central place for images and that will help provide many accurate statistics for such class of images and why would users upload them. Asaifm (talk) 14:50, 18 June 2014 (UTC)
  12. Strongly Support Support. --Liuxinyu970226 (talk) 13:04, 19 July 2014 (UTC)
  13. Support Support good idea, it will save many things --Ibrahim.ID (talk) 05:26, 17 August 2014 (UTC)
  14. --John123521 (talk) 15:00, 11 September 2014 (UTC)
  15. I had the same idea. Strong support -Nizil Shah (talk) 20:57, 19 October 2014 (UTC)
  16. I ended up on commons because I wanted a CC-BY-NC icon for OEIS:. And I like Lawrene Lessing's On Free, and the Differences between Culture and Code lecture. –Be..anyone (talk) 05:05, 26 October 2014 (UTC)
  17. Quite. Andreas JN466 12:50, 12 July 2015 (UTC)
  18. Nikki (talk) 09:15, 7 August 2015 (UTC)
  19. Alternate logo proposal
    Support Support I have been arguing about this for a long time, this would bring unfair use issue to a single location. We HAVE TO obey US copyright law and we choose to obey local laws where wikis are more widely used. This is just the existing practice and such a centralized unfree content wiki would eliminate a number of problems. I think files can be migrated to such an non-free content wiki without disrupting existing use. In fact preferably this should be done without re-downloading and re-uploading the files. Now that we have SUL fully integrated, attribution would not be an issue. One question is what would this wiki be called? I would not want to call it uncommons. Such a shift may have positive legal consequences where we can mirror the entire file server on a European country because it is now entirely freely licensed. -- とある白い猫 chi? 12:43, 7 August 2015 (UTC)
    I would oppose the proposed logo as it will be confusing to distinguish commons from the non free content wiki for some people, especially if they are color blind. I would go for File:Red copyright.svg since that will be the only type of content on this wiki. Or it could be something inspired from it. -- とある白い猫 chi? 12:55, 7 August 2015 (UTC)
    The logo is not fixed so this is a good alternative. All I did with the logo was turn the Commons logo upside down and swapped the colours. The transfer to a single wiki could be done by bots, maybe even using an import right. The name also isn't fixed (although I've used NonFreeWiki in the requested demo). I've added the logo and the domains you suggested but feel free to make any changes you think are needed. Green Giant (talk) 13:49, 7 August 2015 (UTC)
    I am not a graphics artist. Perhaps this can be put on Commons:Graphic Lab/Illustration workshop where our more creative and talented users can come up with something? Perhaps we want to focus on WMF colors such as the case with incubator. -- とある白い猫 chi? 15:34, 7 August 2015 (UTC)
  20. General support for the concept. The devil is in the details, but details can be worked out. Before NFW is created, basic policies and procedures should be developed. Then it should be clearly proposed that Commons host this, creating special tagging or classificationt of files. There would then not need to be any interwiki moves from Commons to NFW or vice-versa, it would become a page move (perhaps to a new namespace). Copyright expertise is needed to handle licensing issues, and, for better or worse, that expertise exists on Commons. To preserve local autonomy, any local usage of a file should establish NFW hosting. If that local usage is true copyvio, then, it will be visible and should be handled. The current situation is unsatisfactory. The goal of the WMF policy is that any non-free usages be machine-readably tagged with a rationale, so that commercial re-users are warned. If, however, NFW removes local autonomy as to what files they choose to host, I would be opposed. Local autonomy creates the possibility of conflict with global consensus, yet local autonomy is a very important safeguard. As usual, there are comments that imagine "copyvio" is illegal in the U.S. Not exactly. It depends, and the WMF is not at risk from hosted copyvio, as long as it promptly takes it down under a DMCA request, which it normally does. --Abd (talk) 15:07, 18 August 2015 (UTC)
  21. Support. Reducing the burden on local communities. --minhhuy (talk) 10:18, 4 September 2015 (UTC)


  1. Strong Opppose - Problems block implementation that must be dealt with before this could move forwards: The proposal fails to deal with issues such as en-wiki allowing files that are out of copyright in America, but not on Commons. Implementing this could be disasterous if done without a concrete, coherent proposal for dealing with such issues. It also separates the non-free files from their fair-use content, and makes problems with orphaned fair use much harder to deal with in absence of concrete systems for dealing with such. As well, a good number of supposed "non-free" files, when checked, turn out to be public domain when checked; for example, it's not uncommon for pre-1923 American books and music scores to have first edition covers uploaded under fair use, which is simply wrong. Adam Cuerden (talk) 14:03, 14 August 2015 (UTC)
    I'm not seeing the objection as being to the concept of NFW, rather as being a concern about implementation details, and I'm not getting that Adam Cuerden understands the proposal. "Fair Use" is one example of Non-free content, not something clearly separate. Under WMF policy, fair use is actually required for NC licensed material to be hosted; however, NFW would classify such files to keep the issue distinct; and thus NFW would become a source for finding NC files for NC users. Two birds with one stone. "Orphaned fair use" is an oxymoron, it is not fair use if not used. However, I would suggest that instead of deleting orphaned files, they be replaced with thumbnails, if they are not already thumbnails. I.e., what Google search does: display thumbnails for file identification, then show links to pages where the files are hosted. Generally, license information provided should not be deleted unless clearly fraudulent, and it is arguable that even that should not be deleted, merely annotated and hidden. NFW should be maximally transparent. I see no looming "disaster" here. If a file is legal to host in the U.S., say under fair use, and not legal in another jurisdiction, this "problem" already exists. Local language wikis may decide to follow local law, that is completely up to them. That a file is hosted on NFW does not make its use locally automatically legitimate. It does make it possible. --Abd (talk) 15:16, 18 August 2015 (UTC)
    Files would be restricted in usage unlike commons. Wiki's that choose to use these files must have a compatible local fair use. So for instance German wikipedia will not be able to use these files - be it files fully copyrighted, or only free in the US. -- とある白い猫 chi? 18:24, 2 September 2015 (UTC)

Other comments[edit]