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-08-22"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
−
<p><strong>Attendees</strong>:</p><ul><li>Jilayne Lovejoy, OpenLogic</li><li>Ibrahim Haddad, Linux Foundation</li><li>Adam Cohn, Cisco</li><li>Mark Gisi, Windriver</li><li>Paul Madick, HP</li><li>Tom Incorvia, Microfocus</li><li>Jack Manbeck, TI</li><li>Jason Buttara, Cisco</li></ul><p><strong>AGENDA</strong></p><p>1) Website comments: link to meeting minutes in secondary drop-down menu goes to old page.</p><p>2) Who's going to be at LinuxCon: no: Paul, Tom, Adam, Mark, Jason &nbsp;yes: Jilayne, Jack, Ibrahim,&nbsp;</p><p>3) FSF License List - picked up where left off last meeting:</p><ul><li>discussed Guillerme email feedback re: adding all licenses from Fedora</li><li>some of the items listed on Fedora list aren't really licenses, though - want licenses on SPDX License List to be fully vetted. &nbsp;decided to continue on as we did last meeting to get through the whole list and make sure to include some rationale as to why anything was decided to not add. &nbsp;Spreadsheet will be posted and people not on the call can comment as we go through the rest of the list. &nbsp;Once we have gone through the whole list there will be a period of time for additional comments before officially adding licenses to the list.</li><li>what is the guiding principle for adding a license/to be on the list (other than attributes that need to be obtained)?</li><ul><li>we probably have some implications of this, but nothing explicit</li><li>what is open source in this case - is it commonly used open source licenses or commonly used licenses on open source projects</li><li>need to have distinction from "freeware," e.g. Sun/Oracle Binary Code LIcenses or other licenses that change often and too hard to keep up with current versions</li><li>Mark to make a first draft of this definition/description</li></ul><li>License naming guideline that came up:</li><ul><li>for a BSD license derivative - if the common license name uses "BSD" then adopt SPDX naming, e.g. 3-clause, then the name of the derivative and similar short identifier</li><li>but where the license has a common name that does not use "BSD" then use common name and create short identifier from that name (as well as what is used on other lists, e.g. Fedora) --&gt; add this info license list field guidelines</li></ul><li>got to line 33 (Do What the F*ck You Want license) in the spreadsheet - Jilayne to update and re-post here and then will finish the rest of the list next call.</li></ul>
+
== Attendees ==
 +
 
 +
* Jilayne Lovejoy, OpenLogic
 +
* Ibrahim Haddad, Linux Foundation
 +
* Adam Cohn, Cisco
 +
* Mark Gisi, Windriver
 +
* Paul Madick, HP
 +
* Tom Incorvia, Microfocus
 +
* Jack Manbeck, TI
 +
* Jason Buttara, Cisco
 +
 
 +
== Website comments ==
 +
 
 +
ink to meeting minutes in secondary drop-down menu goes to old page.
 +
 
 +
== Who's going to be at LinuxCon ==
 +
 
 +
no: Paul, Tom, Adam, Mark, Jason yes: Jilayne, Jack, Ibrahim,
 +
 
 +
== FSF License List ==
 +
 
 +
picked up where left off last meeting:
 +
 
 +
* discussed Guillerme email feedback re: adding all licenses from Fedora
 +
* some of the items listed on Fedora list aren't really licenses, though - want licenses on SPDX License List to be fully vetted. decided to continue on as we did last meeting to get through the whole list and make sure to include some rationale as to why anything was decided to not add. Spreadsheet will be posted and people not on the call can comment as we go through the rest of the list. Once we have gone through the whole list there will be a period of time for additional comments before officially adding licenses to the list.
 +
* what is the guiding principle for adding a license/to be on the list (other than attributes that need to be obtained)?
 +
** we probably have some implications of this, but nothing explicit
 +
** what is open source in this case - is it commonly used open source licenses or commonly used licenses on open source projects
 +
** need to have distinction from "freeware," e.g. Sun/Oracle Binary Code LIcenses or other licenses that change often and too hard to keep up with current versions
 +
** Mark to make a first draft of this definition/description
 +
* License naming guideline that came up:
 +
** for a BSD license derivative - if the common license name uses "BSD" then adopt SPDX naming, e.g. 3-clause, then the name of the derivative and similar short identifier
 +
** but where the license has a common name that does not use "BSD" then use common name and create short identifier from that name (as well as what is used on other lists, e.g. Fedora) → add this info license list field guidelines
 +
* got to line 33 (Do What the F*ck You Want license) in the spreadsheet - Jilayne to update and re-post here and then will finish the rest of the list next call.
 +
 
 +
[[Category:Legal|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 17:44, 5 March 2013

Attendees

  • Jilayne Lovejoy, OpenLogic
  • Ibrahim Haddad, Linux Foundation
  • Adam Cohn, Cisco
  • Mark Gisi, Windriver
  • Paul Madick, HP
  • Tom Incorvia, Microfocus
  • Jack Manbeck, TI
  • Jason Buttara, Cisco

Website comments

ink to meeting minutes in secondary drop-down menu goes to old page.

Who's going to be at LinuxCon

no: Paul, Tom, Adam, Mark, Jason yes: Jilayne, Jack, Ibrahim,

FSF License List

picked up where left off last meeting:

  • discussed Guillerme email feedback re: adding all licenses from Fedora
  • some of the items listed on Fedora list aren't really licenses, though - want licenses on SPDX License List to be fully vetted. decided to continue on as we did last meeting to get through the whole list and make sure to include some rationale as to why anything was decided to not add. Spreadsheet will be posted and people not on the call can comment as we go through the rest of the list. Once we have gone through the whole list there will be a period of time for additional comments before officially adding licenses to the list.
  • what is the guiding principle for adding a license/to be on the list (other than attributes that need to be obtained)?
    • we probably have some implications of this, but nothing explicit
    • what is open source in this case - is it commonly used open source licenses or commonly used licenses on open source projects
    • need to have distinction from "freeware," e.g. Sun/Oracle Binary Code LIcenses or other licenses that change often and too hard to keep up with current versions
    • Mark to make a first draft of this definition/description
  • License naming guideline that came up:
    • for a BSD license derivative - if the common license name uses "BSD" then adopt SPDX naming, e.g. 3-clause, then the name of the derivative and similar short identifier
    • but where the license has a common name that does not use "BSD" then use common name and create short identifier from that name (as well as what is used on other lists, e.g. Fedora) → add this info license list field guidelines
  • got to line 33 (Do What the F*ck You Want license) in the spreadsheet - Jilayne to update and re-post here and then will finish the rest of the list next call.
Retrieved from "https://wiki.spdx.org/index.php?title=Legal_Team/Minutes/2012-08-22&oldid=2186"