@idhamari It is great to see all the work you have done so far :100:
That said the project seems to be missing a license file. :scream:
No worry, I suggest you follow these few steps:
[ ] :one: 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.
[ ] :two: Add the the license file to your project. This guide may be helpful.
[ ] :three: Add a section like the following at the end of your project's README.md file:
:warning: 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.
cc: @sjh26
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.
Reading issue github/choosealicense.com#196 (No license" does not allow commercial or private use) is also informative.
Links
Description
Link
Which open source license is appropriate for my project?
@idhamari It is great to see all the work you have done so far :100:
That said the project seems to be missing a license file. :scream:
No worry, I suggest you follow these few steps:
[ ] :one: 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.
[ ] :two: Add the the license file to your project. This guide may be helpful.
[ ] :three: Add a section like the following at the end of your project's
README.md
file::warning: Make sure to update the
abcdefghi
andYYYY-MM-DD
placeholders respectively with the short commit SHA and the commit date corresponding to step 2 abovecc: @sjh26
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.
Reading issue github/choosealicense.com#196 (
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.