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

Difference between revisions of "General Meeting/Minutes/2019-08-01"

From SPDX Wiki
Jump to: navigation, search
(Created page with "* Attendance: 11 * Lead by Phil Odence * Minutes of July meeting approved == Special Presentations - Umang Taneja, Tanjong Smith, GSoC == * Umang ** License submittal work...")
 
(Outreach Team Report - Kate: - action item agreed to in meeting dropped off. Adding it back.)
 
(One intermediate revision by the same user not shown)
Line 37: Line 37:
 
* Spec
 
* Spec
 
** Progress on Appendix for including other fields in the source like the license ID
 
** Progress on Appendix for including other fields in the source like the license ID
*** Keeping scope at file level
+
*** Worked with Legal team members and general agreement to keep scope at file level
*** Tags with SPDX prefix
+
*** Recommend using existing Tags with SPDX prefix, and expectation that format follows fields.
*** Allows to make it easier for tools to pick up.
+
*** Motivation is that this makes it easier for tools to pick up data accurately from source.
** Source file analysis
+
** SPDX document generation from project sources (demo'd last month)
*** Philip demoed
+
*** Philip is looking for projects to try the tool on,  if you have some you want to experiment with,  please contact him.
*** Heavy testing mode
+
 
* Tools
 
* Tools
 
** GSoC
 
** GSoC
Line 66: Line 65:
  
 
* Shane has readied the survey
 
* Shane has readied the survey
 +
* Phil to reach out to Shane and Jack and determine deployment plan.
  
 
== Cross Functional -  ==
 
== Cross Functional -  ==

Latest revision as of 19:31, 1 August 2019

  • Attendance: 11
  • Lead by Phil Odence
  • Minutes of July meeting approved


Special Presentations - Umang Taneja, Tanjong Smith, GSoC

  • Umang
    • License submittal workflow automation
      • Aim is to enhance user experience
      • Compare submitted text against existing licenses to see if there’s duplication or close match
      • Problems he’s trying address
        • What if the license is on the list, proposed, rejected…or a close match to one of those
        • Current XML formatting- word-wrap doesn’t match license
      • Also creating/documenting an API
    • Tasks:
      • Create API- use without logging in, so can be accessed by other tools
      • Create License Matcher- looks for exact and close matches
        • Returns all matches and close matches
      • Compare with not accepted as well as rejected licenses.
        • Reports appropriately according to match
        • Relies on user input regarding whether to go ahead with submittal
      • Improve formatting of generated license
    • Screenshots available at: https://docs.google.com/document/d/1NMcLZVXxBV2PZobPJh1OugbCfC2d8kbAOX4m4TauEYk/edit?usp=sharing
    • Some discussion of how the workflow should work with close matches
    • Aiming for demo in future Legal Team meeting
  • Tanjong
    • License namespace
      • A way to name valid licenses outside of the License List
      • Created namespace and UI
      • Also a mechanism for turning into a license request
      • Took feedback from the joint/legal team meeting

Tech Team Report - Kate/Gary

  • Spec
    • Progress on Appendix for including other fields in the source like the license ID
      • Worked with Legal team members and general agreement to keep scope at file level
      • Recommend using existing Tags with SPDX prefix, and expectation that format follows fields.
      • Motivation is that this makes it easier for tools to pick up data accurately from source.
    • SPDX document generation from project sources (demo'd last month)
      • Philip is looking for projects to try the tool on, if you have some you want to experiment with, please contact him.
  • Tools
    • GSoC
      • Continues to go very well
      • All students passed second evaluation
    • Looking for feedback from community:
      • License matching algorithm approaches
        • Some encoded rules
        • Some depended on XML markup
        • Should we encode in XML or handle programmatically? (Discuss with Gary)

Legal Team Report - Jilayne/Paul/Steve

  • License List
    • 3.6 version went out last month
    • Working issues in 3.7
      • Good input/support from Tech Team
    • Recent meetings have been joint with Tech Team
      • Very helpful at this point


Outreach Team Report - Kate

  • Shane has readied the survey
  • Phil to reach out to Shane and Jack and determine deployment plan.

Cross Functional -

  • None

Attendees

  • Phil Odence, Black Duck/Synopsys
  • Matthew Crawford, ARM
  • Umang Taneja, GSoC
  • Tanjong Smith, GSoC
  • Steve Winslow, LF
  • Gary O’Neall, SourceAuditor
  • Kate Stewart, Linux Foundation
  • Paul Madick, Dimension Data
  • Mark Atwood, Amazon
  • Jilayne Lovejoy, Canonical
  • Jack Manbeck, TI