|
welcome to 2019!
Hi all, I hope everyone had some nice time off and enjoyed the holidays. You should have all gotten a recurring invite from Steve Winslow for the 2019 bi-weekly legal calls at 9am Pacific time. Our fi
Hi all, I hope everyone had some nice time off and enjoyed the holidays. You should have all gotten a recurring invite from Steve Winslow for the 2019 bi-weekly legal calls at 9am Pacific time. Our fi
|
By
J Lovejoy
· #2513
·
|
|
FSF Licensing and Compliance Lab: 2018 and the future
and yes, I am aware that they listed the SPDX short identifiers incorrectly and have reached out to the FSF asking for a correction. Still good mention in spirit, though! Jilayne
and yes, I am aware that they listed the SPDX short identifiers incorrectly and have reached out to the FSF asking for a correction. Still good mention in spirit, though! Jilayne
|
By
J Lovejoy
· #2509
·
|
|
FSF Licensing and Compliance Lab: 2018 and the future
In case some of you are not on the FSF mailing list, SPDX had a nice mention here! :) Jilayne Begin forwarded message: From: "Donald Robertson, III, FSF" <info@...> Subject: FSF Licensing and Comp
In case some of you are not on the FSF mailing list, SPDX had a nice mention here! :) Jilayne Begin forwarded message: From: "Donald Robertson, III, FSF" <info@...> Subject: FSF Licensing and Comp
|
By
J Lovejoy
· #2508
·
|
|
v3.4 is now live! (and a couple other updates)
Hi all, version 3.4 of the SPDX License List is now live! https://spdx.org/licenses/ You can read release notes here: https://github.com/spdx/license-list-XML I’m really pleased that we got this one d
Hi all, version 3.4 of the SPDX License List is now live! https://spdx.org/licenses/ You can read release notes here: https://github.com/spdx/license-list-XML I’m really pleased that we got this one d
|
By
J Lovejoy
· #2506
·
|
|
Linux kernel enforcement statement discussion (and personal note)
fair enough. hence, stepping away from keyboard now!
fair enough. hence, stepping away from keyboard now!
|
By
J Lovejoy
· #2503
·
|
|
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 m
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 m
|
By
J Lovejoy
· #2500
·
|
|
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
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
|
By
J Lovejoy
· #2499
·
|
|
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 an
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 an
|
By
J Lovejoy
· #2498
·
|
|
use of SPDX identifiers by Western Digital
to be fair and not to take anything away from Alan’s effort, there is another “hardware company” that has been using SPDX identifiers in its open source software projects for a few years now :) but, t
to be fair and not to take anything away from Alan’s effort, there is another “hardware company” that has been using SPDX identifiers in its open source software projects for a few years now :) but, t
|
By
J Lovejoy
· #2493
·
|
|
Linux kernel enforcement statement discussion
To be fair to the SPDX community, this hasn’t been discussed here until recently, so I don’t think it’s fair to say the discussion has been going on for so long or that it’s been a year in considerati
To be fair to the SPDX community, this hasn’t been discussed here until recently, so I don’t think it’s fair to say the discussion has been going on for so long or that it’s been a year in considerati
|
By
J Lovejoy
· #2483
·
|
|
call tomorrow / 3.4 release work to be done
Hi all, We are not in what should be the final days of prep for the next release. Looking over the list of issues tagged for 3.4, I’m not sure we’ll realistically get them all over the line, but we wi
Hi all, We are not in what should be the final days of prep for the next release. Looking over the list of issues tagged for 3.4, I’m not sure we’ll realistically get them all over the line, but we wi
|
By
J Lovejoy
· #2482
·
|
|
use of SPDX identifiers by Western Digital
Just spotted another project using SPDX identifiers in source file: Western Digital appears to be using them in their newly-released Open Source RISC-V SweRV Instruction Set Simulator https://github.c
Just spotted another project using SPDX identifiers in source file: Western Digital appears to be using them in their newly-released Open Source RISC-V SweRV Instruction Set Simulator https://github.c
|
By
J Lovejoy
· #2480
·
|
|
GPL Cooperation Commitment variations
Richard, You stated: But, is Red Hat intending on using the SPDX identifier in source files of Red Hat projects that have adopted the project variant or SPDX documents? Jilayne
Richard, You stated: But, is Red Hat intending on using the SPDX identifier in source files of Red Hat projects that have adopted the project variant or SPDX documents? Jilayne
|
By
J Lovejoy
· #2478
·
|
|
Linux kernel enforcement statement discussion
actually, on that note, if a project did want to adopt GPL-3.0 termination clause for L/GPL-2.0 licensed code (whether a new project or existing project), wouldn’t it make more sense to use the GPL-CC
actually, on that note, if a project did want to adopt GPL-3.0 termination clause for L/GPL-2.0 licensed code (whether a new project or existing project), wouldn’t it make more sense to use the GPL-CC
|
By
J Lovejoy
· #2477
·
|
|
Linux kernel enforcement statement discussion
Somewhat breaking my own rule here, as I don’t really think the details of admissibility or ease of explaining external evidence to a court is really on-topic for the SPDX License List… but since you’
Somewhat breaking my own rule here, as I don’t really think the details of admissibility or ease of explaining external evidence to a court is really on-topic for the SPDX License List… but since you’
|
By
J Lovejoy
· #2475
·
|
|
Linux kernel enforcement statement discussion
Thanks Dennis for weighing in here. While I generally agree that incorrect use is not a bar to something (if it was, we would have never gotten very far in this project), it does concern me and always
Thanks Dennis for weighing in here. While I generally agree that incorrect use is not a bar to something (if it was, we would have never gotten very far in this project), it does concern me and always
|
By
J Lovejoy
· #2470
·
|
|
Linux kernel enforcement statement discussion
Hi all, I was hoping that others long-standing members of the SPDX legal community would jump in on this thread, but a few days have gone by now and no further discussion, so let me summarize some per
Hi all, I was hoping that others long-standing members of the SPDX legal community would jump in on this thread, but a few days have gone by now and no further discussion, so let me summarize some per
|
By
J Lovejoy
· #2464
·
|
|
GPL Cooperation Commitment variations
Hi all, I know I just wrote in the minutes that this task was on Richard F, but I was too curious not to have a cursory look myself! Attached is a compare of the project to corporate variant; and of t
Hi all, I know I just wrote in the minutes that this task was on Richard F, but I was too curious not to have a cursory look myself! Attached is a compare of the project to corporate variant; and of t
|
By
J Lovejoy
· #2449
·
|
|
meeting minutes: Linux kernel enforcement statement / GPL Cooperation Commitment
Hi all, Thanks for a productive call today. I’ve posted a summary of the discussion in the meeting minutes here: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-11-29 Please note: there was general
Hi all, Thanks for a productive call today. I’ve posted a summary of the discussion in the meeting minutes here: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-11-29 Please note: there was general
|
By
J Lovejoy
· #2448
·
|
|
meeting tomorrow/Thursday
just realized this only went to Richard. See corrected meeting time/zones below! Begin forwarded message: From: J Lovejoy <opensource@...> Subject: Re: meeting tomorrow/Thursday Date: November
just realized this only went to Richard. See corrected meeting time/zones below! Begin forwarded message: From: J Lovejoy <opensource@...> Subject: Re: meeting tomorrow/Thursday Date: November
|
By
J Lovejoy
· #2447
·
|