WTFPL

Last updated
Do What the Fuck You Want To Public License
WTFPL logo.svg
The WTFPL logo
AuthorBanlu Kemiyatorn, Sam Hocevar
Latest version2
Publisher Sam Hocevar
Published2004
SPDX identifierWTFPL
FSF approved Yes [1]
OSI approved No
GPL compatible Yes [1]
Copyleft No [1]
Linking from code with a different licence Yes
Website www.wtfpl.net

The WTFPL is a permissive free software license. [1] As a public domain like license, the WTFPL is essentially the same as dedication to the public domain. [2] It allows redistribution and modification of the work under any terms. The name is an abbreviation of Do What The Fuck You Want To Public License.

Contents

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

Characteristics

The WTFPL intends to be a permissive, public-domain-like license. The license is not a copyleft license. [1] 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] [ failed verification ]

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

Terms

Version 2

The text of Version 2, the most current version of the license, written by Sam Hocevar: [4] 

           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.

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.

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] yalu102 [10] and MediaWiki extensions. [11] More than 5,000 Wikimedia Commons files and more than 24,000 Projects on GitHub were published under the terms of the WTFPL. [12] [13]

Discussion

The license was confirmed as a GPL-compatible free software license by the Free Software Foundation, but its use is "not recommended". [1] In 2009, the Open Source Initiative chose not to approve the license as an open-source license due to redundancy with the Fair License. [2]

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

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

Google does not allow its employees to contribute to projects under public domain equivalent licenses like the WTFPL (and Unlicense CC0), while allowing contributions to 0BSD licensed and US government PD projects. [22]

See also

Related Research Articles

<span class="mw-page-title-main">Free software</span> Software licensed to be freely used, modified and distributed

Free software, libre software, or libreware is computer software distributed under terms that allow users to run the software for any purpose as well as to study, change, and distribute it and any adapted versions. Free software is a matter of liberty, not price; all users are legally free to do what they want with their copies of a free software regardless of how much is paid to obtain the program. Computer programs are deemed "free" if they give end-users ultimate control over the software and, subsequently, over their devices.

The MIT License is a permissive software license originating at the Massachusetts Institute of Technology (MIT) in the late 1980s. As a permissive license, it puts very few restrictions on reuse and therefore has high license compatibility.

<span class="mw-page-title-main">Open-source license</span> Software license allowing source code to be used, modified, and shared

Open-source licenses are software licenses that allow content to be used, modified, and shared. They facilitate free and open-source software (FOSS) development. Intellectual property (IP) laws restrict the modification and sharing of creative works. Free and open-source licenses use these existing legal structures for an inverse purpose. They grant the recipient the rights to use the software, examine the source code, modify it, and distribute the modifications. These criteria are outlined in the Open Source Definition.

<span class="mw-page-title-main">Apache License</span> Free software license

The Apache License is a permissive free software license written by the Apache Software Foundation (ASF). It allows users to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software under the terms of the license, without concern for royalties. The ASF and its projects release their software products under the Apache License. The license is also used by many non-ASF projects.

A software license is a legal instrument governing the use or redistribution of software. Under United States copyright law, all software is copyright protected, in both source code and object code forms, unless that software was developed by the United States Government, in which case it cannot be copyrighted. Authors of copyrighted software can donate their software to the public domain, in which case it is also not covered by copyright and, as a result, cannot be licensed.

Beerware is a tongue-in-cheek term for software released under a very relaxed license. It provides the end user with the right to use a particular program.

The Common Development and Distribution License (CDDL) is a free and open-source software license, produced by Sun Microsystems, based on the Mozilla Public License (MPL). Files licensed under the CDDL can be combined with files licensed under other licenses, whether open source or proprietary. In 2005 the Open Source Initiative approved the license. The Free Software Foundation (FSF) considers it a free software license, but one which is incompatible with the GNU General Public License (GPL).

A permissive software license, sometimes also called BSD-like or BSD-style license, is a free-software license which instead of copyleft protections, carries only minimal restrictions on how the software can be used, modified, and redistributed, usually including a warranty disclaimer. Examples include the GNU All-permissive License, MIT License, BSD licenses, Apple Public Source License and Apache license. As of 2016, the most popular free-software license is the permissive MIT license.

This comparison only covers software licenses which have a linked Wikipedia article for details and which are approved by at least one of the following expert groups: the Free Software Foundation, the Open Source Initiative, the Debian Project and the Fedora Project. For a list of licenses not specifically intended for software, see List of free-content licences.

<span class="mw-page-title-main">Public-domain software</span> Software in the public domain

Public-domain software is software that has been placed in the public domain, in other words, software for which there is absolutely no ownership such as copyright, trademark, or patent. Software in the public domain can be modified, distributed, or sold even without any attribution by anyone; this is unlike the common case of software under exclusive copyright, where licenses grant limited usage rights.

<span class="mw-page-title-main">Public-domain-equivalent license</span> License that waives all copyright

Public-domain-equivalent license are licenses that grant public-domain-like rights and/or act as waivers. They are used to make copyrighted works usable by anyone without conditions, while avoiding the complexities of attribution or license compatibility that occur with other licenses.

