Difference between revisions of "Technical Team/Minutes/2012-04-04"

From SPDX Wiki
Jump to: navigation, search
 
Line 1: Line 1:
<p class="MsoNormal">Minutes for April 4, 2012 Face to Face meeting at Linux Collaboration Summit</p><p>Attendees:</p><p>Marshall Clow</p><p>Kate Stewart</p><p>Ed Warnicke</p><p>Jack Manbeck</p><p>Gary O’Neall</p><p>Peter Williams</p><p>Bill Schineller</p><p>Kirsten Newcomer</p><p>&nbsp;</p><p><strong>Discussed proposed agenda for Thursday afternoon (4/5) meeting</strong></p><ul><li>Use case discussion (Thursday)</li><li>Mandatory vs. non-mandatory / backwards compatibility</li><li>SPDX Tech web site<ul><li>Review progress; request update from volunteers, and from Steve C.</li></ul></li></ul><p>&nbsp;<strong>Steps needed to close on v 1.1 of the spec</strong></p><ul><li>Get Tech team to sign off, then publish to general team for final review</li><li>Open issues:<ul><li>final pass to ensure RDF and spec are in synch -- Kate</li><li>Appendix 1 will be updated to reflect what’s on the website as of date -- Kate</li><li>Review section 1 to see if it needs to be updated&nbsp; -- Kirsten</li><li>Compare version 1.1 and 1.0 side by side -- Kirsten</li><li>5.3 &amp; 5.4:<ul><li>Per discussion, these fields will be made OPTIONAL -- Kate</li><li>Peter to provide a proposal for how to present RDF examples for these fields</li></ul></li></ul></li><li>Provide guidelines to consumers for adopting 1.1<ul><li>Minimum: update Data License and Package verification code</li><li>Available OSS tools support multiple versions of the spec</li></ul></li></ul><p>&nbsp;<strong>Proposed governance model for SDPX Technical group</strong></p><ul><li>Post agenda one day ahead of call</li><ul><li>Kate owns and will delegate as needed</li></ul><li>Proposals to be voted on will be posted to wiki and sent to mailing list</li><ul><li>Votes sent to mailing list</li><li>Votes tabulated on wiki (with names)</li></ul><ul><li>We will use Plus one model for votes<ul><li>Plus one (+) is a yes vote</li><li>Minus (-) is a no vote</li><li>Zero (0) is a present / don’t care vote</li></ul></li></ul><li>Any objection / negative vote results in a call scheduled on the topic<ul><li>We assume that if you voted minus, you’ll participate in call</li></ul></li></ul><p><strong>Brief discussion of signing &amp; review fields</strong></p><ul><li>Suggest using annotations on already signed files for review data</li></ul><p><strong>Discussed schedule for 2.0. Potential schedule:</strong></p><ul><li>Draft by end of 2012, with beta program<ul><li>Need tools lined up to support beta</li><li>Provide v2.0 SPDX document as an example</li><li>2.0 GA is about 1 year out</li></ul></li></ul><p><strong>Proposed To-Do list for next 12 months</strong></p><ul><li>Mailing list for users: spdx-users</li><li>Publicize IRC channel; ensure registered</li><li>Additional tools needed</li><ul><li>SPDX document for existing tools -- Gary</li><li>SPDX validator – enhance viewer</li><li>Reading packages and generating SPDX files – Ninka, Fossology<ul><li>Gary has offered to help Fossology</li></ul></li><li>License matching normalization – Kate</li><li>License matcher – input text, and check to see if one of the standard licenses, leverage normalization tool</li></ul><ul><li>Existing tools now handle tag value format<ul><li>Go between tag and rdf and spreadsheet</li></ul></li></ul><li>Tooling available with<ul><li>Ubuntu – Kate &amp; Gary</li><li>RPM</li></ul></li><li>SPDX tools available via SaaS model<ul><li>Amazon offers an option here</li><li>Gary has an instance already; UI needed</li><li>Ask LF to pay for hosting this instance for fixed domain (Kate/Jack will approach Jim when we’re ready)</li></ul></li><li>Additional documentation is needed</li><ul><li>Getting Started Guide with SPDX</li><li>YouTube video</li><li>Update tools documentation – Kirsten</li><li>Translated version of v1.1 into Japanese – Kirsten to see if I can find a volunteer to do this by June</li><ul><li>Future: identify process for getting spec and related materials translated by community volunteers</li></ul></ul></ul><p>SPDX 2.0 Use Case review &amp; discussion: changes based on discussion captured in wiki changes</p><ul><li>NOTE: Review to continue starting with item 12.</li></ul><p>&nbsp;</p><p>As always, comments and corrections are most welcome!</p><p>Kirsten</p>
+
<p class="MsoNormal">Minutes for April 4, 2012 Face to Face meeting at Linux Collaboration Summit</p><p>Attendees:</p><p>Marshall Clow</p><p>Kate Stewart</p><p>Ed Warnicke</p><p>Jack Manbeck</p><p>Gary O’Neall</p><p>Peter Williams</p><p>Bill Schineller</p><p>Kirsten Newcomer</p><p>&nbsp;</p><p><strong>Discussed proposed agenda for Thursday afternoon (4/5) meeting</strong></p><ul><li>Use case discussion (Thursday)</li><li>Mandatory vs. non-mandatory / backwards compatibility</li><li>SPDX Tech web site<ul><li>Review progress; request update from volunteers, and from Steve C.</li></ul></li></ul><p>&nbsp;<strong>Steps needed to close on v 1.1 of the spec</strong></p><ul><li>Get Tech team to sign off, then publish to general team for final review</li><li>Open issues:<ul><li>final pass to ensure RDF and spec are in synch -- Kate</li><li>Appendix 1 will be updated to reflect what’s on the website as of date -- Kate</li><li>Review section 1 to see if it needs to be updated&nbsp; -- Kirsten</li><li>Compare version 1.1 and 1.0 side by side -- Kirsten</li><li>Compare RDF terms, Spec terms, and tool implementation for 1.1 - Gary</li><li>5.3 &amp; 5.4:<ul><li>Per discussion, these fields will be made OPTIONAL -- Kate</li><li>Peter to provide a proposal for how to present RDF examples for these fields</li></ul></li></ul></li><li>Provide guidelines to consumers for adopting 1.1<ul><li>Minimum: update Data License and Package verification code</li><li>Available OSS tools support multiple versions of the spec</li></ul></li></ul><p>&nbsp;<strong>Proposed governance model for SDPX Technical group</strong></p><ul><li>Post agenda one day ahead of call</li><ul><li>Kate owns and will delegate as needed</li></ul><li>Proposals to be voted on will be posted to wiki and sent to mailing list</li><ul><li>Votes sent to mailing list</li><li>Votes tabulated on wiki (with names)</li></ul><ul><li>We will use Plus one model for votes<ul><li>Plus one (+) is a yes vote</li><li>Minus (-) is a no vote</li><li>Zero (0) is a present / don’t care vote</li></ul></li></ul><li>Any objection / negative vote results in a call scheduled on the topic<ul><li>We assume that if you voted minus, you’ll participate in call</li></ul></li></ul><p><strong>Brief discussion of signing &amp; review fields</strong></p><ul><li>Suggest using annotations on already signed files for review data</li></ul><p><strong>Discussed schedule for 2.0. Potential schedule:</strong></p><ul><li>Draft by end of 2012, with beta program<ul><li>Need tools lined up to support beta</li><li>Provide v2.0 SPDX document as an example</li><li>2.0 GA is about 1 year out</li></ul></li></ul><p><strong>Proposed To-Do list for next 12 months</strong></p><ul><li>Mailing list for users: spdx-users</li><li>Publicize IRC channel; ensure registered</li><li>Additional tools needed</li><ul><li>SPDX document for existing tools -- Gary</li><li>SPDX validator – enhance viewer</li><li>Reading packages and generating SPDX files – Ninka, Fossology<ul><li>Gary has offered to help Fossology</li></ul></li><li>License matching normalization – Kate &amp; Daniel G.</li><li>License matcher – input text, and check to see if one of the standard licenses, leverage normalization tool</li></ul><ul><li>Existing tools now handle tag value format<ul><li>Go between tag and rdf and spreadsheet</li></ul></li></ul><li>Tooling available with<ul><li>Ubuntu – Kate &amp; Gary</li><li>RPM</li></ul></li><li>SPDX tools available via SaaS model<ul><li>Amazon offers an option here</li><li>Gary has an instance already; UI needed</li><li>Ask LF to pay for hosting this instance for fixed domain (Kate/Jack will approach Jim when we’re ready)</li></ul></li><li>Additional documentation is needed</li><ul><li>Getting Started Guide with SPDX</li><li>YouTube video</li><li>Update tools documentation – Kirsten</li><li>Translated version of v1.1 into Japanese – Kirsten to see if I can find a volunteer to do this by June</li><ul><li>Future: identify process for getting spec and related materials translated by community volunteers</li></ul></ul></ul><p>SPDX 2.0 Use Case review &amp; discussion: changes based on discussion captured in wiki changes</p><ul><li>NOTE: Review to continue starting with item 12.</li></ul><p>&nbsp;</p><p>As always, comments and corrections are most welcome!</p><p>Kirsten</p>

