THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "Legal Team/Minutes/2011-10-05"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
<p class="MsoNormal"><strong><span style="text-decoration: underline;"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">SPDX Legal Workstream Meeting Minutes</span></span></strong></p><p class="MsoNormal"><strong><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">5 October 2011</span></strong></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Esteban Rockett, Motorola</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Adam Cohn, Cisco</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Karen Copenhaver, Choate Hall</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Jilayne Lovejoy, OpenLogic</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Kirsten Newcomer, Black Duck</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Peter Williams, OpenLogic</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Mark Gisi, Wind River</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Tom Incorvia, Microfocus</span></p><p class="MsoNormal"><span style="font-family: Arial; font-size: 10pt;">&nbsp;</span></p><p class="MsoNormal"><span style="text-decoration: underline;"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">I) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LInux website update: coming online again slowly, but SPDX site still not up. Issues:</span></span></p><ul><li><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">we've been sending people there and not up; tools not accessible, etc.&nbsp;</span></li><ul><li><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">What are our backup mechanisms if this happened again? No backup solution right now, but John Ellis and Martin M. working on this</span></li></ul><li><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">email lists also down - Phil suggested to create google groups to preserve email lists, he is working on that now</span></li><ul><li><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Kate is also setting up IRC</span></li></ul></ul><p class="MsoNormal"><span style="text-decoration: underline;"><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">II)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Update on Discussion w/ Breakout Group on CC-0 &amp; Draft Preamble</span></span><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;"><br /></span></p><ul><li><span style="font-size: 11pt;">circulated below draft of preamble for CC-0 for review by group.&nbsp; Rockett to take it to Eben Moglen next for his input</span></li><li><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">companies more concerned with "disclaimer" that even though put info in here, no responsibility for reliance on info downstream, so may need language as such. Could use disclaimer of warranties from GPL v3 because it was an attempt to address international perspective for this</span></li><li><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">or could say in preamble, "to the extent there is any IP rights at all (whether database rights) in any jurisdiction, it's covered by CC-0…" and "regardless of whether there is IP coverage, the disclaimer paragraph applies to all contributions"</span></li><li><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">maybe good to talk to Eben and get his feedback and go from there</span></li><li><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">See Mark's "rationale" document for a good summarization of the five key goals/concerns here</span></li><ul><li><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">Goal of this document is to stand by itself as an explanation and to show the comprehensive process that was undertaken to make this decision (will be posted)</span></li></ul></ul><p class="MsoNormal"><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;"> <strong>** Draft SPDX CC-0 Preamble **</strong><br /> Compliance with the SPDX specification includes populating the SPDX fields therein with data related to such fields ("SPDX-Metadata").<br /> <br /> The SPDX specification contains numerous fields where an SPDX author may provide relevant explanatory text in SPDX-Metadata.<br /> <br /> Without opining on the lawfulness of "database rights" (in jurisdictions where applicable), such explanatory text is copyrightable subject matter in most Berne Convention countries.<br /> <br /> By using the SPDX specification, or any portion hereof, you hereby agree that any copyright rights (as determined by your jurisdiction) in any SPDX-Metadata, including without limitation explanatory text, shall be subject to the terms of the below recited Creative Commons CC0 1.0 Universal license (reproduced in its entirety below).</span></p><p class="MsoNormal"><span style="text-decoration: underline;"><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">III)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style="text-decoration: underline;"><span style="font-size: 10.0pt; font-family: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: EN-US;">European OpenSource &amp; Free Software Law Event (EOLE) </span></span><span lang="EN-GB"><a href="http://eolevent.eu/en"><span style="font-size: 10.0pt; font-family: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; color: blue; mso-ansi-language: EN-US;" lang="EN-US">http://eolevent.eu/en</span></a></span><span style="text-decoration: underline;"><span style="font-size: 10.0pt; font-family: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: EN-US;">on Nov 4 in Barcelona </span></span></p><p class="MsoNormal"><span style="font-family: Arial; font-size: 10pt;">Malcom Bain might be going - Karen to reach out to him, could get him up to speed easily even though he has not been involved</span></p><p class="MsoNormal"><span style="text-decoration: underline;"><span style="font-size: 11.0pt; font-family: Calibri; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US;">IV)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Update on Discussion w/Breakout Group on Templatizing </span></span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">&nbsp;</span><span style="font-family: Arial; font-size: 10pt;">Jilayne sent around draft document setting forth guidelines (if you didn't get this, let someone know to forward)</span></p><p class="MsoNormal"><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Outstanding issues: "BSD" license issue regarding where/how to allow replaceable text and how/what to allow matching on for headers alone</span></p><p class="MsoListParagraphCxSpFirst" style="text-indent: -.25in; mso-list: l0 level1 lfo2;"><!--[if !supportLists]--><span style="font-size: 10.0pt; font-family: Calibri; mso-fareast-font-family: Calibri; mso-bidi-font-family: Calibri;" lang="EN-GB">-<span style="font: 7.0pt 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><!--[endif]--><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Jilayne and Rockett to draw up straw mans on these issues and distribute for feedback at next meeting </span></p><p class="MsoListParagraphCxSpLast" style="text-indent: -.25in; mso-list: l0 level1 lfo2;"><!--[if !supportLists]--><span style="font-size: 10.0pt; font-family: Calibri; mso-fareast-font-family: Calibri; mso-bidi-font-family: Calibri;" lang="EN-GB">-<span style="font: 7.0pt 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><!--[endif]--><span style="font-size: 10.0pt; font-family: Arial; mso-bidi-font-family: Arial;" lang="EN-GB">Distribute to tech group at this point as well for feedback there</span></p>
+
== Attendees ==
 +
 
 +
* Esteban Rockett, Motorola
 +
* Adam Cohn, Cisco
 +
* Karen Copenhaver, Choate Hall
 +
* Jilayne Lovejoy, OpenLogic
 +
* Kirsten Newcomer, Black Duck
 +
* Peter Williams, OpenLogic
 +
* Mark Gisi, Wind River
 +
* Tom Incorvia, Microfocus
 +
 
 +
== Linux website update ==
 +
 
 +
Coming online again slowly, but SPDX site still not up
 +
 
 +
Issues:
 +
 
 +
* we've been sending people there and not up; tools not accessible, etc.
 +
** What are our backup mechanisms if this happened again? No backup solution right now, but John Ellis and Martin M. working on this
 +
* email lists also down - Phil suggested to create google groups to preserve email lists, he is working on that now
 +
** Kate is also setting up IRC
 +
 
 +
== Update on Discussion w/ Breakout Group on CC-0 &amp; Draft Preamble ==
 +
 
 +
* circulated below draft of preamble for CC-0 for review by group. Rockett to take it to Eben Moglen next for his input
 +
* companies more concerned with "disclaimer" that even though put info in here, no responsibility for reliance on info downstream, so may need language as such. Could use disclaimer of warranties from GPL v3 because it was an attempt to address international perspective for this
 +
* or could say in preamble, "to the extent there is any IP rights at all (whether database rights) in any jurisdiction, it's covered by CC-0…" and "regardless of whether there is IP coverage, the disclaimer paragraph applies to all contributions"
 +
* maybe good to talk to Eben and get his feedback and go from there
 +
* See Mark's "rationale" document for a good summarization of the five key goals/concerns here
 +
** Goal of this document is to stand by itself as an explanation and to show the comprehensive process that was undertaken to make this decision (will be posted)
 +
 
 +
'''Draft SPDX CC-0 Preamble'''
 +
 
 +
Compliance with the SPDX specification includes populating the SPDX fields therein with data related to such fields ("SPDX-Metadata").
 +
 
 +
The SPDX specification contains numerous fields where an SPDX author may provide relevant explanatory text in SPDX-Metadata.
 +
 
 +
Without opining on the lawfulness of "database rights" (in jurisdictions where applicable), such explanatory text is copyrightable subject matter in most Berne Convention countries.
 +
 
 +
By using the SPDX specification, or any portion hereof, you hereby agree that any copyright rights (as determined by your jurisdiction) in any SPDX-Metadata, including without limitation explanatory text, shall be subject to the terms of the below recited Creative Commons CC0 1.0 Universal license (reproduced in its entirety below).
 +
 
 +
== European OpenSource &amp; Free Software Law Event (EOLE) ==
 +
 
 +
[http://eolevent.eu/|European OpenSource and Free Software Law Event]
 +
 
 +
Nov 4 in Barcelona
 +
 
 +
Malcom Bain might be going - Karen to reach out to him, could get him up to speed easily even though he has not been involved
 +
 
 +
== Update on Discussion w/Breakout Group on Templatizing ==
 +
 
 +
Jilayne sent around draft document setting forth guidelines (if you didn't get this, let someone know to forward)
 +
 
 +
Outstanding issues: "BSD" license issue regarding where/how to allow replaceable text and how/what to allow matching on for headers alone
 +
 
 +
Jilayne and Rockett to draw up straw mans on these issues and distribute for feedback at next meeting
 +
 
 +
Distribute to tech group at this point as well for feedback there
 +
 
 +
[[Category:Legal|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 17:40, 5 March 2013

Attendees

  • Esteban Rockett, Motorola
  • Adam Cohn, Cisco
  • Karen Copenhaver, Choate Hall
  • Jilayne Lovejoy, OpenLogic
  • Kirsten Newcomer, Black Duck
  • Peter Williams, OpenLogic
  • Mark Gisi, Wind River
  • Tom Incorvia, Microfocus

Linux website update

Coming online again slowly, but SPDX site still not up

Issues:

  • we've been sending people there and not up; tools not accessible, etc.
    • What are our backup mechanisms if this happened again? No backup solution right now, but John Ellis and Martin M. working on this
  • email lists also down - Phil suggested to create google groups to preserve email lists, he is working on that now
    • Kate is also setting up IRC

Update on Discussion w/ Breakout Group on CC-0 & Draft Preamble

  • circulated below draft of preamble for CC-0 for review by group. Rockett to take it to Eben Moglen next for his input
  • companies more concerned with "disclaimer" that even though put info in here, no responsibility for reliance on info downstream, so may need language as such. Could use disclaimer of warranties from GPL v3 because it was an attempt to address international perspective for this
  • or could say in preamble, "to the extent there is any IP rights at all (whether database rights) in any jurisdiction, it's covered by CC-0…" and "regardless of whether there is IP coverage, the disclaimer paragraph applies to all contributions"
  • maybe good to talk to Eben and get his feedback and go from there
  • See Mark's "rationale" document for a good summarization of the five key goals/concerns here
    • Goal of this document is to stand by itself as an explanation and to show the comprehensive process that was undertaken to make this decision (will be posted)

Draft SPDX CC-0 Preamble

Compliance with the SPDX specification includes populating the SPDX fields therein with data related to such fields ("SPDX-Metadata").

The SPDX specification contains numerous fields where an SPDX author may provide relevant explanatory text in SPDX-Metadata.

Without opining on the lawfulness of "database rights" (in jurisdictions where applicable), such explanatory text is copyrightable subject matter in most Berne Convention countries.

By using the SPDX specification, or any portion hereof, you hereby agree that any copyright rights (as determined by your jurisdiction) in any SPDX-Metadata, including without limitation explanatory text, shall be subject to the terms of the below recited Creative Commons CC0 1.0 Universal license (reproduced in its entirety below).

European OpenSource & Free Software Law Event (EOLE)

OpenSource and Free Software Law Event

Nov 4 in Barcelona

Malcom Bain might be going - Karen to reach out to him, could get him up to speed easily even though he has not been involved

Update on Discussion w/Breakout Group on Templatizing

Jilayne sent around draft document setting forth guidelines (if you didn't get this, let someone know to forward)

Outstanding issues: "BSD" license issue regarding where/how to allow replaceable text and how/what to allow matching on for headers alone

Jilayne and Rockett to draw up straw mans on these issues and distribute for feedback at next meeting

Distribute to tech group at this point as well for feedback there