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

Difference between revisions of "Technical Team/Minutes/2020-06-02"

From SPDX Wiki
Jump to: navigation, search
(SPDX 2.2.1)
(GSoC)
Line 27: Line 27:
  
 
==GSoC==
 
==GSoC==
* Met with all the students
+
* All mentors have met with their students
* coding has started
+
* Coding has started
 +
* Adding a standing agenda item for the students to ask questions each meeting.
  
 
==SPDX Tools in the Repo==
 
==SPDX Tools in the Repo==

Revision as of 18:13, 2 June 2020

June 2, 2020

Attendees

  • Jim Hutchison
  • Rex Jaeschke
  • Kate Stewart
  • William Bartholomew
  • Gary O’Neall
  • Nisha Kumar
  • Steve Winslow
  • John Mudge
  • Takashi Ninjouji
  • Peter Shin
  • Rose Judge
  • Thomas Steenbergen

Topics: Rex/John update on 2.2.1 GSoC SPDX Tools


SPDX 2.2.1

  • Update from Rex
    • Help wanted on a few issues (tagged as help needed)
    • John making progress on translating code into format.
    • Would like to target next week for all issues to be resolved, and put out for general review.

GSoC

  • All mentors have met with their students
  • Coding has started
  • Adding a standing agenda item for the students to ask questions each meeting.

SPDX Tools in the Repo

  • Java Classic
  • Java Tools
  • Python
    • Need an update from Philippe
    • Gary offered to help
    • Needs be brought up to 2.2
    • Tern could use the Python library for as a validator
    • Could use the community bridge mentoring program to help – Gary will follow-up on the mentoring call
  • GoLang
    • Currently 2.1
    • Next working on 2.2
    • Summer of code project to implement RDF format
  • JavaScript
    • Summer of Code project but needs some work
    • Could potentially use Kotlin as a substitute
  • Kotlin
    • ORT uses SPDX
    • Could separate out a separate library
  • License mapping
    • Left off on how to map the ID’s to the aliases
    • Each language can implement
    • Future topic

SPDX 3.0

  • Steve provided an overview of meta-issues
    • Different projects use different terms – agreement to use Meta issue
    • Suggestion to use Github template for the meta issues
      • Steve will create a template for META issues
    • We could use templates for the different profiles
  • Labels
    • suggest “profile licensing”
    • suggest “profile base”
    • suggest “profile security”
    • Kate will add some additional profile labels
  • No meta issue for security for now – will use labels

Next Week’s Agenda

  • 2.2.1 update
  • GSoC
  • License profile – joint call with legal starting at 15 minutes after the hours