Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider switch to a GPL-compatible license #82

Closed
Waquo opened this issue Jul 1, 2014 · 1 comment
Closed

Consider switch to a GPL-compatible license #82

Waquo opened this issue Jul 1, 2014 · 1 comment

Comments

@Waquo
Copy link

Waquo commented Jul 1, 2014

Hi,
a quick glance at the source of mori and the GPL leads me to believe that it is not possible to use mori in GPL-licensed code, whereas using the same data-structures from GPL-licensed code written in ClosureScript is no problem at all.

I'm assuming that using the same license (EPL) both for mori and for ClojureScript with opposite outcomes was not intentional.

As I understand it (IANAL), using standard ClojureScript data-structures is not a problem, as they are accessed through a "Standard Interface" as defined by the GPL:
http://www.gnu.org/licenses/gpl-3.0.en.html

A “Standard Interface” means an interface that either is an official standard defined by a
recognized standards body, or, in the case of interfaces specified for a particular
programming language, one that is widely used among developers working in that
language.

While the fact that ClojureScript is implemented in a GPL-incompatible license is not a problem, this does not appear to apply to mori.

Unless I'm missing something, mori is just a library under a GPL-incompatible license and as such not usable in work licensed under the GPL.

@swannodette
Copy link
Owner

Thanks, but no license change will be considered at this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants