Page protected with pending changes

GNU Free Documentation License

From Wikipedia, the free encyclopedia
  (Redirected from Back-Cover Texts)
Jump to navigation Jump to search
"GFDL" redirects here. For other uses, see GFDL (disambiguation).

GNU Free Documentation License
GFDL Logo.svg
The GFDL logo
AuthorFree Software Foundation
Latest version1.3
PublisherFree Software Foundation, Inc.
PublishedCurrent version:
November 3, 2008
DFSG compatibleYes, with no invariant sections (see below)
FSF approvedYes
GPL compatibleNo
CopyleftYes

The GNU Free Documentation License (GNU FDL or simply GFDL) is a copyleft license for free documentation, designed by the Free Software Foundation (FSF) for the GNU Project. It is similar to the GNU General Public License, giving readers the rights to copy, redistribute, and modify (except for "invariant sections") a work and requires all copies and derivatives to be available under the same license. Copies may also be sold commercially, but, if produced in larger quantities (greater than 100), the original document or source code must be made available to the work's recipient.

The GFDL was designed for manuals, textbooks, other reference and instructional materials, and documentation which often accompanies GNU software. However, it can be used for any text-based work, regardless of subject matter. For example, the free online encyclopedia Wikipedia uses the GFDL[1] (coupled with the Creative Commons Attribution Share-Alike License) for all of its text.

History[edit]

The GFDL was released in draft form for feedback in September 1999.[2] After revisions, version 1.1 was issued in March 2000, version 1.2 in November 2002, and version 1.3 in November 2008. The current state of the license is version 1.3.[3]

The first discussion draft of the GNU Free Documentation License version 2 was released on September 26, 2006, along with a draft of the new GNU Simpler Free Documentation License.

On December 1, 2007, Wikipedia founder Jimmy Wales announced that a long period of discussion and negotiation between and amongst the Free Software Foundation, Creative Commons, the Wikimedia Foundation and others had produced a proposal supported by both the FSF and Creative Commons to modify the Free Documentation License in such a fashion as to allow the possibility for the Wikimedia Foundation to migrate the projects to the similar Creative Commons Attribution Share-Alike (CC BY-SA) license.[4][5] These changes were implemented on version 1.3 of the license, which includes a new provision allowing certain materials released under the license to be used under a Creative Commons Attribution Share-Alike license also.[3]

Conditions[edit]

Material licensed under the current version of the license can be used for any purpose, as long as the use meets certain conditions.

  • All previous authors of the work must be attributed.
  • All changes to the work must be logged.
  • All derivative works must be licensed under the same license.
  • The full text of the license, unmodified invariant sections as defined by the author if any, and any other added warranty disclaimers (such as a general disclaimer alerting readers that the document may not be accurate for example) and copyright notices from previous versions must be maintained.
  • Technical measures such as DRM may not be used to control or obstruct distribution or editing of the document.

Secondary sections[edit]

The license explicitly separates any kind of "Document" from "Secondary Sections", which may not be integrated with the Document, but exist as front-matter materials or appendices. Secondary sections can contain information regarding the author's or publisher's relationship to the subject matter, but not any subject matter itself. While the Document itself is wholly editable, and is essentially covered by a license equivalent to (but mutually incompatible with) the GNU General Public License, some of the secondary sections have various restrictions designed primarily to deal with proper attribution to previous authors.

Specifically, the authors of prior versions have to be acknowledged and certain "invariant sections" specified by the original author and dealing with his or her relationship to the subject matter may not be changed. If the material is modified, its title has to be changed (unless the prior authors give permission to retain the title).

The license also has provisions for the handling of front-cover and back-cover texts of books, as well as for "History", "Acknowledgements", "Dedications" and "Endorsements" sections. These features were added in part to make the license more financially attractive to commercial publishers of software documentation, some of whom were consulted during the drafting of the GFDL.[6][7] "Endorsements" sections are intended to be used in official standard documents, where distribution of modified versions should only be permitted if they are not labeled as that standard any more.[7]

