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 15:01, 26 August 2016 by Goneall (Talk | contribs)

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 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: Proposed solution to add a boolean attribute named deprecated to the SPDX element with a default value of false. For the "+" deprecated licenses, we would copy the XML file, rename it to include the "+" and add deprecated=true to the SPDX attributed.
  • add deprecated licenses to repository and review Gary 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)

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

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

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

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

  • probably then one more pass at tools, etc.

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