THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Legal Team/Minutes/2012-04-05 (LF Collab Summit)"
From SPDX Wiki
< Legal Team | Minutes
| Line 1: | Line 1: | ||
| − | + | <p><span style="text-decoration: underline;"><strong>SPDX Legal Work Group meeting minutes - 5 April 2012</strong></span></p><p> </p><p class="p1"><strong>Linux Foundation Collab Summit - SPDX face-to-face</strong></p><p class="p1"><strong>Thursday, April 5, 2012</strong></p><p class="p2"> </p><p class="p3"><span class="s1"><strong>1) Different headers for the same license issue</strong></span>: </p><p class="p3">How to capture in License List where the same license text has different "meanings' indicated by different headers. Key examples: MPL v2.0 (Exhibit A or Exhibit A & B); L/GPL licenses ("or later" or "only"). Complete agreement that this information needs to be captured. Question is how to capture/implement?</p><ul><li>A)<span class="s1">PROPOSAL 1</span>: leave 'as is' on license list now which is that these scenarios are captured as a different "line item" (with distinct license name and identifier) for each header scenario that can change the meaning of the license (e.g. GPL-2.0; GPL-2.0+) </li></ul><ol class="ol1"><ul><li class="li3">i)Pros:</li><ul><li class="li3">a)Fedora and Fossology already uses similar short names as we have now (i.e. GPLv2 or GPLv2+)</li><li class="li3">b)Predictable and specifically identified, which is intrinsic to goal of license list</li></ul><li class="li3">ii)Cons:</li><ul><li class="li3">a)Won't match other lists</li></ul><li class="li3">iii)Other considerations:</li><ul><li class="li3">a)if we stay with this route, propose that short identifier says "only" in it?<span class="s2"> </span></li><ul><li class="li3">(1)But then, what about when you aren't sure - which short identifier do you use? Default to "or later?" Is more intuitive to use "GPL-2.0" plain?</li></ul></ul></ul></ol><ul><li>B)<span class="s1">PROPOSAL 2</span>: license list is just the licenses themselves. Headers or alternative exhibits are captured on a separate list that then modifies the license list. </li></ul><ol class="ol1"><ul><li class="li3">i)e.g. On the master license list, GPL v2 would be just that GPL-2.0 (without indicating "or later" or "only"), then the separate list would have the headers variations of the "or later" text present or removed. The short identifier could then be modified by a sub-set of identifier or identifier extension, such as "GPL-2.0" + "or later" or "GPL-v2.0" + "only" - likewise for MPL and its exhibits. Presumably, each scenario would have it's own extension modifier</li><ul><li class="li3">a)potential problems - more to keep track of and more complicated. Is the net result all the different than Proposal 1? </li></ul></ul></ol><p class="p3"><strong>DISCUSSION</strong>:</p><ul class="ul1"><li class="li3"><em>vigorous discussion around pros and cons of #1 and #2 </em></li><li class="li3"><em>variation proposed that combined both proposals</em></li><li class="li3"><em>major problem/drawback with proposal #2 and any variation thereof is potential for explosion of scenarios where modifiers could be used in non-conformant way causing ambiguity or confusion which goes against goal of license list </em></li><li class="li3"><em>advantage of current scenario - it's simple (even if lengthy) and has rigidity needed; but some clarification needed</em></li></ul><p class="p3"><strong>DECISION</strong></p><p class="p3"> leave as is = separate "line items" for GPL v2 only and GPL v2 or later</p><p class="p2"> </p><p class="p3"><strong>TO-DOs</strong></p><ul><li>add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa </li><ul><li>(Jilayne to do for next version of license list)</li></ul><li>add other MPL 2.0 scenarios for Exhibit B (see Luis email and meeting minutes) </li><ul><li>(Jilayne to do for next version of license list)</li></ul><li>need to come up with list of all licenses that fall into this category (same license text appearing more than once on license list) and determine the "default" if SPDX file creator only files license with no delineating header or other information</li><ul><li>(Jilayne or someone else? to come up with list and then discuss on one of next legal calls)</li></ul></ul><p class="p6"> </p><p class="p3"><strong>OTHER RELATED DISCUSSION</strong></p><ul><li>C)<span class="s1">GPL exceptions</span> </li></ul><ol class="ol1"><ul><li>i)how to display license text? Should it be the entire GPL license + exception; or just the header and exception; or just match on the exception text? </li></ul><ol class="ol2"><ul><li><em>a)Did not discuss</em></li></ul></ol><ul><li>ii)How does this interplay with proposals above? If #1, then as is on list, but still need to answer above questions, if #2, then could treat exceptions as part of modifier/extension list? </li></ul><ol class="ol2"><ul><li class="li3"><em>a)Also leave as is in terms of separate line items</em></li><li class="li3"><em>b)acknowledgement that SPDX license list does not have all exceptions and will need to add more (research needed on this to identify holes)</em></li><li class="li3"><em>c)could we come up with a system of separate license modifiers that could be added on modularly to a "GPL-2.0"? </em></li></ul></ol></ol><p class="p7"> </p><ul><li>D)<span class="s1">Standard headers for license</span>s</li></ul><ol class="ol1"><ul><li class="li3"><em>i)Currently this field only shows up on license list spreadsheet, but not on spdx.org license pages; need to add this field including ability to indicate there isn't a standard header, as is the case for most licenses </em></li><ul><li class="li3"><em>a) </em>(Jilayne and Gary to begin working on)</li></ul><li class="li3"><em>ii)need to review license list, to make sure standard headers are correct; remove or indicate "replaceable" text; check if any are missing </em></li><ul><li class="li3">a)(Karen C. and Bill to start this task)</li></ul></ul></ol><p> </p> | |
Revision as of 19:01, 6 April 2012
SPDX Legal Work Group meeting minutes - 5 April 2012
Linux Foundation Collab Summit - SPDX face-to-face
Thursday, April 5, 2012
1) Different headers for the same license issue:
How to capture in License List where the same license text has different "meanings' indicated by different headers. Key examples: MPL v2.0 (Exhibit A or Exhibit A & B); L/GPL licenses ("or later" or "only"). Complete agreement that this information needs to be captured. Question is how to capture/implement?
- A)PROPOSAL 1: leave 'as is' on license list now which is that these scenarios are captured as a different "line item" (with distinct license name and identifier) for each header scenario that can change the meaning of the license (e.g. GPL-2.0; GPL-2.0+)
- i)Pros:
- a)Fedora and Fossology already uses similar short names as we have now (i.e. GPLv2 or GPLv2+)
- b)Predictable and specifically identified, which is intrinsic to goal of license list
- ii)Cons:
- a)Won't match other lists
- iii)Other considerations:
- a)if we stay with this route, propose that short identifier says "only" in it?
- (1)But then, what about when you aren't sure - which short identifier do you use? Default to "or later?" Is more intuitive to use "GPL-2.0" plain?
- B)PROPOSAL 2: license list is just the licenses themselves. Headers or alternative exhibits are captured on a separate list that then modifies the license list.
- i)e.g. On the master license list, GPL v2 would be just that GPL-2.0 (without indicating "or later" or "only"), then the separate list would have the headers variations of the "or later" text present or removed. The short identifier could then be modified by a sub-set of identifier or identifier extension, such as "GPL-2.0" + "or later" or "GPL-v2.0" + "only" - likewise for MPL and its exhibits. Presumably, each scenario would have it's own extension modifier
- a)potential problems - more to keep track of and more complicated. Is the net result all the different than Proposal 1?
DISCUSSION:
- vigorous discussion around pros and cons of #1 and #2
- variation proposed that combined both proposals
- major problem/drawback with proposal #2 and any variation thereof is potential for explosion of scenarios where modifiers could be used in non-conformant way causing ambiguity or confusion which goes against goal of license list
- advantage of current scenario - it's simple (even if lengthy) and has rigidity needed; but some clarification needed
DECISION
leave as is = separate "line items" for GPL v2 only and GPL v2 or later
TO-DOs
- add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa
- (Jilayne to do for next version of license list)
- add other MPL 2.0 scenarios for Exhibit B (see Luis email and meeting minutes)
- (Jilayne to do for next version of license list)
- need to come up with list of all licenses that fall into this category (same license text appearing more than once on license list) and determine the "default" if SPDX file creator only files license with no delineating header or other information
- (Jilayne or someone else? to come up with list and then discuss on one of next legal calls)
OTHER RELATED DISCUSSION
- C)GPL exceptions
- i)how to display license text? Should it be the entire GPL license + exception; or just the header and exception; or just match on the exception text?
- a)Did not discuss
- ii)How does this interplay with proposals above? If #1, then as is on list, but still need to answer above questions, if #2, then could treat exceptions as part of modifier/extension list?
- a)Also leave as is in terms of separate line items
- b)acknowledgement that SPDX license list does not have all exceptions and will need to add more (research needed on this to identify holes)
- c)could we come up with a system of separate license modifiers that could be added on modularly to a "GPL-2.0"?
- D)Standard headers for licenses
- i)Currently this field only shows up on license list spreadsheet, but not on spdx.org license pages; need to add this field including ability to indicate there isn't a standard header, as is the case for most licenses
- a) (Jilayne and Gary to begin working on)
- ii)need to review license list, to make sure standard headers are correct; remove or indicate "replaceable" text; check if any are missing
- a)(Karen C. and Bill to start this task)
