5 ms·
I'm glad Debian is putting their foot down on this issue. There are way too many careless and sometimes downright bad licenses floating around. I've seen, and
by Alupis 12y ago
I'm glad Debian is putting their foot down on this issue. There are way too many careless and sometimes downright bad licenses floating around.
I've seen, and argued against, people using the WTFPL before: http://www.wtfpl.net/about/ http://www.wtfpl.net/about/
Some, even in projects that could be considered "serious" and reused in another project (I won't touch a WTFPL licenses project because to me, it's not a license and is way to legally ambiguous).
I've seen way to many developers think they can write up some text and call it a license and it's "good". Not the case.
Pick a real license that was written by lawyers and has well understood (and preferably previously challenged) legal ramifications.
- yellowapple 12y agoI don't see how "You just DO WHAT THE FUCK YOU WANT TO" is ambiguous, legally or otherwise. That said, this would probably be better served with an explicit public-domain declaration or equivalent (like the CC0 license).
- Alupis 12y agoIt's ambiguous for several reasons. There's not much preventing me from re-assinging copyright to myself (in countries that allow it) and then suing the original creator. There's nothing to stop me from taking your code, re-licensing it under say a proprietary license, then suing the original creator. There's nothing that stops me from taking your project's branding/symbol/graphics/name and claiming it as my own and then suing you. There's nothing that stops me from taking your work and then not providing attribution back to the original creator. By default there is nothing that absolves the license holder from warranty nor implied fitness for use. (If it destroys my computer running your code, I can sue you, and worse, you accept liability by default). That is, unless you include the optional snippet of text that absolves any warranty issues... but since it's optional, and not on the main license page (it's in the FAQ page), many authors forget to include this. There are other things too... like, legally, what does "DO WHAT THE FUCK YOU WANT" actually mean? The law is black and white (or at least we try to be), being in the grey opens the door for abuse. Has it been challenged before in a legal sense? Has a lawyer reviewed it? While I certainly understand the intent and spirit of this license; this license appears to be nothing more than a bad (and somewhat distasteful) joke that serves more harm than good. I agree, better off choosing a public domain license or one of the several vetted FOSS licensees.
- clarry 12y agoWe discussed this before[1] but you failed to back up any claims about this re-licensing and re-assigning business you vent about here. You still haven't explained how you can take away someone else's rights. Copyright licenses are used to grant other people rights, not to take them away. You still haven't read the Berne convention, have you? Can you point at a case in any country that suggests the license could be interpreted outside the context of copyright? I.e. that "do what the fuck you want" in a copyright license can be seen as granting someone rights beyond the ones (related to copying, modification, performance, etc.) that are normally exclusive to the author and therefore require him to use a license to grant others these same rights? If you can't back anything up, I don't think you should be spreading your own interpretations in this manner, presenting them as truth. We already have far too many people confused over licenses, and passing that confusion on doesn't help anyone. [1] https://news.ycombinator.com/item?id=8043969 https://news.ycombinator.com/item?id=8043969
- Alupis 12y agoPerhaps I missed something... But I don't see where you substantiate any of your claims. You seem to just want to defend an obviously joke license. This license, from my interpretations, forfeits most of the copyright protections, including allowing someone to re-license (per the FAQ of the license). At the end of the day, you are free to use whatever license you think suits you best. That does not mean it actually suits you best. (As demonstrated by Debian putting their foot down on other BS licenses such as this).
- clarry 12y agoRe-licensing remains a horribly confusing term, which is something I complained about. Some people use it to mean substitute the license on your copy with some other license, and then pass copies on under that new license. This appears to be the way the FAQ uses the term. The way you use the term, you seem to think that you can actually do some magic and revoke the author's rights, then impose your conditions on him, and possibly sue him for violating these conditions. That's just bullshit, it doesn't work like that. Unless you know something the rest of the world doesn't. You keep saying copyright licenses are used to "forfeit" (by which I assume you mean surrender) rights, so as to (exclusively) transfer them from you to someone else. It doesn't work like that. They are used to grant other people rights. They normally do not remove any rights from the author. And you still maintain your circular definition of copyright, in which authorhood or copyright itself is a right protected by copyright and that through one of the rights protected by copyright (and granted to you by an author's license), you can obtain that right which is copyright (or authorhood). Can you please back any of it up?