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

You have no license #26

Closed
MarkTraceur opened this issue Jan 26, 2014 · 7 comments
Closed

You have no license #26

MarkTraceur opened this issue Jan 26, 2014 · 7 comments
Labels
documentation Issues/PRs modifying the documentation.

Comments

@MarkTraceur
Copy link

In a cursory look through this repository, there is no license available. This means that contributors will be skittish, redistributors will be punishable under U.S. and other copyright law, and don't even get me started about redistributing modified copies.

Please say something about a license in your README, include the full text of the license you choose in a COPYING file, and (ideally) add copyright and license headers in each file in the project.

Thanks!

@waldyrious
Copy link
Member

👍

@kenany
Copy link

kenany commented Jan 26, 2014

Looks like BSD, but of course the full license text is required, especially since it is ambiguous as to whether it is BSD 2-clause or 3-clause at the moment.

@rprieto
Copy link
Contributor

rprieto commented Jan 27, 2014

Thanks a good point, thanks. I was tempted to go BSD3 (code can be redistributed / downstream modifications allowed / no warranties or damage liabilities / name cannot be reused for derivatives or endorsements) but I don't have a deep knowledge of licenses, especially if it comes to mixing code & content. Does you have any recommendations?

@waldyrious
Copy link
Member

I can't comment on the appropriateness of BSD2 vs. BSD3 (my personal choice would probably be BSD2), but just in case you're considering other (non-BSD) licensing choices, you might find this post which I came across the other day, potentially useful: I think offers a nice overview of the kind of projects where it makes sense to pick a permissive license as opposed to a copyleft license.

@zlatanvasovic
Copy link
Contributor

Why not MIT? MIT is the most universan and the most readable license ever (I don't want you have all rights licenses).

@rprieto
Copy link
Contributor

rprieto commented Jan 31, 2014

Fixed. Went with MIT which is very similar to BSD, but the permissions/restrictions definitely are easier to understand.

@rprieto rprieto closed this as completed Jan 31, 2014
@zlatanvasovic
Copy link
Contributor

Thanks.

2014-01-31 Romain Prieto notifications@github.com:

Fixed. Went with MIT http://opensource.org/licenses/MIT which is very
similar to BSD, but the permissions/restrictions definitely are easier to
understand.


Reply to this email directly or view it on GitHubhttps://github.com//issues/26#issuecomment-33755777
.

Zlatan Vasović - ZDroid

@waldyrious waldyrious added the documentation Issues/PRs modifying the documentation. label Sep 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Issues/PRs modifying the documentation.
Projects
None yet
Development

No branches or pull requests

5 participants