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
It is great to see all the work you have done so far 馃挴
That said the project seems to be missing a license file. 馃槺
No worry, I suggest you follow these few steps:
1锔忊儯 Choose a license. We suggest you use a permissive license that includes patent and contribution clauses. This will help protect developers and ensure the code remains freely available. We suggest you the Apache 2.0. Read here to learn more about licenses.
2锔忊儯 Add the the license file to your project. This guide may be helpful.
3锔忊儯 Add a section like the following at the end of your project's README.md file:
鈿狅笍 Make sure to update the abcdefghi and YYYY-MM-DD placeholders respectively with the short commit SHA and the commit date corresponding to step 2 above
## License
This software is licensed under the terms of the [Apache Licence Version 2.0](LICENSE).
The license file was added at revision [abcdefghi](https://github.com/Slicer/slicer_download/commit/abcdefghi) on YYYY-MM-DD, but you may consider that the license applies to all prior revisions as well.
Background
Without a license file, interpreting the licensing terms becomes complex. In a nutshell, code hosted on GitHub without a license is likely made available through section D. 5. License Grant to Other Users of the GitHub terms of service.
It is great to see all the work you have done so far 馃挴
That said the project seems to be missing a license file. 馃槺
No worry, I suggest you follow these few steps:
1锔忊儯 Choose a license. We suggest you use a permissive license that includes patent and contribution clauses. This will help protect developers and ensure the code remains freely available. We suggest you the Apache 2.0. Read here to learn more about licenses.
2锔忊儯 Add the the license file to your project. This guide may be helpful.
3锔忊儯 Add a section like the following at the end of your project's
README.md
file:abcdefghi
andYYYY-MM-DD
placeholders respectively with the short commit SHA and the commit date corresponding to step 2 aboveBackground
Without a license file, interpreting the licensing terms becomes complex. In a nutshell, code hosted on GitHub without a license is likely made available through section D. 5. License Grant to Other Users of the GitHub terms of service.
Reading issue
No license does not allow commercial or private use
is also informative.Links
Disclaimers
I am not a lawyer. As such, my suggestions can not serve as legal advice.
This comment was adapted from my GitHub saved replies, it is licensed under a Creative Commons Attribution 4.0 International License and you are welcome to reuse it.![Creative Commons License](https://camo.githubusercontent.com/5a78a346d2d7d167ef8a84ce2e9fa150a8c7bc61065c9fdd6af784705d3af3ab/68747470733a2f2f692e6372656174697665636f6d6d6f6e732e6f72672f6c2f62792f342e302f38307831352e706e67)
The text was updated successfully, but these errors were encountered: