Hosts: Kate O'Neill, Robert (Bob) Turner
September, 2022
Thanks for coming, thanks to the conference organisers, thanks to those who have advised!
I'm not a legal professional and I can't advise on the law.
::: incremental
The right by law to be the entity which determines who may publish, copy and distribute a piece of writing, music, picture or other work of authorship.
https://en.wiktionary.org/wiki/copyright
- Berne Convention of 1886: Copyright is immediately bestowed upon a work the moment it is created, without requiring any registration.
:::
If you're a researcher, probably not you!:
::: incremental
- Staff - usually the university (UK law, US law).
- Research students - usually the university (e.g. University of Sheffield student IP).
- Different rules for undergrads.
- Funded research can have specific agreements in place - check with your PI, or your funding agreements.
:::
::: incremental
- Gives right to use copyright material in specific ways, without changing ownership.
- No license : no right to copy (or to use).
:::
From the UK R&D Roadmap, OGL 3
:::::::::::::: {.columns} ::: {.column width="50%"} "Copyleft" e.g. GPL3 ::: ::: {.column width="50%"} More permissive e.g. MIT ::: ::::::::::::::
Your organisation may have policy / guidance.
- Not recommended:
- Lack of disclaimer
- Lack software specific terms
- License compatibility problems
Should the organisations we work for or study at grant us permission to license the code we produce as we chose?
Can we make good decisions on whether code should remain closed source for commercial reasons? Is more support needed?
How do we ensure copyright and licensing are correctly managed for projects where people from multiple organisations contribute code?
How much does the issue of licensing cause useful code to languish on researchers and RSEs laptops, compared with other barriers?
Thanks again to everyone involved!