-
Notifications
You must be signed in to change notification settings - Fork 50
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
Missing license info #11
Comments
Perhaps. Is it necessary? I see that also there is a way to just mention it in the README, but again, it's not obligatory (because of "may include"). I really don't want to add unnecessary files or to pollute sources. But I could include that phrase in README if |
IANAL, but reading the license, it sounds like the text itself needs to be physically present somewhere in the repo (which makes sense to me because you are basically enumerating the rights you are granting). I understand your reasoning behind wanting to minimize the number of files. Personally, I would opt for a Sidenote: I would also personally include the license copy in the header of each file; that way, if a consumer chooses to only use a subset of your repo (e.g. one of the examples), it's clear who owns the copyright and under what license it's being made available. |
hello, licensing your code would be very welcome, i'd like to use it :) If you just create the file LICENSE via github online it will make a little license selector where you can just click a template |
I see in
Cargo.toml
thatlicense
is set to"MIT"
but I don't see aLICENSE
file anywhere in the repo or headers on any of the source/example files. Would it be possible to get these added?The text was updated successfully, but these errors were encountered: