choosealicense.com/_licenses/wtfpl.txt

---
title: "Do What The F*ck You Want To Public License"
spdx-id: WTFPL
source: http://www.wtfpl.net/txt/copying/

description: The easiest license out there. It gives the user permissions to do whatever they want with your code.

how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.

using:

permissions:
  - commercial-use
  - modifications
  - distribution
  - private-use

conditions: []

limitations: []

---

            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.
Added the WTFPL licence 2014-06-24 15:39:47 +02:00			`---`
fix up wtfpl; 2015-08-19 16:46:40 -04:00			`title: "Do What The F*ck You Want To Public License"`
spdx-id required, nickname only for licenses with customary short names 2016-05-24 16:21:13 -05:00			`spdx-id: WTFPL`
make wtfpl source: field point to url with license text 2017-11-13 16:01:45 -08:00			`source: http://www.wtfpl.net/txt/copying/`
Added the WTFPL licence 2014-06-24 15:39:47 +02:00
Correct the spelling of "license" in wtfpl Just a minor correction i found while browsing. 2016-06-15 21:44:52 +02:00			`description: The easiest license out there. It gives the user permissions to do whatever they want with your code.`
Added the WTFPL licence 2014-06-24 15:39:47 +02:00
fix up wtfpl; 2015-08-19 16:46:40 -04:00			`how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.`
Added the WTFPL licence 2014-06-24 15:39:47 +02:00
make `using` required for new licenses 2017-05-30 14:17:13 -07:00			`using:`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`permissions:`
fix up wtfpl; 2015-08-19 16:46:40 -04:00			`- commercial-use`
			`- modifications`
			`- distribution`
			`- private-use`
Added the WTFPL licence 2014-06-24 15:39:47 +02:00
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`conditions: []`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`limitations: []`
Added the WTFPL licence 2014-06-24 15:39:47 +02:00
			`---`

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

Fix copyright line, which pertains to the license itself See http://www.wtfpl.net/faq/ 2017-03-02 17:37:03 -08:00			`Copyright (C) 2004 Sam Hocevar <sam@hocevar.net>`
Added the WTFPL licence 2014-06-24 15:39:47 +02:00
			`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.`