Program agenda:
- What is open-source software
- Different types of open-source software
- Defining permissive and copyleft licenses
- Common misperceptions
- Obligations and compliance related to OS software licensing
- How open-source software licenses may create risks to a university’s IP portfolio
- Patents and OS licenses – can they co-exist?
- How to educate university faculty and researchers to be mindful of open-source activities and the university’s IP goals
University faculty, researchers, and students typically utilize open-source software to facilitate research or incorporate into their own innovations because it is easily accessible, free of charge, and contains useful features.
But don’t mistake the free-of-cost nature as also meaning free of legal obligations or the potential to impact your university’s commercialization efforts that incorporate OS code. In addition to copyright and trademark compliance, there may also be complications with funding agencies, patent holders, and your own ability to pursue patents or other forms of IP protection.
On top of that, the issues surrounding open source are often misunderstood by researchers (and sometimes by TTOs), making it essential that you have a solid foundation of OS know-how to answer faculty questions as well as to plot your IP strategy.
There are two primary types of open-source licenses: permissive and copyleft, with many variations within those broader categories. Evaluating each and knowing which license is right for your situation – and what obligations and complications they may introduce — is crucial to navigating this tricky area.
To help you and your faculty gain a solid understanding of this often misunderstood topic – and incorporate that knowledge into your IP protection plans — we’ve tapped IP attorney Tyson Benson to lead this practical one-hour program.
