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

License #3

Closed
davidbrochart opened this issue May 9, 2021 · 4 comments
Closed

License #3

davidbrochart opened this issue May 9, 2021 · 4 comments

Comments

@davidbrochart
Copy link

Any chance you can change the license to MIT or BSD?

@joouha
Copy link
Owner

joouha commented May 9, 2021

I might consider this - what's your reason for asking?

@davidbrochart
Copy link
Author

Just that they are more permissive, and GPL is often viewed as more problematic.

@fperez
Copy link

fperez commented May 19, 2021

First, thanks @joouha for this great tool! Just to add my two cents to this topic: obviously it's entirely your right to choose your license :) But I wanted to note that in general, the scientific Python/Jupyter ecosystem has settled on BSD (and similar) licenses overall. This happened organically over the years, following the lead of Python itself which is not GPL, but some of the reasoning behind it is well captured in this message from the creator of matplotlib, John Hunter, written back in 2004.

In general, if you relicense your code to be compatible with the rest of Jupyter, it will be easier to connect with the rest of the project, potentially reuse/integrate pieces of euporie elsewhere, etc.

You're 100% within your rights to keep it GPL if that is your preference, but that means the rest of Jupyter can't really use your code (Jupyter users, myself included, will obviously enjoy your contributions!) in any part of Jupyter, as we are not going to relicense all of Jupyter to GPL ever.

I hope this helps, and regardless of your decision, many thanks for this great contribution!

@joouha
Copy link
Owner

joouha commented May 21, 2021

Thanks for your message @fperez - your explanation certainly helps!

I'll admit I hadn't given as much thought to licensing as I probably should have. I think your point about being able to integrate more easily with the rest of the Jupyter ecosystem is compelling, and John Hunter's essay is certainly a very interesting and thought provoking read.

I've re-licensed euporie under the MIT license :-)

(Closed by 67f2942)

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

3 participants