Skip to content

Commit

Permalink
Fix keypoint on GPL
Browse files Browse the repository at this point in the history
As the GPL does not mandate sharing,
putting the whole derivative under the
GPL license is only required if licensees
decide to share it.
  • Loading branch information
fkohrt authored Sep 18, 2024
1 parent db7155f commit aa93046
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion episodes/11-licensing.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down

0 comments on commit aa93046

Please sign in to comment.