Revision as of 23:41, 5 April 2012

Minutes for April 4, 2012 Face to Face meeting at Linux Collaboration Summit

Attendees:

Marshall Clow

Kate Stewart

Ed Warnicke

Jack Manbeck

Gary O’Neall

Peter Williams

Bill Schineller

Kirsten Newcomer

 

Discussed proposed agenda for Thursday afternoon (4/5) meeting

  • Use case discussion (Thursday)
  • Mandatory vs. non-mandatory / backwards compatibility
  • SPDX Tech web site
    • Review progress; request update from volunteers, and from Steve C.

 Steps needed to close on v 1.1 of the spec

  • Get Tech team to sign off, then publish to general team for final review
  • Open issues:
    • final pass to ensure RDF and spec are in synch -- Kate
    • Appendix 1 will be updated to reflect what’s on the website as of date -- Kate
    • Review section 1 to see if it needs to be updated  -- Kirsten
    • Compare version 1.1 and 1.0 side by side -- Kirsten
    • Compare RDF terms, Spec terms, and tool implementation for 1.1 - Gary
    • 5.3 & 5.4:
      • Per discussion, these fields will be made OPTIONAL -- Kate
      • Peter to provide a proposal for how to present RDF examples for these fields
  • Provide guidelines to consumers for adopting 1.1
    • Minimum: update Data License and Package verification code
    • Available OSS tools support multiple versions of the spec

 Proposed governance model for SDPX Technical group

  • Post agenda one day ahead of call
    • Kate owns and will delegate as needed
  • Proposals to be voted on will be posted to wiki and sent to mailing list
    • Votes sent to mailing list
    • Votes tabulated on wiki (with names)
    • We will use Plus one model for votes
      • Plus one (+) is a yes vote
      • Minus (-) is a no vote
      • Zero (0) is a present / don’t care vote
  • Any objection / negative vote results in a call scheduled on the topic
    • We assume that if you voted minus, you’ll participate in call

