Hi, Just heard from LF IT that our SPDX site & wiki will be rebooting this weekend, as the apply the Meltdown/Spectre remediation. It should just be down for 5 minutes early this weekend, so this is m

And in addition to Linux getting serious in terms of adding SPDX identifiers, we also have FreeBSD applying them to their code base. Kate ---------- Forwarded message ---------- From: Pedro Giffuni <p

Some of you have already noticed that this started in 2016 but as of 4.14, we had a major breakthrough and cleanup of all the files without a license reference all had SDPX identifiers added to them.

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 dial in

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 Session MarkG de

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 to ex

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 that sc

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 the sour

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. http://dirkriehle.com/publications/2017-2/license-clearance-i

Great work Thomas! Thank you very much for your efforts to get our current (and future) specifications into a more community friendly format! :-) Kate

Yes. We've got Thurs(16th)11:15am-5pm reserved for SPDX. More next week.... :-) Kate

Hi Bradley, There are no licensing requirements for tools themselves to participate in the bake-off, the only requirement is that they are able to produce (and ideally consume) valid SPDX files. We're

Hi, The SPDX tech team will be hosting an SPDX Tools BakeOff at LinuxCon Europe on 6 October 2016. Participation can be remote by phone or in person. The Bake-off (also known by some as a Plugfest) wi

Hi Michael, Yes, feel free to join us on the weekly call (Tuesday at 1pm Eastern) details: http://wiki.spdx.org/view/Technical_Team for Q&A or send email to spdx-tech@... with your question

Thanks Gary, Sorry I had to leave mid way through the report. Couple of minor adjustments to the minutes. The review window for SPDX 2.1 spec is now closed. Its been open for a 1.5 months, and feedbac

Greetings, The tech team is winding up the remaining minor changes, and has declared the SPDX 2.1 specification ready for wider public review. The review window will end on July 29th, and if there are

Hi Dave, Welcome. :-) Information on the general meetings and past minutes can be found on: http://wiki.spdx.org/view/General_Meeting Kate

For those interested in improving the automated tracking of copyright, licensing and security information in the supply chain, we've managed to get a Supply Chain mini-summit added on after LinuxCon o

Hi Phil, Yes, that is the concern that is motivating this proposal. Not at this time, but the new logo ideas were designed by the same designer that work on the open compliance logo. Both options have

Hi, As part of the discussion tomorrow I'd like to get some input on the options for new branding for SPDX. As SPDX is one of the underpinings to support open compliance, it would be good if our logo'