4 ms·
Sorry, but please don't. The license has serious problems for developers. To start simple, first, while yeah, a judge is probably going to find you can do what
by DannyBee 14y ago
Sorry, but please don't.
The license has serious problems for developers.
To start simple, first, while yeah, a judge is probably going to find you can do whatever you want, because it's not very explicit, there will be arguments over what you were allowed to do. It is entirely possible a judge will decide what is really meant is that you can do whatever reasonable thing you want to.
Worse, it does not effectively disclaim liability for the software developer. He claims he doesn't want "obnoxious things", such as "reproducing a huge disclaimer that is written in all caps".
The reason that all caps language is used is because of a history of court decisions and laws around what is required to effectively disclaim implied warranties.
Right now, the license does not properly disclaim any implied warranties, which puts the developer at risk.
Worse than this, the text block he suggests putting in text if you want to disclaim warranty (http://www.wtfpl.net/faq/ http://www.wtfpl.net/faq/) would likely be ineffective in a lot of places.
I know everyone likes to think they won't get sued. But it does happen. It will wipe you out. It isn't worth taking a moral stand against a few lines of text in a source file.
To answer your other point, if you want good licenses, you have to actually know what the hell you are doing.
I really do understand that people want to not have to give a shit about this stuff, and have simple and clear licensing. Really.
But this is not the path to accomplishing that.
The legal and political world takes a long time to adapt. Things like like free and open source software will eventually be sanely handled in the law. WTFPL is not going to be anywhere in that history.
- anon1385 14y ago>there will be arguments over what you were allowed to do much like the GPL then
- SwellJoe 14y agoIn my experience, most of the people arguing over it haven't read it (or don't understand basic copyright concepts). It's a pretty clear license...but, it gets talked about a lot by folks who misrepresent it, either willfully or out of ignorance.
- burntsushi 14y agoIf a warranty disclaimer from another well-vetted license were used in the WTFPL, would that solve most of the problem? (Sans the judge ruling that it's only limited to reasonable things.)
- DannyBee 14y agoMostly, but at that point, why use it? Why not use MIT without the copyright notice reproduction clause? It would be 1. Better written 2. As easy to understand 3. Well tested and effective.
- ValentineC 14y ago> The reason that all caps language is used is because of a history of court decisions and laws around what is required to effectively disclaim implied warranties. Right now, the license does not properly disclaim any implied warranties, which puts the developer at risk. Just trying to learn a bit about US law here. This part intrigued me, and from what I've Googled so far, it's because of a requirement for the warranty to be "conspicuous". [1][2] Is all caps the most commonly accepted minimum as advised by lawyers (especially when they're advising business types who couldn't care less about putting it in red or bold or something else)? [1] http://www.mslater.com/post/104847-why-are-warranty-disclaimers-in-all http://www.mslater.com/post/104847-why-are-warranty-disclaim... [2] http://www.adamsdrafting.com/all-capitals/ http://www.adamsdrafting.com/all-capitals/
- DannyBee 14y agoThe all-caps is because of conspicuousness, yes, but there are other requirements. UCC, for example (most contracts/licenses for software would fall under UCC, rather than common law), says basically (I'm pasting a capsule summary from a case book, i can cite the underlying provisions in the actual code, but this summary is accurate): First, the seller must clearly and explicitly do so at the time of contracting by using words that communicate the risks that fall on the buyer. To exclude the implied warranty of merchantability, the language of the disclaimer must mention “merchantability” and, if written, must be conspicuous. To exclude the implied warranty of fitness, the exclusion must be in writing and be conspicuous. Thus, fine print disclaimer may be inoperative. If an express warranty is also given, words or conduct relevant to its creation and words or conduct tending to negate or limit a warranty must be construed whenever reasonable as consistent with each other. Any words of disclaimer or modification of warranty should be strictly construed against the seller. In general, words or conduct tending to negate or limit a warranty are inoperative to the extent that construction is unreasonable.
- angersock 14y agoI really do understand that people want to not have to give a shit about this stuff, and have simple and clear licensing. Really. But this is not the path to accomplishing that. You've hit it on the head--unfortunately, what else are we to do? I don't trust the general legal intuitions of ourselves and our peers, since we seem to be so rubbish at creating a useful legal and political climate for our industry (based on ~30 years of case law). So, in the meantime, let's instead live in our ideal world, pull no punches, and cross the legal bridges when (and if) they come up. Perhaps a proper rallying will be tenable then, instead of us all being chickens. As for licenses, I think Apache currently is best for "serious grown-up usage", no, what with the patent indemnification and all, or am I misinformed?
- DannyBee 14y ago"I don't trust the general legal intuitions of ourselves and our peers, since we seem to be so rubbish at creating a useful legal and political climate for our industry (based on ~30 years of case law)." This is entirely because of the penchant for the average software/etc engineer to stick their head as far in the sand as it can go, and then complain that this is ineffective. It is only in the past few years that this has changed, and headway has already started to be made behind the scenes. "As for licenses, I think Apache currently is best for "serious grown-up usage", no, what with the patent indemnification and all, or am I misinformed?" This is, IMHO, correct. The only downside to apache is that the defensive patent termination clause only terminates patent rights. If there were no patents on the software, and they sue you over patents, they can go right on using it. Sadly, it's not possible to make a license that does terminate both copyrights and patents on being sued, and still hae such a license be GPL compatible.
- chimeracoder 14y ago> The only downside to apache is that the defensive patent termination clause only terminates patent rights. If there were no patents on the software, and they sue you over patents, they can go right on using it. IANAL - could you explain what you mean by this?