Date 1 - 2 of 2
GPL-CC and Kernel enforcement statement
Dear legal eagles:
I just saw that the request to have a proper SPDX license id for the
Kernel enforcement statement has been closed . I guess I should
have followed the discussion that happened late last year since I
started this on list way back when ...
I am looking at all the non-SPDX licenses detected in the kernel to
submit them for addition and I am not clear why this would be
rejected: this text is detected alright when you scan the kernel and
has been for a long while (at least by ScanCode). And the same applies
to the GPL-CC . IMHO as a license compliance toolsmith, if this is
something licensing-related, then it should be detected. It it is
detected and is in common enough, then it should have a name/id.
1. Do such statements/commitments texts are worthy of detection by a
license scanner? I think so. Otherwise, why would they exist?
2. Are they common enough? Beyond the kernel, there is a growing
number of projects and companies adopting these   and is even
suggested by GitHub's choosealicence , so I would say yes.
What is wrong with this reasoning? Could someone explain to me in
simple terms why not including these in the list?
Thank you ++ for your help!
Hi Philippe,toggle quoted message Show quoted text
I’m not going to re-hash what was a very lengthy and (surprisingly to me) heated discussion on the Linux kernel enforcement statement, since that is all in the email list archives.
But as to your examples of , , and  below - they are all adopting the GPL Cooperation Commitment for projects, which is exactly the purpose that was drafted for. You will see the email I just sent explaining the thinking behind adding the GPL Cooperation Commitment for projects to the SPDX License List. I think these examples reinforce that thinking.
On Mar 15, 2019, at 5:10 AM, Philippe Ombredanne <pombredanne@...> wrote:
|1 - 2 of 2|