Legal Team/Minutes/2016-07-21 - Revision history

Jlovejoy at 20:46, 21 July 2016

2016-07-21T20:46:24Z

Jlovejoy at 20:38, 21 July 2016

2016-07-21T20:38:41Z

Jlovejoy at 18:06, 21 July 2016

2016-07-21T18:06:32Z

Jlovejoy at 17:50, 21 July 2016

2016-07-21T17:50:36Z

Jlovejoy at 17:50, 21 July 2016

2016-07-21T17:50:18Z

Jlovejoy at 17:49, 21 July 2016

2016-07-21T17:49:15Z

Jlovejoy at 17:34, 21 July 2016

2016-07-21T17:34:11Z

Jlovejoy: Created page with "== Attendees == * Kris Reeves * Gary O"Neall * Paul Madick * Jilayne Lovejoy * Dennis Clark * Phil Odence * Sam Ellis == Agenda == 1) v2.5 is now live - send email that it's..."

2016-07-21T17:33:51Z

Created page with "== Attendees == * Kris Reeves * Gary O"Neall * Paul Madick * Jilayne Lovejoy * Dennis Clark * Phil Odence * Sam Ellis == Agenda == 1) v2.5 is now live - send email that it's..."

New page

== Attendees ==
* Kris Reeves
* Gary O"Neall
* Paul Madick
* Jilayne Lovejoy
* Dennis Clark
* Phil Odence
* Sam Ellis

== Agenda ==
1) v2.5 is now live - send email that it's live now to general call and re-sort

2) XML files and review - what needs to be done to get to release stage:
# finish main review of licenses so that all can merged and other clean-up (see sub-list below)
# 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)
# 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
** License matching guidelines page
license list overview page; add info/explanation about XML tags
** define a new process for License List (
** 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.
** Gary to update tools for new XML format

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

@@ Line 15: / Line 15: @@
 * sortable table fixed so that it sorts regardless of lower case/ upper case
-) XML files and review - what needs to be done to get to release stage:
+'''2) SPDX License List XML files''' - what needs to be done to get to release stage:
-# finish main review of licenses so that all can merged and other clean-up (see sub-list below)
+# finish main review of licenses so that all can merged and other clean-up, which also includes: ''(finish by end of August)
-# 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)
+#* opening and closing < SPDX > tag are not always same case - should be all upper-case
-# 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
+#* 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.
-# review various webpages for updating (Alan) - work on in next few weeks, proposal of changes
+#* for those that are tagged as "requires acknowledgement" - reminder to not merge --> Kris to deal with those all at once
-** License matching guidelines page
+#*  Kris to do another pass to do some clean-up, including body tag to be removed
-** License list overview page; add info/explanation about XML tags (with input from Kris and Gary for tags)
+# exceptions need to be added to XML - Kris will add to Github for review, will have own pull requests (Note from Gary: tools don't care whether in same or different directory)
-# define a new process for License List (how to request a new license, what kind of pull requests we want, underlying process etc.)
+# 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)
-# Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats
+# review various webpages for updating --> Alan to do this ''(have first pass for review by group by mid-August)''
-* * Gary already has basic structure in place; time frame such that he could do testing in mid- to end-September
+#* License matching guidelines page
-* * end-of September would aim to have preview of website so we can check it, probably then one more pass at tools, etc.
+#* License list overview page; add info/explanation about XML tags (with input from Kris and Gary for tags)
 # 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)
 Timing:
-* ok to not have Q3 release and aim to have this all done mid-quarter --> end of October
+* ok to not have Q3 release and aim to have this all done mid-quarter --> goal to have full conversion by end of October!!

@@ Line 11: / Line 11: @@
 == Agenda ==
-) v2.5 is now live - send email that it's live now to general call and re-sort
+'''1) v2.5 is now live'''
 ) 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
 # 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.)
 # Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats

@@ Line 17: / Line 17: @@
 # 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)
 # 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)
+# 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
+* * 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.)
 # Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats

@@ Line 18: / Line 18: @@
 # 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)
-  ** License matching guidelines page
+  * * License matching guidelines page
 * * License list overview page; add info/explanation about XML tags
 # define a new process for License List (how to request a new license, what kind of pull requests we want, underlying process etc.)

@@ Line 18: / Line 18: @@
 # 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)
-* * License matching guidelines page
+ ** License matching guidelines page
 * * License list overview page; add info/explanation about XML tags
 # define a new process for License List (how to request a new license, what kind of pull requests we want, underlying process etc.)