4 ms·
I wish the Clojure guys would come up with some clear and direct messaging around its license. When I started exploring Clojure one weekend a few months back,
by StevePerkins 13y ago
I wish the Clojure guys would come up with some clear and direct messaging around its license. When I started exploring Clojure one weekend a few months back, I found that it's the only language I've ever seen that uses the Eclipse Public License. In turn, the EPL is the only license I've ever seen where the FAQ is even more ambiguous and confusing than the license text itself!
I did some sniffing around to see what the practical effects (if any) are for applications written in Clojure, and on their own mailing list the topic is a bit of a mess:
https://groups.google.com/forum/#!topic/clojure/bpnKr88rvt8 https://groups.google.com/forum/#!topic/clojure/bpnKr88rvt8
https://groups.google.com/forum/#!topic/clojure/mGf_SuHsSGc https://groups.google.com/forum/#!topic/clojure/mGf_SuHsSGc
Everyone seems to agree that forking or modifying Clojure itself would trigger all sorts of license requirements (e.g. GPL-incompatibility, you might need to use the EPL, etc).
However, nobody on their mailing list seems to agree on what the licensing means for normal applications that happen to be written in Clojure and use its library at runtime. Is that a "derivative work", or not? Does the fact that you write applications in Clojure have any bearing on the licenses that you may choose?
I know that it's somewhat possible to mix the EPL with almost anything... because I've worked with some Aptana IDE's that are based on Eclipse, yet use GPL v3 with several paragraphs of caveats and exceptions. (http://www.aptana.com/legal http://www.aptana.com/legal , http://www.aptana.com/legal/aplgplex http://www.aptana.com/legal/aplgplex) Not sure about GPL v2.
I just don't want to have to think about this stuff AT ALL as an application developer who isn't making changes to the programming language or core runtime library. The murkiness on their own mailing list has definitely been a deterrent from my exploring Clojure more seriously.
- hga 13y agoHmmm, when looked into this a few days ago with an eye towards a Clojure port (in part a fork) what I remember finding is that the EPL allows separate "modules" to have a different license, although of course that couldn't be an incompatible one like the GPL based on the latter's linking requirements. The Aptana legal link looks pretty clear at first glance, "the EPL is not particularly compatible with the GPL". I think we would have heard by now if there were any viral problems with normal applications built on top of it, Clojure has been a very big thing in the Lisp world for years.
- spacemanaki 13y agoIANAL but I don't think you need to worry about this too much as an application or open source developer USING Clojure the language and Clojure's standard libs. This question and its answers on Stack Overflow points to an interpretation that makes sense intuitively to me, but again, not a lawyer, pretty ignorant of this stuff, etc... http://stackoverflow.com/questions/168254/can-you-write-gpl-software-using-cpl-libraries http://stackoverflow.com/questions/168254/can-you-write-gpl-... It would be nice if someone from the Clojure team would add a FAQ page or something about the license to clojure.org as it pertains to users of the language... Since this seems to come up a lot.