Technical Team/Minutes/2019-05-21

May 21, 2019

Attendees

• Kate Stewart
• Thomas Steenbergen
• Mathew Crawford
• Nisha Kumar

Spec version 2.1.1

• Spec available at https://spdx.github.io/spdx-spec/
• End of 2 week approval period
• Finalized
• Branching
• Jack needs to sends the code not as an attachment
  • Gary to ping Jack
• Need to publish the 2.1.1 to the website
• Thomas will publish HTML

TERN

• Review of sample document
• Discussion on how to handle non-listed licenses (e.g. BSD that’s used in Python)
  • Suggest LicenseRef-BSD
• Discussion on mapping license references
  • ORT has a mapping module https://github.com/heremaps/oss-review-toolkit/blob/490c2da69435182db19c6dbdebad863de41a7108/spdx-utils/src/main/kotlin/SpdxLicenseAliasMapping.kt

https://github.com/heremaps/oss-review-toolkit/blob/518e17c0b1385cc403960cfdfdff69e76240cb27/spdx-utils/src/main/kotlin/SpdxDeclaredLicenseMapping.kt

• • License matches for text may not be precise using many tools
  • License matching guidelines are only implemented in the SPDX tools: https://github.com/spdx/tools/blob/master/src/org/spdx/compare/LicenseCompareHelper.java
  • Different policies may impact which license terms refer to which licenses
  • A URL approach was used for Maven POM files
• Nisha will look into enhancing tools-python to support the TERN use cases
• Quick fix for Tern to be SPDX compliant is to simply add "LicenseRef-" in front of each license and "AND" it e.g. "MIT BSD GPL2+" => "LicenseRef-MIT AND LicenseRef-BSD AND LicenseRef-GPL2+"

GSoC

• Coding phase starts next week