Skip to content

Dual License clarification #32

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

Closed
HSH73 opened this issue Sep 11, 2023 · 3 comments
Closed

Dual License clarification #32

HSH73 opened this issue Sep 11, 2023 · 3 comments

Comments

@HSH73
Copy link

HSH73 commented Sep 11, 2023

Hi, please clarify the license. Currently the license refers only to AGPL-3-or later.
Given the fix: adjust license for dual licensing committed Feb 16, I assume you have re-licensed the software to a dual licensing model allowing users to choose between the AGPL and the MIT license (which is great, given many users from companies like us are not allowed to use AGPL'ed code as per their FOSS guidelines).
However, given currently the change to the dual licensing model seems to be be only viewable from the change in the package.json (7493edd), it would be great if you could clarify the /dual) license in the license folder (https://github.com/matmen/ImageScript/blob/master/LICENSE), which currently still refers only to the AGPL license (?).
For instance, adding the MIT license text with your copyright notice and a sentance like "Th_is code is dual licensed under the APGL-3-or later OR the MIT License. You can choose between either of those licenses_" would be extremly heplful.
Thank you!

@HSH73
Copy link
Author

HSH73 commented Nov 6, 2023

Hi matmen, sorry for bothering you again.
I see you added language regarding "multi-licenses", but I read it in a way as if both licenses were to apply cumulatively to the same code, which however does not seem to make sense, given the licenses contradict each other (in a way that the MIT license is totally "consumed" by the AGPL 3.0 which contains overriding obligations).
Could you please make clear in the license that this is a dual license where the user can decide if either MIT OR AGPL 3.0 applies?
Thank you

@matmen
Copy link
Owner

matmen commented Nov 6, 2023

Hey, no worries. Does something like

This software is licensed under the following license(s):
- GNU AFFERO GENERAL PUBLIC LICENSE, Version 3
- MIT License

== SPDX-License-Identifier: AGPL-3.0-or-later OR MIT ==

You may choose to comply with either one of the above
mentioned licenses, but a license must be chosen.

The corresponding license files can be found in the projects
root directory, prefixed with LICENSE, suffixed with their
corresponding SPDX identifier.

work for you?

@HSH73
Copy link
Author

HSH73 commented Nov 6, 2023

appriciated, much clearer then!

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