Legal Team/Templatizing/ActionPlan

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.

Update (as per Sept 16 meeting):

• decided to do a 2-stage release, as described below
• a bit behind for first stage by end of October, but will push on!

Action Items - Stage 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: 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)
• licenses tagged as "required acknowledgment" do not merge, need another tag (KRIS)
  • may need input from legal team?

Finalize XML tag names

• Gary to bring to tech team for Sept 20 call, tech team to decide, with final review/sanity check by legal team
• do another pass and some other general clean-up, e.g., remove body tag, fix lower case spdx tags and update tags as per tech team recommendations (KRIS)

Check website generation / tools

• As of Sept 16 call, Gary had done a first pass on tools to generate website and caught a bunch of validation errors, many of which were from lower case <spdx> tag. Gary to see what other validations were and fix and merge if simply or create pull request/submit to legal team if needs review
• other updates to spdx-tools for new XML format (including website generation) - for 5 different formats? (Gary?)

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

• 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)
  • 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. (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

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