I will follow this email with an updated invitation to the General Meeting. Please accept the recurring meeting even if you can’t make the upcoming Dec meeting.

We were excited to see this and wanted to share. As part of Project REUSE the FSFE is recommending use of SPDX License Identifiers.

Hi, We were able to get the SPDXTeam Uberconference updated last Thursday to remove the limit on number of people attending the call. Yay!!! However, as a result of this, we had to change the

Hi Phil, Couple of comments on the Prague section, added them inline, but that's probably not clear - so can you substitute the following in the minutes? Prague SPDX Open Source Tools

https://wiki.spdx.org/view/General_Meeting/Minutes/2017-11-02 General Meeting/Minutes/2017-11-02 < General Meeting‎ | Minutes Attendance: 5 Lead by Phil Odence Minutes of Oct meeting

For folks who keep a digital calendar, there's an iCalendar file which includes this meeting in flight with [1]. You can import the calendar from [2] now if you don't want to wait for the PR to land,

Should be a short one with no guest speaker. European’s note that US has not yet switched back to Standard time, so time is off by an hour from normal. GENERAL MEETING Meeting Time:

In 2016 we explored how the benefits of the Blockchain could be leveraged to assist with open source compliance across a complex manufacturing supply chain [1]. Our interest was sparked after

The MODULE_LICENSE macro used in the kernel is a clear license statement. And better than a terse "Copyright (c) John Doe, GPL" that is seen in the kernel since there is a clear documentation of its

Hi, great to see this direction of development. This will are least clarify all the files which carry nothing expect the Marko MODUL_LICENSE("GPL"); Because one of the interesting questions is "is

FYI: In case you missed it: SPDX identifiers have landed in kernel land... Read the whole thread at https://patchwork.kernel.org/patch/10016189/ And as a side effect, some new patches elsewhere are

Here you go: https://wiki.spdx.org/view/General_Meeting/Minutes/2017-10-05 BLACKDUCK L. Philip Odence VP/General Manager Black Duck On-Demand Black Duck Software, Inc. 800 District Avenue,

Please join us for a special presentation by Alexander Lisianoi another SPDX 2017 Google Summer of Code student participant. He is a software engineer working towards his Masters at Technical

Hi Jonas, I would call this a bug in the SPDX tools. If you could log an issue in the git repo and upload a tag/value file which reproduces the error, I'll take a look at it

Hi Jonas Prior to 2.0, the expectation was that there would only be a single package with a set of files in each SPDX document. When we introduced relationships/identifiers, in 2.0, we were able

Hi everyone, as you know, the FSFE is working on a project, REUSE, which has as one of its recommendations to produce a SPDX conformant bill of materials, if one can be generated automatically. As

https://wiki.spdx.org/view/General_Meeting/Minutes/2017-09-07 General Meeting/Minutes/2017-09-07 < General Meeting‎ | Minutes Attendance: 11 Lead by Phil Odence Minutes of July meeting

Hi Neal, We agree, some tooling is needed to generate the signing of the files that is needed in an SPDX document for an accurate manifest. Both FOSSology and ScanCode are open source projects

Sorry, all, didn’t mean to cc the list. But you might find my blog amusing as well. From: <spdx-bounces@...> on behalf of Philip Odence <podence@...> Date: Wednesday, September 6, 2017 at 6:13

Wow, Kate, great stuff! Thanks for sharing. I’ll talk to Jack about putting reference on the website. In the meantime, for your