alan-turing-institute / alan-turing-institute/github-example
Adding a licence to your repository
- Dominant language
- No language data
- Stars
- 0
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
### 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:
- [BSD-3-Clause](https://opensource.org/license/BSD-3-clause) for [permissive](https://en.wikipedia.org/wiki/Permissive_software_license) source code licencing.
- [AGPL-3.0](https://www.gnu.org/licenses/agpl-3.0.en.html) for [copyleft](https://en.wikipedia.org/wiki/Copyleft) code licencing.
- [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0) for [permissive](https://en.wikipedia.org/wiki/Permissive_software_license) licensing of non-code content.
- [CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/deed.en) for [copyleft](https://en.wikipedia.org/wiki/Copyleft) licensing of non-code content.
**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](https://choosealicense.com/) or [opensource.org/licenses](https://opensource.org/licenses) to help you choose.
#### 2. Add your license to the repository
Follow the GitHub [docs](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository) on how to add a license to your repository:
1. Go to the repository root
2. Click **Add file** → **Create new file**
3. Name the file `LICENSE`, `LICENSE.md`, or `LICENSE.txt`
4. 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](https://mathison.turing.ac.uk/page/2239) and REG's [Open Source Policy](https://alan-turing-institute.github.io/REG-handbook/docs/how_we_work/open_source_policy/) or contact the REG Open Source Service Area.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.