From bf9580db716779e2a4ab07ca599dd8960a7f5a36 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Thu, 16 Jun 2022 14:46:08 +1200 Subject: [PATCH] vault backup: 2022-06-16 14:46:08 --- content/notes/20-software-licensing.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/notes/20-software-licensing.md b/content/notes/20-software-licensing.md index 083d51e33..c972b28cd 100644 --- a/content/notes/20-software-licensing.md +++ b/content/notes/20-software-licensing.md @@ -27,8 +27,12 @@ what does it mean for people to use your software. What responsitilities do you - others e.g., creative commons - allow a selection of *facets* [Creative commons](notes/software-licensing.md#Creative%20commons) - Appreciate that code can be multi-licensed - - + - e.g., floss for non-commercial use but commercially licenced otherwise - Understand how to apply a license to code + - project should include complete license text: LICENSE file in top-level of project directory + - also good idea to add to each file - Appreciate licenses can be mutually incompatible + - e.g., developing software that combines two FLOSS code bases that have different code licenses. + - could be impossible to satisfy both licenses simultaneously. [software-licensing](notes/software-licensing.md) \ No newline at end of file