License proliferation is the phenomenon of an abundance of already existing and the continued creation of new software licenses for software and software packages in the FOSS ecosystem. License proliferation affects the whole FOSS ecosystem negatively by the burden of increasingly complex license selection, license interaction, and license compatibility considerations.

<span class="mw-page-title-main">Free-software license</span> License allowing software modification and redistribution

A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software. These actions are usually prohibited by copyright law, but the rights-holder of a piece of software can remove these restrictions by accompanying the software with a software license which grants the recipient these rights. Software using such a license is free software as conferred by the copyright holder. Free-software licenses are applied to software in source code and also binary object-code form, as the copyright law recognizes both forms.

BSD licenses are a family of permissive free software licenses, imposing minimal restrictions on the use and distribution of covered software. This is in contrast to copyleft licenses, which have share-alike requirements. The original BSD license was used for its namesake, the Berkeley Software Distribution (BSD), a Unix-like operating system. The original version has since been revised, and its descendants are referred to as modified BSD licenses.

<span class="mw-page-title-main">Copyleft</span> Practice of mandating free use in all derivatives of a work

Copyleft is the legal technique of granting certain freedoms over copies of copyrighted works with the requirement that the same rights be preserved in derivative works. In this sense, freedoms refers to the use of the work for any purpose, and the ability to modify, copy, share, and redistribute the work, with or without a fee. Licenses which implement copyleft can be used to maintain copyright conditions for works ranging from computer software, to documents, art, scientific discoveries and even certain patents.

<span class="mw-page-title-main">GNU General Public License</span> Series of free software licenses

The GNU General Public License is a series of widely used free software licenses or copyleft that guarantee end users the four freedoms to run, study, share, and modify the software. The license was the first copyleft for general use and was originally written by Richard Stallman, the founder of the Free Software Foundation (FSF), for the GNU Project. The license grants the recipients of a computer program the rights of the Free Software Definition. These GPL series are all copyleft licenses, which means that any derivative work must be distributed under the same or equivalent license terms. It is more restrictive than the Lesser General Public License and even further distinct from the more widely used permissive software licenses BSD, MIT, and Apache.

A free license or open license is a license which allows others to reuse another creator’s work as they wish. Without a special license, these uses are normally prohibited by copyright, patent or commercial license. Most free licenses are worldwide, royalty-free, non-exclusive, and perpetual. Free licenses are often the basis of crowdsourcing and crowdfunding projects.

A public license or public copyright licenses is a license by which a copyright holder as licensor can grant additional copyright permissions to any and all persons in the general public as licensees. By applying a public license to a work, provided that the licensees obey the terms and conditions of the license, copyright holders give permission for others to copy or change their work in ways that would otherwise infringe copyright law.

Software relicensing is applied in open-source software development when software licenses of software modules are incompatible and are required to be compatible for a greater combined work. Licenses applied to software as copyrightable works, in source code as binary form, can contain contradictory clauses. These requirements can make it impossible to combine source code or content of several software works to create a new combined one.

<span class="mw-page-title-main">Unlicense</span> Anti-copyright license

The Unlicense is a public domain equivalent license for software which provides a public domain waiver with a fall-back public-domain-like license, similar to the CC Zero for cultural works. It includes language used in earlier software projects and has a focus on an anti-copyright message.

References

  1. 1 2 3 4 5 6 "Various Licenses and Comments about Them". GNU Operating System. Free Software Foundation.
  2. 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. [...] Mr. Michlmayr did not agree with the reasons cited for possible rejection of the WFTPL license since public domain doesn't exist in Europe. [...] Mr. Michlmayr moved that we reject the WFTPL as redundant to the Fair License.
  3. 1 2 Sam Hocevar (2012-12-27). "Frequently Asked Questions". WTFPL – Do What the Fuck You Want to Public License. Retrieved 2016-07-19.
  4. 1 2 Sam Hocevar (2012-12-26). "WTFPL version 2" . Retrieved 2016-07-19.
  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. ↑ "incomplete iOS 10.2 jailbreak for 64 bit devices by qwertyoruiopz and marcograssi". GitHub. 2017-02-02. Retrieved 2022-10-06.
  11. ↑ "Category:WTFPL licensed extensions". MediaWikiWiki. 2016. Retrieved 2016-07-19.
  12. ↑ "Category:WTFPL". Wikimedia Commons. 2018. Retrieved 2022-09-30.
  13. ↑ "Build software better, together". GitHub. Retrieved 2022-07-24.
  14. ↑ "Copyfree Licenses". Copyfree. The Copyfree Initiative.
  15. ↑ Callaway, Tom (2016-05-17). "Licensing:Main". Fedora Project Wiki. Retrieved 2016-07-10.
  16. ↑ 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.
  17. ↑ theiostream (2012-03-24). "Introducing WTFPL v3" (Blog). tumblr. Archived from the original on July 5, 2014. Retrieved 2016-07-19.
  18. ↑ 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. Archived from the original on 2016-04-23. Retrieved 2016-07-19. … with a CYA clause ….
  19. ↑ 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.
  20. ↑ 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.
  21. ↑ Nina Paley (2011-06-24). "How To Free Your Work". QuestionCopyright.org. Retrieved 2016-07-19.
  22. ↑ "Open Source Patching" . Retrieved 2020-09-29.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.