Skip to content

Update LICENSE to be a bit more explicit #47

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

Merged
merged 1 commit into from
Mar 24, 2016
Merged

Update LICENSE to be a bit more explicit #47

merged 1 commit into from
Mar 24, 2016

Conversation

EdwardBetts
Copy link
Contributor

Make it clear right away that this library is LGPL version 2.1 or later.

Make it clear right away that this library is LGPL version 2.1 or later.
@derek73
Copy link
Owner

derek73 commented Mar 23, 2016

Why is that important? I can choose whichever license I want and I did not choose the current license with any awareness of which license would be better. I've been considering changing the license to MIT just so it was the same as Python but I was under the impression LGPL and MIT are compatible.

@EdwardBetts
Copy link
Contributor Author

I've packaged python nameparser for Debian. It should be available soon.

I'm not a full Debian Developer so I had to have my package reviewed by a mentor. He suggested that I might ask you to make the license more specific. The full text description already says version 2.1 or later, so I thought it doesn't hurt to say it near the beginning of the file.

I think the switch from LGPL to MIT is a good idea. The FSF discourages the use of the LGPL.

You're right that LGPL and MIT are compatible.

@derek73 derek73 merged commit 8b33b02 into derek73:master Mar 24, 2016
@EdwardBetts EdwardBetts deleted the patch-2 branch April 12, 2016 13:42
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

Successfully merging this pull request may close these issues.

2 participants