From aa93046bda0c961a7c1ad08974e91f1db2e7de37 Mon Sep 17 00:00:00 2001 From: Florian Kohrt Date: Wed, 18 Sep 2024 13:26:46 +0200 Subject: [PATCH] Fix keypoint on GPL As the GPL does not mandate sharing, putting the whole derivative under the GPL license is only required if licensees decide to share it. --- episodes/11-licensing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/episodes/11-licensing.md b/episodes/11-licensing.md index 038e548d94..b2a8729715 100644 --- a/episodes/11-licensing.md +++ b/episodes/11-licensing.md @@ -96,7 +96,7 @@ the licenses discussed in this session? How is it different? :::::::::::::::::::::::::::::::::::::::: keypoints - The `LICENSE`, `LICENSE.md`, or `LICENSE.txt` file is often used in a repository to indicate how the contents of the repo may be used by others. -- People who incorporate General Public License (GPL'd) software into their own software must make their software also open under the GPL license; most other open licenses do not require this. +- People who incorporate General Public License (GPL'd) software into their own software must make the derived software also open under the GPL license if they decide to share it; most other open licenses do not require this. - The Creative Commons family of licenses allow people to mix and match requirements and restrictions on attribution, creation of derivative works, further sharing, and commercialization. - People who are not lawyers should not try to write licenses from scratch.