-
Notifications
You must be signed in to change notification settings - Fork 213
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
Please, consider to specify a license #12
Comments
lol |
Funny. How can we choose a license if it's contributed by sooo many people |
Ask the contributors and choose one which they are happy; future contributions should agree with the license. In my opinion it's better to do that than defaulting to the laws, that the most of us, we don't know and in my case I don't exactly understand, however you're free to do what you want. |
Hey, |
For me looks ok, because I'm clear what I could do with this without hiring a lawyer. |
WTF License is that ROFLMFAO |
10/10 license |
"In the event that you happen to make a zillion bucks off of |
someone please close this issue |
First of all, thanks to release this work on a public repository.
Nonetheless, this repo doesn't have any concrete license (or it isn't easy to see), so I would like that you consider to choose one to avoid the confusion that it causes with its absence, the work has applied the default copyright laws which the most of the people we aren't sure the implications because we aren't lawyers.
This page may help you to decide which one is more convenient for you and all the benefits that an open license has over a closed one, however, don't get me wrong, choose the one that fits better to your specific case, independently if it's open or not.
Thanks for considering.
The text was updated successfully, but these errors were encountered: