Last modified: 2014-03-07 11:44:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T46023, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44023 - Wikivoyage should not require GFDL licensing grant
Wikivoyage should not require GFDL licensing grant
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
WikimediaMessages (Other open bugs)
master
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-16 05:51 UTC by Erik Moeller
Modified: 2014-03-07 11:44 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Erik Moeller 2013-01-16 05:51:53 UTC
All Wikivoyage languages currently require the CC-BY-SA/GFDL dual-licensing grant. WMF legal advises that since Wikivoyage incorporates a lot of CC-BY-SA-only material, it would be cleaner to avoid the GFDL dual-licensing. This does not conflict with importing content back into Wikipedia, as importing CC-BY-SA-only content is explicitly permitted under the Terms of Use.

This version of the copyright warning has been vetted by legal:
http://en.wikivoyage.org/w/index.php?title=MediaWiki:Wikimedia-copyrightwarning&oldid=2085117

To consistently implement it across Wikivoyage licenses while leaving other projects unaffected, we may want to add a new wikivoyage-copyrightwarning message to WikimediaMessages and ensure it only gets rendered in place of wikimedia-copyrightwarning on Wikivoyage sites.

Unless legal advises differently, I will leave this as low priority for now since the GFDL grant doesn't seem to be actively harmful (even if it is invalid in many cases).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links