Inbound FOSS IP Policies
The most common of all inbound FOSS policies is intellectual property (IP). If your company has any policy at all around inbound free and open source software, it’s probably because of IP concerns. An IP policy is intended to respect the license terms and the IP of the authors of FOSS projects, but it’s also there for the protection of the company’s own intellectual property.
The IP policy will require that all inbound FOSS be tracked and logged in some way. That log should include the name of the software, its license or licenses, where to find the source code for the project, and how the project is going to be used in the company. Often, the policy states that no FOSS can be used until it’s been approved by company ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access