https://wiki.spdx.org/index.php?title=Legal_Team/Minutes/2012-03-07&feed=atom&action=historyLegal Team/Minutes/2012-03-07 - Revision history2024-03-29T10:49:52ZRevision history for this page on the wikiMediaWiki 1.23.13https://wiki.spdx.org/index.php?title=Legal_Team/Minutes/2012-03-07&diff=1458&oldid=prevMartinMichlmayr: Convert to MediaWiki syntax2013-03-06T11:41:57Z<p>Convert to MediaWiki syntax</p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 11:41, 6 March 2013</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"><p><strong>SPDX Legal Team - meeting minutes for 7 March 2012</strong></p><ul><li></del>Tom Incorvia, Microfocus<del class="diffchange diffchange-inline"></li><li></del>Adam Cohn, Cisco<del class="diffchange diffchange-inline"></li><li></del>Colin Wright, McKesson<del class="diffchange diffchange-inline"></li><li></del>Mark Gisi, Windriver<del class="diffchange diffchange-inline"></li><li></del>Peter Williams, OpenLogic<del class="diffchange diffchange-inline"></li><li></del>Michael Herzog, NexB<del class="diffchange diffchange-inline"></li><li></del>Jilayne Lovejoy, OpenLogic<del class="diffchange diffchange-inline"></li><li></del>Karen Copenhaver, Choate Hall<del class="diffchange diffchange-inline"></li><li></del>Luis Villa, Greenberg Taurig<del class="diffchange diffchange-inline"></li></ul><p></del>Agenda:<del class="diffchange diffchange-inline"></p><ol><li></del>Update on various feedback<del class="diffchange diffchange-inline"></li><li></del>to-do's on the hopper - including priority items to get done before April 6 SPDX Forum in San Jose<del class="diffchange diffchange-inline"></li></ol><p></del>("assignments" and action items in all caps)<del class="diffchange diffchange-inline"></p><p>1) </del>License List is getting more attention as seen by recent correspondance by persons outside the group looking to use the license list as a reference/standard/resource for referring to licenses. <del class="diffchange diffchange-inline">&nbsp;</del>Take-away of this is the the License List is shaping up to be an "entry point" from SPDX generally, i.e. easier to adopt names, as many organizations have a need to have a standard way to refer to licenses. from there may lead to adoption of spec. <del class="diffchange diffchange-inline">&nbsp;</del>Sub-text - even higher priority/pressure to resolve outstanding issues and create guidelines for matching, etc. so we can move to a more stable maintenence role. <del class="diffchange diffchange-inline">&nbsp;&nbsp;</p><ul><li></del>Notably: Phil, Karen, and Jilayne had a call with David Wheeler from IDA regarding having the license list include a way to identify U.S. Gov't works and the legal reality that that represents. <del class="diffchange diffchange-inline">&nbsp;</del>David is going to send some standard headers, so this will be something to add to the list and configure in the near future. <del class="diffchange diffchange-inline">&nbsp;</li><ul><li></del>will entail a new short identifier, possibly an explanation and reference to relevant U.S. statutes and may include multiple headers that "point" to this same designation.<del class="diffchange diffchange-inline"></li><li></del>JILAYNE AND KAREN TO FOLLOW-UP AND GET PROPOSAL GOING FOR THIS<del class="diffchange diffchange-inline"></li></ul></ul><p>2) </del>To-dos<del class="diffchange diffchange-inline">:</p><ul><li></del>finish <del class="diffchange diffchange-inline"><strong></del>license text review<del class="diffchange diffchange-inline"></strong></li><ul><li></del>got licenses back from Adam, Phil, Paul, Peter; Michael and Rockett still working on theirs. <del class="diffchange diffchange-inline">&nbsp;</del>There were many changes/updates, so good we did this!<del class="diffchange diffchange-inline"></li><li></del>goal to have this DONE by next call - about 60 more licenses to assign. volunteers for next round listed below. <del class="diffchange diffchange-inline">&nbsp;</del>if anyone else can assist, please tell Jilayne asap!! see<del class="diffchange diffchange-inline">&nbsp;http:</del>//<del class="diffchange diffchange-inline">spdx.org/wiki/legal-team-meeting-minutes-</del>2012-02-22 for description of process<del class="diffchange diffchange-inline"></li><ul><li></del>COLIN <del class="diffchange diffchange-inline">&nbsp;</del>- lines 102 thru 113<del class="diffchange diffchange-inline"></li><li></del>ADAM <del class="diffchange diffchange-inline">&nbsp;</del>- lines 114 thru 125<del class="diffchange diffchange-inline"></li><li></del>PHIL - lines 126 thru 137<del class="diffchange diffchange-inline"></li></ul></ul></ul><ul><li><strong></del>OSI license list issues<del class="diffchange diffchange-inline"></strong> </del>- Karl Fogel responded (email went to group)<del class="diffchange diffchange-inline"></li><ul><li></del>JILAYNE TO FOLLOW-UP SEE IF WE CAN GET ISSUES SORTED BY APRIL 6TH FORUM<del class="diffchange diffchange-inline"></li></ul></ul><ul><li></del>resolve other License List issues among group: (see further discussion below)<del class="diffchange diffchange-inline"></li><ul><li><strong></del>BSD Licenses overview<del class="diffchange diffchange-inline"></strong> </del>- Tom sent email to group prior to meeting for discussion, see for reference<del class="diffchange diffchange-inline"></li><ul><li></del>recommendation to ADD: BSD 4-Clause specific to the U. of California in order to accomodate the scenario where a original 4-clause license is retroactively turned into a 3-clause as per July 22, 1999 notice from William Hoskins, Directore of Office of Tech Licensing, UC-Berkeley<del class="diffchange diffchange-inline"></li><ul><li></del>in contrast, a match to the "plain" BSD 4-clause will not carry this retroactive change and just refer to the full 4 clause license<del class="diffchange diffchange-inline"></li><li></del>add to license list along with the notice in the Notes field and an explanation as needed<del class="diffchange diffchange-inline"></li><li></del>DECISION BY GROUP: Yes to adding this license<del class="diffchange diffchange-inline"></li></ul><li></del>text variations such as "copyright holder" v. "copyright owner" - equivalent? can we handle via equivalent words list or need to deal with more broadly in matching guidelines? also need to consider where "or contributors" is present or not<del class="diffchange diffchange-inline"></li><ul><li></del>under US law,<del class="diffchange diffchange-inline">&nbsp;</del>"copyright holder" v. "copyright owner" can be considered the same, but would want European perspective on this - PENDING someone on call who can speak to this<del class="diffchange diffchange-inline"></li><li></del>generally, these issues need to be dealt with via the license match guidelines for when to "ignore" some of this text - TBD<del class="diffchange diffchange-inline"></li></ul><li></del>Review of current naming of various BSD licenses - okay as is, no change recommended<del class="diffchange diffchange-inline"></li><li></del>FreeBSD and NetBSD both have an extra line at end or beginning. <del class="diffchange diffchange-inline">&nbsp;</del>under matching guidelines this would be considered a different license (than standard BSD). <del class="diffchange diffchange-inline">&nbsp;</del>Due to there both being prominent projects, should these two licenses be added as separate?<del class="diffchange diffchange-inline"></li><ul><li></del>TOM TO SEND EMAIL TO LIST TO DESCRIBE SCENARIO AND DISCUSS AT NEXT MEETING<del class="diffchange diffchange-inline"></li></ul></ul><li></del>also discussed concept of buckets for types of licenses, i.e. attribution v. permissive - bunch of ideas around this, as well as acknowledgement that this may go beyond scope of SPDX? <del class="diffchange diffchange-inline">&nbsp;</li><ul><li></del>Mark to submit proposal for review by group as not enough time to discuss now<del class="diffchange diffchange-inline"></li><li></li></ul><li><strong></del>MPL 2.0<del class="diffchange diffchange-inline"></strong> </del>exhibits discussion (including discussion of GPL only or or later) - Luis Villa joined call to assist with explanation and guidance<del class="diffchange diffchange-inline"></li><ul><li></del>Luis gave an overview of the MPL v2.0 exhibits and rationale behind (also on previous email thread)<del class="diffchange diffchange-inline"></li><li></del>discussed in tangent with GPL only v. or later issue - currently have these as separate line items on License List - everyone agrees that capturing that distinction is key/wanted, but how best to do so? <del class="diffchange diffchange-inline">&nbsp;</del>how we have it currently or one license line item with the options of different headers?<del class="diffchange diffchange-inline"></li><ul><li></del>suggested to have some kind of modifiers, i.e license is GPL v2 and modfied with an "or later" or "only" (or even "exception") designator<del class="diffchange diffchange-inline"></li><li></del>different list for headers? that inter-operates with License List?<del class="diffchange diffchange-inline"></li><li></del>legal team needs to decide WHAT needs to be identified then go to technical team to determine HOW to implement<del class="diffchange diffchange-inline"></li><li></del>suggested futher discussion on next call and set aside time during workgroup meeting on Thursday, April 5 at Linux Collab Summit to flesh this issue out a bit more.<del class="diffchange diffchange-inline"></li></ul></ul><li></li><li><strong></del>GPL exceptions<del class="diffchange diffchange-inline"></strong> </del>- how do we "define" the actua license text (for the license list itself, as well as matching guidelines: should it be the license itself plus the exception text or the exception text only?)<del class="diffchange diffchange-inline"></li></ul></ul><ul><li><strong></del>license matching guidelines<del class="diffchange diffchange-inline"></strong> </del>- finish/pickup where left off a couple calls ago. still need to cover the headers/notices matching issue and replaceable text (template) issues as the big remaining items - gets intertwined with License List issues<del class="diffchange diffchange-inline"></li></ul><ul><li><strong></del>website migration<del class="diffchange diffchange-inline"></strong> </del>- no progress on this and legal team is now weak link - need someone to take on this task and get done asap. <del class="diffchange diffchange-inline">&nbsp;</del>May also need to re-think navigation for legal portion as well as additional pages/information but for now, just need to get stuff copied/moved into new format.<del class="diffchange diffchange-inline"></li><ul><li></del>MARK TO TAKE LEAD WITH THIS (MAY ENGAGE PIERRE FOR HELP, IF NEEDED)<del class="diffchange diffchange-inline"></li></ul></ul><ul><li><strong></del>Process for adding new licenses to list<del class="diffchange diffchange-inline"></strong></li><ul><li></del>currently with business team, but does it make sense to have it go back to legal team or a sub-group thereof<del class="diffchange diffchange-inline"></li><li></del>current process discussed is outlined here: <del class="diffchange diffchange-inline">&nbsp;http://spdx.org/wiki/process-adding-license-list-draft<</del>/<del class="diffchange diffchange-inline">li><li></del>ideally need to review this and be able to describe at SPDX Forum on April 6<del class="diffchange diffchange-inline"></li></ul></ul><ul><li><strong></del>Prepare for SPDX Forum<del class="diffchange diffchange-inline"></strong> </del>on April 6<del class="diffchange diffchange-inline"></li><ul><li></del>GARY AND JILAYNE TO PRESENT ON "Getting started with SPDX" - suggestions from group welcome :)<del class="diffchange diffchange-inline"></li><li></del>registration should be up soon, look for email from Kim<del class="diffchange diffchange-inline"></li><li></del>info here for now: <del class="diffchange diffchange-inline">&nbsp;http</del>:<del class="diffchange diffchange-inline">//spdx.org/wiki/spdx-forum-managing-open-source-software-licenses-suppliers-and-customers</li></ul></ul><p>&nbsp;</p></del></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== Attendees ==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Tom Incorvia, Microfocus</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Adam Cohn, Cisco</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Colin Wright, McKesson</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Mark Gisi, Windriver</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Peter Williams, OpenLogic</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Michael Herzog, NexB</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Jilayne Lovejoy, OpenLogic</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Karen Copenhaver, Choate Hall</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Luis Villa, Greenberg Taurig</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== </ins>Agenda: <ins class="diffchange diffchange-inline">==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline"># </ins>Update on various feedback</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline"># </ins>to-do's on the hopper - including priority items to get done before April 6 SPDX Forum in San Jose</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>("assignments" and action items in all caps)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== License List ==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>License List is getting more attention as seen by recent correspondance by persons outside the group looking to use the license list as a reference/standard/resource for referring to licenses. Take-away of this is the the License List is shaping up to be an "entry point" from SPDX generally, i.e. easier to adopt names, as many organizations have a need to have a standard way to refer to licenses. from there may lead to adoption of spec. Sub-text - even higher priority/pressure to resolve outstanding issues and create guidelines for matching, etc. so we can move to a more stable maintenence role.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>Notably: Phil, Karen, and Jilayne had a call with David Wheeler from IDA regarding having the license list include a way to identify U.S. Gov't works and the legal reality that that represents. David is going to send some standard headers, so this will be something to add to the list and configure in the near future.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>will entail a new short identifier, possibly an explanation and reference to relevant U.S. statutes and may include multiple headers that "point" to this same designation.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>JILAYNE AND KAREN TO FOLLOW-UP AND GET PROPOSAL GOING FOR THIS</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">== </ins>To-dos <ins class="diffchange diffchange-inline">==</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>finish <ins class="diffchange diffchange-inline">'''</ins>license text review<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>got licenses back from Adam, Phil, Paul, Peter; Michael and Rockett still working on theirs. There were many changes/updates, so good we did this!</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>goal to have this DONE by next call - about 60 more licenses to assign. volunteers for next round listed below. if anyone else can assist, please tell Jilayne asap!! see <ins class="diffchange diffchange-inline">[[Legal_Team</ins>/<ins class="diffchange diffchange-inline">Minutes</ins>/2012-02-22<ins class="diffchange diffchange-inline">]] </ins>for description of process</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>COLIN - lines 102 thru 113</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>ADAM - lines 114 thru 125</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>PHIL - lines 126 thru 137</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* '''</ins>OSI license list issues<ins class="diffchange diffchange-inline">''' </ins>- Karl Fogel responded (email went to group)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>JILAYNE TO FOLLOW-UP SEE IF WE CAN GET ISSUES SORTED BY APRIL 6TH FORUM</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* </ins>resolve other License List issues among group: (see further discussion below)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** '''</ins>BSD Licenses overview<ins class="diffchange diffchange-inline">''' </ins>- Tom sent email to group prior to meeting for discussion, see for reference</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>recommendation to ADD: BSD 4-Clause specific to the U. of California in order to accomodate the scenario where a original 4-clause license is retroactively turned into a 3-clause as per July 22, 1999 notice from William Hoskins, Directore of Office of Tech Licensing, UC-Berkeley</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>in contrast, a match to the "plain" BSD 4-clause will not carry this retroactive change and just refer to the full 4 clause license</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>add to license list along with the notice in the Notes field and an explanation as needed</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>DECISION BY GROUP: Yes to adding this license</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>text variations such as "copyright holder" v. "copyright owner" - equivalent? can we handle via equivalent words list or need to deal with more broadly in matching guidelines? also need to consider where "or contributors" is present or not</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>under US law, "copyright holder" v. "copyright owner" can be considered the same, but would want European perspective on this - PENDING someone on call who can speak to this</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>generally, these issues need to be dealt with via the license match guidelines for when to "ignore" some of this text - TBD</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>Review of current naming of various BSD licenses - okay as is, no change recommended</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>FreeBSD and NetBSD both have an extra line at end or beginning. under matching guidelines this would be considered a different license (than standard BSD). Due to there both being prominent projects, should these two licenses be added as separate?</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>TOM TO SEND EMAIL TO LIST TO DESCRIBE SCENARIO AND DISCUSS AT NEXT MEETING</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>also discussed concept of buckets for types of licenses, i.e. attribution v. permissive - bunch of ideas around this, as well as acknowledgement that this may go beyond scope of SPDX?</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>Mark to submit proposal for review by group as not enough time to discuss now</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** '''</ins>MPL 2.0<ins class="diffchange diffchange-inline">''' </ins>exhibits discussion (including discussion of GPL only or or later) - Luis Villa joined call to assist with explanation and guidance</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>Luis gave an overview of the MPL v2.0 exhibits and rationale behind (also on previous email thread)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">*** </ins>discussed in tangent with GPL only v. or later issue - currently have these as separate line items on License List - everyone agrees that capturing that distinction is key/wanted, but how best to do so? how we have it currently or one license line item with the options of different headers?</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>suggested to have some kind of modifiers, i.e license is GPL v2 and modfied with an "or later" or "only" (or even "exception") designator</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>different list for headers? that inter-operates with License List?</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>legal team needs to decide WHAT needs to be identified then go to technical team to determine HOW to implement</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">**** </ins>suggested futher discussion on next call and set aside time during workgroup meeting on Thursday, April 5 at Linux Collab Summit to flesh this issue out a bit more.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** '''</ins>GPL exceptions<ins class="diffchange diffchange-inline">''' </ins>- how do we "define" the actua license text (for the license list itself, as well as matching guidelines: should it be the license itself plus the exception text or the exception text only?)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* '''</ins>license matching guidelines<ins class="diffchange diffchange-inline">''' </ins>- finish/pickup where left off a couple calls ago. still need to cover the headers/notices matching issue and replaceable text (template) issues as the big remaining items - gets intertwined with License List issues</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* '''</ins>website migration<ins class="diffchange diffchange-inline">''' </ins>- no progress on this and legal team is now weak link - need someone to take on this task and get done asap. May also need to re-think navigation for legal portion as well as additional pages/information but for now, just need to get stuff copied/moved into new format.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>MARK TO TAKE LEAD WITH THIS (MAY ENGAGE PIERRE FOR HELP, IF NEEDED)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* '''</ins>Process for adding new licenses to list<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>currently with business team, but does it make sense to have it go back to legal team or a sub-group thereof</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>current process discussed is outlined here: <ins class="diffchange diffchange-inline">[[Business_Team</ins>/<ins class="diffchange diffchange-inline">Process_for_Adding_to_License_List_Draft]]</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>ideally need to review this and be able to describe at SPDX Forum on April 6</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">* '''</ins>Prepare for SPDX Forum<ins class="diffchange diffchange-inline">''' </ins>on April 6</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>GARY AND JILAYNE TO PRESENT ON "Getting started with SPDX" - suggestions from group welcome :)</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>registration should be up soon, look for email from Kim</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">** </ins>info here for now: <ins class="diffchange diffchange-inline">[[Old/SPDX_Forum</ins>:<ins class="diffchange diffchange-inline">_Managing_Open_Source_Software_Licenses_with_Suppliers_and_Customers]]</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[[Category:Legal|Minutes]]</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[[Category:Minutes]]</ins></div></td></tr>
</table>MartinMichlmayrhttps://wiki.spdx.org/index.php?title=Legal_Team/Minutes/2012-03-07&diff=1457&oldid=prevJlovejoy at 18:17, 12 March 20122012-03-12T18:17:44Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 18:17, 12 March 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong>SPDX Legal Team - meeting minutes for 7 March 2012</strong></p><ul><li>Tom Incorvia, Microfocus</li><li>Adam Cohn, Cisco</li><li>Colin Wright, McKesson</li><li>Mark Gisi, Windriver</li><li>Peter Williams, OpenLogic</li><li>Michael Herzog, NexB</li><li>Jilayne Lovejoy, OpenLogic</li><li>Karen Copenhaver, Choate Hall</li><li>Luis Villa, Greenberg Taurig</li></ul><p>Agenda:</p><ol><li>Update on various feedback</li><li>to-do's on the hopper - including priority items to get done before April 6 SPDX Forum in San Jose</li></ol><p>("assignments" and action items in all caps)</p><p>1) License List is getting more attention as seen by recent correspondance by persons outside the group looking to use the license list as a reference/standard/resource for referring to licenses. &nbsp;Take-away of this is the the License List is shaping up to be an "entry point" from SPDX generally, i.e. easier to adopt names, as many organizations have a need to have a standard way to refer to licenses. from there may lead to adoption of spec. &nbsp;Sub-text - even higher priority/pressure to resolve outstanding issues and create guidelines for matching, etc. so we can move to a more stable maintenence role. &nbsp;&nbsp;</p><ul><li>Notably: Phil, Karen, and Jilayne had a call with David Wheeler from IDA regarding having the license list include a way to identify U.S. Gov't works and the legal reality that that represents. &nbsp;David is going to send some standard headers, so this will be something to add to the list and configure in the near future. &nbsp;</li><ul><li>will entail a new short identifier, possibly an explanation and reference to relevant U.S. statutes and may include multiple headers that "point" to this same designation.</li><li>JILAYNE AND KAREN TO FOLLOW-UP AND GET PROPOSAL GOING FOR THIS</li></ul></ul><p>2) To-dos:</p><ul><li>finish <strong>license text review</strong></li><ul><li>got licenses back from Adam, Phil, Paul, Peter; Michael and Rockett still working on theirs. &nbsp;There were many changes/updates, so good we did this!</li><li>goal to have this DONE by next call - about 60 more licenses to assign. volunteers for next round listed below. &nbsp;if anyone else can assist, please tell Jilayne asap!! see&nbsp;http://spdx.org/wiki/legal-team-meeting-minutes-2012-02-22 for description of process</li><ul><li>COLIN &nbsp;- lines 102 thru 113</li><li>ADAM &nbsp;- lines 114 thru 125</li></ul></ul></ul><ul><li><strong>OSI license list issues</strong> - Karl Fogel responded (email went to group)</li><ul><li>JILAYNE TO FOLLOW-UP SEE IF WE CAN GET ISSUES SORTED BY APRIL 6TH FORUM</li></ul></ul><ul><li>resolve other License List issues among group: (see further discussion below)</li><ul><li><strong>BSD Licenses overview</strong> - Tom sent email to group prior to meeting for discussion, see for reference</li><ul><li>recommendation to ADD: BSD 4-Clause specific to the U. of California in order to accomodate the scenario where a original 4-clause license is retroactively turned into a 3-clause as per July 22, 1999 notice from William Hoskins, Directore of Office of Tech Licensing, UC-Berkeley</li><ul><li>in contrast, a match to the "plain" BSD 4-clause will not carry this retroactive change and just refer to the full 4 clause license</li><li>add to license list along with the notice in the Notes field and an explanation as needed</li><li>DECISION BY GROUP: Yes to adding this license</li></ul><li>text variations such as "copyright holder" v. "copyright owner" - equivalent? can we handle via equivalent words list or need to deal with more broadly in matching guidelines? also need to consider where "or contributors" is present or not</li><ul><li>under US law,&nbsp;"copyright holder" v. "copyright owner" can be considered the same, but would want European perspective on this - PENDING someone on call who can speak to this</li><li>generally, these issues need to be dealt with via the license match guidelines for when to "ignore" some of this text - TBD</li></ul><li>Review of current naming of various BSD licenses - okay as is, no change recommended</li><li>FreeBSD and NetBSD both have an extra line at end or beginning. &nbsp;under matching guidelines this would be considered a different license (than standard BSD). &nbsp;Due to there both being prominent projects, should these two licenses be added as separate?</li><ul><li>TOM TO SEND EMAIL TO LIST TO DESCRIBE SCENARIO AND DISCUSS AT NEXT MEETING</li></ul></ul><li>also discussed concept of buckets for types of licenses, i.e. attribution v. permissive - bunch of ideas around this, as well as acknowledgement that this may go beyond scope of SPDX? &nbsp;</li><ul><li>Mark to submit proposal for review by group as not enough time to discuss now</li><li></li></ul><li><strong>MPL 2.0</strong> exhibits discussion (including discussion of GPL only or or later) - Luis Villa joined call to assist with explanation and guidance</li><ul><li>Luis gave an overview of the MPL v2.0 exhibits and rationale behind (also on previous email thread)</li><li>discussed in tangent with GPL only v. or later issue - currently have these as separate line items on License List - everyone agrees that capturing that distinction is key/wanted, but how best to do so? &nbsp;how we have it currently or one license line item with the options of different headers?</li><ul><li>suggested to have some kind of modifiers, i.e license is GPL v2 and modfied with an "or later" or "only" (or even "exception") designator</li><li>different list for headers? that inter-operates with License List?</li><li>legal team needs to decide WHAT needs to be identified then go to technical team to determine HOW to implement</li><li>suggested futher discussion on next call and set aside time during workgroup meeting on Thursday, April 5 at Linux Collab Summit to flesh this issue out a bit more.</li></ul></ul><li></li><li><strong>GPL exceptions</strong> - how do we "define" the actua license text (for the license list itself, as well as matching guidelines: should it be the license itself plus the exception text or the exception text only?)</li></ul></ul><ul><li><strong>license matching guidelines</strong> - finish/pickup where left off a couple calls ago. still need to cover the headers/notices matching issue and replaceable text (template) issues as the big remaining items - gets intertwined with License List issues</li></ul><ul><li><strong>website migration</strong> - no progress on this and legal team is now weak link - need someone to take on this task and get done asap. &nbsp;May also need to re-think navigation for legal portion as well as additional pages/information but for now, just need to get stuff copied/moved into new format.</li><ul><li>MARK TO TAKE LEAD WITH THIS (MAY ENGAGE PIERRE FOR HELP, IF NEEDED)</li></ul></ul><ul><li><strong>Process for adding new licenses to list</strong></li><ul><li>currently with business team, but does it make sense to have it go back to legal team or a sub-group thereof</li><li>current process discussed is outlined here: &nbsp;http://spdx.org/wiki/process-adding-license-list-draft</li><li>ideally need to review this and be able to describe at SPDX Forum on April 6</li></ul></ul><ul><li><strong>Prepare for SPDX Forum</strong> on April 6</li><ul><li>GARY AND JILAYNE TO PRESENT ON "Getting started with SPDX" - suggestions from group welcome :)</li><li>registration should be up soon, look for email from Kim</li><li>info here for now: &nbsp;http://spdx.org/wiki/spdx-forum-managing-open-source-software-licenses-suppliers-and-customers</li></ul></ul><p>&nbsp;</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong>SPDX Legal Team - meeting minutes for 7 March 2012</strong></p><ul><li>Tom Incorvia, Microfocus</li><li>Adam Cohn, Cisco</li><li>Colin Wright, McKesson</li><li>Mark Gisi, Windriver</li><li>Peter Williams, OpenLogic</li><li>Michael Herzog, NexB</li><li>Jilayne Lovejoy, OpenLogic</li><li>Karen Copenhaver, Choate Hall</li><li>Luis Villa, Greenberg Taurig</li></ul><p>Agenda:</p><ol><li>Update on various feedback</li><li>to-do's on the hopper - including priority items to get done before April 6 SPDX Forum in San Jose</li></ol><p>("assignments" and action items in all caps)</p><p>1) License List is getting more attention as seen by recent correspondance by persons outside the group looking to use the license list as a reference/standard/resource for referring to licenses. &nbsp;Take-away of this is the the License List is shaping up to be an "entry point" from SPDX generally, i.e. easier to adopt names, as many organizations have a need to have a standard way to refer to licenses. from there may lead to adoption of spec. &nbsp;Sub-text - even higher priority/pressure to resolve outstanding issues and create guidelines for matching, etc. so we can move to a more stable maintenence role. &nbsp;&nbsp;</p><ul><li>Notably: Phil, Karen, and Jilayne had a call with David Wheeler from IDA regarding having the license list include a way to identify U.S. Gov't works and the legal reality that that represents. &nbsp;David is going to send some standard headers, so this will be something to add to the list and configure in the near future. &nbsp;</li><ul><li>will entail a new short identifier, possibly an explanation and reference to relevant U.S. statutes and may include multiple headers that "point" to this same designation.</li><li>JILAYNE AND KAREN TO FOLLOW-UP AND GET PROPOSAL GOING FOR THIS</li></ul></ul><p>2) To-dos:</p><ul><li>finish <strong>license text review</strong></li><ul><li>got licenses back from Adam, Phil, Paul, Peter; Michael and Rockett still working on theirs. &nbsp;There were many changes/updates, so good we did this!</li><li>goal to have this DONE by next call - about 60 more licenses to assign. volunteers for next round listed below. &nbsp;if anyone else can assist, please tell Jilayne asap!! see&nbsp;http://spdx.org/wiki/legal-team-meeting-minutes-2012-02-22 for description of process</li><ul><li>COLIN &nbsp;- lines 102 thru 113</li><li>ADAM &nbsp;- lines 114 thru 125<ins class="diffchange diffchange-inline"></li><li>PHIL - lines 126 thru 137</ins></li></ul></ul></ul><ul><li><strong>OSI license list issues</strong> - Karl Fogel responded (email went to group)</li><ul><li>JILAYNE TO FOLLOW-UP SEE IF WE CAN GET ISSUES SORTED BY APRIL 6TH FORUM</li></ul></ul><ul><li>resolve other License List issues among group: (see further discussion below)</li><ul><li><strong>BSD Licenses overview</strong> - Tom sent email to group prior to meeting for discussion, see for reference</li><ul><li>recommendation to ADD: BSD 4-Clause specific to the U. of California in order to accomodate the scenario where a original 4-clause license is retroactively turned into a 3-clause as per July 22, 1999 notice from William Hoskins, Directore of Office of Tech Licensing, UC-Berkeley</li><ul><li>in contrast, a match to the "plain" BSD 4-clause will not carry this retroactive change and just refer to the full 4 clause license</li><li>add to license list along with the notice in the Notes field and an explanation as needed</li><li>DECISION BY GROUP: Yes to adding this license</li></ul><li>text variations such as "copyright holder" v. "copyright owner" - equivalent? can we handle via equivalent words list or need to deal with more broadly in matching guidelines? also need to consider where "or contributors" is present or not</li><ul><li>under US law,&nbsp;"copyright holder" v. "copyright owner" can be considered the same, but would want European perspective on this - PENDING someone on call who can speak to this</li><li>generally, these issues need to be dealt with via the license match guidelines for when to "ignore" some of this text - TBD</li></ul><li>Review of current naming of various BSD licenses - okay as is, no change recommended</li><li>FreeBSD and NetBSD both have an extra line at end or beginning. &nbsp;under matching guidelines this would be considered a different license (than standard BSD). &nbsp;Due to there both being prominent projects, should these two licenses be added as separate?</li><ul><li>TOM TO SEND EMAIL TO LIST TO DESCRIBE SCENARIO AND DISCUSS AT NEXT MEETING</li></ul></ul><li>also discussed concept of buckets for types of licenses, i.e. attribution v. permissive - bunch of ideas around this, as well as acknowledgement that this may go beyond scope of SPDX? &nbsp;</li><ul><li>Mark to submit proposal for review by group as not enough time to discuss now</li><li></li></ul><li><strong>MPL 2.0</strong> exhibits discussion (including discussion of GPL only or or later) - Luis Villa joined call to assist with explanation and guidance</li><ul><li>Luis gave an overview of the MPL v2.0 exhibits and rationale behind (also on previous email thread)</li><li>discussed in tangent with GPL only v. or later issue - currently have these as separate line items on License List - everyone agrees that capturing that distinction is key/wanted, but how best to do so? &nbsp;how we have it currently or one license line item with the options of different headers?</li><ul><li>suggested to have some kind of modifiers, i.e license is GPL v2 and modfied with an "or later" or "only" (or even "exception") designator</li><li>different list for headers? that inter-operates with License List?</li><li>legal team needs to decide WHAT needs to be identified then go to technical team to determine HOW to implement</li><li>suggested futher discussion on next call and set aside time during workgroup meeting on Thursday, April 5 at Linux Collab Summit to flesh this issue out a bit more.</li></ul></ul><li></li><li><strong>GPL exceptions</strong> - how do we "define" the actua license text (for the license list itself, as well as matching guidelines: should it be the license itself plus the exception text or the exception text only?)</li></ul></ul><ul><li><strong>license matching guidelines</strong> - finish/pickup where left off a couple calls ago. still need to cover the headers/notices matching issue and replaceable text (template) issues as the big remaining items - gets intertwined with License List issues</li></ul><ul><li><strong>website migration</strong> - no progress on this and legal team is now weak link - need someone to take on this task and get done asap. &nbsp;May also need to re-think navigation for legal portion as well as additional pages/information but for now, just need to get stuff copied/moved into new format.</li><ul><li>MARK TO TAKE LEAD WITH THIS (MAY ENGAGE PIERRE FOR HELP, IF NEEDED)</li></ul></ul><ul><li><strong>Process for adding new licenses to list</strong></li><ul><li>currently with business team, but does it make sense to have it go back to legal team or a sub-group thereof</li><li>current process discussed is outlined here: &nbsp;http://spdx.org/wiki/process-adding-license-list-draft</li><li>ideally need to review this and be able to describe at SPDX Forum on April 6</li></ul></ul><ul><li><strong>Prepare for SPDX Forum</strong> on April 6</li><ul><li>GARY AND JILAYNE TO PRESENT ON "Getting started with SPDX" - suggestions from group welcome :)</li><li>registration should be up soon, look for email from Kim</li><li>info here for now: &nbsp;http://spdx.org/wiki/spdx-forum-managing-open-source-software-licenses-suppliers-and-customers</li></ul></ul><p>&nbsp;</p></div></td></tr>
</table>Jlovejoyhttps://wiki.spdx.org/index.php?title=Legal_Team/Minutes/2012-03-07&diff=1456&oldid=prevJlovejoy at 20:46, 7 March 20122012-03-07T20:46:15Z<p></p>
<p><b>New page</b></p><div><p><strong>SPDX Legal Team - meeting minutes for 7 March 2012</strong></p><ul><li>Tom Incorvia, Microfocus</li><li>Adam Cohn, Cisco</li><li>Colin Wright, McKesson</li><li>Mark Gisi, Windriver</li><li>Peter Williams, OpenLogic</li><li>Michael Herzog, NexB</li><li>Jilayne Lovejoy, OpenLogic</li><li>Karen Copenhaver, Choate Hall</li><li>Luis Villa, Greenberg Taurig</li></ul><p>Agenda:</p><ol><li>Update on various feedback</li><li>to-do's on the hopper - including priority items to get done before April 6 SPDX Forum in San Jose</li></ol><p>("assignments" and action items in all caps)</p><p>1) License List is getting more attention as seen by recent correspondance by persons outside the group looking to use the license list as a reference/standard/resource for referring to licenses. &nbsp;Take-away of this is the the License List is shaping up to be an "entry point" from SPDX generally, i.e. easier to adopt names, as many organizations have a need to have a standard way to refer to licenses. from there may lead to adoption of spec. &nbsp;Sub-text - even higher priority/pressure to resolve outstanding issues and create guidelines for matching, etc. so we can move to a more stable maintenence role. &nbsp;&nbsp;</p><ul><li>Notably: Phil, Karen, and Jilayne had a call with David Wheeler from IDA regarding having the license list include a way to identify U.S. Gov't works and the legal reality that that represents. &nbsp;David is going to send some standard headers, so this will be something to add to the list and configure in the near future. &nbsp;</li><ul><li>will entail a new short identifier, possibly an explanation and reference to relevant U.S. statutes and may include multiple headers that "point" to this same designation.</li><li>JILAYNE AND KAREN TO FOLLOW-UP AND GET PROPOSAL GOING FOR THIS</li></ul></ul><p>2) To-dos:</p><ul><li>finish <strong>license text review</strong></li><ul><li>got licenses back from Adam, Phil, Paul, Peter; Michael and Rockett still working on theirs. &nbsp;There were many changes/updates, so good we did this!</li><li>goal to have this DONE by next call - about 60 more licenses to assign. volunteers for next round listed below. &nbsp;if anyone else can assist, please tell Jilayne asap!! see&nbsp;http://spdx.org/wiki/legal-team-meeting-minutes-2012-02-22 for description of process</li><ul><li>COLIN &nbsp;- lines 102 thru 113</li><li>ADAM &nbsp;- lines 114 thru 125</li></ul></ul></ul><ul><li><strong>OSI license list issues</strong> - Karl Fogel responded (email went to group)</li><ul><li>JILAYNE TO FOLLOW-UP SEE IF WE CAN GET ISSUES SORTED BY APRIL 6TH FORUM</li></ul></ul><ul><li>resolve other License List issues among group: (see further discussion below)</li><ul><li><strong>BSD Licenses overview</strong> - Tom sent email to group prior to meeting for discussion, see for reference</li><ul><li>recommendation to ADD: BSD 4-Clause specific to the U. of California in order to accomodate the scenario where a original 4-clause license is retroactively turned into a 3-clause as per July 22, 1999 notice from William Hoskins, Directore of Office of Tech Licensing, UC-Berkeley</li><ul><li>in contrast, a match to the "plain" BSD 4-clause will not carry this retroactive change and just refer to the full 4 clause license</li><li>add to license list along with the notice in the Notes field and an explanation as needed</li><li>DECISION BY GROUP: Yes to adding this license</li></ul><li>text variations such as "copyright holder" v. "copyright owner" - equivalent? can we handle via equivalent words list or need to deal with more broadly in matching guidelines? also need to consider where "or contributors" is present or not</li><ul><li>under US law,&nbsp;"copyright holder" v. "copyright owner" can be considered the same, but would want European perspective on this - PENDING someone on call who can speak to this</li><li>generally, these issues need to be dealt with via the license match guidelines for when to "ignore" some of this text - TBD</li></ul><li>Review of current naming of various BSD licenses - okay as is, no change recommended</li><li>FreeBSD and NetBSD both have an extra line at end or beginning. &nbsp;under matching guidelines this would be considered a different license (than standard BSD). &nbsp;Due to there both being prominent projects, should these two licenses be added as separate?</li><ul><li>TOM TO SEND EMAIL TO LIST TO DESCRIBE SCENARIO AND DISCUSS AT NEXT MEETING</li></ul></ul><li>also discussed concept of buckets for types of licenses, i.e. attribution v. permissive - bunch of ideas around this, as well as acknowledgement that this may go beyond scope of SPDX? &nbsp;</li><ul><li>Mark to submit proposal for review by group as not enough time to discuss now</li><li></li></ul><li><strong>MPL 2.0</strong> exhibits discussion (including discussion of GPL only or or later) - Luis Villa joined call to assist with explanation and guidance</li><ul><li>Luis gave an overview of the MPL v2.0 exhibits and rationale behind (also on previous email thread)</li><li>discussed in tangent with GPL only v. or later issue - currently have these as separate line items on License List - everyone agrees that capturing that distinction is key/wanted, but how best to do so? &nbsp;how we have it currently or one license line item with the options of different headers?</li><ul><li>suggested to have some kind of modifiers, i.e license is GPL v2 and modfied with an "or later" or "only" (or even "exception") designator</li><li>different list for headers? that inter-operates with License List?</li><li>legal team needs to decide WHAT needs to be identified then go to technical team to determine HOW to implement</li><li>suggested futher discussion on next call and set aside time during workgroup meeting on Thursday, April 5 at Linux Collab Summit to flesh this issue out a bit more.</li></ul></ul><li></li><li><strong>GPL exceptions</strong> - how do we "define" the actua license text (for the license list itself, as well as matching guidelines: should it be the license itself plus the exception text or the exception text only?)</li></ul></ul><ul><li><strong>license matching guidelines</strong> - finish/pickup where left off a couple calls ago. still need to cover the headers/notices matching issue and replaceable text (template) issues as the big remaining items - gets intertwined with License List issues</li></ul><ul><li><strong>website migration</strong> - no progress on this and legal team is now weak link - need someone to take on this task and get done asap. &nbsp;May also need to re-think navigation for legal portion as well as additional pages/information but for now, just need to get stuff copied/moved into new format.</li><ul><li>MARK TO TAKE LEAD WITH THIS (MAY ENGAGE PIERRE FOR HELP, IF NEEDED)</li></ul></ul><ul><li><strong>Process for adding new licenses to list</strong></li><ul><li>currently with business team, but does it make sense to have it go back to legal team or a sub-group thereof</li><li>current process discussed is outlined here: &nbsp;http://spdx.org/wiki/process-adding-license-list-draft</li><li>ideally need to review this and be able to describe at SPDX Forum on April 6</li></ul></ul><ul><li><strong>Prepare for SPDX Forum</strong> on April 6</li><ul><li>GARY AND JILAYNE TO PRESENT ON "Getting started with SPDX" - suggestions from group welcome :)</li><li>registration should be up soon, look for email from Kim</li><li>info here for now: &nbsp;http://spdx.org/wiki/spdx-forum-managing-open-source-software-licenses-suppliers-and-customers</li></ul></ul><p>&nbsp;</p></div>Jlovejoy