How do I add the WTFPL license to my project?

4

I have a project that will have free distribution, modification, copying and whatever else, and I saw the WTFPL license that works that way.

On your website we have the text template to be inserted into the project, as seen below:

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

 Copyright (C) 2004 Sam Hocevar <[email protected]> 

 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 FU** YOU WANT TO PUBLIC LICENSE 
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 

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

My question is: Should I change the date, name and email of the text or leave the same?

I ask this question, because if we look at the Showcase , we can see several examples with the same text, but also some with the change in the data, so this doubt.

    
asked by anonymous 05.05.2016 / 17:32

2 answers

2
  

No source is better than the official license site, so let's see what it says about it.

On the FAQ page of the license, we have a "small" tutorial on how to add the license to your project, which follows two steps:

1. Have an original copy of the file in your project or refer to the official website file, that is, with the data shown in the license: [...] 2004 Sam Hocevar < [email protected]> [...] . Usually the file is named COPYING.WTFPL .

2nd Add the year and author declarations in your project.

Copyright © 2000 Your Name <your@address>
This work is free. You can redistribute it and/or modify it under the
terms of the Do What The Fuck You Want To Public License, Version 2,
as published by Sam Hocevar. See the COPYING file for more details.

If for some reason the project does not have the file, reference this way:

Copyright © 2000 Your Name <your@address>
This work is free. You can redistribute it and/or modify it under the
terms of the Do What The Fuck You Want To Public License, Version 2,
as published by Sam Hocevar. See http://www.wtfpl.net/ for more details.

In summary, you should either have both in your project or refer to the license's website.

Maybe this image will explain better:

Foranexample, this project on GitHub has an example of using the license.

For more information, see the license's own site .

    
05.05.2016 / 18:56
2

Of course, if this is really very important you should seek a lawyer.

If I can give you some advice, I would use a license that is more (re) known and probably more "serious". I do not see an advantage in using this. I would prefer an explicit public domain , if this is the case, although this is not a good license from a legal point of view, than one of this type.

In my understanding is to customize with your data (except the date of the text of the license itself). It's like this in the most obvious licenses:

With Randrade's reply I see one more reason not to use this license. She is confused, misleading, needs to go after her documentation to know what it means, the opposite of what she tries to "sell."

    
05.05.2016 / 18:31