docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-11-06 03:38:49 +01:00
Code Issues Releases Wiki Activity
46270d6389
choosealicense.com/_licenses/wtfpl.txt

34 lines
946 B
Plaintext
Raw Normal View History

Added the WTFPL licence
2014-06-24 15:39:47 +02:00
---
fix up wtfpl;
2015-08-19 22:46:40 +02:00
title: "Do What The F*ck You Want To Public License"
Added the WTFPL licence
2014-06-24 15:39:47 +02:00
source: http://www.wtfpl.net/
Made it less explicit and moved to hidden category By removing 'fuck' from the title, 'the fuck' from the license description and moving this license to the hidden section I hope it is now suitable for merging.
2015-08-07 13:31:05 +02:00
description: The easiest licence 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 22:46:40 +02: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
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 22:33:15 +01:00
conditions: []
Added the WTFPL licence
2014-06-24 15:39:47 +02:00
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 22:33:15 +01:00
permissions:
fix up wtfpl;
2015-08-19 22:46:40 +02:00
- commercial-use
- modifications
- distribution
- private-use
Added the WTFPL licence
2014-06-24 15:39:47 +02:00
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 22:33:15 +01: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 up wtfpl;
2015-08-19 22:46:40 +02:00
Copyright (C) 2004 [fullname] <[email]>
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.
Reference in New Issue Copy Permalink