[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Potential LSR licensing violations
From: |
Thomas Morley |
Subject: |
Re: Potential LSR licensing violations |
Date: |
Thu, 20 Oct 2022 21:41:12 +0200 |
Am Do., 20. Okt. 2022 um 02:34 Uhr schrieb Jean Abou Samra <jean@abou-samra.fr>:
> I figured that now I am an LSR editor, I had to learn about what
> legal responsibility I have when accepting contributions.
Well, I think the work of an LSR editor is roughly described in CG 7. LSR work.
Afaict, license issues are not mentioned.
Apart from obvious cases [*] I don't think it's my duty as an LSR
editor to think about the problem at all.
More: discussions about license issues inevitably causes headache to me.
If we extend the duties of LSR editors in that way, i'll immediately
step down from that role.
Sorry,
Harm
[*] I hope copyright with https://lsr.di.unimi.it/LSR/Item?id=1005 is
sufficently solved. See discussions:
https://lists.gnu.org/archive/html/bug-lilypond/2016-04/msg00004.html
and finally:
https://lists.gnu.org/archive/html/bug-lilypond/2020-03/msg00060.html
- 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, 2022/10/20
Re: Potential LSR licensing violations,
Thomas Morley <=
Re: Potential LSR licensing violations, Jean Abou Samra, 2022/10/21