Update Introduction to Open Source License Compliance Management (LFC…#138
Update Introduction to Open Source License Compliance Management (LFC…#138
Conversation
…193).md Making consistent with updated online LFC193
| @@ -297,7 +297,9 @@ Depending on the Open Source license(s) involved, your compliance obligations ma | |||
|
|
|||
| ### Open Source Compliance Issues that May Occur During the Distribution of Software | |||
There was a problem hiding this comment.
This heading is something that we could/should reword a bit.
The chapter is talking more about "hidden" or "silent" "distribution or possible network license (AGPL (also SSPL, but that's not an open source license) issue and this heading does not really reflect that.
Some ideas (quick and needs to be discussed with broader group):
- Open Source License Compliance Issues with network licenses and silent client-side code executions
- Open Source License Compliance Issues with AGPL and similar license and executing JavaScript or similar code on client side browsers
There was a problem hiding this comment.
opened issue - we can discuss in next call.
There was a problem hiding this comment.
opened issue - we can discuss in next call.
Good. I think that after a couple of months not looking at the material, new "issues" come up.
|
|
||
| - Who is the software component distributed to? | ||
| - Who is the software component distributed to (i.e. distributed internally or externally to the Organization)? | ||
| - ***To which countries the software is distributed?*** |
There was a problem hiding this comment.
It is good that the question has: "In the context of Open Source license compliance".
winterrocks
left a comment
winterrocks
left a comment
There was a problem hiding this comment.
Good changes. I added a comment about the heading:
Open Source Compliance Issues that May Occur During the Distribution of Software
that we may want to reword a bit.
| In the context of Open Source license compliance which of the following questions are important to ask around the distribution of software? Select all answers that apply. (MULTIPLE CHOICE - PLEASE ADD FALSE QUESTIONS ***LIKE THIS***) | ||
|
|
||
| - Who is the software component distributed to? | ||
| - Who is the software component distributed to (i.e. distributed internally or externally to the Organization)? |
| 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. | ||
|
|
||
| Additionally, services that (automatically and silently) deliver executable code such as JavaScript or other client-side components to a user’s device or browser from a server, is often overlooked and can also trigger license conditions. |
There was a problem hiding this comment.
These are good changes. Heading (see the comment above) is something we could tweak a bit, but maybe for the next LFC193 update.
2 participants
…193).md
Making consistent with updated online LFC193