THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Technical Team/Minutes/2019-11-26

From SPDX Wiki
< Technical Team‎ | Minutes
Revision as of 19:07, 26 November 2019 by Goneall (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

November 26, 2019

Attendees

  • Gary O’Neall
  • Alexios Zavras
  • Kate Stewart
  • Jim Hutchinson
  • Rose Judge
  • Steve Winslow
  • Matthew Crawford

2.2 Release

  • Review / close on issues discussed previously
    • Merged #151 – license list
    • Merged #150 – updated charter
    • Merged JSON YAML examples – we’ll add any PR’s for additional open issues
    • Issue #38 – OWL ontology – merging even though there are issues – we will create issues and PR’s against the added document
    • Issue #39 – Model – merging even though there are issues – we will create issues and PR’s against the added document
    • Issue #74 – fix is too extensive, need more specific PR’s to review and accept - closing
  • Issues which need merge conflicts – Thomas volunteered to resolve and merge if approved.
    • Issue #107
    • Issue #139
    • Issue #79
    • Issue #40
  • New relationships Issue #154
    • Difference between preq and dependency is not clear
      • PREREQUISITE is a superset of DEPENDENCY – it may include items that are not explicitly stated in some build artifact

Discussion on Appendix V: Using SPDX short identifiers in Source Files

  • Alexios pointed out that there are several source files that have an SPDX identifier and continues with additional license text
    • This causes issues for tools that expect the SPDX identifier to be the sole expression of a license for that file
  • Discussion on how to add/represent/resolve additional text
  • Discussion on substantial modifications made to files which have additional licenses
  • REUSE has recommendations that seem to resolve this issue
  • Current text in Appendix V does not reflect these recommendations
  • Alexios to create a PR as a proposal
  • Steve will review the PR and comment