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 #59

Closed
WizardUli opened this issue Apr 1, 2018 · 3 comments
Closed

License #59

WizardUli opened this issue Apr 1, 2018 · 3 comments

Comments

@WizardUli
Copy link

Hi

Would you consider changing the license to something more permissive like Apache license 2.0 (CadQuery is using it ;) ) or at least LGPL (if you really insist on using license from FSF. (FreeCAD is using it.))?

Please don't get me wrong. GPL makes sense for end-products for end-users but not for libraries, frameworks or anything designed to be extended and/or used in scripts.

Cheers
Michal

@fragmuffin
Copy link
Member

@grawp
Yes, I would definitely like to change the license.
Thanks for reminding me, I just put a restrictive license down to begin with before I had decided on a more permanent one.

Let me read over the nuances of each, and I'll choose another less restrictive licence this week.

Having the same license as cadquery makes a lot of sense, so I expect I'll use the Apache v2.0 as you said.

fragmuffin added a commit that referenced this issue Apr 4, 2018
@fragmuffin
Copy link
Member

@grawp
I've changed the license to Apache v2.0 as you suggested; I agree that having the same license as cadquery greatly simplifies people's usage of this library.

This change hasn't been released to PyPI, but it will be when the next change gets released.

@fragmuffin
Copy link
Member

@grawp
I just released v0.2.1 on pypi, but I've only now realised that PyPI's metadata still indicates a GPLv3 license.
I'll make sure this is fixed in the next release.

But in practical/legal terms, v0.2.1 is Apache v2.0 licensed, this can be proven by all LICENSE files in the cadquery-0.2.1 released tag in git.

Sorry for the mess 😢

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