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

switch to MIT license #183

Closed
8 tasks done
BurntSushi opened this issue Jun 23, 2017 · 10 comments
Closed
8 tasks done

switch to MIT license #183

BurntSushi opened this issue Jun 23, 2017 · 10 comments

Comments

@BurntSushi
Copy link
Owner

BurntSushi commented Jun 23, 2017

The WTFPL causes people to not want to use this library. Historically, I've been against changing the license mostly because it's just a pain to do so. Ideally, we'd like to get a sign off from all people that have made non-trivial contributions. (And if we can't, we either need to stop the re-licensing process or remove/rewrite those contributions. I'm not particularly inclined to the do latter, but if we can do the former, than we should.)

So, this issue is going to track the relicensing progress. I'll start by listing some of the major contributors, where I interpreted "major" as "100 lines of code or more."

@BurntSushi
Copy link
Owner Author

Once everyone has signed off, we will switch to the MIT.

@rjeczalik
Copy link
Contributor

MIT 👍

@sqs
Copy link
Contributor

sqs commented Jun 23, 2017

Sounds good to me. I consent to the relicensing.

@halostatue
Copy link
Contributor

👍 I affirm relicensing of my contribution.

@bbuck
Copy link
Contributor

bbuck commented Jun 23, 2017

I will consent to relicensing as well.

@sethwklein
Copy link
Contributor

MIT is fine with me.

@cespare
Copy link
Collaborator

cespare commented Jun 23, 2017

I'm fine with MIT.

@ttacon
Copy link
Contributor

ttacon commented Jun 23, 2017

Sounds good to me!

@BurntSushi
Copy link
Owner Author

Thanks everyone!

... That was much easier than I thought.

@thaJeztah
Copy link

@BurntSushi are there plans to tag a new release, now that the license changed?

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

9 participants