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 1: Line 1:
−
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: Initial Release ==
 
==Action Items - Stage 1: Initial Release ==
−
Update as of Nov 10th legal call
 
  
 
=== Finish main review of all licenses so that all can merged (Who: ALL)===
 
=== Finish main review of all licenses so that all can merged (Who: ALL)===
−
This also includes:
+
* Kris to put original "conversion" tool (to convert text files into XML format, to then be reviewed) in public repository so anyone else can use it or improve it (KRIS)
−
* <span style="color: red;">add exceptions to repository (KRIS) and review (ALL to review)</span>
+
* <span style="color: red;">convert and add exceptions to repository (KRIS or someone from tech team using Kris' tool) and review exceptions to merge (ALL)</span>
 
** 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
−
* add /deal with deprecated licenses  
+
* <span style="color: red;">convert and add deprecated licenses to repository (GARY) and review to merge (ALL)</span>
 
** 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.   
 
** 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.   
−
** <span style="color: red;">add deprecated licenses to repository (GARY) and review (ALL to review)</span>
 
 
* licenses tagged as "required acknowledgment" do not merge, need another tag --> decided to make this a future feature; keep labeling these for future update
 
* licenses tagged as "required acknowledgment" do not merge, need another tag --> decided to make this a future feature; keep labeling these for future update
−
** may need input from legal team?
+
** may need input from legal team at that point
−
* <span style="color: red;">true-up changes to licenses in list from 2.3 to current, 2.6 (ANYONE, see spreadsheet)</span>
+
* <span style="color: red;">true-up changes to existing licenses from 2.3 to current, 2.6 (ANYONE, see spreadsheet)</span>
−
* <span style="color: red;">add new licenses to repo and convert to XML (KRIS) and review (ALL to review)</span>
+
* <span style="color: red;">convert and add new licenses to repo from 2.4, 2.5. 2.6 (KRIS or someone from tech team using Kris' tool) and review to merge (ALL to review)</span>
−
* <span style="color: red;">do another pass and some other general clean-up, e.g., remove body tag, fix lower case spdx tags, get rid of HTML &-; characters, and update tags as per tech team recommendations (find someone else from tech team??</span>
+
* <span style="color: red;">general clean-up of all licenses (once review is completed and all have been merged), e.g., remove body tag, fix lower case spdx tags, get rid of HTML &-; characters, and update tags as per tech team recommendations (someone from tech team)</span> --> discuss at OSLS
−
 
+
  
 
=== Finalize XML tag names ===
 
=== 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 - DONE
 
* Gary to bring to tech team for Sept 20 call, tech team to decide, with final review/sanity check by legal team - DONE
 
** process: build a table for existing field name (machine-readable name for these from current spec) and new XML tag
 
** process: build a table for existing field name (machine-readable name for these from current spec) and new XML tag
−
** Gary took to tech team, and had joint call with legal and tech team to finalize. notes here: http://wiki.spdx.org/view/Technical_Team/Minutes/2016-10-25
+
** Gary took to tech team, and had joint call with legal and tech team to finalize. notes here: http://wiki.spdx.org/view/Technical_Team/Minutes/2016-10-25 and https://docs.google.com/document/d/1z9n44xLH2MxT576KS_AbTOBtecyl5cw6RsrrQHibQtg/edit
−
* <span style="color: red;">update tags as per tech team recommendations (see above)</span>
+
* update tags as per tech team recommendations (see above)
  
 
=== Check website generation / tools ===
 
=== 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
 
* 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
 
* <span style="color: red;">other updates to spdx-tools for new XML format (including website generation) - for 5 different formats? (Gary?) </span>
 
* <span style="color: red;">other updates to spdx-tools for new XML format (including website generation) - for 5 different formats? (Gary?) </span>
−
* preview of website before release?
+
* preview of website before release
  
 
=== Documentation ===
 
=== Documentation ===
 
* Update info for README on Github (Dennis to draft, ALL review)
 
* Update info for README on Github (Dennis to draft, ALL review)
−
** first review completed on Nov 10th call. second review via email/remote - DONE (add link here)
+
** completed - see here: https://docs.google.com/document/d/1kGSs3CXbtjF_uZmVsjhXMGChyP-pzlszktTr8t4PmmI/edit#
 
* Review various webpages for updating (changes to be made now? or what until stage 2?) - Alan did first pass, which raised various questions and other things to address, need to revisit now that naming issue has been resolved with tech team
 
* Review various webpages for updating (changes to be made now? or what until stage 2?) - Alan did first pass, which raised various questions and other things to address, need to revisit now that naming issue has been resolved with tech team
 
** license matching guidelines page
 
** license matching guidelines page

Revision as of 22:10, 17 January 2017

Action Items - Stage 1: Initial Release

Finish main review of all licenses so that all can merged (Who: ALL)

  • Kris to put original "conversion" tool (to convert text files into XML format, to then be reviewed) in public repository so anyone else can use it or improve it (KRIS)
  • convert and add exceptions to repository (KRIS or someone from tech team using Kris' tool) and review exceptions to merge (ALL)
    • note from Gary: tools don't care whether in same or different directory
  • convert and add deprecated licenses to repository (GARY) and review to merge (ALL)
    • 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.
  • licenses tagged as "required acknowledgment" do not merge, need another tag --> decided to make this a future feature; keep labeling these for future update
    • may need input from legal team at that point
  • true-up changes to existing licenses from 2.3 to current, 2.6 (ANYONE, see spreadsheet)
  • convert and add new licenses to repo from 2.4, 2.5. 2.6 (KRIS or someone from tech team using Kris' tool) and review to merge (ALL to review)
  • general clean-up of all licenses (once review is completed and all have been merged), e.g., remove body tag, fix lower case spdx tags, get rid of HTML &-; characters, and update tags as per tech team recommendations (someone from tech team) --> discuss at OSLS

Finalize XML tag names

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?)
  • preview of website before release

Documentation

Action Items - Stage 2: Full XML conversion

Coordination with tech team and SPDX Spec v2.2

  • revisions to current appendix in spec as to markup (e.g., var v. alt markup tag)
  • explanation of XML tags - to go in markup appendix or new appendix?

Define a new process for License List via Github and with new XML format

  • i.e., how to request a new license, what kind of pull requests we want, underlying process etc.
  • included checking with Kate re: moving license list to Github primary (instead of LF Git and mirrored to Github)

Documentation

  • see stage 1 list - any further updates?

SPDX tools and website generation

  • see stage 1 list - any further updates?

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
Retrieved from "https://wiki.spdx.org/index.php?title=Legal_Team/Templatizing/ActionPlan&oldid=4091"