|
From: | Jean Abou Samra |
Subject: | Re: Potential LSR licensing violations |
Date: | Fri, 21 Oct 2022 13:27:07 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 |
Le 21/10/2022 à 13:21, Kevin Barry a écrit :
On Fri, Oct 21, 2022 at 01:12:09PM +0200, Jean Abou Samra wrote:-- AFAIK, this is the first time we have to do a relicensing, and the odds of a legal case involving LilyPond are very small due to its low-key profile in the industry. I feel this would be much ado about nothing.This is why I think it's usually better not to pay any attention to licence issues that don't come in the form of cease-and-desist or whatever. This whole exercise was (IMO) much ado about nothing.
It would have helped IMO if all the more or less unrelated side questions had been raised in separate threads…
And we are now left with the question of whether licensing is now part of the duties of LSR editors. As Thomas said, it's not mentioned in the CG. I guess we have to add it?
What's the specification of that job? As I wrote to Harm (but maybe the mailing list didn't deliver that post to you yet), I don't think there is a lot to do. If you see a clear license violation, correct it, as we've done here. But this is likely to be rare and I don't think actively actively searching for violations is a good use of one's time. Jean
[Prev in Thread] | Current Thread | [Next in Thread] |