Commit 8b7bac1d authored by Cassandra Gould van Praag's avatar Cassandra Gould van Praag
Browse files

fixes #15

parent 91ed9bf0
Pipeline #10978 passed with stages
in 2 minutes and 17 seconds
...@@ -15,7 +15,44 @@ A guide to how to license your code and things you should consider ...@@ -15,7 +15,44 @@ A guide to how to license your code and things you should consider
--- ---
Coming soon **Contents**
{: .label .label-yellow } - [Why license your material](#why-license-your-material)
- [What license to choose](#what-license-to-choose)
- [How to apply the license and copyright notice](#how-to-apply-the-license-and-copyright-notice)
This page will describe why licensing is recommended, and considerations around protecting IP for commercial value. It will link to the [University recommendations on open source licensing](
## Why license your material
It is essential to license your research outputs so other users understand how you would like them to be re-used, and under what terms.
Important considerations around licensing include the potential for commercial use of your materials, attribution, and integration with any existing licenses if you are releasing material which builds on an existing source (for example, a plug in to FSL).
### Intellectual properties and commercial reuse
Material which you create while a student or staff at the University are the [Intellectual Property of the University of Oxford](
If your work has commercial potential, you should explore opportunities for issuing an academic only license and creating a system for commercial entities to pay for the use of your work. This is in line with [Oxford University Innovation (OUI) recommendations]( OUI are pleased to explore the commercial potential of your work with you and will set up services for commercial licensing.
### Attribution
You deserve to be credited for your work. Although there is an established norm to cite academic papers for the avoidance of plagiarism, this norm is not well established for academic code. Any license which you issue is a legally binding agreement; adding an attribution clause will go a long way to normalising the expectation that you should receive credit for the work you do.
### Existing licenses
If your code builds on existing material, the originators of that material may have issued it with a licence which requires you to share new material with the same level of freedom. This is know as a "share alike" licence. Please carefully check your source material for existing license and ensure you comply with any terms for re-use or distribution.
## What license to choose
In general, we recommend a [CC-BY-4.0 license]( This enables others to reuse your work as long as they attribute you as the originator. This license also allows the University to retain copyright.
The University also has detailed [recommendations on open source licensing]( Please review these recommendations if you are unsure whether a CC-BY-4.0 license is appropriate.
For a more complete exploration of software licensing, we recommend you visit the [The Turing Way handbook to reproducible, ethical and collaborative data science](
## How to apply the license and copyright notice
To apply a licence, you simply have to state the name of the licence somewhere in your material. This could be in the `README` file, or in a separate `LICENSE` file. You may wish to copy the full terms of the license text into the file, but this is not necessary. If you include a license file, it is good practice to include it in the [root directory]( of your project, to ensure it is easily found.
For the Copyright notice, you should include the below in our `README` and as a footnote on any published pages (replace `YYYY` with the year the material was created):
> Copyright, YYYY, University of Oxford. All rights reserved
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment