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.
This course gives an in-depth understanding on managing contract portfolio, including research contracts, license agreements, and other collaboration agreements.
Ram Siddappa
Erasmus MC, Netherlands
A lot of fruitful discussions with experienced peers. Very helpful sessions.
Sara Matt-Leubner
University of Innsbruck, Austria
Working and Learning with old and new friends – best way to do it!
Sara Matt-Leubner
University of Innsbruck, Austria
Always simply inspiring! That is ASTP.
Filip Auinger
Palacký University Olomouc, Czech Republic
As always, superb topics and inspirational speakers. Great networking. Well worth the time out of the office!!! Great work HQ, thank you.
Peter Deakin
Chalmers University of Technology, Sweden
Join our newsletter and get the latest news