THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
General Meeting/Minutes/2018-10-04
From SPDX Wiki
- Attendance: 8
- Lead by Phil Odence
- Minutes of Sept meeting approved
Contents
Tech Team Report - Kate/Gary
- Spec
- Focus on multiple formats
- How do deal with XML, JSON, YAML
- Proposal to link to software heritage identifies
- SW heritage- presentation came out recently on how code should be ID’ed in repos
- Seems to make sense to extend references to point to
- General agreement on last tech call
- Focus on multiple formats
- Tooling
- Got integrated on line tools up
- License submittal
- XML editor
- Beta quality, ready to go. http://spdxtools.sourceauditor.com
- Got integrated on line tools up
- GSOC has worked very well
- Should thank Google
- Post on Website
- Could use some social media
- Topic for Outreach
- May want to point projects to FSFEurope software reuse site which advocates SPDX https://reuse.software/
- Would be a good credibility builder
- The link is on the site, but not easy to find
- Should thank Google
- Other Groups
- NTIA- Government group defining a BoM standard
- Prototype work in health care
- Fingers crossed that they will use SPDX
- SWID
- Active discussion
- Mapping fields between SPDX an SW
- Other groups may be able to use our use cases
- They are wrestling with what is a components
- Also, how a company can keep their own supplementary license list
- Can do via a SPDX doc that is just licenses and make external reference to
- Steve W will help out
Legal Team Report - Jilayne
- New license backlog
- Trying to clear out for next release
- Looking forward to new tooling
- Could use testing help
- Need some Python help on the tools
- Mostly fixing up formatting stuff
Outreach Team Report - Jack
- Little activity
- Regrouping
Attendees
- Phil Odence, Black Duck/Synopsys
- Kate Stewart, Linux Foundation
- Gary O’Neall, SourceAuditor
- Matthew Crawford, ARM
- Jilayne Lovejoy
- Jack Manbeck, TI
- Steve Winslow, LF
- Mark Atwood, Amazon