WTFPL

Do What the Fuck You Want To Public License

The WTFPL logo
Author Banlu Kemiyatorn, Sam Hocevar
Latest version 2
Publisher Sam Hocevar
Published 2004
FSF approved Yes
OSI approved No
GPL compatible Yes
Copyleft No
Linking from code with a different license Yes
Website www.wtfpl.net

The WTFPL (Do What the Fuck You Want To Public License) is a permissive license most commonly used as a free software license. As a public domain like license, the WTFPL is essentially the same as dedication to the public domain.[1] It allows for redistribution and modification of the software under any terms. As of May 2016, the WTFPL was used by less than one percent of open source software projects.

The first version of the WTFPL, released in March 2000, was written by Banlu Kemiyatorn for his own software project.[2] Sam Hocevar, Debian's former project leader, wrote version 2.[3]

Characteristics

The WTFPL intends to be a permissive, public domain-like license. The license is not a copyleft license.[4] The license differs from public domain in that an author can use it even if they do not necessarily have the ability to place their work in the public domain according to their local laws.[5]

The WTFPL does not include a no-warranty disclaimer,[2] unlike other permissive licenses, such as the MIT License.[6] Though the WTFPL is untested in court,[2] the official website offers a disclaimer to be used in software source code.[2]

Terms

Version 1

do What The Fuck you want to Public License

Version 1.0, March 2000
Copyright (C) 2000 Banlu Kemiyatorn (]d).
136 Nives 7 Jangwattana 14 Laksi Bangkok
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Ok, the purpose of this license is simple
and you just

DO WHAT THE FUCK YOU WANT TO.

Version 2

The text of the license, written by Sam Hocevar:[3]

           DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                   Version 2, December 2004

Copyright (C) 2004 Sam Hocevar <sam@hocevar.net>

Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.

           DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
  TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

 0. You just DO WHAT THE FUCK YOU WANT TO.

Reception

Usage

The WTFPL is not in wide use among open source software projects; according to Black Duck Software, the WTFPL is used by less than one percent of open-source projects.[7] Examples include the OpenStreetMap Potlatch online editor,[8] the video game Liero (version 1.36),[9] and MediaWiki extensions.[10] Some Wikimedia Commons files were published under the terms of the WTFPL.[11]

Discussion

The license was confirmed as a GPL-compatible free software license by the Free Software Foundation, but its use is "not recommended".[12] In 2009, the Open Source Initiative chose not to approve the license as an open source license, saying:

It's no different from dedication to the public domain. Author has submitted license approval request -- author is free to make public domain dedication. Although he agrees with the recommendation, Mr. Michlmayr notes that public domain doesn't exist in Europe. Recommend: Reject.[1]

The WTFPL version 2 is an accepted Copyfree license.[13] It is also accepted by Fedora as a free license and GPL compatible.[14]

Some software authors have said that the license is not very serious;[15] forks tried to address wording ambiguity and liability concerns.[16][17] OSI founding president Eric S. Raymond interpreted the license as written satire against the restrictions of the GPL and other software licenses;[18] WTFPL version 2 author Sam Hocevar later confirmed that the WTFPL is a parody of the GPL.[19] Free culture activist Nina Paley said she considered the WTFPL a free license for cultural works.[20]

See also

References

  1. 1 2 "OSI Board Meeting Minutes, Wednesday, March 4, 2009". Open Source Initiative. 2009-03-04. Retrieved 2013-04-03. [...] the following licenses to be discussed and approved/disapproved by the Board. [...] WTFPL Submission: [...] Comments: It's no different from dedication to the public domain. Author has submitted license approval request -- author is free to make public domain dedication. Although he agrees with the recommendation, Mr. Michlmayr notes that public domain doesn't exist in Europe. Recommend: Reject
  2. 1 2 3 4 Sam Hocevar (2012-12-27). "Frequently Asked Questions". WTFPL – Do What the Fuck You Want to Public License. Retrieved 2016-07-19.
  3. 1 2 Sam Hocevar (2012-12-26). "WTFPL version 2". Retrieved 2016-07-19.
  4. "Various Licenses and Comments about Them". GNU Operating System. Free Software Foundation. Retrieved 2016-07-10. This is a lax permissive non-copyleft free software license, compatible with the GNU GPL. [emphasis added]
  5. Kreutzer, Till. "Validity of the Creative Commons Zero 1.0 Universal Public Domain Dedication and its usability for bibliographic metadata from the perspective of German Copyright Law" (PDF). Büro für informationsrechtliche Expertise.
  6. "The MIT License". Open Source Initiative.
  7. "Top Open Source Licenses". Black Duck Software. Archived from the original on 2016-05-10.
  8. "LICENCE.txt". Potlatch 2. GitHub. December 2004. Retrieved 2012-01-16.
  9. "license.txt". Liero official website. 2013-09-03. Retrieved 2016-07-12. The original Liero data and binary files are copyright 1998 Joosa Riekkinen
    They are, unless otherwise stated, available under the WTFPL license:
    http://sam.zoy.org/wtfpl/
  10. "Category:WTFPL licensed extensions". MediaWikiWiki. 2016. Retrieved 2016-07-19.
  11. "Category:WTFPL". Wikimedia Commons. 2016. Retrieved 2016-07-19.
  12. "Licenses - Free Software Foundation". Free Software Foundation.
  13. "Copyfree Licenses". Copyfree. The Copyfree Initiative.
  14. Callaway, Tom (2016-05-17). "Licensing:Main". Fedora Project Wiki. Retrieved 2016-07-10.
  15. Suder, Kuba (2011-01-15). "On Open Source licensing". Apples & Rubies (Blog). There are at least two not very serious licenses which have essentially the same meaning as public domain. I'm talking about the Beerware license and WTFPL ('Do What The Fuck You Want To' license). I really like these because they pretty well represent my opinion about the legalese bullshit that most licenses are so full of.
  16. theiostream (2012-03-24). "Introducing WTFPL v3" (Blog). tumblr. Retrieved 2016-07-19.
  17. Ben McGinnes (2013-10-01). "Do What The Fuck You Want To But It's Not My Fault Public License v1 (WTFNMFPL-1.0)". tl;drLegal. Retrieved 2016-07-19. … with a CYA clause ….
  18. Eric S. Raymond (2010-05-19). "Software licenses as conversation" (Blog). esr.iblio.org. Retrieved 2016-07-19. It’s even clearer that the Do What the Fuck You Want To Public License is a satire. The author is one of those who thinks the Free Software Foundation has traduced the word 'free' by hedging the GNU General Public License about with restrictions and boobytraps in the name of 'freedom' – and he’s got an issue or two with BSD as well. He is poking fun at both camps, not gently at all. His page about the WTFPL is funny-because-it’s-true hilarious, and I admit that I feel a sneaking temptation to start using it myself.
  19. Sam Hocevar (2015-09-21). "Should I change the name of the WTFPL?". Programmers Stack Exchange (User comment). Retrieved 2016-07-19. The WTFPL is a parody of the GPL, which has a similar copyright header and list of permissions to modify (i.e. none), see for instance gnu.org/licenses/gpl-3.0.en.html. The purpose of the WTFPL wording is to give more freedom than the GPL does.
  20. Nina Paley (2011-06-24). "How To Free Your Work". QuestionCopyright.org. Retrieved 2016-07-19.
Wikimedia Commons has media related to WTFPL.
This article is issued from Wikipedia - version of the 12/2/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.