Legal Team/Templatizing/ActionPlan - Revision history

Brad.edmondson: /* General Cleanup / Future Tag Changes */

2017-08-04T20:21:42Z

‎General Cleanup / Future Tag Changes

Jlovejoy: /* General Cleanup */

2017-06-08T18:02:55Z

‎General Cleanup

Jlovejoy: /* Exceptions */

2017-06-08T17:33:37Z

‎Exceptions

Jlovejoy: /* Action Items - Stage 1a: XML Conversion of Existing Licenses */

2017-06-08T17:31:32Z

‎Action Items - Stage 1a: XML Conversion of Existing Licenses

Jlovejoy at 16:17, 18 April 2017

2017-04-18T16:17:38Z

Brad.edmondson: /* General Cleanup */ add consistency check for license families (e.g. CC-BY)

2017-02-21T19:17:37Z

‎General Cleanup: add consistency check for license families (e.g. CC-BY)

Brad.edmondson: /* True-up license list to current release */ add text-cleanup tasks and make general clean-up separate from true-up

2017-02-16T23:53:55Z

‎True-up license list to current release: add text-cleanup tasks and make general clean-up separate from true-up

Jlovejoy: /* Check website generation / tools */

2017-02-16T20:32:04Z

‎Check website generation / tools

Jlovejoy: /* Incorporating Synonyms into XML license documents */

2017-02-16T20:23:49Z

‎Incorporating Synonyms into XML license documents

Jlovejoy: /* Action Items - Stage 2: Go live with XML conversion */

2017-02-16T20:03:28Z

‎Action Items - Stage 2: Go live with XML conversion

@@ Line 34: / Line 34: @@
 ** get rid of HTML-escaped characters where not needed / keep those that are needed (e.g., greater than / less than symbols)
 ** update XML tag names as per tech team recommendations (see below)
 * Clean-up or formatting issues to be considered later:
