Updates license from GPL to LGPL #18
Open
Conversation
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
LGPL license allows this package to be used in a different (proprietary) licensed projects without having to make its source code available, while keeping the mysql-import library open source.
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.
LGPL license allows this package to be used in a different (proprietary) licensed projects without having to make its source code available, while keeping the mysql-import library open source.
With GPL-3.0 license, if someone uses the mysql-import package in their project, it MUST be also GPL license and must share the source code.
Explanation here: https://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL
That's why I'm proposing a change to the LGPL license.