This repository does not appear to have a license.
Without a license, no one is allowed to download, copy, modify, or use your code — even though the repository is public.
Since your repo is public, you should provide a license to explicitly tell others how they may use your work. This typically means publishing your software under one of the OSI approved licences, or in the case of non-code contributions one of the Creative Commons licences that supports derivative works. REG's default choices are:
Note that to change the license of an existing project, you need the permission of all copyright holders, i.e. everyone who has contributed. This is one reason to add a license early on.
What to do
1. Choose a license
To select the best license for your repo you may wish to use one of the licenses listed above or use choosealicense.com or opensource.org/licenses to help you choose.
2. Add your license to the repository
Follow the GitHub docs on how to add a license to your repository:
- Go to the repository root
- Click Add file → Create new file
- Name the file
LICENSE, LICENSE.md, or LICENSE.txt
- Click Choose a license template and select one that fits your needs
3. Close this issue
Once you've added a license, please close this issue.
If this repository is intentionally unlicensed, please close this issue with a comment explaining why. If you want to forbid use of your code, we still recommend adding a proprietary license to make your intent clear.
This bot is run by the REG Open Source Service Area. If you have any questions, please refer to the Turing's Open Publication of Research Outputs Policy Statement and REG's Open Source Policy or contact the REG Open Source Service Area.
This repository does not appear to have a license.
Without a license, no one is allowed to download, copy, modify, or use your code — even though the repository is public.
Since your repo is public, you should provide a license to explicitly tell others how they may use your work. This typically means publishing your software under one of the OSI approved licences, or in the case of non-code contributions one of the Creative Commons licences that supports derivative works. REG's default choices are:
Note that to change the license of an existing project, you need the permission of all copyright holders, i.e. everyone who has contributed. This is one reason to add a license early on.
What to do
1. Choose a license
To select the best license for your repo you may wish to use one of the licenses listed above or use choosealicense.com or opensource.org/licenses to help you choose.
2. Add your license to the repository
Follow the GitHub docs on how to add a license to your repository:
LICENSE,LICENSE.md, orLICENSE.txt3. Close this issue
Once you've added a license, please close this issue.
If this repository is intentionally unlicensed, please close this issue with a comment explaining why. If you want to forbid use of your code, we still recommend adding a proprietary license to make your intent clear.
This bot is run by the REG Open Source Service Area. If you have any questions, please refer to the Turing's Open Publication of Research Outputs Policy Statement and REG's Open Source Policy or contact the REG Open Source Service Area.