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

Dual License consideration APL2.0 / EPL2.0 #158

Closed
chandrasekhar1996 opened this issue Dec 28, 2021 · 2 comments
Closed

Dual License consideration APL2.0 / EPL2.0 #158

chandrasekhar1996 opened this issue Dec 28, 2021 · 2 comments

Comments

@chandrasekhar1996
Copy link

I am planning on using this layout library in my project which has Apache License 2.0 . I have a concern with the compatibility of the EPL2.0 license with Apache License. Would you be open to considering using a dual license EPL2.0 and APL2.0 which would be really helpful for all Apache License projects?

@uruuru
Copy link
Member

uruuru commented Jan 9, 2022

There are no plans towards dual licensing.

@Sytten
Copy link

Sytten commented Jul 17, 2023

@uruuru I would like to revive this issue considering the huge number of downloads on NPM and the likely high number of people that are currently not in compliance by pulling this library as peer dependency of other MIT licenses projects (like mermaid). The EPL 2.0 is really not a friendly license because using a JS bundler like webpack likely means that a commercial project is creating a derivative work and is in breach of the license.

I really see no benefit for elkjs to continue using EPL 2.0 (at least for the JS portion of the code) and even businesses willing to pay for the library currently can't obtain a more permissive license. An MIT or Apache 2.0 License would be my suggestion and if you are looking to commercialise it then I would suggest looking at the model used by Into.js.

Thanks for your consideration!

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

3 participants