Commercial redistribution[edit]

The GFDL requires the ability to "copy and distribute the Document in any medium, either commercially or noncommercially" and therefore is incompatible with material that excludes commercial re-use. As mentioned above, the GFDL was designed with commercial publishers in mind, as Stallman explained:

The GFDL is meant as a way to enlist commercial publishers in funding free documentation without surrendering any vital liberty. The 'cover text' feature, and certain other aspects of the license that deal with covers, title page, history, and endorsements, are included to make the license appealing to commercial publishers for books whose authors are paid.[6]

Material that restricts commercial re-use is incompatible with the license and cannot be incorporated into the work. However, incorporating such restricted material may be fair use under United States copyright law (or fair dealing in some other countries) and does not need to be licensed to fall within the GFDL if such fair use is covered by all potential subsequent uses. One example of such liberal and commercial fair use is parody.

Compatibility with Creative Commons licensing terms[edit]

Although the two licenses work on similar copyleft principles, the GFDL is not compatible with the Creative Commons Attribution-ShareAlike license.

However, at the request of the Wikimedia Foundation,[3] version 1.3 added a time-limited section allowing specific types of websites using the GFDL to additionally offer their work under the CC BY-SA license. These exemptions allow a GFDL-based collaborative project with multiple authors to transition to the CC BY-SA 3.0 license, without first obtaining the permission of every author, if the work satisfies several conditions:[3]

  • The work must have been produced on a "Massive Multiauthor Collaboration Site" (MMC), such as a public wiki for example.
  • If external content originally published on a MMC is present on the site, the work must have been licensed under Version 1.3 of the GNU FDL, or an earlier version but with the "or any later version" declaration, with no cover texts or invariant sections. If it was not originally published on an MMC, it can only be relicensed if it were added to an MMC before November 1, 2008.

To prevent the clause from being used as a general compatibility measure, the license itself only allowed the change to occur before August 1, 2009. At the release of version 1.3, the FSF stated that all content added before November 1, 2008 to Wikipedia as an example satisfied the conditions. The Wikimedia Foundation itself after a public referendum, invoked this process to dual-license content released under the GFDL under the CC BY-SA license in June 2009, and adopted a foundation-wide attribution policy for the use of content from Wikimedia Foundation projects.[8][9][10]

Enforcement[edit]

There have currently been no cases involving the GFDL in a court of law, although its sister license for software, the GNU General Public License, has been successfully enforced in such a setting.[11] Although the content of Wikipedia has been plagiarized and used in violation of the GFDL by other sites, such as Baidu Baike, no contributors have ever tried to bring an organization to court due to violation of the GFDL. In the case of Baidu, Wikipedia representatives asked the site and its contributors to respect the terms of the licenses and to make proper attributions.[12]

Criticism[edit]

Some critics consider the GFDL a non-free license. Some reasons for this are that the GFDL allows "invariant" text which cannot be modified or removed, and that its prohibition against digital rights management (DRM) systems applies to valid usages, like for "private copies made and not distributed".[13]

Notably, the Debian project,[14] Thomas Bushnell,[15] Nathanael Nerode,[16] and Bruce Perens[17] have raised objections. Bruce Perens saw the GFDL even outside the "Free Software ethos":[17]

"FSF, a Free Software organization, isn't being entirely true to the Free Software ethos while it is promoting a license that allows invariant sections to be applied to anything but the license text and attribution. [...] the GFDL isn't consistent with the ethos that FSF has promoted for 19 years."

In 2006, Debian developers voted to consider works licensed under the GFDL to comply with their Debian Free Software Guidelines provided the invariant section clauses are not used.[18] The results was GFDL without invariant sections is DFSG compliant.[18] However, their resolution stated that even without invariant sections, GFDL-licensed software documentation "is still not free of trouble", namely because of its incompatibility with the major free software licenses.[18]

Those opposed to the GFDL have recommended the use of alternative licenses such as the BSD License or the GNU GPL.[18]

