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

Difference between revisions of "General Meeting/Minutes/2012-05-31"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
<p><span style="color: #666666; font-size: 12px; line-height: 18px;">Attendance: 10</span></p><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;">May 17 minutes approved<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;"><strong>Legal Team Report - Jilayne<br /></strong></p><ul style="list-style-type: disc; margin-top: 0px; margin-right: 0px; margin-bottom: 10px; margin-left: 20px; font-size: 12px; padding: 0px;"><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Finalizing work defining the team's mission purpose of License List&nbsp;that were published two weeks ago. Please comment now or hold your peace. Latest draft:</li><ul><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;"><p class="p1"><strong>Legal Work Group description:</strong></p><p class="p2"><em>"The SPDX Legal Team supports and provides recommendations to the SPDX working groups regarding licensing issues for the specification itself; maintains the SPDX License List; and promotes the SPDX specification to the legal community at-large."</em></p><p class="p1"><span class="s1"><em>&nbsp;</em></span><strong>SPDX License List description:</strong></p><p class="p2"><em>"The SPDX License List is a list of commonly found open source software licenses for the purposes of being able to easily and efficiently identify such licenses in an SPDX document. The SPDX License List includes a standardized short identifier, full name for each license, vetted license text, other basic information, and a canonical permanent URL. By providing a short identifier, users can efficiently refer to a license without having to redundantly reproduce the full license."</em><span class="s2">&nbsp;</span></p></li></ul><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Have been providing input to 1.1 spec to incorporate latest thinking on License List and to ensure consistent vocabulary.</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Working to make sure new website content is up to date.</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Turning attention back to matching guidelines. Aiming to reach closure with 1.1 release (about a month)</li></ul><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;"><strong>Business Team Report - Scott/Jack<br /></strong></p><ul style="list-style-type: disc; margin-top: 0px; margin-right: 0px; margin-bottom: 10px; margin-left: 20px; font-size: 12px; padding: 0px;"><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Business Team is eager for feedback from other team's on Mission/Vision. Looking to come to closure in the next few weeks. Expectation is that this will help with prioritization of use cases for the 2.0 effort. Latest version (embedded in a set of slides):&nbsp;<a href="http://www.spdx.org/system/files/spdx_mission_review_may_2012_v2.pdf">http://www.spdx.org/system/files/spdx_mission_review_may_2012_v2.pdf</a></li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Also, pulling together a description of Business Team's function. Scott has drafted and will be working on this in the next Business Team meeting.</li></ul><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;"><strong>Technical Team Report - Kate</strong></p><ul style="list-style-type: disc; margin-top: 0px; margin-right: 0px; margin-bottom: 10px; margin-left: 20px; font-size: 12px; padding: 0px;"><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">2.0 work</li><ul><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">A little over half the use cases have been fleshed out. Others are considering in a "graveyard" unless more work gets done on them.</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">http://www.spdx.org/wiki/spdx-20-use-cases&nbsp;</li></ul><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">1.1 work</li><ul><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Hoping to bring to closure in the next few weeks.</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Near final draft to be posted next week, then open for two weeks of comment.</li></ul></ul><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; padding: 0px;"><strong><br /></strong></p><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;"><strong>Cross Functional Issues – Phil</strong></p><ul style="list-style-type: disc; margin-top: 0px; margin-right: 0px; margin-bottom: 10px; margin-left: 20px; font-size: 12px; padding: 0px;"><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Website Update - Pierre</li><ul style="font-size: 12px;"><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">The effort has been rejuvinated. Content is moving to the new staging area.&nbsp;</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Web team is ready to flip the switch when content is set. No date set.</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Pierre is confirming that Steve is prepared to move wholesale sections (past meeting minutes, License List, etc.)</li></ul><li><span style="font-size: 12px;">LinuxCon Papers</span></li><ul><li><span style="font-size: 12px;">Scott submitting 1.1 update proposal&nbsp;</span></li><li><span style="font-size: 12px;">Gary has submitted a proposal for talking about the OSS tools</span></li></ul></ul><p style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;"><strong><br /></strong></p><p class="p1" style="margin-top: 5px; margin-right: 0px; margin-bottom: 10px; margin-left: 0px; font-size: 12px; color: #666666; line-height: 18px; font-weight: normal; padding: 0px;"><strong>Attendees</strong></p><ul class="ul1" style="list-style-type: disc; margin-top: 0px; margin-right: 0px; margin-bottom: 10px; margin-left: 20px; font-size: 12px; padding: 0px;"><li class="li2" style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Phil Odence, Black Duck Software</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Pierre LaPonte, nexB</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Kate Stewart, Canonical</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Michael Herzog, nexB</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Scott Lamons, HP</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Jack Manbeck, TI</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Jilayne Lovejoy, OpenLogic</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Chuck Gaudreau, Protecode</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Gary O'Neall, SourceAuditor</li><li style="margin-top: 0px; margin-right: 0px; margin-bottom: 5px; margin-left: 0px;">Mark Gisi, WindRiver</li></ul><p>&nbsp;</p>
+
* Attendance: 10
 +
* May 17 minutes approved
 +
 
 +
== Legal Team Report - Jilayne ==
 +
 
 +
* Finalizing work defining the team's mission purpose of License List that were published two weeks ago. Please comment now or hold your peace. Latest draft:
 +
