Organisations (usually specific employees) and authors of the program code are responsible for compliance with internal guidelines and are responsible for ensuring that all criteria necessary to license the software under an Open Source Licence are met. In particular, they are responsible for ensuring that no third party has rights to the software or part of the software that would prevent open source licensing. For example, if the code embedded in the software was developed during a project with an industrial partner or was developed by a third party.
This is often ‘delegated’ to legal officers, while there is a great deal of liability and risk of making mistakes about ownership. There is also a great commercial benefit in tracking property that can be offered for licensing and for sale.
For that reason, in some organisations, software must be registered in a repository even alongside the Github-like repository that researchers also use to distribute their code. In some organisations this repository is not used or its use is limited. Initiatives to implement it may have failed.
The roundtable will address learnings such as:
This webinar is organised by the Digital Innovations SIG. Join the Digital Innovations SIG to stay informed.
Was great to meet counterparts in my profession who may share my experiences, but who may also have other ideas and approaches.
Tim Moser
Netherlands Cancer Institute, Netherlands
Most experienced technology transfer crew in the Europe.
Krzysztof Maternicki
Jan Dlugosz University, Poland
Perfect balance of learning and networking.
Smiljka Vikic-Topic
University of Zagreb, Croatia
ASTP has excellent courses to immerse yourself into the world of tech transfer.
Qing Cai
Vrije Universiteit Brussel, Belgium
Good opportunity to discuss common issues with fellow professionals and to get updates about the community.
Giuseppe Visimberga
Leiden University, Netherlands
Join our newsletter and get the latest news