The FLOSS Manuals foundation, an organization devoted to creating manuals for free software, decided to eschew the GFDL in favor of the GPL for its texts in 2007, citing the incompatibility between the two, difficulties in implementing the GFDL, and the fact that the GFDL "does not allow for easy duplication and modification", especially for digital documentation.[19]

DRM clause[edit]

The GNU FDL contains the statement:

You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute.

A criticism of this language is that it is too broad, because it applies to private copies made but not distributed. This means that a licensee is not allowed to save document copies "made" in a proprietary file format or using encryption.

In 2003, Richard Stallman said about the above sentence on the debian-legal mailing list:[20]

This means that you cannot publish them under DRM systems to restrict the possessors of the copies. It isn't supposed to refer to use of encryption or file access control on your own copy. I will talk with our lawyer and see if that sentence needs to be clarified.

Invariant sections[edit]

A GNU FDL work can quickly be encumbered because a new, different title must be given and a list of previous titles must be kept. This could lead to the situation where there are a whole series of title pages, and dedications, in each and every copy of the book if it has a long lineage. These pages cannot be removed until the work enters the public domain after copyright expires.

Richard Stallman said about invariant sections on the debian-legal mailing list:[21]

The goal of invariant sections, ever since the 80s when we first made the GNU Manifesto an invariant section in the Emacs Manual, was to make sure they could not be removed. Specifically, to make sure that distributors of Emacs that also distribute non-free software could not remove the statements of our philosophy, which they might think of doing because those statements criticize their actions.

GPL incompatible in both directions[edit]

The GNU FDL is incompatible in both directions with the GPL—material under the GNU FDL cannot be put into GPL code and GPL code cannot be put into a GNU FDL manual.[22] At the June 22nd and 23rd 2006 international GPLv3 conference in Barcelona, Eben Moglen hinted that a future version of the GPL could be made suitable for documentation:[23]

By expressing LGPL as just an additional permission on top of GPL we simplify our licensing landscape drastically. It's like for physics getting rid of a force, right? We just unified electro-weak, ok? The grand unified field theory still escapes us until the document licences too are just additional permissions on top of GPL. I don't know how we'll ever get there, that's gravity, it's really hard.

Burdens when printing[edit]

The GNU FDL requires that licensees, when printing a document covered by the license, must also include "this License, the copyright notices, and the license notice saying this License applies to the Document". This means that if a licensee prints out a copy of an article whose text is covered under the GNU FDL, they must also include a copyright notice and a physical printout of the GNU FDL, which is a significantly large document in itself. Worse, the same is required for the standalone use of just one (for example, Wikipedia) image.[24] Wikivoyage, a web site dedicated to free content travel guides, chose not to use the GFDL because it considers it unsuitable for short printed texts.[25]

Other free content licenses[edit]

Some of these were developed independently of the GNU FDL, while others were developed in response to perceived flaws in the GNU FDL.

List of projects that use the GFDL[edit]

This list is incomplete; you can help by expanding it.

See also[edit]

References[edit]

  1. ^ "Wikipedia:About", Wikipedia, 2018-07-26, retrieved 2018-09-07
  2. ^ Richard Stallman (12 September 1999). "New Documentation License--Comments Requested". Newsgroup: gnu.misc.discuss. Usenet: gnusenet199909120759.DAA04152@psilocin.gnu.org. Retrieved August 17, 2017.
  3. ^ a b c d "FDL 1.3 FAQ". Gnu.org. Retrieved 2011-11-07.
  4. ^ Lessig, Lawrence (2007-12-01). "Some important news from Wikipedia to understand clearly (Lessig Blog)". Lessig.org. Retrieved 2011-11-07.
  5. ^ "Wikimediafoundation.org". Wikimediafoundation.org. Retrieved 2011-11-07.
  6. ^ a b Richard Stallman: Why publishers should use the GNU FDL Accessed on 2009-07-17
  7. ^ a b GNU project: Frequently Asked Questions about the GNU Licenses: Why don't you use the GPL for manuals?
  8. ^ "Wikimedia community approves license migration". Wikimedia Foundation. Wikimedia Foundation. Retrieved 2009-05-21.
  9. ^ Wikimedia license update approval
  10. ^ Licensing update rolled out in all Wikimedia wikis on wikimedia.org by Erik Moeller on June 30th, 2009 "Perhaps the most significant reason to choose CC-BY-SA as our primary content license was to be compatible with many of the other admirable endeavors out there to share and develop free knowledge"
  11. ^ Jones, Pamela (2010-08-03). "BusyBox and the GPL Prevail Again - Updated 4Xs". Groklaw. Retrieved 2019-05-17.
  12. ^ "Baidu May Be Worst Wikipedia Copyright Violator". PC World. 6 August 2007. Retrieved 10 September 2007.
  13. ^ Nerode, Nathanael (2007-12-10). "Why You Shouldn't Use the GNU FDL". Archived from the original on 2007-12-10. Retrieved 2011-11-07.
  14. ^ Srivastava, Manoj (2006). "Draft Debian Position Statement about the GNU Free Documentation License (GFDL)". Retrieved 2007-09-25. It is not possible to borrow text from a GFDL'd manual and incorporate it in any free software program whatsoever. This is not a mere license incompatibility. It's not just that the GFDL is incompatible with this or that free software license: it's that it is fundamentally incompatible with any free software license whatsoever. So if you write a new program, and you have no commitments at all about what license you want to use, saving only that it be a free license, you cannot include GFDL'd text. The GNU FDL, as it stands today, does not meet the Debian Free Software Guidelines. There are significant problems with the license, as detailed above; and, as such, we cannot accept works licensed under the GNU FDL into our distribution.
  15. ^ "Thomas Bushnell dismissed from Hurd project for criticizing GFDL". archive.is. 2003-11-19. Archived from the original on 2012-07-13. Retrieved 2017-04-16.
  16. ^ Nerode, Nathanael (2003-09-24). "Why You Shouldn't Use the GNU FDL". Archived from the original on 2003-10-09. Retrieved 2011-11-07.
  17. ^ a b Bruce Perens (2 Sep 2003). "stepping in between Debian and FSF". lists.debian.org/debian-legal. Retrieved 2016-03-20. FSF, a Free Software organization, isn't being entirely true to the Free Software ethos while it is promoting a license that allows invariant sections to be applied to anything but the license text and attribution. FSF is not Creative Commons:the documentation that FSF handles is an essential component of FSF's Free Software, and should be treated as such. In that light, the GFDL isn't consistent with the ethos that FSF has promoted for 19 years.
  18. ^ a b c d Debian Project: Resolution: Why the GNU Free Documentation License is not suitable for Debian. Voted February–March 2006. (Accessed June 20, 2009)
  19. ^ FLOSS Manuals Foundation (6 June 2007). "License Change". FLOSS Manuals Blog. FLOSS Manuals Foundation. Archived from the original on 28 February 2008. Retrieved 20 June 2009.
  20. ^ Richard Stallman (2003-09-06), Re: A possible GFDL compromise. Accessed on 2007-09-25.
  21. ^ Richard Stallman, (2003-08-23), Re: A possible GFDL compromise. Accessed on 2007-09-25.
  22. ^ Richard Braakman on Debian-legal about GFDL/GPL incompatibility
  23. ^ Transcript of Eben Moglen at the 3rd international GPLv3 conference; 22nd June 2006: LGPL, like merging electronic weak. Accessed on 2009-06-20.
  24. ^ "Why the Wikimedia projects should not use GFDL as a stand alone license for images". Notablog.notafish.com. Retrieved 2011-11-07.
  25. ^ Wikivoyage:Project:Why Wikivoyage isn't GFDL
  26. ^ Judson, Thomas W. (2015). "Abstract Algebra: Theory and Applications".

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=GNU_Free_Documentation_License&oldid=953114618"