View source for General Meeting/Minutes/2011-06-02

<p style="text-align: left;">Attendance: 13<br />Minutes for 20110519 approved<br />&nbsp;&nbsp;&nbsp;&nbsp; <br /><strong>Technical Team Report - Gary</strong></p><ul style="text-align: left;"><li>Tools: have received good feedback; addressed a few technical issues; available for beta use</li><li>Spec: final polishing has been largely completed; waiting for one more review from legal which is expected by Friday am PT</li></ul><p style="text-align: left;"><strong>Business Team Report - Kim</strong></p><ul style="text-align: left;"><li>3 beta teams are working; target for beta completion &amp; feedback is end of June; request that all teams work toward this date<br /><ul><li>HP/WindRiver &amp; OL/Antelink are in progress</li><li>Kickoff for Motorola/TI still to be scheduled, but there's been activity. Rockett will work with Gary to get kickoff scheduled</li></ul></li><li>Website refresh subteam has been created. Details on this working group can be found here: <br /><ul><li>http://spdx.org/wiki/website-refresh</li></ul></li><li>GA launch process is next big thing to focus on<ul><li>Planned for LinuxCon in Vancouver</li><li>Phil O. has a speaking slot</li><li>Goal include press release and mention in keynote</li></ul></li></ul><p style="text-align: left;"><strong>Legal Team Report - Rockett</strong></p><ul style="text-align: left;"><li>Last scrub on 5/16 spec in progress. Final comments due by Friday am PT time, 6/3</li><li>Recommend Open Data Commons PDDL license for SPDX MetaData (http://www.opendatacommons.org/licenses/pddl/); will send link to broader group for final sign-off</li><li>License templatizing is the next big focus</li><li>Also noted that we'll need a process for adding licenses to SPDX list very soon; Kim says Biz Team has a proposal for a process and she'll plan to share more broadly</li></ul><p style="text-align: left;"><strong>Cross Functional Issues – Discussion</strong></p><ul><li>Website update- Steve<ul><li>Sandbox for testing new website structure in place</li><li>Team plans to create storyboards for 3-4 personas using mind map tools</li><li>wiki pages for working grou now available http://spdx.org/wiki/website-refresh</li></ul></li><li>Questions/recommendations for presenting data for binaries and archives such as jar files -- Kim<ul><li>There's been recent email about how to represent data for binaries that are combinations of OSS, 3rd party, and proprietary code in SPDX documents</li><li>Issue has also come up for OL/Antelink beta partners; OL/Antelink have decided to use compound licensing for jar files when needed; should we recommend the same approach for binaries?</li><li>There was a lively discussion on this topic with input from Steve Cropper, Kim Weins, Michael Herzog, Kate Stewart</li><li>Main conclusion: Recommendations for how to handle these use cases need to be added to the draft FAQ <br /><ul><li>Draft FAQ is available here: http://spdx.org/wiki/draft-spdx-faq</li><li>FAQ should address questions about proprietary and 3rd party as well as OSS licenses</li><li>Kim added a number of topics to the FAQ; need volunteers to provide additional info on these topics</li></ul></li><li>A side issue regarding how best to connect package and SPDX document was also discussed</li><li>The topic of package hierarchy also came up<br /><ul><li>Michael H. noted that the SPDX team made a conscious choice not to tackle this for v1 of the specification</li><li>v1 spec is intended to address lower level or sub-assembly items and a BOM is not yet represented in the spec</li><li>Recommended that a section on items specifically deferred be added to the FAQ so that new users have visibility into these decisions</li><li>Michael also volunteered to pull together info on well traveled routes for BOMs that we might want to leverage&nbsp;&nbsp;&nbsp; </li></ul></li></ul></li></ul><p style="text-align: left;"><br /><strong>Open Action Items</strong></p><ul><li>MartinM- Report back on # of people on respective mailing lists. ONGOING</li><li>Kim -- share Biz Team proposed process for adding licenses to SPDX list more broadly</li><li>Michael H. -- provide info on existing BOM standards that should be useful for future consideration</li><li>Legal/Biz Teams- Review and update Master Schedule</li><li>?? -- volunteers needed to review and update the FAQ: http://spdx.org/wiki/draft-spdx-faq</li></ul><p style="text-align: left;"><strong>Closed Action Items</strong></p><ul><li>Kirsten- Notify Kim of need to clean up business section of website.</li><li>MartinM- Get master list of website pages to Kate</li></ul><p class="p1" style="text-align: left;"><strong>Attendees</strong></p><ul class="ul1"><li class="li2" style="text-align: left;">Kirsten Newcomer, Black Duck Software</li><li class="li2" style="text-align: left;">Kamal Hassin, Protecode</li><li class="li2" style="text-align: left;">Kim Weins, OpenLogic</li><li class="li2" style="text-align: left;">Esteban Rockett, Motorola</li><li class="li2" style="text-align: left;">Gary O'Neall, Source Auditor</li><li class="li2" style="text-align: left;">Michael Herzog, NexB</li><li style="text-align: left;">Martin Michlmayr, HP</li><li style="text-align: left;">Kate Stewart, Canonical</li><li style="text-align: left;">Peter Williams, OpenLogic</li><li style="text-align: left;">Jillayne Lovejoy, OpenLogic</li><li style="text-align: left;">Brandon Robinson, Cisco</li><li style="text-align: left;">Steve Cropper, Cisco</li><li style="text-align: left;">Tom Incorvia, Microfocus</li></ul>