Hi all, On our call a few days ago, Steve raised the idea of using the next release to JUST focus on documentation improvements. There haven’t been a ton of new license requests and some of the docume

Hi all, I just went through all the issue in terms of what we can likely get in for the 3.18 release. Seems like most issues are already assigned to Steve or I :) Could someone pick up this one and pr

Hot off the press! Link to blog post of this here: https://communityblog.fedoraproject.org/important-changes-to-software-license-information-in-fedora-packages-spdx-and-more/ Thanks for the support on

Hi all, Just a quick reminder that the SPDX-legal call will be at the top of the hour. We'll focus on what tasks can be completed for the next release and, if there's time, I have an update on Fedora

Greetings all, The SPDX spec version 2.3 is now available for review at https://spdx.github.io/spdx-spec/v2.3-RC1/. A summary of the changes can be found in the SPEC Annex I. If you identify any issue

~ J Lovejoy [2022-07-26 06:00 +0200]: Interesting question! I, too, am a bit confused of the various URLs. Asked the other way round: are there also stable links for older versions, e.g. a permalink f

(cross-posting to tech and legal team, as I suspect others may be interested) Hi SPDX-tech team, I just wanted to confirm my understanding of the various formats we now have for the SPDX specification

I'm working on some draft documentation for Fedora around use of SPDX expressions in RPM spec file License: fields. I was surprised to apparently not see anything in the SPDX spec that says that the A

Hi all, We have our regularly schedule call tomorrow/Thursday at noon US eastern time. After a bit of a hiatus, we’ll get back to our usual order of business. Please have a look through the current is

Hi McCoy! I’m moving the SPDX-general list to BCC and replying to SPDX-legal as that is the right place for this discussion. Where is this question coming up in terms of context? That is, are you thin

Greetings SPDX tech and legal teams, A reminder we are continuing the license namespace policy discussions on this Friday, July 1, 2022, at the same time as the prior meetings (15:00 UTC, 11AM Eastern

Greetings all, Below is information on the follow-up meetings regarding license namespaces. Please mark your calendars if you are interested in attending – I will not be sending out any calendar invit

Hi all, did you know: „the and any this you license software for that not use with may code such agreement other terms under are rights work your all from shall source including copyright provided wil

Hi Sebastian, Sorry - I've been negligent at sending out the follow-up meeting information. I missed the end of last week's call, but I believe it was decided to not have a call this week due to the L

Dear all, I thought there was supposed to be a Namespace Proposal meeting at this time today, but I've joined the video call and there are only a couple of others here. Best wishes, Sebastian

Hi all, With a conference going on and end of quarter, we’ll skip our call this week. Please have a look at any open GitHub issues in the meantime! Jilayne Sent from my phone, please excuse brevity an

All, I strongly support Gary's approach of identifying requirements first, then identifying and selecting from technical solutions that meet all requirements. The requirements are: * The SPDX legal te

Greetings SPDX tech and legal teams, A reminder we are continuing the license namespace discussions tomorrow, Friday, 10 June 2022, at the same time (15:00 UTC, 8AM Pacific). We will be using the Lega

Just a reminder, we will be continuing the License Namespace discussion this Friday (likely today by the time you get this email) at 15:00 UTC/8AM Pacific at the coordinates below: https://meet.jit.si

Here is an example license list: https://scancode-licensedb.aboutcode.org/ Regards, Dennis Clark