[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Potential LSR licensing violations
From: |
Han-Wen Nienhuys |
Subject: |
Re: Potential LSR licensing violations |
Date: |
Thu, 20 Oct 2022 21:29:34 +0200 |
On Thu, Oct 20, 2022 at 2:34 AM Jean Abou Samra <jean@abou-samra.fr> wrote:
> So far, so good. However, take this snippet:
>
> https://lsr.di.unimi.it/LSR/Item?id=102
>
> It begins with 300 lines of code that used to be in the LilyPond
> repository, released under the GPL, before they were considered
> legacy and moved to a snippet. I am pretty sure this violates
> the GPL. 300 lines looks too much for fair use law to apply,
> doesn't it?
Why not ask Jan who wrote the chords snippet if is he OK to relicense
the snippet as public domain? (or, maybe he already did this when the
snippet was submitted)
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
- Re: Potential LSR licensing violations, (continued)
- Re: Potential LSR licensing violations, Luca Fascione, 2022/10/20
- Re: Potential LSR licensing violations, Jean Abou Samra, 2022/10/20
- Re: Potential LSR licensing violations, Luca Fascione, 2022/10/20
- Re: Potential LSR licensing violations, Luca Fascione, 2022/10/20
- Re: Potential LSR licensing violations, Jean Abou Samra, 2022/10/21
- Re: Potential LSR licensing violations, Luca Fascione, 2022/10/21
- Re: Potential LSR licensing violations, Jean Abou Samra, 2022/10/21
- Re: Potential LSR licensing violations, Luca Fascione, 2022/10/20
Re: Potential LSR licensing violations,
Han-Wen Nienhuys <=
Re: Potential LSR licensing violations, Thomas Morley, 2022/10/20
Re: Potential LSR licensing violations, Jean Abou Samra, 2022/10/21