What would concern me about using that WTFPL license is there's no disclaimer about fitness for use/purpose, which might mean to someone "do what the fuck you want - including suing me".
Not trying to look like a scaremonger, just a personal view.
Toybox (http://landley.net/toybox/) takes an interesting approach in that they use the ISC license, minus the notice clause. (Strangely, they call call it a 2-clause BSD license, even though it really isn't, but whatever). I'm generally not a fan of license proliferation, but I do kinda like what they've done here.
And the lack of disclaimer of warranty in the WTFPL is not fear-mongering... it's a real issue, and one of the reasons we (Google) don't allow our engineers to use it.
Comments
I chose the ISC license for both of my projects.
http://opensource.org/licenses/ISC
What would concern me about using that WTFPL license is there's no disclaimer about fitness for use/purpose, which might mean to someone "do what the fuck you want - including suing me".
Not trying to look like a scaremonger, just a personal view.
Toybox (http://landley.net/toybox/) takes an interesting approach in that they use the ISC license, minus the notice clause. (Strangely, they call call it a 2-clause BSD license, even though it really isn't, but whatever). I'm generally not a fan of license proliferation, but I do kinda like what they've done here.
And the lack of disclaimer of warranty in the WTFPL is not fear-mongering... it's a real issue, and one of the reasons we (Google) don't allow our engineers to use it.