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

Difference between revisions of "Business Team/Minutes/2012-01-19"

From SPDX Wiki
Jump to: navigation, search
Line 1: Line 1:
<p><strong>Attendees</strong></p><ul><li>Kim Weins</li><li>Chuck Gaudreau</li><li>Gary O'Neill</li><li>Scott Lamons</li><li>Jilayne Lovejoy</li></ul><p><strong>Agenda</strong></p><ul><li>Web Site</li><li>Update on CC0 "license" feedback</li><li>EclipseCon BOF</li><li>Software Supply Chain Summit</li><li>License List Process</li><li></li></ul><p><strong>Notes</strong></p><ul><li>&nbsp;Web site training</li><li>Update on CC0 license</li><ul><li>Kim sent email to Ian Skerrett at Eclipse, Robin Johnson at Gentoo, Spot at Fedora about the change in the data license from</li></ul><li>Eclipse BOF</li><li>Process for companies to adopt - Per Scott L</li><ul><li>Can start with procurement team to ask suppliers to provide it</li><li>Will need to educate procurement team</li><li>Will need places on website to point suppliers to</li><li>Will need tools to help them</li><ul><li>Idea is that you feed it software repositories to scan for licenses and then you can input the SPDX specific fields and create SPDX files</li></ul><li>Could also ask their developers that are making internal requests to provide SPDX</li></ul></ul>
+
<p><strong>Attendees</strong></p><ul><li>Kim Weins</li><li>Chuck Gaudreau</li><li>Gary O'Neill</li><li>Scott Lamons</li><li>Jilayne Lovejoy</li></ul><p><strong>Agenda</strong></p><ul><li>Web Site</li><li>Update on CC0 "license" feedback</li><li>EclipseCon BOF</li><li>Software Supply Chain Summit</li><li>License List Process</li><li></li></ul><p><strong>Notes</strong></p><ul><li>Web site training</li><ul><li>We had training on moving stuff to</li></ul><li>Update on CC0 license</li><ul><li>Kim sent email to Ian Skerrett at Eclipse, Robin Johnson at Gentoo, Spot at Fedora about the change in the data license from</li></ul><li>Eclipse BOF</li><li>Process for companies to adopt - Per Scott L</li><ul><li>Can start with procurement team to ask suppliers to provide it</li><li>Will need to educate procurement team</li><li>Will need places on website to point suppliers to</li><li>They have a standard spreadsheet format for proposal tracking of all OSS requests -- but it's not the SPDX format</li><ul><li>WOuld need to be able to have extra fields that are company specific and have the tools ignore/add those.</li></ul><li>Will need tools to help them</li><ul><li>Idea is that you feed it software repositories to scan for licenses and then you can input the SPDX specific fields and create SPDX files</li></ul><li>Could also ask their developers that are making internal requests to provide SPDX</li></ul></ul>

Revision as of 17:02, 19 January 2012

Attendees

  • Kim Weins
  • Chuck Gaudreau
  • Gary O'Neill
  • Scott Lamons
  • Jilayne Lovejoy

Agenda

  • Web Site
  • Update on CC0 "license" feedback
  • EclipseCon BOF
  • Software Supply Chain Summit
  • License List Process

Notes

  • Web site training
    • We had training on moving stuff to
  • Update on CC0 license
    • Kim sent email to Ian Skerrett at Eclipse, Robin Johnson at Gentoo, Spot at Fedora about the change in the data license from
  • Eclipse BOF
  • Process for companies to adopt - Per Scott L
    • Can start with procurement team to ask suppliers to provide it
    • Will need to educate procurement team
    • Will need places on website to point suppliers to
    • They have a standard spreadsheet format for proposal tracking of all OSS requests -- but it's not the SPDX format
      • WOuld need to be able to have extra fields that are company specific and have the tools ignore/add those.
    • Will need tools to help them
      • Idea is that you feed it software repositories to scan for licenses and then you can input the SPDX specific fields and create SPDX files
    • Could also ask their developers that are making internal requests to provide SPDX