You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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.
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?
The text was updated successfully, but these errors were encountered: