4-1-licensing.qmd

## Licensing

Reusing other researcher's work is inherent in science. Licensing plays a central role for reuse, so we should know how it works.
	
{{< video https://www.youtube.com/watch?v=WjC171bOwLQ >}}

In my workshops on open and reproducible research licensing often comes up as a topic of fear.

*What am I allowed to do? Should I better let the legal department decide? How do I avoid going to jail?*

Most of the time choosing a license is actually quite simple. So let me help you loose your fear of it! 🤗

### Choosing a license for texts, data, media, ...

I really like the Creative Commons licenses for most research outputs (and other things I produce, like [this booklet](/license.qmd)).

They are easy to understand and to pick. On the CC-website you can find a simple tool to help you choose your license:

**[creativecommons.org/choose](https://creativecommons.org/choose)**

In research we want to almost always use the CC-BY or CC0 license.

- [CC0](https://creativecommons.org/publicdomain/zero/1.0/) (also known as CC0 1.0 Universal) means that the output is in the public domain and can by used by everyone for anything.
- [CC-BY](https://creativecommons.org/licenses/by/4.0/) (also known as Attribution 4.0 International) requires the user to give credit to the creator but gives freedom on what can be done with the output. This is the license I use 90% of the time.

#### Why not non-commercial?

[CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/) is another license I often see used, but I do not like it in the context of research. Why? The "NC" for non-commerical prohibits commercial use for anyone but the owner. That means, for example, that educators (like me) cannot use it, if there are fees or commercial learning platforms involved. Even blogs and Wikipedia struggle with NC if there are commercial derivatives or components. Read more here.


### Choosing a license for software

Software needs specific licenses. So for software there is another website you can use for choosing a license.

**[choosealicense.com](https://choosealicense.com)**

Again there is a license that works for most open projects: the MIT license.

::: captioned-image-container
![https://choosealicense.com](images/mit-license.png){width=50% fig-alt="Screenshot of https://choosealicense.com section 'I want it simple and permissive'"}
:::

That seems pretty simple, right? For more complex situations and when you have to worry about license compatibility of your code with software components that you use, please check out:

- The Turing Way chapter on [License Compatibility](https://the-turing-way.netlify.app/reproducible-research/licensing/licensing-compatibility)
- Talk "[All you need to know about Software Licenses](https://zenodo.org/record/8246557)" by Tobias Schlauch

### Other

For other licenses, such as for hardware, choosealicense.com also has help for you:
[choosealicense.com/non-software](https://choosealicense.com/non-software/)

I hope this short intro to licensing was helpful to you! Please note that I am not a legal expert but a self taught open science enthusiast.