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

Difference between revisions of "Technical Team/Minutes/2011-08-23"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
<p><span style="font-family: Times New Roman; font-size: small;">Minutes 8/23/2011</span></p>
+
== Attendees ==
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;">Attendees:</span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Bill Schineller</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Kirsten Newcomer</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Branden Robinson</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Peter Williams</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Gary O’Neall</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Kate Stewart</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Nicholaas Loke</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Jack Manbeck</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Marshal Clow</span></li></ul>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;">Agenda:</span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<ul><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">Weekly call Logistics</span></li><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">LinuxCon Feedback</span></li><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">Proposal for Spec Version numbering</span></li><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">Tools source structure</span></li><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">Verification Code algorithm</span></li><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">Composite Packages</span></li><li><span style="font-size: small;">·</span>        <span style="font-family: Times New Roman; font-size: small;">“Garbage Files”</span></li></ul>
+
  
 +
* Bill Schineller
 +
* Kirsten Newcomer
 +
* Branden Robinson
 +
* Peter Williams
 +
* Gary O’Neall
 +
* Kate Stewart
 +
* Nicholaas Loke
 +
* Jack Manbeck
 +
* Marshal Clow
  
 +
== Agenda ==
  
 +
* Weekly call Logistics
 +
* LinuxCon Feedback
 +
* Proposal for Spec Version numbering
 +
* Tools source structure
 +
* Verification Code algorithm
 +
* Composite Packages
 +
* “Garbage Files”
  
 +
== Logistics ==
  
 +
* Move to 2:00 Eastern to accommodate west coast- considering that we don’t currently have any attendees from Europe. Kate will update Wiki.
  
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
== Feedback from LinuxCon ==
<p><span style="font-family: Times New Roman; font-size: small;">Logistics:</span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Move to 2:00 Eastern to accommodate west coast- considering that we don’t currently have any attendees from Europe.  Kate will update Wiki.</span></li></ul>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;">Feedback from LinuxCon:</span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Discussed relationship between SPDX packages and the needed for a hierarchical relationship</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Discussed PDDL</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Discussed compatibility between tags and RDF for future development</span></li></ul>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;">Numbering for Spec. version:</span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Format AA.BB.CC </span><ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">AA – Major version - Incremented for changes incompatible with previous versions (current definition)</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">BB – Minor version -  would be used when changes may impact the consumer, but is compatible with previous versions</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">CC – Micro version - would be used when the changes do not impact to the consumer of SPDX</span></li></ul></li>
+
</ul>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;">Tools source structure:</span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Create separate repositories for the different language tools</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Create a separate git-repo named “Python-SPDX-Tools”</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Rename current tools repo to “Java-SPDX-Tools”</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Kate will either send info to Gary or send info to Linux Foundation to make changes</span></li></ul>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-size: small;"><span style="font-family: Times New Roman;">Note: Bugzilla has a target field to indicate which release the resolution is targeted for.  There are no targets for detail “CC” versions; we will use the major version targets for those changes.  </span></span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-size: small;"><span style="font-family: Times New Roman;">Verification code algorithm:  </span></span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Need to specify a better separator character “\n” is ambiguous – Kate will choose a character and update spec</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Update to the verification code algorithm would result in an increment to the micro version (e.g. 1.0.1)</span></li></ul>
+
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
<p><span style="font-family: Times New Roman; font-size: small;">Bug 818 – Composite packages:</span></p>
+
<ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Agreed to create a request for proposal</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Will update bug with additional information discussed on the call</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Two approaches were discussed:</span><ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Include all composite information in one document</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Enable multiple documents to cross reference each other</span><ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Link files</span></li>
+
<li><span style="font-family: Times New Roman; font-size: small;">Unique IDs</span><ul>
+
<li><span style="font-family: Times New Roman; font-size: small;">Can use the verification code</span></li></ul></li>
+
</ul></li>
+
</ul></li>
+
  
<li><span style="font-family: Times New Roman; font-size: small;">Signing documents</span><ul>
+
* Discussed relationship between SPDX packages and the needed for a hierarchical relationship
<li><span style="font-family: Times New Roman; font-size: small;">How does adding reviewer information impact the signing?</span></li></ul></li>
+
* Discussed PDDL
 +
* Discussed compatibility between tags and RDF for future development
  
<li><span style="font-family: Times New Roman; font-size: small;">Composite packages requirements</span><ul>
+
== Numbering for Spec. version ==
<li><span style="font-family: Times New Roman; font-size: small;">Requirements will be included in the request for proposal</span></li>
+
 
<li><span style="font-family: Times New Roman; font-size: small;">We will discuss the requirements on next week’s call</span></li></ul></li>
+
* Format AA.BB.CC
</ul>
+
** AA – Major version - Incremented for changes incompatible with previous versions (current definition)
<p><span style="font-family: Times New Roman; font-size: small;"> </span></p>
+
** BB – Minor version - would be used when changes may impact the consumer, but is compatible with previous versions
<p><span style="font-family: Times New Roman; font-size: small;">“Garbage Files” (e.g. .svn files):</span></p>
+
** CC – Micro version - would be used when the changes do not impact to the consumer of SPDX
<ul>
+
 
