Skip to content
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

GPL means I can't use this work in my MIT licensed project. #12

Open
winny- opened this issue Feb 22, 2014 · 2 comments
Open

GPL means I can't use this work in my MIT licensed project. #12

winny- opened this issue Feb 22, 2014 · 2 comments

Comments

@winny-
Copy link

winny- commented Feb 22, 2014

Hi! First off I want to thank you @Damgaard for creating an amazingly easy-to-use Python package for the Imgur API.

I am writing this issue today suggesting you reconsider relicensing your code under LGPLv3 so my little project and other differently licensed projects may enjoy the results of your open source contribution. As the sole copyright holder you have the right to relicense your work in upcoming releases/commits (see this StackOverflow question for details).

Some more information on the issue:

@Damgaard
Copy link
Owner

Thank you for using my package. I don't really have that much experience with licenses, I'll need to read up on it (thanks for the links) before I can consider changing the license.

@winny-
Copy link
Author

winny- commented Feb 24, 2014

@Damgaard I've learned some details about Python modules licensed under the GPL. The problem I talked about in the issue are kind of true. It appears to be a gray area since Python module imports are only used during byte-compilation and execution (I think), but like any other library it is still "called into".

From my new understanding, I think as long as I don't include pyimgur in a stand alone distribution (zipping it with my project, for instance), my MIT licensed code stays MIT licensed. However, as soon as pyimgur and my work are distributed together or otherwise "combined", the entire work becomes GPL — which works because my code is MIT licensed and MIT is GPL compatible. I would prefer to keep my work permissively licensed even in this scenario, so this is where LGPL would be preferable.

Bottom line: After some further research, I think my original point is moot. I also still believe it is a positive idea to relicense under LGPL for later releases, but please don't let my original argument above decide for you. The big benefit of my suggested change is there is less ambiguity with how pyimgur may be used.

Thank you for getting back to me. IANAL so please verify my suggestions.

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