Brief discussion of signing & review fields

  • Suggest using annotations on already signed files for review data

Discussed schedule for 2.0. Potential schedule:

  • Draft by end of 2012, with beta program
    • Need tools lined up to support beta
    • Provide v2.0 SPDX document as an example
    • 2.0 GA is about 1 year out

Proposed To-Do list for next 12 months

  • Mailing list for users: spdx-users
  • Publicize IRC channel; ensure registered
  • Additional tools needed
    • SPDX document for existing tools -- Gary
    • SPDX validator – enhance viewer
    • Reading packages and generating SPDX files – Ninka, Fossology
      • Gary has offered to help Fossology
    • License matching normalization – Kate & Daniel G.
    • License matcher – input text, and check to see if one of the standard licenses, leverage normalization tool
    • Existing tools now handle tag value format
      • Go between tag and rdf and spreadsheet
  • Tooling available with
    • Ubuntu – Kate & Gary
    • RPM
  • SPDX tools available via SaaS model
    • Amazon offers an option here
    • Gary has an instance already; UI needed
    • Ask LF to pay for hosting this instance for fixed domain (Kate/Jack will approach Jim when we’re ready)
  • Additional documentation is needed
    • Getting Started Guide with SPDX
    • YouTube video
    • Update tools documentation – Kirsten
    • Translated version of v1.1 into Japanese – Kirsten to see if I can find a volunteer to do this by June
      • Future: identify process for getting spec and related materials translated by community volunteers

SPDX 2.0 Use Case review & discussion: changes based on discussion captured in wiki changes

  • NOTE: Review to continue starting with item 12.

 

As always, comments and corrections are most welcome!

Kirsten