<li><span style="font-family: Times New Roman; font-size: small;">All files need to be included in the file info, even “garbage files”</span></li>
+
== Tools source structure ==
<li><span style="font-family: Times New Roman; font-size: small;">Proposal to create a new file type – “CRUFT” – proposal for the mailing list. Gary will write a proposal in the form of a bug and send to the mailing list. [Bug 944 has been added with the proposal]</span></li></ul>
+
 
 +
* Create separate repositories for the different language tools
 +
* Create a separate git-repo named “Python-SPDX-Tools”
 +
* Rename current tools repo to “Java-SPDX-Tools”
 +
* Kate will either send info to Gary or send info to Linux Foundation to make changes
 +
 
 +
Note: Bugzilla has a target field to indicate which release the resolution is targeted for. There are no targets for detail “CC” versions; we will use the major version targets for those changes.
 +
 
 +
== Verification code algorithm ==
 +
 
 +
* Need to specify a better separator character “\n” is ambiguous – Kate will choose a character and update spec
 +
* Update to the verification code algorithm would result in an increment to the micro version (e.g. 1.0.1)
 +
 
 +
== Bug 818 – Composite packages ==
 +
 
 +
* Agreed to create a request for proposal
 +
* Will update bug with additional information discussed on the call
 +
* Three approaches were discussed:
 +
** Include all composite information in one document
 +
** Keep package documents separate and have separate new type of file to cross reference.
 +
** Enable multiple documents to cross reference each other
 +
*** Link files
 +
*** Unique IDs
 +
**** Can use the verification code
 +
* Signing documents
 +
** How does adding reviewer information impact the signing?
 +
* Composite packages requirements
 +
** Requirements will be included in the request for proposal
 +
** We will discuss the requirements on next week’s call
 +
 
 +
== “Garbage Files” (e.g. .svn files) ==
 +
 
 +
* All files need to be included in the file info, even “garbage files”
 +
* Proposal to create a new file type – “CRUFT” – proposal for the mailing list. Gary will write a proposal in the form of a bug and send to the mailing list. (Bug 944 has been added with the proposal)
 +
 
 +
[[Category:Technical|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 13:58, 6 March 2013

Attendees

  • Bill Schineller
  • Kirsten Newcomer
  • Branden Robinson
  • Peter Williams
  • Gary O’Neall
  • Kate Stewart
  • Nicholaas Loke
  • Jack Manbeck
  • Marshal Clow

Agenda

  • Weekly call Logistics
  • LinuxCon Feedback
  • Proposal for Spec Version numbering
  • Tools source structure
  • Verification Code algorithm
  • Composite Packages
  • “Garbage Files”

Logistics

  • Move to 2:00 Eastern to accommodate west coast- considering that we don’t currently have any attendees from Europe. Kate will update Wiki.

Feedback from LinuxCon

  • Discussed relationship between SPDX packages and the needed for a hierarchical relationship
  • Discussed PDDL
  • Discussed compatibility between tags and RDF for future development

Numbering for Spec. version

  • Format AA.BB.CC
    • AA – Major version - Incremented for changes incompatible with previous versions (current definition)
    • BB – Minor version - would be used when changes may impact the consumer, but is compatible with previous versions
    • CC – Micro version - would be used when the changes do not impact to the consumer of SPDX

Tools source structure

  • Create separate repositories for the different language tools
  • Create a separate git-repo named “Python-SPDX-Tools”
  • Rename current tools repo to “Java-SPDX-Tools”
  • Kate will either send info to Gary or send info to Linux Foundation to make changes

Note: Bugzilla has a target field to indicate which release the resolution is targeted for. There are no targets for detail “CC” versions; we will use the major version targets for those changes.

Verification code algorithm

  • Need to specify a better separator character “\n” is ambiguous – Kate will choose a character and update spec
  • Update to the verification code algorithm would result in an increment to the micro version (e.g. 1.0.1)

Bug 818 – Composite packages

  • Agreed to create a request for proposal
  • Will update bug with additional information discussed on the call
  • Three approaches were discussed:
    • Include all composite information in one document
    • Keep package documents separate and have separate new type of file to cross reference.
    • Enable multiple documents to cross reference each other
      • Link files
      • Unique IDs
        • Can use the verification code
  • Signing documents
    • How does adding reviewer information impact the signing?
  • Composite packages requirements
    • Requirements will be included in the request for proposal
    • We will discuss the requirements on next week’s call

“Garbage Files” (e.g. .svn files)

  • All files need to be included in the file info, even “garbage files”
  • Proposal to create a new file type – “CRUFT” – proposal for the mailing list. Gary will write a proposal in the form of a bug and send to the mailing list. (Bug 944 has been added with the proposal)