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

Difference between revisions of "General Meeting/Minutes/2010-08-26"

From SPDX Wiki
Jump to: navigation, search
Line 1: Line 1:
<h2><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;">ADMINISTRATIVE</h3><p>Agenda</p><ul><li>Attendance - 18</li><li>Approval of minutes from BoF session – Approved.</li><li>New Logistics and Expanding Group</li><li>Outreach and evangelism:<ul><li>Common Messaging/Presentation – Phil O</li><li>Industry Venues – Phil R<ul><li>LinuxCon Debrief- Phil O</li></ul></li><li>Website – Martin M</li></ul></li></ul><h3 style="font-size: 1.17em;">Logistics</h3><p>PhilO discussed need for evolving logistics with the group getting larger and including new folks. We're doing away with the "Who just joined?" approach to attendance and will mainly depend on log-ins to Webshare to record attendance. In addition everyone is encouraged to state their name when speaking. There also some discussion (actually it came up towards the end of the meeting) about providing minutes via a link rather than an attached Word doc.</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;"><span style="font-weight: normal; font-size: 10px;"><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;">Common Messaging/Presentation</h3></span></h2><p>PhilO is updating the presentation to reflect Kate's LinuxCon presentation content.</p></span></h2></span></h3></span></h2><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;">Industry Venues</h3></span></h2><p>PhilO reported on LinuxCon. Jim Zemlin's keynote was all about the new Open Compliance Program, and SPDX was prominently featured. SPDX got some good PR out of it and one article said it was the key to the bigger program. Phil Koltun delivered a more detailed session on the OCP and Kate had one on SPDX. Both were well attended. Finally, we had a Birds of a Feature session.</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;">Website</h3></span></h2><p>&nbsp;</p><p>Kudos to Martin for helping PhilO get the new spdx.org launched in time for LinuxCon. There was some discussion about making it more obvious how one joins both the group and the mailing list; it's better to be redundant in order to be more welcoming. There was also a discussion about getting examples up to date and getting the Wiki going again. We finally got into a discussion about hosting code for tools. Possibilities were: SourceForge, GitHub.</p><p>&nbsp;</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;">Rollout</h3></span></h2><p>PhilO mentioned the JohnE and KimW have been working on a rollout plan, expanding on both out technical efforts and outreach/evangelism efforts. More at the next meeting.</p><p>&nbsp;</p></span></h2><h2><span style="font-size: small;"><span style="font-size: 12px;"><span style="font-weight: normal; font-size: 10px;"><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><h3 style="font-size: 1.17em;">ACTION ITEMS</h3></span></h2></span></span></span></h2>
+
<h2><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;">ADMINISTRATIVE</h3><p>Agenda</p><ul><li>Attendance - 18</li><li>Approval of minutes from BoF session – Approved.</li><li>New Logistics and Expanding Group</li><li>Outreach and evangelism:<ul><li>Common Messaging/Presentation – Phil O</li><li>Industry Venues – Phil R<ul><li>LinuxCon Debrief- Phil O</li></ul></li><li>Website – Martin M</li></ul></li></ul><h3 style="font-size: 1.17em;">Logistics</h3><p>PhilO discussed need for evolving logistics with the group getting larger and including new folks. We're doing away with the "Who just joined?" approach to attendance and will mainly depend on log-ins to Webshare to record attendance. In addition everyone is encouraged to state their name when speaking. There also some discussion (actually it came up towards the end of the meeting) about providing minutes via a link rather than an attached Word doc.</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h3><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;">Common Messaging/Presentation</h3><p>PhilO is updating the presentation to reflect Kate's LinuxCon presentation content.</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;">Industry Venues</h3><p>PhilO reported on LinuxCon. Jim Zemlin's keynote was all about the new Open Compliance Program, and SPDX was prominently featured. SPDX got some good PR out of it and one article said it was the key to the bigger program. Phil Koltun delivered a more detailed session on the OCP and Kate had one on SPDX. Both were well attended. Finally, we had a Birds of a Feature session.</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;">Website</h3><p>&nbsp;</p><p>Kudos to Martin for helping PhilO get the new spdx.org launched in time for LinuxCon. There was some discussion about making it more obvious how one joins both the group and the mailing list; it's better to be redundant in order to be more welcoming. There was also a discussion about getting examples up to date and getting the Wiki going again. We finally got into a discussion about hosting code for tools. Possibilities were: SourceForge, GitHub.</p><p>&nbsp;</p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;">Rollout</h3><p>PhilO mentioned the JohnE and KimW have been working on a rollout plan, expanding on both out technical efforts and outreach/evangelism efforts. More at the next meeting.</p><p>&nbsp;</p><h2><span style="font-size: small;"><span style="font-size: 12px;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></span></span></h2><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;">&nbsp;</span></h2><h3 style="font-size: 1.17em;">ACTION ITEMS</h3>
  
 
<ul><li>PhilO/Martin - Update on participation page where to join (suggestion was to put link in text, not just at top, consider "I want to use the spec, vs. I want to contribute to the spec" in navigation section.</li><li>Kate- Transfer document (.pdf) back to WIKI.</li><li>PhilO- Update standard presentation with LinuxCon2010 input</li><li>Kate- Clean up the sharing analysis to what is accurate.</li><li>Kate- Publish the current version number of the specification in brackets behind reference</li><li>Kim/PhilO- Add and element of 'What's in this for me?" to presentation</li><li>JeffL (w/Bill/Gary- Update zlib based on new specification</li><li>All- Look for new examples to add to site.</li><li>PhilK- Explore possibility of LF hosting source for SPDX tools.</li><li>Gary- Explore other possible hosting options</li><li>PhilO- Start making minutes available via link.</li><li>BillS- Start up RDF sub-group. Solicite members.</li></ul><p>&nbsp;</p>
 
<ul><li>PhilO/Martin - Update on participation page where to join (suggestion was to put link in text, not just at top, consider "I want to use the spec, vs. I want to contribute to the spec" in navigation section.</li><li>Kate- Transfer document (.pdf) back to WIKI.</li><li>PhilO- Update standard presentation with LinuxCon2010 input</li><li>Kate- Clean up the sharing analysis to what is accurate.</li><li>Kate- Publish the current version number of the specification in brackets behind reference</li><li>Kim/PhilO- Add and element of 'What's in this for me?" to presentation</li><li>JeffL (w/Bill/Gary- Update zlib based on new specification</li><li>All- Look for new examples to add to site.</li><li>PhilK- Explore possibility of LF hosting source for SPDX tools.</li><li>Gary- Explore other possible hosting options</li><li>PhilO- Start making minutes available via link.</li><li>BillS- Start up RDF sub-group. Solicite members.</li></ul><p>&nbsp;</p>
Line 7: Line 7:
 
<p>Agenda</p>
 
<p>Agenda</p>
  
<ul><li>Review mock up from Spot Calloway https://fedoraproject.org/wiki/TomCallaway/SPDX_License_List</li><li>License Short Form Discussion- Kate</li><li>General RDF Discussion</li></ul><h3 style="font-size: 1.17em;"><span style="font-size: x-small;"><span style="font-size: 10px; font-weight: normal;"><h3 style="font-size: 1.17em;">Mock Up</h3><p>Spot was not in attendance, but we reviewed the mock-up. There was fair agreement that its close to what we are looking for (if not "Spot" on)</p><p>&nbsp;</p><h3 style="font-size: 1.17em;"><span style="font-size: x-small;"><span style="font-size: 10px; font-weight: normal;"><h3 style="font-size: 1.17em;">Short Form Licenses</h3><p>Our implicit path had tied a fixed license list of licenses to the spec rev, but JohnE put forth an&nbsp;impassioned&nbsp;argument as to why they should be decoupled: Essentially we'll want the license list to change with more frequency than the spec (months vs. years). A new license can't mean a new spec rev. There was agreement on this point, but and then much discussion about how to manage the license list.&nbsp;</p><p>There was fair agreement just as there is a "playground" for working on the spec and a release process to the current rev, there should be a similar arrangement for licenses (though decoupled) and certainly there should be legal review. There was not complete agreement about the intended scope of the list, but there was agreement that there needed so be some nomination process and that anyone wishing to add a license must be willing to take on the associated work. BobG is willing to be a contributor. A topic of future discussion is how we will come down on the initial V1.0 list of licenses. These issues in contemplated in the rollout framework that we'll be putting forth.</p><p>&nbsp;</p><h3 style="font-size: 1.17em;">RDF</h3><p>We reviewed the intent of using RDF and BillS described what's been done with DOAP as a model. Essentially, we've chosen RDF as a reasonable balance between the needs of people being able to view and create SPDX docs, and machines to be able to consume and produce the format.</p><p>There was agreement that there is lots of work to be done in this area: defining the syntax, defining web repository of license info, documenting usage, etc. We decided that we need a sub-team to take this on. BillS will coordinate and PeterW, Gary and Kate will participate, as well as others who are interested.</p><p>&nbsp;</p><p>&nbsp;</p></span></span></h3><p>&nbsp;</p></span></span></h3><h3 style="font-size: 1.17em;">ATTENDANCE</h3><ul><li>Michael Herzog, NexB</li><li>Bob Gobeille, FOSSology.org, HP</li><li>Ann Thornton, Freescale</li><li>Martin Michlmayr, HP</li><li>Gary O'Neall, Source Auditor</li><li>Jeff Luszcz, Palamida</li><li>Richard Fontana, Red Hat</li><li>Mark Gisi, Wind River</li><li>Phil Koltun, Linux Foundation</li><li>John Ellis, Motorola</li><li>David Wolfe, Freescale</li><li>Tom Incorvia, Micro Focus</li><li>Kim Weins, Open Logic</li><li>Peter Williams, OpenLogic</li><li>Bill Schineller, Black Duck Software</li><li>Jack Manbeck, TI</li><li>Kate Stewart, Canonical</li><li>Philip Odence, Black Duck Software</li></ul><p>&nbsp;</p>
+
<ul><li>Review mock up from Spot Calloway https://fedoraproject.org/wiki/TomCallaway/SPDX_License_List</li><li>License Short Form Discussion- Kate</li><li>General RDF Discussion</li></ul><h3 style="font-size: 1.17em;"><span style="font-size: x-small;"><span style="font-size: 10px; font-weight: normal;">&nbsp;</span></span></h3><h3 style="font-size: 1.17em;">Mock Up</h3><p>Spot was not in attendance, but we reviewed the mock-up. There was fair agreement that its close to what we are looking for (if not "Spot" on)</p><p>&nbsp;</p><h3 style="font-size: 1.17em;"><span style="font-size: x-small;"><span style="font-size: 10px; font-weight: normal;">&nbsp;</span></span></h3><h3 style="font-size: 1.17em;">Short Form Licenses</h3><p>Our implicit path had tied a fixed license list of licenses to the spec rev, but JohnE put forth an&nbsp;impassioned&nbsp;argument as to why they should be decoupled: Essentially we'll want the license list to change with more frequency than the spec (months vs. years). A new license can't mean a new spec rev. There was much discussion about how to manage the license list.&nbsp;</p><p>There was fair agreement just as there is a "playground" for working on the spec and a release process to the current rev, there should be a similar arrangement for licenses (though decoupled) and certainly there should be legal review. </p><p>There was not complete agreement about the intended scope of the list, but there was agreement that there needed so be some nomination process and that anyone wishing to add a license must be willing to take on the associated work. BobG is willing to be a contributor. A topic of future discussion is how we will come down on the initial V1.0 list of licenses. These issues in contemplated in the rollout framework that we'll be putting forth.</p><p>&nbsp;</p><h3 style="font-size: 1.17em;">RDF</h3><p>We reviewed the intent of using RDF and BillS described what's been done with DOAP as a model. Essentially, we're exploring RDF as a reasonable balance between the needs of people being able to view and create SPDX docs, and machines to be able to consume and produce the format.</p><p>There was agreement that there is lots of work to be done in this area: defining the syntax, defining web repository of license info, documenting usage, etc. We decided that we need a sub-team to take this on. BillS will coordinate and PeterW, Gary and Kate will participate, as well as others who are interested.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><h3 style="font-size: 1.17em;">ATTENDANCE</h3><ul><li>Michael Herzog, NexB</li><li>Bob Gobeille, FOSSology.org, HP</li><li>Ann Thornton, Freescale</li><li>Martin Michlmayr, HP</li><li>Gary O'Neall, Source Auditor</li><li>Jeff Luszcz, Palamida</li><li>Richard Fontana, Red Hat</li><li>Mark Gisi, Wind River</li><li>Phil Koltun, Linux Foundation</li><li>John Ellis, Motorola</li><li>David Wolfe, Freescale</li><li>Tom Incorvia, Micro Focus</li><li>Kim Weins, Open Logic</li><li>Peter Williams, OpenLogic</li><li>Bill Schineller, Black Duck Software</li><li>Jack Manbeck, TI</li><li>Kate Stewart, Canonical</li><li>Philip Odence, Black Duck Software</li></ul><p>&nbsp;</p>

Revision as of 12:57, 23 September 2010

 

ADMINISTRATIVE

Agenda

  • Attendance - 18
  • Approval of minutes from BoF session – Approved.
  • New Logistics and Expanding Group
  • Outreach and evangelism:
    • Common Messaging/Presentation – Phil O
    • Industry Venues – Phil R
      • LinuxCon Debrief- Phil O
    • Website – Martin M

Logistics

PhilO discussed need for evolving logistics with the group getting larger and including new folks. We're doing away with the "Who just joined?" approach to attendance and will mainly depend on log-ins to Webshare to record attendance. In addition everyone is encouraged to state their name when speaking. There also some discussion (actually it came up towards the end of the meeting) about providing minutes via a link rather than an attached Word doc.

 

 

 

 

Common Messaging/Presentation

PhilO is updating the presentation to reflect Kate's LinuxCon presentation content.

 

Industry Venues

PhilO reported on LinuxCon. Jim Zemlin's keynote was all about the new Open Compliance Program, and SPDX was prominently featured. SPDX got some good PR out of it and one article said it was the key to the bigger program. Phil Koltun delivered a more detailed session on the OCP and Kate had one on SPDX. Both were well attended. Finally, we had a Birds of a Feature session.

 

Website

 

Kudos to Martin for helping PhilO get the new spdx.org launched in time for LinuxCon. There was some discussion about making it more obvious how one joins both the group and the mailing list; it's better to be redundant in order to be more welcoming. There was also a discussion about getting examples up to date and getting the Wiki going again. We finally got into a discussion about hosting code for tools. Possibilities were: SourceForge, GitHub.

 

 

Rollout

PhilO mentioned the JohnE and KimW have been working on a rollout plan, expanding on both out technical efforts and outreach/evangelism efforts. More at the next meeting.

 

 

 

ACTION ITEMS

  • PhilO/Martin - Update on participation page where to join (suggestion was to put link in text, not just at top, consider "I want to use the spec, vs. I want to contribute to the spec" in navigation section.
  • Kate- Transfer document (.pdf) back to WIKI.
  • PhilO- Update standard presentation with LinuxCon2010 input
  • Kate- Clean up the sharing analysis to what is accurate.
  • Kate- Publish the current version number of the specification in brackets behind reference
  • Kim/PhilO- Add and element of 'What's in this for me?" to presentation
  • JeffL (w/Bill/Gary- Update zlib based on new specification
  • All- Look for new examples to add to site.
  • PhilK- Explore possibility of LF hosting source for SPDX tools.
  • Gary- Explore other possible hosting options
  • PhilO- Start making minutes available via link.
  • BillS- Start up RDF sub-group. Solicite members.

 

TECHNICAL

Agenda

 

Mock Up

Spot was not in attendance, but we reviewed the mock-up. There was fair agreement that its close to what we are looking for (if not "Spot" on)

 

 

Short Form Licenses

Our implicit path had tied a fixed license list of licenses to the spec rev, but JohnE put forth an impassioned argument as to why they should be decoupled: Essentially we'll want the license list to change with more frequency than the spec (months vs. years). A new license can't mean a new spec rev. There was much discussion about how to manage the license list. 

There was fair agreement just as there is a "playground" for working on the spec and a release process to the current rev, there should be a similar arrangement for licenses (though decoupled) and certainly there should be legal review.

There was not complete agreement about the intended scope of the list, but there was agreement that there needed so be some nomination process and that anyone wishing to add a license must be willing to take on the associated work. BobG is willing to be a contributor. A topic of future discussion is how we will come down on the initial V1.0 list of licenses. These issues in contemplated in the rollout framework that we'll be putting forth.

 

RDF

We reviewed the intent of using RDF and BillS described what's been done with DOAP as a model. Essentially, we're exploring RDF as a reasonable balance between the needs of people being able to view and create SPDX docs, and machines to be able to consume and produce the format.

There was agreement that there is lots of work to be done in this area: defining the syntax, defining web repository of license info, documenting usage, etc. We decided that we need a sub-team to take this on. BillS will coordinate and PeterW, Gary and Kate will participate, as well as others who are interested.

 

 

 

ATTENDANCE

  • Michael Herzog, NexB
  • Bob Gobeille, FOSSology.org, HP
  • Ann Thornton, Freescale
  • Martin Michlmayr, HP
  • Gary O'Neall, Source Auditor
  • Jeff Luszcz, Palamida
  • Richard Fontana, Red Hat
  • Mark Gisi, Wind River
  • Phil Koltun, Linux Foundation
  • John Ellis, Motorola
  • David Wolfe, Freescale
  • Tom Incorvia, Micro Focus
  • Kim Weins, Open Logic
  • Peter Williams, OpenLogic
  • Bill Schineller, Black Duck Software
  • Jack Manbeck, TI
  • Kate Stewart, Canonical
  • Philip Odence, Black Duck Software