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

Relicense under dual Apache2/MIT #28

Closed
6 tasks done
hynek opened this issue Oct 28, 2014 · 8 comments
Closed
6 tasks done

Relicense under dual Apache2/MIT #28

hynek opened this issue Oct 28, 2014 · 8 comments

Comments

@hynek
Copy link
Owner

@hynek hynek commented Oct 28, 2014

structlog has historically been licensed under the Apache 2 license because it offers protection against certain patent-related jerk moves.

Unfortunately that also limits structlog’s usefulness because it’s incompatible with GPLv2 (yes I don’t like the GPL but I also don’t like “eye for an eye”).

Over at cryptography we’ve consulted an actual IP lawyer, and turns out a dual license fixes this: pyca/cryptography#1209

Therefore I’d like to re-license the project under a dual Apache 2/MIT license which gives me best of both worlds.

For that, I have to ask my contributors for permission. According to GitHub, that are the following ones:

Please be so kind and reply with something along of “Permission granted.” to this ticket and I’ll tick you off (this sentence has been edited, @radix is in fact capable of reading :)).

Thank you!

P.S. Changes by those who don’t agree will be re-written. So your veto won’t stop the change; sorry. :)

@hynek
Copy link
Owner Author

@hynek hynek commented Oct 28, 2014

Permission granted.

Loading

@radix
Copy link
Contributor

@radix radix commented Oct 28, 2014

Permission granted to relicense my changes to dual apache 2/MIT. (I can't tick the box)

Loading

@illenseer
Copy link
Contributor

@illenseer illenseer commented Oct 28, 2014

Permission granted.

Loading

@iffy
Copy link
Contributor

@iffy iffy commented Oct 28, 2014

Permission granted. And thank you for ticking me off :)

Loading

@gcbirzan
Copy link
Contributor

@gcbirzan gcbirzan commented Nov 6, 2014

Permission granted and sorry for the delay!

Loading

@hynek
Copy link
Owner Author

@hynek hynek commented Nov 6, 2014

Thanks everyone, I wish @daybarr would have agreed too but since his contribution was a simple typo fix, I’m going ahead anyway. Thanks everyone.

Loading

@hynek hynek closed this in 71e6964 Nov 6, 2014
@daybarr
Copy link
Contributor

@daybarr daybarr commented Nov 6, 2014

Permission granted for my tiny typo contribution ;) Sorry, I somehow missed the original notification. I wondered why I was being sent the updates...

Loading

@hynek
Copy link
Owner Author

@hynek hynek commented Nov 6, 2014

ha perfect thanks :)

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants