Hi SPDX-legal, I have added a potential project for GSoC related to improvements to the SPDX License Submission tool, especially as relates to generating the files once a license is accepted. You can

Sorry for the short notice reminder. Given the end of the month and next release time frame is rapidly approaching, we’ll focus today’s meeting on divvying up work to get licenses added. I also want t

Hi Kyle, You raise some specific points that highlight some things we have worked on recently, so responding here inline. Jilayne On 1/24/23 4:13 PM, Kyle Mitchell wrote: Richard and I have been worki

Thanks for this write-up, Richard. Having spent an exorbitant amount of my time over the years of my involvement in SPDX trying to politely say "no" to licenses for the reasons you describe below, I c

Hi all, This is a reminder that Thursday, Jan 12th at the regular legal-team call time, we will have a joint call for the tech and legal teams to discuss the change proposal: https://github.com/spdx/c

Hi all, As discussed on our last call, we'll have our regularly scheduled meeting Thurs, Dec 22 at noon Eastern US time. We'll use the time to go through the review of a license and how to make a PR f

Awesome, Gary! Thanks for the update. Looks like some of the items listed in the issue you link to are on Max's list, so that's good. Jilayne On 12/9/22 12:12 PM, Gary O'Neall wrote:

Hi again Max, and thanks Richard for filling in on some of this. Max - While you are not the first person who has asked about some of these, you might be the first person to have done such a thorough

Hi SPDX legal and tech teams, I’m cross-posting this for wider visibility as some of this impacts both teams: In regard to legal team meetings for the rest of 2022: we will have our regularly schedule

Max, All of what you have done here was already done years ago (~2011, mostly by me, working with various OSI members at that time) in terms of "matching" up the OSI list and is documented on the SPDX

Hi all, Just a reminder of our regular legal team meeting at 9am Pacific time. We'll look at some of the open issues and discuss how to best tackle the many new license submissions we have! See: https

On 11/15/22 12:34 PM, Luis Villa wrote: JL: to be clear, this proposal is about an improved way to capture "exceptions" that are NOT on the SPDX License List, so relevant to the extent that such a hyp

Hi Luis, While I'm barely getting my head around the many complications related to the reality of AI models and data, let alone the related licensing issues... Let me try to answer some of your questi

Hi all, As per our license review protocol, we need 3 SPDX-legal team members to agree to add a license (not counting the submitter). Can we get more people to weigh in on these: https://github.com/sp

Hi all, In light of our discussion on our last call about how to make it easier and faster to get licenses reviewed (and adhere to our 3 “votes” from spdx-legal members for a license to be included),

Hi all, We have our regular meeting Thursday at noon Eastern time. The US set back the clocks this past weekend, so we should be back to the usual time intervals. As we move into the next release cycl

Hi all, I deviated slightly from the plan as discussed at our last call regarding updating the FAQs. I went ahead and made a PR here: https://github.com/spdx/license-list-XML/pull/1692 as working in t

Hi folks, We have a regular SPDX-legal call at the top of the hour (noon, Eastern time) at https://meet.jit.si/SPDXLegalMeeting We'll have a look at whatever needs attention to close out our "document

Hi Anna, Welcome! You have interpreted the CC0-1.0 designation and comment regarding confidentiality correctly. (Note, it is now section 6.2 in version 2.3 of the spec: https://spdx.github.io/spdx-spe

Please see our first Change Proposal submission from Alexios here: https://github.com/spdx/change-proposal/blob/main/proposals/ExceptionRef.md This is a cross-team issue for tech and legal teams. Plea