Slashdot Mirror


Wikipedia Moving From GFDL To Creative Commons License

FilterMapReduce writes "The Wikimedia Foundation has resolved to migrate the copyright licensing of all of its wiki projects, including Wikipedia, from the GNU Free Documentation License to the Creative Commons Attribution-Share Alike 3.0 License. The migration is scheduled to be completed on June 15. After the migration, reprints of material from the wikis will no longer require a full copy of the GFDL to be attached, and the attribution rules will require only a link to the wiki page. Also, material submitted after the migration cannot be forked with GFDL "invariant sections," which are impossible to incorporate back into a wiki in most cases. The GFDL version update that made the migration possible and the community vote that informed the decision were previously covered on Slashdot."

32 of 90 comments (clear)

  1. For those playing at home by tepples · · Score: 4, Informative

    Like the GNU Free Documentation License, the Creative Commons Attribution ShareAlike license is a free, copyleft license designed for works other than computer programs. It just lacks some of the practical problems that come with the GNU FDL, which was designed specifically for software manuals that run dozens of pages long. Individual encyclopedia articles are much shorter than that, and the ability to incorporate the license by reference is a better match for Wikimedia Foundation's uses. But the Creative Commons licenses have some of their own practical problems, such as requiring distributors to remove an upstream author's credit upon request.

    1. Re:For those playing at home by buchner.johannes · · Score: 5, Informative

      GNU FDL was chosen as CC was not available at the time. Now CC has additionally become an accepted standard with a lot of material out there. It is great news as this makes it easier to mix content from and to their projects.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    2. Re:For those playing at home by Carnildo · · Score: 4, Informative

      Was it the license that was preventing a downloadable dump of Wikipedia from being distributed on an iPhone?

      No, it's the size. A text dump of the current version of the English Wikipedia (no images, no history) is 45 GB.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    3. Re:For those playing at home by bcrowell · · Score: 5, Insightful

      Wikipedia has a useful FAQ about the relicensing.

      The parent post makes some good points about what was undesirable about the GFDL. In addition, there's the issue of needless proliferation of licenses. What everybody originally intended here was to make a commons that everyone could draw from. If A makes an animation, and B writes a song, and C performs B's song, and A, B, and C all try their best to put their work in the commons, then D should be able to come along and make a video consisting of A's animation with a sound track consisting of C's performance of B's song. There shouldn't be artificial obstacles just because A, B, and C chose different licenses.

      I'm not saying there should only be one free-as-in-speech license for written materials. We do need at least two, because there are real philosophical differences between BSD-style licenses and GPL-style licenses. But there is not a real philosophical difference between the GFDL and CC-BY-SA.

    4. Re:For those playing at home by atomicthumbs · · Score: 4, Informative

      Or 4.7 gigs compressed, if you only download the articles.

      --
      http://pinopsida.com
    5. Re:For those playing at home by tepples · · Score: 2, Informative

      I'm not saying there should only be one free-as-in-speech license for written materials. We do need at least two, because there are real philosophical differences between BSD-style licenses and GPL-style licenses.

      CC-BY and CC-BY-SA appear to nicely fit the roles you mention. But the credit removal requirement in even CC-BY might cause license incompatibility if a free program under a GNU license uses CC-BY images, audio, etc. Or am I misreading the definition of "aggregate" in the GPL?

    6. Re:For those playing at home by BadAnalogyGuy · · Score: 5, Funny

      I only read Wikipedia for the articles.

    7. Re:For those playing at home by Max+Littlemore · · Score: 2, Informative

      Hear hear. Now that this decision has been made, how long until the full transition occurs? It certainly looks like a much better choice. From the *wikipedia page on the Creative Commons licenses:

      "Some within the copyleft movement argue that only the Attribution-ShareAlike license is actually a true copyleft license [24] and that there is no standard of freedom between Creative Commons licenses (as there is, for example, within the free software and open source movements). [25] An effort within the movement to define a standard of freedom has resulted in the Definition of Free Cultural Works.[26] In February 2008, Creative Commons recognized the definition and added an "Approved for Free Cultural Works" badge to its two Creative Commons licenses which comply -- Attribution and Attribution-ShareAlike. "

      So Attribution-ShareAlike is a true copyleft license, but how long until we can reuse bits of wiki without having to include a full license?

      ------

      *The quoted material from wikipedia is reposted under the GNU Free Documentaion License. A full copy of the license is included below to comply with the licensing requirements.

      GNU Free Documentation License
      Version 1.3, 3 November 2008

      Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.

      Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

      0. PREAMBLE
      The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

      This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

      We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

      1. APPLICABILITY AND DEFINITIONS
      This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

      A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

      A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

      The "Invariant Sections" are certain Secondary Section

      --
      I don't therefore I'm not.
    8. Re:For those playing at home by Teancum · · Score: 3, Insightful

      GNU FDL was chosen as CC was not available at the time. Now CC has additionally become an accepted standard with a lot of material out there. It is great news as this makes it easier to mix content from and to their projects.

      While that may have been Jimbo Wales motivation for the GNU FDL, the real truth goes a bit deeper than even that. This is far too simple of an explaination.

      There was another encyclopedia effort called the GNU-pedia being led by none other than Richard Stallman who tried to start an open-source collaboratively written encyclopedia. This was started about the same time that Nupedia was just getting off the ground as well. Nupedia had a slight head-start in terms of getting going a little bit earlier, although the licensing terms for Nupedia were not nailed down as the whole concept of an open-source encyclopedia was still getting established.

      Due to the bureaucratic overhead in Nupedia, a much more free-form wiki-style encyclopedia was created by many of the participants in this early encyclopedia effort, and that became what we know today as Wikipedia. Again, with the already established crowd with ties to GNU projects and committed to the general philosophy of the GPL, the GNU FDL was a natural choice... where that document license was just being released. Having Richard Stallman brow beat Jimmy Wales certainly didn't hurt either, although I don't think it was that hard of a decision to be made at the time.

      BTW, there were other "open source" type licenses at the time besides the GFDL, even if what we know today as the "Creative Commons" suite of licenses didn't really exist in its current form.

      All that has really happened here is the "or later version" clause of the GFDL has been allowed to include a somewhat similar philosophical Creative Commons license as something considered a later version or edition of this particular license. What the Wikimedia Foundation board of trustees has done is to make a political move to explicitly move the content of the Wikimedia projects (not just Wikipedia) to the Creative Commons license explicitly mentioned in that new clause.

      That the WMF board also helped to write that clause of the GFDL due to placing political pressure on Richard Stallman and those involved in the Free Software Foundation sort of brings this thing full circle as well. A lot more is happening here besides "the folks at Wikipedia seeing the light" and suddenly deciding to switch licenses.

      BTW, I do think harmonization of the various free document licenses is on the whole a good thing, and having the weight of the Wikipedia editors and enthusiasts championing a broader license in terms of something used in more documents can only make that resulting license a much more stable license and less likely to be modified to something generally unacceptable to that community.

      Still, to suggest that the GFDL was chosen only because the CC-BY-SA license was not yet written is a gross oversimplification of what really happened and doesn't tell the true story. Those who put reliance on the GPL, however, beware. That license could have the same thing happen in the future, based on whatever whim or political winds happen that can influence the Free Software Foundation.

      The one thing that I do regret never happened is some sort of harmonization between the GPL and GFDL.... primarily in regards to open source textbooks and commentaries on software design. It at least had a shot with the licensing staying within the scope of the Free Software Foundation, but now that the Creative Commons governing body is in charge, it seems like something that will never happen. This is still a problem with the CC-BY-SA license and won't get resolved any time in the near future.

    9. Re:For those playing at home by Teancum · · Score: 4, Informative

      I assume this includes all the talk pages, user profile pages, votes for deletion pages, nerd rage about pictures of a human turd and pages outlining wikipedia policies right?

      This is a fair question, actually, even if it is posed in a rough AC manner.

      The short answer is yes, it includes all of these other pages as well, including stuff subject to deletion and spam put on Wikipedia by vandals.

      That doesn't make goatse.cx now available under the terms of the CC-BY-SA license, but it does make this page available under those terms, and any side commentaries on the topic as well, even if it is otherwise off-topic on other pages of Wikipedia.

    10. Re:For those playing at home by ais523 · · Score: 2, Insightful

      *The quoted material from wikipedia is reposted under the GNU Free Documentaion License. A full copy of the license is included below to comply with the licensing requirements.

      Pretty much a perfect example of what's wrong with the GFDL; although arguably your quote from Wikipedia above was fair use, other legitimate reuses of it might not be. The GFDL was designed for books, where quoting the entire license is no problem; it wasn't designed for Slashdot comments, or newspaper articles, or any of a huge number of other possible situations.

      --
      (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
  2. Might I be the first to say... by Landak · · Score: 4, Interesting

    ...is this the start of the end of the GFDL?

    --
    My UID is prime. Is yours?
    1. Re:Might I be the first to say... by orngjce223 · · Score: 3, Interesting

      Not really, the GFDL is for things that are much longer, and y'know Wikipedia articles really aren't supposed to be very long (the one on the "United States" is about as big as they get).

      Basically, imagine the GFDL tacked onto a five-sentence stub Wikpedia article about a town in France. Then imagine the GFDL tacked onto a hundred-page software manual. It's (proportionally speaking) a pretty big difference, which makes it very practical in the latter case but not in the former.

      --
      Note: I was 13 when I wrote most of this. Take with several grains of salt.
    2. Re:Might I be the first to say... by Kjella · · Score: 2, Informative

      Everything you said is correct except you gave no real reason why the GFDL should continue to exist. You're free to include the full CC license too if you feel like, and if you only did it by reference I doubt many would care. The CCs have pretty much become the standard for any type of free non-code material, and I can't see any good reason why software documentation should need a special license different from any other text.

      --
      Live today, because you never know what tomorrow brings
  3. Okay by Anonymous Coward · · Score: 5, Funny

    I just got off the phone with the big guy, you know, RMS himself. St. Ignacio or whatever.

    And he's fucking pissed.

    He said and I quote, "Looks like these fuckers don't know who they're dealing with. They need to be taught a lesson... freedom ain't free."

    Apparently, he's planning on liberating wikipedia by force.

    1. Re:Okay by David+Gerard · · Score: 5, Informative

      RMS actually thinks it's a good idea :-)

      --
      http://rocknerd.co.uk
    2. Re:Okay by MessedRocker · · Score: 2, Interesting

      The FSF actually got the GFDL changed so that Wikipedia would be able to ditch it.

  4. Re:Just wait by binarylarry · · Score: 3, Funny

    What does Richard Marx have to do with all of this?

    He's the number one selling soul singer songwriter of the 80's!

    --
    Mod me down, my New Earth Global Warmingist friends!
  5. Re:I didn't RTFA by jrumney · · Score: 5, Informative

    Wikipedia is very different from a file upload site like Flickr, in that each page is not the work of one individual, but the combined work of many. Consistent licensing is essential - noone wants to have to check all the licenses of previous edits before they add their own to ensure that no license conflict happens.

  6. Re:I didn't RTFA by Meshach · · Score: 2, Interesting

    Good point. The original license does not account for the fluid nature of articles at wikipedia. From a legal perspective this seems like an improvement (IANAL though).

    --
    "Maybe this world is another planet's hell"
    Aldous Huxley
  7. Re:Wikipedia does something right for a change by FilterMapReduce · · Score: 2, Informative

    Well, the migration couldn't have happened if the FSF didn't sign off on the change; they were the only ones with the authority to make an update to the GFDL allowing it. Although it seems that the FSF's decision came out of a negotiation that took place back in 2007, so perhaps it wasn't really their idea and it was more a matter of bowing to pressure from the masses. Also, I have no idea how RMS personally felt about it.

    I definitely agree that the GFDL was totally unsuitable for Wikipedia.

  8. Re:I didn't RTFA by buchner.johannes · · Score: 4, Insightful

    Is existing GFDL content compatible with the CC licence?

    I think (please correct me) what they did was write a GFDL version compatible with the CC. Then they upgraded the licence of the existing content and thus now they can switch over to CC.

    I'd read the article, but it's slashdotted :-[

    Why can't individual contributors choose their licence like they can with Flickr?

    Wikipedia is not a blog. It would become a format like urbandictionary.com or everything2.com: no rewriting and collaborating on content, rather single statements of various truthiness.

    --
    NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
  9. Re:Freedom Nerds by petrus4 · · Score: 5, Insightful

    It seems to me that the freedom nerds have ended up creating incompatible freedom licenses and have thus shackled themselves in such a way as to prevent them from sucking each other off.

    That's a fairly accurate interpretation, yes. However, the point is that the CC licenses allow for mutual fellatio among a greater and more inclusive cross-section of nerds, while also involving less legal restrictions.

    Some of us tend to view this as an extremely positive and beneficial thing, because after all, when we're talking about mutual oral sex between nerds, what's not to love?

  10. Re:Wikipedia does something right for a change by TheRaven64 · · Score: 3, Informative

    It is slightly chilling for anyone using another FSF license. You can omit the 'or later versions' license and have the possibility that the later versions of other FSF licenses will be incompatible with your version (e.g. LGPLv3 is incompatible with GPLv2; good luck if you were working on a GPLv2-only project that depended on a library that has moved from LGPLv2-or-later to LGPLv3-or-later). Or you can include it and have the possibility that the FSF will decide to grant an exemption for a specific large organisation and allow them to relicense your work.

    --
    I am TheRaven on Soylent News
  11. Re:Wikipedia does something right for a change by David+Gerard · · Score: 2, Informative
    --
    http://rocknerd.co.uk
  12. Re:I didn't RTFA by Carnildo · · Score: 4, Informative

    Is existing GFDL content compatible with the CC licence?

    I think (please correct me) what they did was write a GFDL version compatible with the CC. Then they upgraded the licence of the existing content and thus now they can switch over to CC.

    Close: Wikipedia was licensed under the GFDL version 1.2 or later. What the FSF did was write version 1.3 with a clause saying that any GFDL-licensed wiki (with safeguards to prevent license-washing) could be re-licensed under the Creative Commons Attribution Share-Alike license 3.0.

    --
    "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  13. Re:Tech news? by 93+Escort+Wagon · · Score: 3, Insightful

    How did this minor piece of lawyering end up on a tech news site?

    You mean as compared to the usual game reviews and Apple rumors?

    --
    #DeleteChrome
  14. Re:Wikipedia does something right for a change by Draek · · Score: 2

    If you include the "or later" you're already allowing the license creators (in this case, the FSF) the ability to arbitrarily relicense your work, it's just that in this case the FSF decided the CC group was a trustworthy enough bunch to take care of that one from now on.

    Frankly, I see no reason why you'd trust the FSF but not CC, and if you didn't trust the FSF already you should've left out the "or later" part in the first place. So personally, I see this as nothing more than a convenient opportunity to leave some of the licensing cruft that comes with the GFDL out of Wikipedia et al, and that's a big win for everyone.

    --
    No problem is insoluble in all conceivable circumstances.
  15. Re:Scary power.... by ais523 · · Score: 2, Insightful

    I used to go around and remove content that was cut and copied between pages by non original authors, because it violated the GFDL because the original authors information was not kept in the edit histories, naturally I was banned.

    Why did you not just add the old history to the new history (either by putting it on the talk page with a link in the edit summary, adding it to the edit history, or by asking an admin to merge the histories for you)? You could have made your point, corrected the licensing situation, and not been trollish.

    --
    (1)DOCOMEFROM!2~.2'~#1WHILE:1<-"'?.1$.2'~'"':1/.1$.2'~#0"$#65535'"$"'"'&.1$.2'~'#0$#65535'"$#0'~#32767$#1"
  16. Re:Scary power.... by Chlorine+Trifluoride · · Score: 2, Informative
  17. Re:Scary power.... by Chlorine+Trifluoride · · Score: 2, Funny

    Oh, and [citation needed].

  18. GFDL has invariant sections by tepples · · Score: 2, Informative

    I've been caught in the trap of referencing one license by shorthand when it really is another license that is being discussed

    You mean like the GPL vs. the LGPL?

    Or to put it more bluntly, there is no "Creative Commons license".... there is a whole bunch of 'em and they are mostly incompatible with each other.

    FSF had the same problem with the Open Publication License: the basic license was free, but it allowed option A (no derivatives) and option B (non-commercial), either of which made a work using it non-free.

    At least if you were referencing the GFDL, you knew you were talking about a specific document that was well defined without this sort of ambiguity.

    The GFDL has its own non-free option, and it is called Invariant Sections.