5 ms·
Though worth noting that ASLv2 is not compatible with straight GPLv2 (the "or later" part of "version 2 or later" is crucial). This is why some projects dual-li
by kibwen 10y ago
Though worth noting that ASLv2 is not compatible with straight GPLv2 (the "or later" part of "version 2 or later" is crucial). This is why some projects dual-license as MIT/ASLv2, because MIT is compatible with GPLv2.
- KenoFischer 10y agoLLVM's proposed switch included a provision to make it explicitly compatible with GPLv2. That seems like a nice precedent to follow for other projects that are considering Apache 2 as their license.
- kibwen 10y agoI'd say that works for LLVM only because Apple can afford lawyers who can argue that provision if it ever came to that (not that I think it ever would). AFAICT, ASLv2 is superior to BSD/MIT in all practical respects except for the GPLv2 compatibility, and if it were so trivially easy to make a version of ASLv2 that didn't have that downside, then I feel like some company would have already done that and instantly created The One Permissive License To Rule Them All (and in the eyes of the law, bind them). Until such an exceptional provision becomes established precedent, I'd suggest that small projects stick to vetted licenses rather than pitching in with anything novel.
- int_19h 10y ago> AFAICT, ASLv2 is superior to BSD/MIT in all practical respects except for the GPLv2 compatibility Not for the companies. Many prefer MIT over ASL precisely because they don't want any sort of patent grants.
- riffraff 10y agoWhy do they prefer to avoid patent grants? It seems unreasonable to me.
- yarrel 10y agoIt is, but it's what they want.
- kibwen 10y agoAFAICT this is overstating the patent-related aspects of ASL. It doesn't require a patent grant or nullify any parents you hold, or even prevent you from suing others over misuse of those patents. All it does is provide mutually assured destruction: if you sue someone over the use of your patent within this software, then you forfeit any legal protection from others who have patents within this software. This is extremely company-friendly, because companies are the ones who tend to go around suing over patents, and also the ones who feel compelled to stock up on patents to use defensively.
- jabl 10y agoIf you're worried about the GPLv2 and ASLv2 incompatibility, why not dual license as ASLv2/GPLv2 then instead of ASLv2/MIT?
- JoshTriplett 10y agoBecause porcine flight seems more likely than many OpenSSL developers agreeing to license anything under the GPL?
- jabl 10y agoI wasn't thinking of OpenSSL specifically but rather as a general question. E.g. why is Rust ASL2/MIT licensed (my guess is that it's just what Graydon originally chose for whichever reasons and nobody cares enough to change it)?
- steveklabnik 10y agoIt was originally only Apache2, but MIT was added later to add GPLv2 compatibility.
- bonzini 10y agoDual-license MIT/ASLv2 is pointless, since MIT is not incompatible with ASLv2: it allows relicensing and is pretty much a subset of ASLv2. Likewise, LGPL/GPL/MPL is pointless because LGPL already allows you to take the work and relicense it under the GPL.
- hsivonen 10y agoDual MIT/ASLv2 is how Rust achieves GPLv2 compatibility while requiring contributions to be under the superior (to MIT) ASLv2 language, too. ASLv2/GPLv2 dual would achieve the GPLv2 compat goal without potential unintended other consequences arising from the MIT part. The old Mozilla tri-license had both LGPL and GPL to relieve recipients from following the (impractical) letter of LGPLv2.1 when choosing to do the LGPLv2.1 to GPLv2 step.