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

[Suggestion] Add License (or not) #28

Closed
JordanForeman opened this issue Mar 11, 2015 · 4 comments
Closed

[Suggestion] Add License (or not) #28

JordanForeman opened this issue Mar 11, 2015 · 4 comments

Comments

@JordanForeman
Copy link

This isn't my decision to make, so @kyleshay do what you will. But there are implications of not licensing your code. It looks like this repo is fairly popular, and if it continues to pick up traction you might want to consider adding a license. choosealicense.com is a pretty great resource for this.

This is really just a suggestion, and you can definitely keep this code unlicensed if you want, in which case you can just mark this issue as resolved.

@SunburnedGoose
Copy link
Member

+1

@kyleshay
Copy link
Member

Any suggestions are welcome!

@SunburnedGoose
Copy link
Member

MIT is what I use most often, just requires attribution for your original work. GPL requires that anyone who uses your code must be open-source too.

@loganfuller
Copy link

+1 for MIT

kyleshay added a commit that referenced this issue Mar 19, 2015
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

4 participants