I’ve written an article on using GPL code in your software, covering “the essentials” on:
- The GPL (GNU General Public License) and LGPL (Lesser GPL) *US spelling…
- Challenges of interpreting the GPL
- Key legal issues when incorporating GPL-licensed code in proprietary programs
- Issues and consequences arising from GPL violations.
The article doesn’t cover other open source licences. While GPL is the most well-known open source licence, an interesting issue is the apparent (let’s say alleged) trend away from copyleft open source licences (such as the GPL) towards permissive open source licences such as the Apache, MIT and BSD licences.
Whatever licence is used on a third-party components of your software, it is important from a legal and commercial perspective to ensure that you understand the implications. As outlined in my article, consequences of a GPL (or other) licence breach can include:
- Liability to the licensor or an injunction;
- Problems arising from IP audits or due diligence projects, which could have significant implications for a proposed business/asset sale, valuation, joint-venture or merger;
- Breaches of IP warranties or other contractual obligations to end-users; and
- Potential conflicts with end-user procurement policies (i.e. policies stating that all suppliers must fully comply with licensing requirements)