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

Legal Team/Templatizing/ActionPlan

From SPDX Wiki
< Legal Team‎ | Templatizing
Revision as of 17:36, 25 August 2016 by Jlovejoy (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

finish main review of licenses so that all can merged and other clean-up, which also includes: (finish by end of August) 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 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 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) 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 to do this (have first pass for review by group by mid-August) License matching guidelines page 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, 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) Gary to update spdx-tools for new XML format (including website generation) - for 5 different formats (mid- to late- September) 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. 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)