22 ms·
The MIT License, Line by Line
- AstroJetson 10y agoCrushed under load, to get the cache http://webcache.googleusercontent.com/search?q=cache:https://writing.kemitchell.com/2016/09/21/MIT-License-Line-by-Line.html http://webcache.googleusercontent.com/search?q=cache:https:/... I've always wondered about the nuances around the different licenses, it's nice to get a non-lawyer guide to the MIT one.
- kemitchell 10y agoDang. I didn't get a notification. Recently moved from GitHub pages to a VPS, for strict transport security and other goodies. Instant karma.
- TempleOS 10y agoTempleOS is under the Jesus license. God's world is perfectly just. Highs and lows balance. The only way to get Heaven is to suffer. Eye for Eye 38 “You have heard that it was said, ‘Eye for eye, and tooth for tooth.’[h] 39 But I tell you, do not resist an evil person. If anyone slaps you on the right cheek, turn to them the other cheek also. 40 And if anyone wants to sue you and take your shirt, hand over your coat as well. 41 If anyone forces you to go one mile, go with them two miles. 42 Give to the one who asks you, and do not turn away from the one who wants to borrow from you.
- tbirdz 10y agoDoes anyone know if this will be part of an ongoing series, covering many open source licenses?
- 3JPLW 10y agoThat would be incredible, but if he spends 4600 words explaining those 171 words, I can't imagine the time investment involved in the GPLv2 (2910), GPLv3 (5644), or MPLv2 (2346).
- tbirdz 10y agoThose licenses are very wordy, but not as dense. For example, about a third of the GPLv2 is the preamble that explains the FSF's "four freedoms" of free software philosophy and the ending section after the legal terms that explains how to apply the license to your own product. Cutting those out reduces the GPLv2 to only 2017 words of actual legal text. I also feel like it might be easier to explain a more legalese license like GPLv3, MPLv2 or Apachev2. Like the article explains, the MIT license doesn't use the "language of the law" and uses more common language and language familiar to academics and programmers. A license written with more lawyer-oriented langauge, actually using the same wording as the original laws use, might be much easier for a lawyer like Mr. Mitchell to explain. I'm thinking it's an explicit vs implicit type situation, where even though some licenses are longer they define more things explicity, which means the explanation doesn't have to fill in as many gaps. There are also plenty of simpler licenses that would be great for an explanation. And as part of a series, the author could assume that you are familiar with his MIT license explanation so as to not repeat the same things. Other good candidates I'm thinking would be the BSD licenses, the ISC license, the zlib license, maybe even Apache v2.
- kemitchell 10y agoThere's definitely an amplification factor at work here. This could DoS my professional and personal lives pretty quick ;-P
- kemitchell 10y agoI'm planning many other posts on open-source topics---I've got it bad---but not any other line-by-lines at the moment. If you're interested in this kind of thing, I _highly_ recommend Meeker's, Rosen's, and St. Laurent's books. St. Laurent's, from O'Reilly, might be my least favorite of those three, but it's the closest to the line-by-line style. Meeker's coverage of GPL issues is second to none. Rosen's the best general introduction. Very approachable. Hits some fundamental concepts.
- tbirdz 10y agoSounds interesting. Would you mind sharing the names of those books?
- kemitchell 10y agoI've added a list, with links, to the end of the blog post.
- SamBam 10y ago> The phrase “arising from, out of or in connection with” is a recurring tick symptomatic of the legal draftsman’s inherent, anxious insecurity. Indeed. I'm trying to imagine a court saying "Well... there were damages, but they arose out of the software and not from the software, so therefore- oh, wait! The license actually includes arising "out of" the software as well as "from" the software, so I guess the limitation of liability stands. Case dismissed!"
- sdkmvx 10y agoLawyers are rather fond of such doublets and triplets. Consider free and clear, null and void, terms and conditions, and even law and order. The origin of a lot of legalisms is the historical confusion over language in ancient English courts: Latin, French, or English? Most odd legal grammar is actually of French origin.
- nzp 10y agoIt's one of my favourite lists: https://en.wikipedia.org/wiki/Legal_doublet https://en.wikipedia.org/wiki/Legal_doublet
- saghm 10y agoIt seems to be missing "aid and comfort" (from the clause of the U.S. Constitution about treason). Not sure if this is used anywhere else, but it seems similarly redundant from my non-lawyer perspective, in that if were only "aid" and not comfort, it seems absurd that it would be functionally different
- tzs 10y ago> A legal doublet is a standardized phrase used frequently in English legal language consisting of two or more words that are near synonyms. ... > power and authority Should that really be on the list? Power is the capability to do something, authority is the permission to do it. Sometimes power and authority are near synonyms, such as in frontier areas with little government, but generally in a functioning, civilized society they are quite distinct.
- vonnik 10y agoWe've worked with Kyle Mitchell. He's a smart guy.
- PieterH 10y agoThis is a really good article. There's one part in particular that struck me: "Despite the assumption of some newer open-source developers that sending a pull request on GitHub “automatically” licenses the contribution for distribution on the terms of the project’s existing license—what Richard Fontana of Red Hat calls “inbound=outbound”—United States law doesn’t recognize any such rule. Strong copyright protection, not permissive licensing, is the default." In other words the fork + pull request + merge flow does not work on a project unless you have an explicit step like a CLA, or an alternative solution. We faced this problem early on in ZeroMQ, that asking contributors to take this extra step increased the work for maintainers (to check, is this the first time person X contributes, and have they made a CLA?) It also scared off contributors from businesses, where this often took approval (which took time and was often denied). Our first solution in ZeroMQ was to ask contributors to explicitly state, "I hereby license this patch under MIT," which let us safely merge it into our LGPL codebase. Yet, again, another extra step and again, needs corporate approval. Our current solution is I think more elegant and is one of the arguments I've used in favor of a share-alike license (xGPL originally and MPLv2 more these days) in our projects. That works as follows: * When you fork a project ABC that uses, say, MPLv2, the fork is also licensed under MPLv2. * When you modify the fork, with your patch, your derived work is now also always licensed under MPLv2. This is due to the share-alike aspect. If you use MIT, at this stage the derived work is (or rather, can be) standard copyright. Admittedly if you leave the license header in the source file, it remains MIT. Yet how many maintainers check the header of the inbound source file? Not many IMO. * When you then send a patch from that inbound project, the patch is also licensed under MPLv2. * Ergo there is no need for an explicit grant or transfer of copyright. I wonder if other people have come to the same conclusion, or if there are flaws in my reasoning.
- teamhappy 10y ago> In other words the fork + pull request + merge flow does not work on a project unless you have an explicit copyright assignment step (CLA), or some alternative. FWIW, the Apache license contains a section dedicated to that (5. Submission of Contributions): http://www.apache.org/licenses/LICENSE-2.0 http://www.apache.org/licenses/LICENSE-2.0
- gakada 10y agoIt's funny that the MIT license has the reputation of being "The license you choose when you don't care about attribution, or it would be unreasonable to require attribution". As the article points out, copies of MIT licensed code must include not only the copyright line but the whole damn license.
- tbirdz 10y agoIndeed, for works where I don't care about attribution for binary users I use the zlib license [0] which says "This notice may not be removed or altered from any source distribution." You'd still have to include the notice in any source distribution, but that's not really as onerous in my opinion, since you're already having to distribute all your source files, so what's just one more notice. Of course, my projects normally use a language with a compiler that produces binaries. I'm not sure how this would apply to a language that keeps things in source form like javascript. Maybe webasm will become the new binary form? asm.js? minified javascript? 0: https://opensource.org/licenses/Zlib https://opensource.org/licenses/Zlib
- CamperBob2 10y agoYou'd still have to include the notice in any source distribution, but that's not really as onerous in my opinion, since you're already having to distribute all your source files, so what's just one more notice. But neither MIT nor zlib require you to distribute any source files. With zlib it's pretty clear what's expected, but with MIT, I'm actually not sure what attribution if any is required in a binary-only distribution.
- tbirdz 10y agoJust to clarify my previous statement. I didn't mean to imply that zlib or MIT require you to distribute your source. I meant that if you are distributing your source code (for reasons other than any requirement from zlib or MIT licenses), then it's not too much of an additional burden to include the zlib license attribution, because you'd already be including the files that I had licensed under zlib, and each of those files has a little header saying it's licensed under zlib. Including the zlib license is then not much more work than including another source file from the project. The way I've seen MIT interpreted most often is that you have to distribute the license and attribution even for binary only distribution, or distribution in binary form as part of a larger work. But you're right the language does seem kind of vague on what "The Program" actually means.
- branchly2 10y agoThis looks excellent, and I'm going to curl up with it and a cup of tea tonight to read it more carefully. Thanks! Would love to see the author do one for the GPL. I realize the result would be quite a bit longer.
- deleted 10y ago[deleted]
- richardfontana 10y agoDespite the assumption of some newer open-source developers that sending a pull request on GitHub “automatically” licenses the contribution for distribution on the terms of the project’s existing license—what Richard Fontana of Red Hat calls “inbound=outbound”—United States law doesn’t recognize any such rule. Strong copyright protection, not permissive licensing, is the default. That isn't quite what I mean by "inbound=outbound". Rather, inbound=outbound is a contribution governance rule under which inbound contributions, say a pull request for a GitHub-hosted project, are deemed to be licensed under the applicable outbound license of the project. This is, in fact, the rule under which most open source projects have operated since time immemorial. The DCO is one way of making inbound=outbound more explicit, and I increasingly think one that should be encouraged (if only to combat the practice of using CLAs and the like). But under the right circumstances it works even where the contribution is not explicitly licensed (I think this is what Kyle may be questioning). There are other ways besides the DCO of creating greater certainty, or the appearance of greater certainty, around the inbound licensing act, such as PieterH's suggestion of using a copyleft license like the MPL, or the suggestion of using the Apache License 2.0 (whose section 5 states an inbound=outbound rule as a kind of condition of the outbound license grant).
- loeg 10y agoWhat does DCO mean in this context?
- richardfontana 10y agoThe Developer Certificate of Origin. It's the 'Signed-off-by:' process introduced by the Linux kernel project. http://developercertificate.org/ http://developercertificate.org/ https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=refs/tags/v4.8-rc7#n409 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.... I particularly recommend the presentations and writings of James Bottomley on the DCO, e.g.: http://www.hansenpartnership.com/FOSDEM-DCO-2016/#/begin http://www.hansenpartnership.com/FOSDEM-DCO-2016/#/begin
- 10y ago
- kazinator 10y agoThese licenses have little flaws upon closer examination. One day I was reading the BSD license closely, in the context of its use in the TXR project, and was astonished to find that it was buggy and required tweaking to make it more internally consistent and true to its intent. I added a METALICENSE document where the changes are detailed: http://www.kylheku.com/cgit/txr/tree/METALICENSE http://www.kylheku.com/cgit/txr/tree/METALICENSE http://www.kylheku.com/cgit/txr/tree/LICENSE http://www.kylheku.com/cgit/txr/tree/LICENSE The main problem is that the original says that both the use and redistribution of the software are permitted provided that the "following conditions are met", which is followed by two numbered conditions, 1 and 2. But the two conditions do not govern use at all; they are purely about redistribution! Rather, the intended legal situation is that use of the software means that the user agrees to the liability and warranty disclaimer (which is not a condition). But the BSD license neglects to say that at all; it says use is subject to the conditions (just that 1 and 2), not to the disclaimer.
- nzp 10y agoThere's no bug there. Copyright is about distribution, not use, so the “use” part is probably unnecessary anyway. And the warranty part is not conditional upon the two conditions. The MIT license is practically the same, and the analysis given in the article does not make note of this supposed bug, so we can consider that lawyer-confirmed. IANAL, so it's just my understanding of the issue. I remember people mentioning another possible bug in BSD licenses: if you try to split hairs, and depending on the way you do it, it's questionable if the sentence before the enumerated conditions is part of those conditions or not. If not, that sentence needs not be distributed in copies, so it makes the whole thing meaningless.
- kazinator 10y agoYes, copyright is about distribution, indeed. But licensing isn't purely about copyright! (In the area of proprietary software, it's not even important; the vendor has all the rights and that is clear from the beginning.) A license is not simply a copyright notice, even if it is on free software. (Though of course it includes one.) When you give stuff away for free, you can still be liable for harm arising from it. This applies in ordinary situations, like giving your neighbor an old toaster you don't want, and it causing a fire. So the use aspect of the license with the disclaimer is equally necessary to the rights-granting part. > If you try to split hairs, and depending on the way you do it, it's questionable if the sentence before the enumerated conditions is part of those conditions or not. You raise and excellent point, and I'm going to fix it. I can't see any reason why it should not say "... the above copyright notice, all the introductory text which follows, this list of conditions ...". Really, why isn't it simplified to "this entire license". The GPLv2 cheerfully does this, with the wording "... give any other recipients of the Program a copy of this License along with the Program." That puts an end to any hair splitting about possibly omitted parts.
- cpdean 10y agoWould someone care to elaborate why the "Good, not Evil" clause in the JSON license is bad?
- nitrogen 10y agoThis has been discussed many times before, so search for more details. But the gist is that nobody agrees on what good and evil are, and they are not legally defined terms. For example, some people consider deaths caused by their own country's military as net good, while others believe all military killing is unquestionably net evil. Most people consider blood transfusions good, while some religious groups consider blood transfusions evil. Etc.
- cpdean 10y agoYeah that makes sense. Ambiguity is problematic. Thanks!
- nzp 10y agoIt adds conditions which make it incompatible with GPL, and similar licenses. And in general, it adds a completely arbitrary and uncertain condition, i.e. you can't be legally sure about what you can do with such software, i.e. you can more or less be sued by the author at his whim.
- ajdlinux 10y agoa) It doesn't meet the Free Software Definition or Open Source Definition. What if you want to use the software for evil? b) Who defines what Evil is? What if the author sues you on the grounds that you're using their software for a perfectly legal activity, the morality of which is widely accepted by the general public, but which they personally disagree with? For example, many authors who have written these types of licences are pacifists who disagree with the actions of Western military forces. Are said military applications "Evil"?
- cpdean 10y agoah, gotcha Thanks!
- cyphar 10y ago> The MIT License is the most popular open-source software license. I'm fairly certain the GPL is still more popular.
- matt4077 10y agoMaybe by line count or importance, considering the Linux kernel. By project count, MIT dominates: https://github.com/blog/1964-open-source-license-usage-on-github-com https://github.com/blog/1964-open-source-license-usage-on-gi...
- ashitlerferad 10y agoOn github maybe...
- pjmlp 10y agoGithub isn't the only source of code available on the web. MIT is loved by business, that can take the code from others, packaged it with a new shinny face, sell it and don't return anything back. But one discovers who they are when their customers have problems.
- cyphar 10y agoOn my local machine (since I have texlive installed and each texlive package is a separate package in openSUSE ignore the fact that `LPPL` is the most popular). GPL-2.0+ is ~2x more popular than MIT (and all of the *GPLs together are ~4x more popular) in my admittedly small sample size of packages. % rpm -qai | awk '$1 == "License" { print $3 }' | sort | uniq -c | sort -nr | head -n10 1248 LPPL-1.0 558 GPL-2.0+ 301 MIT 293 LGPL-2.1+ 221 BSD-3-Clause 138 GPL-2.0 131 GPL-3.0+ 115 SUSE-Public-Domain 79 Artistic-1.0 41 Apache-2.0 And actually I haven't counted dual-licensing. Here's an even better script: % rpm -qai | awk '$1 == "License" { print $3 }' | grep GPL | wc -l 1316 % rpm -qai | awk '$1 == "License" { print $3 }' | grep MIT | wc -l 302
- belorn 10y agoThe link provides the API on how to poll github repositories for license data, but is a far cry from being a reliable method in measuring usage. Lets suggest following criteria for a survey: 1#, no duplicates. A survey with duplicate has no meaning. Github data in the blog post do not exclude dubplicates. 2#, no empty projects. A project with no data in it is not actually a project. The Github data do not exclude such projects. 3#, only project with code in them. A lot of github projects is text collaboration, like party planning, discussion around the latests online drama, and so on. Github data do not exclude those. 4#, only project with running code that is useful for at least 1 person. Random data, incomplete or abandon attempts is not actually "a software project". Github data do not attempt to run projects, and very much do not limit its data storage to only code that works. To my knowledge, only one license survey exist that passes those criteria, and that one was based on the curated repository of Debian. The study showed GPL to be heavily favored (80%), but the study concluded that more such studies (and discussion on research methodology) is highly needed.
- tunnuz 10y agoAlso relevant, this free and very accessible book from O'Reilly http://www.oreilly.com/openbook/osfreesoft/book http://www.oreilly.com/openbook/osfreesoft/book that explains the history and caveats of most open source licenses.
- kemitchell 10y agoHighly recommended.
- rando832 10y agoNice HN: Way to absurdly ignore half the sentence because of your bias: "When it comes to patents," Here's an example to show what this is like for something you don't have a bias about: "When it comes to morality, Trump is dead inside." HN response: downvote, downvote "What a warping of reality! Trump's doctor said he is healthy and there is no way a person could be dead inside and keep up his level of activity." lol, facepalm
- reitanqild 10y agoThis is fantastic IMO. More of this. I also think there could be room for something similar about code (but I haven't had time to read aosabook.org yet, so maybe that is wheree I'll find it.) A note on the Crockford joke: I think it is on IBM, not the lawyers: I think he describes somewhere the fun of getting a payment from IBM followed by sending an additional license entitling IBM to use the software for evil.
- Sanddancer 10y agoHe didn't get a payment, but he did give a license for "IBM, its customers, partners, and minions, to use JSLint for evil.” http://dev.hasenj.org/post/3272592502/ibm-and-its-minions http://dev.hasenj.org/post/3272592502/ibm-and-its-minions
- twhb 10y agoA bit off-topic, but I would be very interested in somebody making a case for why an OS license is better than a simple line like "This code is free for everybody to use as they wish." I've read about it plenty, but remain unconvinced. The OS software I write is for the good of everybody, not just its own popularity or the OS community. I'm fine with all uses of it, in whole or in part, whether or not I'm credited. The license reproduction requirement therefore feels like unnecessary noise, and I'd like to think that courts are sane enough that the warranty disclaimer is unnecessary too - is there any real court case where somebody has been sued for a defect in free, OS software, without an explicit warranty, and lost?
- bo1024 10y agoI have always wondered the same.
- zodiac 10y agoI'm not sure about the what advantages the MIT license has over your one-liner, but some people (eg Stallman) believe in using more restrictive mechanisms like https://en.m.wikipedia.org/wiki/Copyleft https://en.m.wikipedia.org/wiki/Copyleft, and your one-liner is inadequate for them
- monfrere 10y agoNot a lawyer, but I always thought maybe someone could take your code, modify it to produce variations A, B, C, the three major use cases of your code, and slap patents on those modified versions of your code. So then anyone who wants to use your code with any of those three use cases in mind (i.e., most people who would want to use your code) would then likely be in trouble. Or something like that. A second issue would be one the author of the article seems worried about, which is that without a warranty-free clause people might sue you for bugs in the code. If you're distributing your code, with a line like "free for everybody to use," there may or may not be implicit quality guarantees, according to the article.
- witty_username 10y agoHas any such lawsuit actually occurred?
- breakingcups 10y agoA very lovely article, I enjoyed it very much since it gives insight into the "syntax" of legal documents in the US. This article brought up a point I find very interesting. The MIT license (and a bunch of other licenses as well) are very US-oriented when it came to their writing, provisions, etc. I'd love to read a similar article exploring licenses like these from a, say, European point of view. Would the same constructs hold up in a German court, for example. What language is missing or superfluous?
- Iv 10y agoI can talk for France. I used to work in a lab depending from the CNRS and arriving there I learned about the French version of the GPL, BSD and LGPL, the CeCILL familly (CeCILL-A, -B or -C respectively) ( https://en.wikipedia.org/wiki/CeCILL https://en.wikipedia.org/wiki/CeCILL ) They claim compatibility with GPL, BSD and LGPL and also that CeCILL was necessary for valid open source licenses in France. That made me raise eyebrows on many levels: - Does it mean the GPL/BSD/LGPL is unenforceable in France? - Does it mean the CeCILL is unenforceable in other countries? - The CeCILL allows to relicense a work under a future revision of the license. I know some GPL projects do that, I personally am extremely suspicious of this possibility. I raised these points but never got good answers from law specialists. The guys I could reach were specialized in "intellectual property valorization" and actually did not know anything about open source. They also made me realize in the french version of the law, the notion that copyright protects a source code is extremely disputable: In France you can't patent or copyright an idea, and numbers and mathematical formulas are recognized as ideas. It is accepted that a computer algorithm is equivalent to a mathematical formula. Ergo, in a source code, you can't protect an algorithm but an implementation. That is, as I understood when pushing a bit more, variable names and whitespace structure are the only copyrightable things in a program. My understanding is that an obfuscater or a code formatter would likely remove any copyright claim from a source code when it comes to french laws. I wish we had an actually active Pirate Party or EFF to try push the limits over that nonsense.
- detaro 10y agoAFAIK German courts specifically have hold up the GPL, but there are some interesting points with other open-source: - CC0 exists because in German (and other countries') laws the only way for something to become public domain is expiry of copyright. CC0 puts it in clearer legal terms that you wish to give up all rights you can give up and not make use of all others. - German law added a "Linux-paragraph" that made it clear that if you grant usage rights to everyone, you can relinquish the right for "appropriate" payment, which added legal security. (Otherwise, if I perform work for you and you don't pay me, I could attempt to force you to pay a fair rate for my work, after the fact) - other licenses might not be as well-tested, and I've seen code offered under "MIT license translated and adapted to German legal concepts" or things like that. Which of course doesn't exactly make it easier to use in other contexts...
- xcopy 10y agothanks for share
- MindTwister 10y agoHuh? I submitted this 23 hours ago with the exact same url, glad to see som discussion though.
- deleted 10y ago[deleted]
- AstroJetson 10y agoIt happens, at one point there were 9 submissions round the Yahoo story.
- nickpsecurity 10y agoLicenses like MIT and BSD should be avoided due to the patent risk in favor of licenses that explicitly grant patent protection like Apache 2.0. The patent troll risk is just way too high. As rando said, companies like Microsoft are even open-sourcing code while raking in hundreds of millions from patent suits against open-source software. That this is even working for them shows the permissive licenses need to eliminate that tactic entirely.