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
(GSoC)
(Next Week’s Agenda)
 
(2 intermediate revisions by the same user not shown)
Line 32: Line 32:
  
 
==SPDX Tools in the Repo==
 
==SPDX Tools in the Repo==
* Java Classic
+
* Java  
* Java Tools
+
** Classic Java Tools - Supports 1.2, 2.0, 2.1, 2.2(except for JSON/YAML/XML)
 +
** New Java Tools - new repo that has API changes from classic java tools.    Supports all formats of 2.2
 
* Python
 
* Python
** Need an update from Philippe
+
** Need an update from Philippe on what happened to 2.1 port worked on via GSoC last summer
** Gary offered to help
+
** Gary offered to help once we have breakdown clarified.
** Needs be brought up to 2.2
+
** Supports 1.2 today,  but needs be brought up to 2.2
 
** Tern could use the Python library for as a validator
 
** 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
 
** Could use the community bridge mentoring program to help – Gary will follow-up on the mentoring call
Line 43: Line 44:
 
** Currently 2.1
 
** Currently 2.1
 
** Next working on 2.2
 
** Next working on 2.2
** Summer of code project to implement RDF format
+
** Summer of code project to implement RDF format being incorporated
 
* JavaScript
 
* JavaScript
** Summer of Code project but needs some work
+
** Last year's GSoC project but needs some work
 
** Could potentially use Kotlin as a substitute
 
** Could potentially use Kotlin as a substitute
 
* Kotlin
 
* Kotlin
Line 53: Line 54:
 
** Left off on how to map the ID’s to the aliases
 
** Left off on how to map the ID’s to the aliases
 
** Each language can implement
 
** Each language can implement
** Future topic
+
** Future topic,  possibly discuss in ACT.
  
 
==SPDX 3.0==
 
==SPDX 3.0==
Line 60: Line 61:
 
** Suggestion to use Github template for the meta issues
 
** Suggestion to use Github template for the meta issues
 
*** Steve will create a template for META issues
 
*** Steve will create a template for META issues
** We could use templates for the different profiles
+
** Consider using templates for the different profiles
 
* Labels
 
* Labels
** suggest “profile licensing”
+
** suggest “profile licensing” - ok'd by Steve
** suggest “profile base”
+
** suggest “profile base” - ok'd by William
** suggest “profile security”
+
** suggest “profile security” - ok'd by Thomas
 
** Kate will add some additional profile labels
 
** Kate will add some additional profile labels
 
* No meta issue for security for now – will use labels
 
* No meta issue for security for now – will use labels
 +
* William will look at a meta-profile
  
 
==Next Week’s Agenda==
 
==Next Week’s Agenda==
 
* 2.2.1 update
 
* 2.2.1 update
* GSoC
+
* GSoC update
 
* License profile – joint call with legal starting at 15 minutes after the hours
 
* License profile – joint call with legal starting at 15 minutes after the hours
  
 
  [[Category:Technical|Minutes]]
 
  [[Category:Technical|Minutes]]

Latest revision as of 18:23, 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 - Supports 1.2, 2.0, 2.1, 2.2(except for JSON/YAML/XML)
    • New Java Tools - new repo that has API changes from classic java tools. Supports all formats of 2.2
  • Python
    • Need an update from Philippe on what happened to 2.1 port worked on via GSoC last summer
    • Gary offered to help once we have breakdown clarified.
    • Supports 1.2 today, but 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 being incorporated
  • JavaScript
    • Last year's GSoC 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, possibly discuss in ACT.

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
    • Consider using templates for the different profiles
  • Labels
    • suggest “profile licensing” - ok'd by Steve
    • suggest “profile base” - ok'd by William
    • suggest “profile security” - ok'd by Thomas
    • Kate will add some additional profile labels
  • No meta issue for security for now – will use labels
  • William will look at a meta-profile

Next Week’s Agenda

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