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

Difference between revisions of "Legal Team/Templatizing/ActionPlan"

From SPDX Wiki
Jump to: navigation, search
Line 10: Line 10:
 
==Action Items==
 
==Action Items==
  
===1) Finish main review of all licenses so that all can merged (Who: ALL // WHEN: end of August)
+
===1) Finish main review of all licenses so that all can merged (Who: ALL // WHEN: end of August)===
 
This also includes:
 
This also includes:
 
* add exceptions to repository and review (KRIS to add // ALL to review)
 
* add exceptions to repository and review (KRIS to add // ALL to review)
 
** note from Gary: tools don't care whether in same or different directory
 
** note from Gary: tools don't care whether in same or different directory
 
* how to deal with deprecated licenses (KRIS and GARY discussed)
 
* how to deal with deprecated licenses (KRIS and GARY discussed)
** outcome:  
+
** outcome: these files are needed for tools... (gary to add more info here, reivew on next call)
 
* add deprecated licenses to repository and review KRIS to add // ALL to review)
 
* add deprecated licenses to repository and review KRIS to add // ALL to review)
opening and closing < SPDX > tag are not always same case - should be all upper-case
+
* do another pass and some other general clean-up, e.g., remove body tag (KRIS)
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.
+
* licenses tagged as "required acknowledgment" do not merge, need another tag (KRIS)
for those that are tagged as "requires acknowledgement" - reminder to not merge --> Kris to deal with those all at once
+
Kris to do another pass to do some clean-up, including body tag to be removed
+
  
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)
+
===2) Review various webpages for updating (Who: ALAN // When: End of August)===
review various webpages for updating --> Alan to do this (have first pass for review by group by mid-August)
+
* license matching guidelines page
License matching guidelines page
+
* license list overview page, including adding explanatory info about XML tags (http://wiki.spdx.org/view/Legal_Team/Templatizing/tags-matching)  
License list overview page; add info/explanation about XML tags (with input from Kris and Gary for tags)
+
** Alan to send via email in document for review before next call
define a new process for License List, i.e., how to request a new license, what kind of pull requests we want, underlying process etc. --> Jilayne to do this (end of August for review by group)
+
 
check with Kate re: moving license list to Github primary (instead of LF Git and mirrored to Github)
+
===3) Define a new process for License List, i.e., how to request a new license, what kind of pull requests we want, underlying process etc. (WHO: Jilayne // When: end of August)===
Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats (mid- to late- September)
+
* included checking with Kate re: moving license list to Github primary (instead of LF Git and mirrored to Github)
Gary already has basic structure in place; time frame such that he could do testing in mid- to end-September
+
** Jilayne to send draft for review via email
end-of September would aim to have preview of website so we can check it, probably then one more pass at tools, etc.
+
 
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)
+
===4) Update spdx-tools for new XML format (including website generation) - for 5 different formats (WHO: Gary // When: mid- to late- September)===
 +
* Gary already has basic structure in place; time frame needs to be such that he could do testing in mid- to end-September
 +
 
 +
===5) Have preview of website so we can check it (WHO: Gary & Jilayne // When: end of Sept)===
 +
* probably then one more pass at tools, etc.
 +
 
 +
===6) Create new tool to take text of new license and convert to XML file (WHO: Kris? // When: doesn't have to be done for release in Oct)
 +
* to do so by hand is a bit tedious. Will still need human review before finalizing

Revision as of 18:36, 25 August 2016

We came up with a timeline and action items on the July 21 legal call for going live with the new SPDX License List. That list is posted here, so we can track progress and update on one place.

Timing

Timing:

Goal to have full conversion and live by end of October 2016

As such, we decided it's okay to not have a Q3 release.

Action Items

1) Finish main review of all licenses so that all can merged (Who: ALL // WHEN: end of August)

This also includes:

  • add exceptions to repository and review (KRIS to add // ALL to review)
    • note from Gary: tools don't care whether in same or different directory
  • how to deal with deprecated licenses (KRIS and GARY discussed)
    • outcome: these files are needed for tools... (gary to add more info here, reivew on next call)
  • add deprecated licenses to repository and review KRIS to add // ALL to review)
  • do another pass and some other general clean-up, e.g., remove body tag (KRIS)
  • licenses tagged as "required acknowledgment" do not merge, need another tag (KRIS)

2) Review various webpages for updating (Who: ALAN // When: End of August)

3) Define a new process for License List, i.e., how to request a new license, what kind of pull requests we want, underlying process etc. (WHO: Jilayne // When: end of August)

  • included checking with Kate re: moving license list to Github primary (instead of LF Git and mirrored to Github)
    • Jilayne to send draft for review via email

4) Update spdx-tools for new XML format (including website generation) - for 5 different formats (WHO: Gary // When: mid- to late- September)

  • Gary already has basic structure in place; time frame needs to be such that he could do testing in mid- to end-September

5) Have preview of website so we can check it (WHO: Gary & Jilayne // When: end of Sept)

  • probably then one more pass at tools, etc.

===6) Create new tool to take text of new license and convert to XML file (WHO: Kris? // When: doesn't have to be done for release in Oct)

  • to do so by hand is a bit tedious. Will still need human review before finalizing