Skip to content

Remove section on proprietary code inclusion in copyleft #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
copernicat wants to merge 1 commit into
base: lfc194_update_2026
Choose a base branch
from
Open

Remove section on proprietary code inclusion in copyleft #147

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions ...urse Content/Implementing Open Source License Compliance Management (LFC194).md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -542,12 +542,6 @@ This type of failure can be discovered using a dependency tracking tool that sho

It can be prevented by offering training to engineering staff on how to avoid linking software components with licenses that conflict with their open source policy and by continuously running the dependency tracking tool over the build environment.

#### Inclusion of proprietary code into copyleft open source

This type of failure can be discovered using audits or scans by tools to identify and analyze the source code that you introduced to the open source component.

It can be avoided by offering training to engineering staff and conducting regular code audits.

### License Compliance Pitfalls

We will now discuss issues specific to license compliance. Like the previous section, this is not intended to be an exhaustive list. However, it should help you understand and avoid the most common license compliance-related challenges. Each of the points discussed below assumes discovery through the manual or automated review of the open source code included in the product or service that you are planning to release.
Expand Down