By Simon Hettrick
Deputy Director, Software Sustainability Institute
Co-Director, Southampton Research Software Group
25 April 2018 - FPSE Impact Network, University of Southampton @sjh5000 ORCID: 0000-0002-6809-5195
Simon Hettrick, the University of Edinburgh on behalf of the Software Sustainability Institute.
These slides: https://goo.gl/CoS7ao
www.software.ac.uk
rsg.soton.ac.uk
These slides: https://goo.gl/CoS7ao
These slides: https://goo.gl/CoS7ao
These slides: https://goo.gl/CoS7ao
Use
software
Fundamental to
results
Develop own code
69%
92%
56%
https://doi.org/10.5281/zenodo.1183562
65%
This is my insight into licensing. It doesn't constitute legal advice. If symptoms persist, consult a lawyer.
These slides: https://goo.gl/CoS7ao
Human-readable instructions
Computer-readable instructions
User is NOT allowed to view
User often has to purchase
User is allowed to view
Various options...
Note: open source does not mean free!
You are licensing the copyright related to the software
Proprietary (or closed) licence
Restricted licence, e.g. academic or non-commercial
Open licence
Copyleft, i.e. "viral licence"
Permissive licence
Public domain (not the same as CC0)
No licence
You can't licence something you don't own
These slides: https://goo.gl/CoS7ao
These slides: https://goo.gl/CoS7ao
Easy for anyone to reuse software: can do anything but must provide attribution and can't hold you liable
However software can be redistributed under different terms and modifications don't have to be shared
These slides: https://goo.gl/CoS7ao
If using a commercial licence, get it checked by a lawyer
If using an open-source licence, use a popular OSI-approved one
Don't write your own licence from scratch!
These slides: https://goo.gl/CoS7ao
Southampton Research Software Group
Research and Innovation services
Research Software Community
Software Carpentry training
These slides: https://goo.gl/CoS7ao
These slides: https://goo.gl/CoS7ao
https://softwaresaved.github.io/software-licensing-workshop/#/