** '''Legal Work Group description:'''''"The SPDX Legal Team supports and provides recommendations to the SPDX working groups regarding licensing issues for the specification itself; maintains the SPDX License List; and promotes the SPDX specification to the legal community at-large."''
 +
** '''SPDX License List description:'''''"The SPDX License List is a list of commonly found open source software licenses for the purposes of being able to easily and efficiently identify such licenses in an SPDX document. The SPDX License List includes a standardized short identifier, full name for each license, vetted license text, other basic information, and a canonical permanent URL. By providing a short identifier, users can efficiently refer to a license without having to redundantly reproduce the full license."''
 +
* Have been providing input to 1.1 spec to incorporate latest thinking on License List and to ensure consistent vocabulary.
 +
* Working to make sure new website content is up to date.
 +
* Turning attention back to matching guidelines. Aiming to reach closure with 1.1 release (about a month)
 +
 
 +
== Business Team Report - Scott/Jack ==
 +
 
 +
* Business Team is eager for feedback from other team's on Mission/Vision. Looking to come to closure in the next few weeks. Expectation is that this will help with prioritization of use cases for the 2.0 effort. Latest version (embedded in a set of slides): [[File:Spdx-mission-review-may-2012-v2.pdf]]
 +
* Also, pulling together a description of Business Team's function. Scott has drafted and will be working on this in the next Business Team meeting.
 +
 
 +
== Technical Team Report - Kate ==
 +
 
 +
* 2.0 work
 +
** A little over half the use cases have been fleshed out. Others are considering in a "graveyard" unless more work gets done on them.
 +
** [[Technical_Team/Use_Cases/2.0]]
 +
* 1.1 work
 +
** Hoping to bring to closure in the next few weeks.
 +
** Near final draft to be posted next week, then open for two weeks of comment.
 +
 
 +
== Cross Functional Issues – Phil ==
 +
 
 +
* Website Update - Pierre
 +
** The effort has been rejuvinated. Content is moving to the new staging area.
 +
** Web team is ready to flip the switch when content is set. No date set.
 +
** Pierre is confirming that Steve is prepared to move wholesale sections (past meeting minutes, License List, etc.)
 +
* LinuxCon Papers
 +
** Scott submitting 1.1 update proposal
 +
** Gary has submitted a proposal for talking about the OSS tools
 +
 
 +
== Attendees ==
 +
 
 +
* Phil Odence, Black Duck Software
 +
* Pierre LaPonte, nexB
 +
* Kate Stewart, Canonical
 +
* Michael Herzog, nexB
 +
* Scott Lamons, HP
 +
* Jack Manbeck, TI
 +
* Jilayne Lovejoy, OpenLogic
 +
* Chuck Gaudreau, Protecode
 +
* Gary O'Neall, SourceAuditor
 +
* Mark Gisi, WindRiver
 +
 
 +
[[Category:General|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 14:07, 7 March 2013

  • Attendance: 10
  • May 17 minutes approved

Legal Team Report - Jilayne

  • Finalizing work defining the team's mission purpose of License List that were published two weeks ago. Please comment now or hold your peace. Latest draft:
    • Legal Work Group description:"The SPDX Legal Team supports and provides recommendations to the SPDX working groups regarding licensing issues for the specification itself; maintains the SPDX License List; and promotes the SPDX specification to the legal community at-large."
    • SPDX License List description:"The SPDX License List is a list of commonly found open source software licenses for the purposes of being able to easily and efficiently identify such licenses in an SPDX document. The SPDX License List includes a standardized short identifier, full name for each license, vetted license text, other basic information, and a canonical permanent URL. By providing a short identifier, users can efficiently refer to a license without having to redundantly reproduce the full license."
  • Have been providing input to 1.1 spec to incorporate latest thinking on License List and to ensure consistent vocabulary.
  • Working to make sure new website content is up to date.
  • Turning attention back to matching guidelines. Aiming to reach closure with 1.1 release (about a month)

Business Team Report - Scott/Jack

  • Business Team is eager for feedback from other team's on Mission/Vision. Looking to come to closure in the next few weeks. Expectation is that this will help with prioritization of use cases for the 2.0 effort. Latest version (embedded in a set of slides): File:Spdx-mission-review-may-2012-v2.pdf
  • Also, pulling together a description of Business Team's function. Scott has drafted and will be working on this in the next Business Team meeting.

Technical Team Report - Kate

  • 2.0 work
    • A little over half the use cases have been fleshed out. Others are considering in a "graveyard" unless more work gets done on them.
    • Technical_Team/Use_Cases/2.0
  • 1.1 work
    • Hoping to bring to closure in the next few weeks.
    • Near final draft to be posted next week, then open for two weeks of comment.

Cross Functional Issues – Phil

  • Website Update - Pierre
    • The effort has been rejuvinated. Content is moving to the new staging area.
    • Web team is ready to flip the switch when content is set. No date set.
    • Pierre is confirming that Steve is prepared to move wholesale sections (past meeting minutes, License List, etc.)
  • LinuxCon Papers
    • Scott submitting 1.1 update proposal
    • Gary has submitted a proposal for talking about the OSS tools

Attendees

  • Phil Odence, Black Duck Software
  • Pierre LaPonte, nexB
  • Kate Stewart, Canonical
  • Michael Herzog, nexB
  • Scott Lamons, HP
  • Jack Manbeck, TI
  • Jilayne Lovejoy, OpenLogic
  • Chuck Gaudreau, Protecode
  • Gary O'Neall, SourceAuditor
  • Mark Gisi, WindRiver