Hi, Am 30.12.2017 um 01:24 schrieb Simon McVittie: > On Fri, 29 Dec 2017 at 22:24:23 +0100, Markus Koschany wrote: >> Am 29.12.2017 um 00:06 schrieb Jonathan Nieder: >>> Using 'Files: *' when different files are under different licenses >>> sacrifices precision, but it doesn't sacrifice accuracy. You can say >>> >>> Files: * >>> License: GPL-2 and Permissive-License-1 and Permissive-License-2 and ... >>> >>> Or you can even write >>> >>> Files: * >>> License: Freeorion >> >> Ok I can see the misunderstanding now. The above statement would be >> incorrect for freeorion because it translates to: >> >> You are allowed to use the files under GPL-2 and Permissive-License-1 >> and Permissive-License-2 and ... >> >> But this is not true. Not all files are dual/triple/-licensed. Actually >> no file is even dual-licensed. > > I think you're confusing this with a disjunction (dual/multi-license), > which is "GPL-2 or Permissive-License-1 or ..." in copyright-format.
Thanks that's right. I confused the and/or syntax which I already had to use in some of my packages. I corrected this in a previous reply to Russ. In a nutshell: My point is that I appreciate Jonathan's idea and would really like to use that format in my packages but as we have already found out and agreed on, this is not the reality because people would either file RC bugs against my packages or reject them right off the bat. We teach Debian maintainers to document all license information in d/copyright who spend hours and days of their life to compose various copyright files but our most veteran developers tell me that's basically all shenanigans and we could write much simpler documents. This looks like a call for action to me. Russ mentioned that we should create a working group to revise our Policy in regard to copyright information and document our requirements properly. Sounds great. I'm all in favor for this proposal. Let's do it..yesterday. That's my greatest wish right now. Shall I file another bug report for this issue?
signature.asc
Description: OpenPGP digital signature