You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cargo.toml lists the license as MIT, but there is no copy of the license in the repo.
If you add a copy of the MIT license in a file named LICENSE in the repo root (remember to put the correct copyright year(s) and author(s)), GitHub will be able to recognize and show this information in the web UI when looking at the repository, which makes it faster and easier for people to see what license this project is released under.
The text was updated successfully, but these errors were encountered:
I was thinking about this some more and came to the conclusion that it would be beneficial for anyone wanting to distribute a copy of this piece of software if you included a copy of the license in the repo, because the terms of the MIT license itself state:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
And if no copy of the license is included in your license then anyone wanting to distribute the software wouldn't know what years to put in the copyright notice of the license. I guess they could look at the git commits, but really only you the author has the power of stating the years IMO.
The
Cargo.toml
lists the license as MIT, but there is no copy of the license in the repo.If you add a copy of the MIT license in a file named
LICENSE
in the repo root (remember to put the correct copyright year(s) and author(s)), GitHub will be able to recognize and show this information in the web UI when looking at the repository, which makes it faster and easier for people to see what license this project is released under.The text was updated successfully, but these errors were encountered: