Update LICENSE to AGPL v3 - #182
Merged
Merged
Conversation
See Discussion #180
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Discussion #180.
4.0.0-beta2 is the last source release and 3.0.0 is the last binary release that is MIT-licensed. All source code in master before this PR is merged is MIT-licensed as well. All source code and releases of any form including and after this commit will be AGPL v3 licensed.
This will likely not impact you if you just use this as a tool on your local computer to translate source code as the project intends. It primarily impacts users that embed the core JavaToCSharp library into their applications, or use the CLI as an automated tool as part of an open-source or commercial platform. See #180 for more details.
Commercial support and licensing is available for any organizations that need a different license.