Skip to content

Update Introduction to Open Source License Compliance Management (LFC… #142

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

Merged
winterrocks merged 1 commit into from
Apr 16, 2026
+1 −1
Merged

Update Introduction to Open Source License Compliance Management (LFC… #142

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
2 changes: 1 addition & 1 deletion ...e Content/Introduction to Open Source License Compliance Management (LFC193).md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -295,7 +295,7 @@ Depending on the Open Source license(s) involved, your compliance obligations ma
5. **Reciprocity.** You may need to ensure that modified versions or derivative works source code is made available and released under the same license that governs the Open Source component.
6. **Other Terms.** The Open Source license may have other obligations or conditions, and these can be terms that may touch upon topics like patent grants to you or from you, and the Open Source license may restrict the use of the copyright holder name or trademark, may require modified versions to use a different name to avoid confusion, or may terminate upon any breach.

### Open Source Compliance Issues that May Occur During the Distribution of Software
### Open Source Compliance Issues that May Occur With SaaS and Web Services

Some Open Source licenses include conditions that are triggered when software is accessed or used over a computer network. In these cases, license obligations may apply even if the software is not distributed in the traditional sense. For example, server-side applications accessed through a web interface can activate these requirements. Under all versions of the [Affero General Public License (AGPL)](https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License), if users interact with a modified program remotely through a computer network, the service operator should make the corresponding source code available to those users.

Expand Down