[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Potential LSR licensing violations
From: |
Jan Nieuwenhuizen |
Subject: |
Re: Potential LSR licensing violations |
Date: |
Fri, 21 Oct 2022 12:32:00 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Jean Abou Samra writes:
Hello Jean,
> Adding you to this lilypond-devel thread.
[..]
> In doing so, Valentin didn't realize that moving this code to LSR was
> a violation of the GPL, because the code was under GPL but LSR
> snippets are in the public domain.
Right. Sounds like an honest oversight.
Thanks for bringing this to my attention.
> To my knowledge, this is a more or less isolated case. It would be
> simpler to have all of LSR in the public domain. Would you mind
> sending a written statement that you release this code under the
> public domain?
Sure.
Hereby I place this [legacy Banter chord names] code in the public
domain or Creative Commons CC0 license, whichever you prefer.
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://lilypond.org
Freelance IT https://JoyOfSource.com | AvatarĀ® https://AvatarAcademy.com
Re: Potential LSR licensing violations, Han-Wen Nienhuys, 2022/10/20
Re: Potential LSR licensing violations, Thomas Morley, 2022/10/20
Re: Potential LSR licensing violations, Jean Abou Samra, 2022/10/21
- Re: Potential LSR licensing violations,
Jan Nieuwenhuizen <=