Hi Aspasia Clojars and the Software Freedom Conservancy have been looking at the EPL 2.0 license and the impact of Clojure libraries adopting it, particularly around GPL compatibility. However I suspect that even if all Clojure libraries adopt the GPL compatibility clause, it would still need Clojure itself to adopt it for people to be able to use GPL software compliantly.
You can see a little bit of discussion around this at http://dev.eclipse.org/mhonarc/lists//epl-discuss/msg00158.html. However the CliffsNotes that came out of that conversation and the EPL-2.0 FAQ <https://www.eclipse.org/org/documents/epl-2.0/faq.php> were: Q: What is the impact of adding a secondary GPL license? <https://www.eclipse.org/org/documents/epl-2.0/faq.php#h.lgjcpvoq08a9> A: It is almost the same as dual licensing EPL/GPL Q: How can I upgrade a project from EPL-1.0 to EPL-2.0? <https://www.eclipse.org/org/documents/epl-2.0/faq.php#h.tci84nlsqpgw> A: The EPL allows new versions of the license to be adopted by projects with little work. A project can use the new version by simply updating the file headers and notices. It would be good practice to discuss this before relicensing though. Q: How can I upgrade a project to EPL-2.0 with GPL secondary license? <https://www.eclipse.org/org/documents/epl-2.0/faq.php#h.cktcxkzh8ks4> A: You must gain permission from all copyright holders to re-license the content (Ed: Projects with a CLA would allow you to do this, as you have already gotten approval from contributors.) Q: Some organizations do not use GPL-licensed content. What are the impacts of licensing a project with EPL-2.0 + GPL secondary license? <https://www.eclipse.org/org/documents/epl-2.0/faq.php#h.ofnb7ks8rr0y> A: While the EPL-2.0 has a concept called "Secondary Licenses", should an adopter not want to use the Secondary License, then the entire construct can simply be ignored. The code can be consumed purely under the EPL-2.0 without any concerns. You should check the original sources for these questions and answers for their full context, as I've edited them here for brevity, hopefully with little loss in precision. Alex: it looks like this was your email about concerns <http://dev.eclipse.org/mhonarc/lists//epl-discuss/msg00043.html> you and Rich had. I can see Mike Milinkovich had some followups with answers, do they satisfy your concerns about the definition of derivative works? I've created issues for Leiningen <https://github.com/technomancy/leiningen/issues/2358> and Clojars <https://github.com/clojars/clojars-web/issues/663> to discuss the EPL-2.0 license in the context of new project templates, and also whether and how Clojars could help projects migrate to EPL-2.0 + GPL. Thanks, Daniel. On Wed, Nov 22, 2017 at 7:22 AM Alex Miller <a...@puredanger.com> wrote: > Hi Aspasia, > > We provided some feedback in the early discussions around EPL 2.0. I > haven't looked closely at the final result, but I don't think a lot of > those concerns were addressed and it's unlikely that Clojure will switch to > EPL 2.0. > > Alex > > > On Tuesday, November 21, 2017 at 11:56:35 AM UTC-6, Aspasia Beneti wrote: >> >> Hi there, >> >> are there any plans of licensing Clojure with EPL 2.0 in the future? I am >> interested in terms of GPL compatibility which as stated here >> <https://en.wikipedia.org/wiki/Eclipse_Public_License> : >> >> *In terms of GPL compatibility, the new license allows the initial >> contributor to a new project to opt in >> <https://en.wiktionary.org/wiki/opt_in> to a secondary license that >> provides explicit compatibility with the GNU General Public License >> <https://en.wikipedia.org/wiki/GNU_General_Public_License> version 2.0, or >> any later version.* >> >> Thanks in advance >> Aspasia >> >> -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
