Difference between revisions of "General Meeting/Minutes/2010-09-09"

<p><span style="font-size: 12px; font-weight: bold;">ADMINISTRATIVE</span></p><h2 style="font-size: 1.5em;"><span style="font-weight: normal; font-size: 10px;"><p><h3 style="font-size: 1.17em;">Agenda</h3></p><ul><li>Attendance - 19</li><li>Approval of minutes - Pending til next meeting</li><li>Outreach and evangelism:<ul><li>Common Messaging/Presentation – PhilO</li><li>Industry Venues – PhilR</li><li>Website – PhilO/MartinM</li></ul></li><li>Rollout- KimW</li></ul><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 reported that he'd updated the presentation. He's added a slide describing to people why they should participate; he and Kim will update in the context of her OWF presentation.</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 reviewed process for new participatns</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>PhilO walked through changes implemented to make how to participate more obvious. There are pointers to where to sign up and get on the mailing list from every major tab.</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>Kim described the motivations for, approach to and elements of the rollout that will require work. There's a fair amount to be done, but it is now well framed. There will likely be a different thread of meetings on rollout issues (vs. spec completion) starting after a face to face meeting in mid-November. Some of the areas that need work would benefit from skills from outside the current group, so please think about others in your organization that might help.</p><p>&nbsp;</p><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;">Issue Tracking</h3></span></h2><p>We agreed that we should implement an issue tracking system for spec issues. We can use Linux Foundations Bugzilla. Peter Williams agreed to drive and administer with help from Marshall.</p><p>&nbsp;</p></span></h2><p>&nbsp;</p></span></h2><h2 style="font-size: 1.5em;"><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><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. DONE</li><li>Kate- Transfer document (.pdf) back to WIKI. IN PROCESS</li><li>PhilO- Update standard presentation with LinuxCon2010 input DONE</li><li>Kate- Clean up the sharing analysis to what is accurate. &nbsp;IN PROCESS</li><li>Kate- Publish the current version number of the specification in brackets behind reference DONE</li><li>Kim/PhilO- Add and element of 'What's in this for me?" to presentation &nbsp;DONE</li><li>JeffL (w/Bill/Gary- Update zlib based on new specification &nbsp;IN PROCESS</li><li>All- Look for new examples to add to site. IN PROCESS</li><li>PhilK- Explore possibility of LF hosting source for SPDX tools. &nbsp;DONE.&nbsp;</li><li>Gary- Explore other possible hosting options. DONE.&nbsp;</li><li>PhilO- Start making minutes available via link. DONE</li><li>BillS- Start up RDF sub-group. Solicite members. &nbsp;DONE</li></ul><p>New</p><p>&nbsp;</p><ul><li>KimW- Sent rollout slides to mailing list</li><li>RDF Group- Work out syntax for 5.6/5.7</li><li>Bill S- Add Ed W to the RDF group</li><li>Kate- Track and (when Wiki is back up) implement changes described in Spec section below.</li><li>PeterW- Implement issue tracking system.</li></ul><p>&nbsp;</p><p>&nbsp;</p><h3 style="font-size: 1.17em;">TECHNICAL</h3><p><h3 style="font-size: 1.17em;">Agenda</h3></p><ul><li>Spec current status and open areas- Kate</li><li>RDF Focus Group update - Bill</li><li>Tools update - Gary</li><li>Issue Tracking</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;">License Discussion</h3><h3 style="font-size: 1.17em;"></h3><h3 style="font-size: 1.17em;"><span style="font-weight: normal; font-size: 10px;">As there has been a lot of discussion of licenses on the mailing list (decoupling from spec, etc.), we decided to have a separate session dedicated to that discussion. Kate will be hosting on Thurs, Sept 16 at 12:00 EDT (one hour later than our normal).</span></h3><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;">Spec</h3><p>No changes have been implemented since the beta release as we are working through some formatting issues getting the .pdf back into Wiki form.</p><p>5.6/5.7 We picked up on the discussion from the maillist of adding 5.6/5.7 fields to the file section which would designate the name and URL of the package from which a file is known to come. There was agreement that we should go ahead with this in concept and that the RDF group would work out the syntax.</p><p>3.3 To deal with the recursive problem (wanting to include the SPDX file in a package but also wanting it to include a SHA-1 for the package) there has been a proposal to do a checksum of the SHA-1s of all the other files in the package. We got into a discussion of "unique identifier" vs. "validator" and it became clear our nomenclature needs to be cleaned up to indicate that this is a validator and not an identifier. Someone proposed "Package Check Sum" as the name of the field and there was agreement. Kate will clean up the language requested more discussion on the maillist of the technical approach.</p><p>Appendices- The RDF group identified the need for an ontology and an XML schema appendix.&nbsp;</p><p><span style="font-size: 12px; font-weight: bold;">RDF Group</span></p><p>There was a good kickoff meeting last Thursday. Most of the discussion was about approaches and concerns. Participants were confident that they would be making headway shortly. Bill found a collaborative ontology site that will be useful in the development.</p><p>&nbsp;</p><h3 style="font-size: 1.17em;"><span style="font-size: x-small;"><span style="font-size: 10px; font-weight: normal;"><p><span style="font-size: 12px; font-weight: bold;">Tools</span></p><p>&nbsp;</p><p>There is an upcoming meeting to discuss in more detail. We resolved that we will utilize the Linux Foundation-hosted GIT instance to house the tools. First project will be Gary's pretty printer (the code of which he believes will be useful for other purposes).</p></span></span></h3><p>&nbsp;</p></span></span></h3><p>&nbsp;</p></span></span></h3><h3 style="font-size: 1.17em;">ATTENDANCE</h3><ul><li>Gary O'Neall, Source Auditor</li><li>Daniel Germain, U of Victoria</li><li>Marshall Clow, Qualcomm</li><li>Peter Williams, OpenLogic</li><li>Kim Weins, OpenLogic</li><li>Kate Stewart, Canonical</li><li>Ed Warnicke, Cisco</li><li>Ann Thornton, Freescale</li><li>Alan Stern, Cisco</li><li>Phil Robb, HP</li><li>Tom Incorvia, Micro Focus</li><li>Phil Koltun, Linux Foundation</li><li>Mark Gisi, Wind River</li><li>Jeff Luszcz, Palamida</li><li>Pierre Lapointe, NexB</li><li>Esteban Rockett, Motorola</li><li>Philip Odence, Black Duck Software</li><li>Eric Weidner, OpenLogic</li><li>Dave McLoughlin, OpenLogic</li></ul><p>&nbsp;</p>