-** does all text need to be wrapped in &lt;p&gt; tags? or could titles just be &lt;title&gt;license title&lt;/title&gt; instead of &lt;title&gt;&lt;p&gt;license title&lt;/p&gt;&lt;/title&gt; ?
+** <s>does all text need to be wrapped in &lt;p&gt; tags? or could titles just be &lt;title&gt;license title&lt;/title&gt; instead of &lt;title&gt;&lt;p&gt;license title&lt;/p&gt;&lt;/title&gt;?</s> Yes, [https://github.com/spdx/license-list-XML/issues/414#issuecomment-320094253 everything needs] &lt;p&gt; and &lt;br&gt; tags
 ** add back the &lt;br&gt; tags Brad removed / generally prettify licenses so that they display as close to original as possible
 ** check license families (CC-BY, GPL, etc.) for consistent markup (e.g., what is optional in CC-BY licenses?)

@@ Line 27: / Line 27: @@
 * Review and merge PRs for new licenses/exceptions since 2.3 (ALL) - DONE
-=== General Cleanup ===
+=== General Cleanup / Future Tag Changes ===
 * <span style="color: red;">After review is complete and all licenses and exceptions have been merged, general clean-up to include: (GARY)</span> -->
 * Initial round of clean-up to include:
@@ Line 38: / Line 38: @@
 ** add back the &lt;br&gt; tags Brad removed / generally prettify licenses so that they display as close to original as possible
 ** check license families (CC-BY, GPL, etc.) for consistent markup (e.g., what is optional in CC-BY licenses?)
-** ... other clean-up?
+** add a tag for "deprecated licenses", possibly add more definitive advice on alternative license expression
 ===Tracking license list version for new licenses===

@@ Line 9: / Line 9: @@
 === Exceptions ===
 * Convert and add exceptions to repository (KRIS) - DONE
-* 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 --> they are in their own directory
 * Review exceptions and merge exception PRs (ALL) - DONE

@@ Line 29: / Line 29: @@
 === General Cleanup ===
 * <span style="color: red;">After review is complete and all licenses and exceptions have been merged, general clean-up to include: (GARY)</span> -->
 ** remove body tag
 ** fix lower case spdx tags
-** get rid of HTML- and UTF8-escaped characters
+** get rid of HTML-escaped characters where not needed / keep those that are needed (e.g., greater than / less than symbols)
 ** update XML tag names as per tech team recommendations (see below)
 ** does all text need to be wrapped in &lt;p&gt; tags? or could titles just be &lt;title&gt;license title&lt;/title&gt; instead of &lt;title&gt;&lt;p&gt;license title&lt;/p&gt;&lt;/title&gt; ?
 ** add back the &lt;br&gt; tags Brad removed / generally prettify licenses so that they display as close to original as possible

@@ Line 10: / Line 10: @@
 * Convert and add exceptions to repository (KRIS) - DONE
 * note from Gary: tools don't care whether in same or different directory
-* <span style="color: red;">Review exceptions and merge exception PRs (ALL)</span>
+* Review exceptions and merge exception PRs (ALL) - DONE
 === Deprecated licenses ===
@@ Line 25: / Line 25: @@
 * <span style="color: red;">Need to true-up changes to existing licenses from 2.3 (when XML repo was created) to current 2.6 release using spreadsheet (JILAYNE)</span>
 * Convert and add new licenses to repo from 2.4, 2.5. 2.6 (KRIS or someone from tech team using Kris' tool) - DONE
-* <span style="color: red;">Review and merge PRs for new licenses/exceptions since 2.3 (ALL)</span>
+* Review and merge PRs for new licenses/exceptions since 2.3 (ALL) - DONE
 === General Cleanup ===
@@ Line 32: / Line 32: @@
 ** fix lower case spdx tags
 ** get rid of HTML- and UTF8-escaped characters
-** update tags as per tech team recommendations (see below)
+** update XML tag names as per tech team recommendations (see below)
 ** does all text need to be wrapped in &lt;p&gt; tags? or could titles just be &lt;title&gt;license title&lt;/title&gt; instead of &lt;title&gt;&lt;p&gt;license title&lt;/p&gt;&lt;/title&gt; ?
 ** add back the &lt;br&gt; tags Brad removed / generally prettify licenses so that they display as close to original as possible
 ** check license families (CC-BY, GPL, etc.) for consistent markup (e.g., what is optional in CC-BY licenses?)
-** ... others?
+** ... other clean-up?
 ===Tracking license list version for new licenses===
 * when a new license is added to the list is currently recorded in the new license request list and in the SPDX License List master spreadsheet. Where will this info be in the new XML world? should we put this meta data in license itself, as a new tag or can we use Github release magic to track that way? --> discuss at OSLS, see minutes here: http://wiki.spdx.org/view/Legal_Team/Minutes/2017-02-15-OSLS
-** added new attribute for this, but will only implement for 2.6 and onward, need to check on attribute name
+** added new attribute for this, but will only implement for 2.6 and onward, need to check on attribute name - In Google doc
-* <span style="color: red;">Add attribute to 2.6 new licenses (???) </span>
+* Add attribute to new licenses as of v2.6 - DONE
 === Finalize XML tag names ===
@@ Line 53: / Line 53: @@
 ** completed - see here: https://docs.google.com/document/d/1kGSs3CXbtjF_uZmVsjhXMGChyP-pzlszktTr8t4PmmI/edit#
 * <span style="color: red;">update README on Jan 30 or after with this text </span>
-* <span style="color: red;">update  webpages where needed: (JILAYNE w/help from rest of legal team) </span>
+* update  webpages where needed: (JILAYNE w/help from rest of legal team) - DONE
 ** links to master files
 ** page on requesting a new license - how to update, just point to README?

@@ Line 58: / Line 58: @@
 == Action Items - Stage 2: Go live with XML conversion==
-=== Check website generation / tools ===
+=== Check website generation and 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
 * <span style="color: red;">other updates to spdx-tools for new XML format to generate the website along with the 5 different license formats in available in the license-list-data git repository (Gary) </span>
 * preview of website before release
 === Documentation ===

@@ Line 86: / Line 86: @@
 * Kris had a plan to do this, but not sure he can contribute that now.
 * will postpone this until someone has a plan and can do the work, but will include in the .xsd schema
 === Create new tool to take text of new license and convert to XML file ===

@@ Line 76: / Line 76: @@
 ** other pages?
 ** info about XML tags (http://wiki.spdx.org/view/Legal_Team/Templatizing/tags-matching) - this may become part of spec as an appendix, but where to put in meantime?
 === Coordination with tech team and SPDX Spec v2.2 ===
@@ Line 86: / Line 82: @@
 * v2.2 of spec is not going out this year, so may want to think about stuff that we might want to go into a new appendix eventually, where should it go in the meantime and plan for a migration?
 * ---> discuss at OSLS
 === Incorporating Synonyms into XML license documents ===
 * Kris had a plan to do this, but not sure he can contribute that now.
 * will postpone this until someone has a plan and can do the work, but will include in the .xsd schema