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

Difference between revisions of "Legal Team/Minutes/2016-07-21"

From SPDX Wiki
Jump to: navigation, search
Line 11: Line 11:
  
 
== Agenda ==  
 
== Agenda ==  
1) v2.5 is now live - send email that it's live now to general call and re-sort
+
'''1) v2.5 is now live'''
 +
* need to send email that it's live now to general call and legal team
 +
* sortable table fixed so that it sorts regardless of lower case/ upper case
  
 
2) XML files and review - what needs to be done to get to release stage:
 
2) XML files and review - what needs to be done to get to release stage:
Line 18: Line 20:
 
# same situation for deprecated licenses - Gary's point that need XML for tools (Gary and Kris were going back and forth on whether own XML files needed for this or not) - to check on outcome of this
 
# same situation for deprecated licenses - Gary's point that need XML for tools (Gary and Kris were going back and forth on whether own XML files needed for this or not) - to check on outcome of this
 
# review various webpages for updating (Alan) - work on in next few weeks, proposal of changes
 
# review various webpages for updating (Alan) - work on in next few weeks, proposal of changes
* * License matching guidelines page
+
** License matching guidelines page
* * License list overview page; add info/explanation about XML tags (with input from Kris and Gary for tags)
+
** License list overview page; add info/explanation about XML tags (with input from Kris and Gary for tags)
 
# define a new process for License List (how to request a new license, what kind of pull requests we want, underlying process etc.)
 
# define a new process for License List (how to request a new license, what kind of pull requests we want, underlying process etc.)
 
# Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats
 
# Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats

Revision as of 20:38, 21 July 2016

Attendees

  • Kris Reeves
  • Gary O"Neall
  • Paul Madick
  • Jilayne Lovejoy
  • Dennis Clark
  • Phil Odence
  • Sam Ellis
  • Mark Gisi
  • Alan Tse

Agenda

1) v2.5 is now live

  • need to send email that it's live now to general call and legal team
  • sortable table fixed so that it sorts regardless of lower case/ upper case

2) XML files and review - what needs to be done to get to release stage:

  1. finish main review of licenses so that all can merged and other clean-up (see sub-list below)
  2. exceptions need to be added to XML - Kris will add to Github for review, will probably put them in own pull requests (tools don't care whether in same or different directory)
  3. same situation for deprecated licenses - Gary's point that need XML for tools (Gary and Kris were going back and forth on whether own XML files needed for this or not) - to check on outcome of this
  4. review various webpages for updating (Alan) - work on in next few weeks, proposal of changes
    • License matching guidelines page
    • License list overview page; add info/explanation about XML tags (with input from Kris and Gary for tags)
  1. define a new process for License List (how to request a new license, what kind of pull requests we want, underlying process etc.)
  2. Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats
  • * Gary already has basic structure in place; time frame such that he could do testing in mid- to end-September
  • * end-of September would aim to have preview of website so we can check it, probably then one more pass at tools, etc.
  1. need new tool to take text of new license and convert to XML file (to do so by hand is a bit tedious). Will still need human review before finalizing. (doesn't have to be done for release stage)

Other notes on XML review:

  • opening and closing <SPDX> tag are not always same case - should be all upper-case
  • discussion on what to do about some licenses that were flagged as having self-referring numbering - will save this data even tho not complete, just in case we want to go that route later; can be an attribute that is not "seen" at this point; don't merge these yet, Kris will add attribute and merge.
  • for those that are tagged as "requires acknowledgement" - reminder, don't merge, Kris to deal with those all at once
  • body tag to be removed
  • Kris to do another pass to do some clean-up

Timing:

  • ok to not have Q3 release and aim to have this all done mid-quarter --> end of October