This has been discussed as nauseam before: http://groups.google.com/group/clojure/browse_frm/thread/6e99caafcf2bbedf/b5519cc219a5baeb
Nothing has changed, so let's give it a rest, please. Rich On Sat, Aug 29, 2009 at 4:11 AM, John Harrop<jharrop...@gmail.com> wrote: > This is a problem. > The GPL is a very popular open source license. If a language does not permit > developers to use the GPL, that language may be severely reducing the number > of developers willing to adopt it. > It would be desirable for clojure.lang and clojure.core to use a modified > license, something perhaps describable as "EPL with classpath exception", > that expressly allows linking with GPL code (with classpath exception or > similar to avoid violating the GPL instead). > Alternatively, dual-licensing lang and core under both the GPL and the EPL > would be possible. Thanks to the contributor agreements, it wouldn't be > necessary to track down all the contributors and get their individual > permission for this, unless the agreements had reciprocal clauses limiting > how Rich could relicense the code base. (I haven't seen them, so wouldn't > know.) > Regardless, this problem bears thinking about and perhaps eventually doing > something about. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---