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
< Legal Team | Templatizing
| Line 11: | Line 11: | ||
* a bit behind for first stage by end of October, but will push on! | * a bit behind for first stage by end of October, but will push on! | ||
| − | ==Action Items - Stage 1== | + | ==Action Items - Stage 1: Initial Release == |
=== Finish main review of all licenses so that all can merged (Who: ALL // WHEN: end of August)=== | === Finish main review of all licenses so that all can merged (Who: ALL // WHEN: end of August)=== | ||
| Line 25: | Line 25: | ||
=== 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 | * Gary to bring to tech team for Sept 20 call, tech team to decide, with final review/sanity check by legal team | ||
| + | ** process: build a table for existing field name (machine-readable name for these from current spec) and new XML tag | ||
* 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) | * 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) | ||
| Line 30: | Line 31: | ||
* 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 | ||
* other updates to spdx-tools for new XML format (including website generation) - for 5 different formats? (Gary?) | * other updates to spdx-tools for new XML format (including website generation) - for 5 different formats? (Gary?) | ||
| + | * preview of website before release? | ||
| − | === Review various webpages for updating ( | + | === Documentation === |
| − | * license matching guidelines page | + | * Update info for README on Github |
| − | * license list overview page, | + | * Review various webpages for updating (changes to be made now? or what until stage 2?) |
| − | + | ** license matching guidelines page | |
| + | ** license list overview page, | ||
| + | ** info about XML tags (http://wiki.spdx.org/view/Legal_Team/Templatizing/tags-matching) - this may be more likely stage 2 and become part of spec as an appendix | ||
| − | == | + | == 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)=== | === 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 | * to do so by hand is a bit tedious. Will still need human review before finalizing | ||
Revision as of 20:48, 15 September 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.
Contents
- 1 Timing
- 2 Action Items - Stage 1: Initial Release
- 3 Action Items - Stage 2: Full XML conversion
- 3.1 Coordination with tech team and SPDX Spec v2.2
- 3.2 Define a new process for License List via Github and with new XML format
- 3.3 Documentation
- 3.4 SPDX tools and website generation
- 3.5 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)
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
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
- process: build a table for existing field name (machine-readable name for these from current spec) and new XML tag
- 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?)
- preview of website before release?
Documentation
- Update info for README on Github
- Review various webpages for updating (changes to be made now? or what until stage 2?)
- license matching guidelines page
- license list overview page,
- info about XML tags (http://wiki.spdx.org/view/Legal_Team/Templatizing/tags-matching) - this may be more likely stage 2 and become part of spec as an appendix
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
