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

<kstewart@...> wrote: I'd like to point out that this recommendation is contingent on being able to automatically scan and generate it. No one is suggesting manual inventory of code to

Hi, Just thought some of you might be interested in some recent announcements with SPDX showing up in them. FSFE just launched a new site today recommending use of SPDX license identifiers in

Please join us for a special presentation by Krys Nuvadga an SPDX 2017 Google Summer of Code student participant. He is a student of the University of Buea, Cameroon. Krys is working on the

Just spotted a very nice reference to SPDX in Dirk Riehle's paper, and thought those on the list might find the paper interesting as well.

Here are the minutes https://wiki.spdx.org/view/General_Meeting/Minutes/2017-08-03 Phil BLACKDUCK L. Philip Odence VP/General Manager Black Duck On-Demand Black Duck Software, Inc. 800

Please join us for a special presentation by Rohit Lodha, another of our Google Summer of Code particpants. I’ll introduce Rohit and his project (on which he will upate us) in his own words: I a

Die 12. 07. 17 et hora 15.25.22 scripsis: […] That makes a lot of sense. And again, huge kudos for all the time you invested in this migration and above all with gathering more contributions in