Re: New License/Exception Request: Python Imaging Library License

Hi Mark, I believe that the proposed PILL addition to the SPDX license list will be a lot easier to swallow (!!!) if you put a Version Number on it. Regards, Dennis Clark On Thu, Dec 13, 2018 at 11:42 AM Mark Atwood via Lists.Spdx.Org wrote: > Provide a proposed Full Name for the license or

Re: Linux kernel enforcement statement discussion (and personal note)

fair enough. hence, stepping away from keyboard now! > On Dec 13, 2018, at 12:40 PM, Michael Cameron > wrote: > > I’m thinking of an app that senses tone and asks the sender “you sure about > sending to all those on the cc?” :-) > From: Spdx-legal@lists.spdx.org on behalf of J > Lovejoy >

Re: Linux kernel enforcement statement discussion (and personal note)

I’m thinking of an app that senses tone and asks the sender “you sure about sending to all those on the cc?” :-) From: Spdx-legal@lists.spdx.org on behalf of J Lovejoy Sent: Thursday, December 13, 2018 1:27:45 PM To: Mike Dolan Cc: SPDX-legal Subject: Re: Linux

Re: Linux kernel enforcement statement discussion (and personal note)

Thanks Mike. I had started another email earlier this morning, but got distracted (ha ha…) by the actual meeting and tying up the 3.4 release, so just sent now. Let me make one thing very clear on a more personal note: 1) I am DONE commenting on this thread for the reasons stated in the email

Re: Linux kernel enforcement statement discussion

I think this is getting closer to the crux, but I also think some terminology and associations of such is getting in the way: there seems to be focus on whether or not the KES is an “exception” or an “additional permission” to the GPL-2.0-only (that is, the license of the kernel) and then that

meeting minutes and update for 3.4 release

Hi all, Today’s meeting minutes have been posted here: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-12-12 We have resolved most of the 3.4 issues and PRs that we could. I’ve also gone through and tagged things as appropriate

Re: Linux kernel enforcement statement discussion

On 2018-12-13 13:19, Michael Dolan wrote: To be frank, I haven't had time to read all the list traffic today but I see there are lengthy discussions. Despite being part of the lengthy discussions, I too am having a hard time staying on top of it all :) Given Jilayne's backlog for this

Re: Linux kernel enforcement statement discussion

On Thu, 2018-12-13 at 09:32 -0800, Bradley M. Kuhn wrote: > James Bottomley wrote: > > Actually, you've missed the most important one raised by several > > people that KES isn't an exception at all. > > I don't think Karen missed it, in fact, she pointed out that she > thought we have consensus

Re: Linux kernel enforcement statement discussion

To be frank, I haven't had time to read all the list traffic today but I see there are lengthy discussions. Given Jilayne's backlog for this release it's clear this won't reach any usual consensus anytime soon so I would suggest we all give her some room to get what needs done for the next

Re: Linux kernel enforcement statement discussion

James Bottomley wrote: > Actually, you've missed the most important one raised by several people > that KES isn't an exception at all. I don't think Karen missed it, in fact, she pointed out that she thought we have consensus on the same point: > In our current use case, KES mostly reads like

Re: Linux kernel enforcement statement discussion

On Thu, Dec 13, 2018 at 08:51:10AM -0500, Karen Sandler wrote: > * A few Linux developers have expressed an opinion that they would not use > this identifier to mark upstream code at this point, mostly because they > have not done the work mentioned above. James in particular has agreed that > it

Re: Linux kernel enforcement statement discussion

I think it's great that so many of us who are not typically involved in spdx discussions are now participating! Since I've been following things, I've noticed that we've had repetitive posts as people reiterate points already made earlier. I think this is true of both the arguments and