blog

Source files for chris.bracken.jp
git clone https://git.bracken.jp/blog.git
Log | Files | Refs | Submodules | README | LICENSE

commit d785b618c70b31f175ba432a909eeda116491d6a
parent 186ad7256726eaa02809a6c16c94c50e93d260f3
Author: Chris Bracken <chris@bracken.jp>
Date:   Fri, 10 May 2024 10:44:38 -0700

Minor tweak to wording

Diffstat:
Mcontent/post/2020-05-22-thoughts-on-licences.md | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/post/2020-05-22-thoughts-on-licences.md b/content/post/2020-05-22-thoughts-on-licences.md @@ -62,9 +62,9 @@ On the content side, I've always posted my web site's content under a [Creative Commons Attribution-ShareAlike][cc_by_sa] licence. But I don't believe that's actually the ideal match based on my priorities. Why is it that I've elected to use a licence that requires that derived works also be licensed under the same -terms rather than under whatever terms someone feels like, so long as credit is -given? In the end I settled on the more permissive [Creative Commons -Attribution][cc_by] licence. +terms rather than under whatever terms someone feels like, so long as +acknowledgement is given? In the end I settled on the more permissive [Creative +Commons Attribution][cc_by] licence. This feels to me a bit like the difference between [BSD][bsd_licence] and [GPL][gpl_licence] terms, where the latter requires that derived works also be