Difference between revisions of "Technical Team/Minutes/2011-02-01"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Minutes 2/1/2011</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">&nbsp;</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Attendees:</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Bill Schineller</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Gary O'Neall</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Peter Williams</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Kate Stewart</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Marshall Clow</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Phil Koltun</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">&nbsp;</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Pre-meeting discussion on version management of the specification.<span style="mso-spacerun: yes;">&nbsp; </span>Need to work through the remaining issues to get the git version of the spec in sync.<span style="mso-spacerun: yes;">&nbsp; </span>After that, we can modify the process to automatically push out the defects.</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Issues review - please refer to the spreadsheet attached to the minutes.<span style="mso-spacerun: yes;">&nbsp; </span>The legend tab describes the priority definitions.</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Changes in the spreadsheet from the original proposed priorities:</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>587 and 625 should probably be merged</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>617 - leave as priority one since the legal team may require</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Move 640, 643, 646 to P1 - these will affect the spec being in sync</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>623 - comment field for author of the SPDX document - move to P1 since this is relatively easy</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Need to add a bug to track the implementation of the xor's for all file hashes to create a unique package signiture</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Reference this new bug in bug 593 - the solution referenced above will solve this bug as well</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Bill added rought estimates on the effort for the P1 defects</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Gary will update bugzilla with all of the priority information from the meeting</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">From this point forward, all submitters of bugs should assign a priority based ont he following critera:</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>1 -&nbsp;Must be resolved for beta</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>2 -&nbsp;Want to resolve for beta, but is a must for the release 1 of the spec (e.g. can be resolved after the start of beta)</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>3 -&nbsp;Want for release 1</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;"><span style="mso-tab-count: 1;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>4 -&nbsp;Target for a future release of the spec</span></span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">We should assign all P1's - if you see any bugs you would like to work on, please assign it to yourself</span></p><p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Calibri; font-size: small;">Some discussion on the support for tag values in Beta.<span style="mso-spacerun: yes;">&nbsp; </span>We will raise this question in the call with prospective beta sites on Thursday.</span></p>
+
== Attendees ==
 +
 
 +
* Bill Schineller
 +
* Gary O'Neall
 +
* Peter Williams
 +
* Kate Stewart
 +
* Marshall Clow
 +
* Phil Koltun
 +
 
 +
== Notes ==
 +
 
 +
Pre-meeting discussion on version management of the specification. Need to work through the remaining issues to get the git version of the spec in sync. After that, we can modify the process to automatically push out the defects.
 +
 
 +
Issues review - please refer to the spreadsheet attached to the minutes. The legend tab describes the priority definitions.
 +
 
 +
Changes in the spreadsheet from the original proposed priorities:
 +
 
 +
587 and 625 should probably be merged
 +
 
 +
617 - leave as priority one since the legal team may require
 +
 
 +
Move 640, 643, 646 to P1 - these will affect the spec being in sync
 +
 
 +
623 - comment field for author of the SPDX document - move to P1 since this is relatively easy
 +
 
 +
Need to add a bug to track the implementation of the xor's for all file hashes to create a unique package signiture
 +
 
 +
Reference this new bug in bug 593 - the solution referenced above will solve this bug as well
 +
 
 +
Bill added rought estimates on the effort for the P1 defects
 +
 
 +
Gary will update bugzilla with all of the priority information from the meeting
 +
 
 +
From this point forward, all submitters of bugs should assign a priority based ont he following critera:
 +
 
 +
1 - Must be resolved for beta
 +
 
 +
2 - Want to resolve for beta, but is a must for the release 1 of the spec (e.g. can be resolved after the start of beta)
 +
 
 +
3 - Want for release 1
 +
 
 +
4 - Target for a future release of the spec
 +
 
 +
We should assign all P1's - if you see any bugs you would like to work on, please assign it to yourself
 +
 
 +
Some discussion on the support for tag values in Beta. We will raise this question in the call with prospective beta sites on Thursday.
 +
 
 +
[[Category:Technical|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 12:56, 6 March 2013

Attendees

  • Bill Schineller
  • Gary O'Neall
  • Peter Williams
  • Kate Stewart
  • Marshall Clow
  • Phil Koltun

Notes

Pre-meeting discussion on version management of the specification. Need to work through the remaining issues to get the git version of the spec in sync. After that, we can modify the process to automatically push out the defects.

Issues review - please refer to the spreadsheet attached to the minutes. The legend tab describes the priority definitions.

Changes in the spreadsheet from the original proposed priorities:

587 and 625 should probably be merged

617 - leave as priority one since the legal team may require

Move 640, 643, 646 to P1 - these will affect the spec being in sync

623 - comment field for author of the SPDX document - move to P1 since this is relatively easy

Need to add a bug to track the implementation of the xor's for all file hashes to create a unique package signiture

Reference this new bug in bug 593 - the solution referenced above will solve this bug as well

Bill added rought estimates on the effort for the P1 defects

Gary will update bugzilla with all of the priority information from the meeting

From this point forward, all submitters of bugs should assign a priority based ont he following critera:

1 - Must be resolved for beta

2 - Want to resolve for beta, but is a must for the release 1 of the spec (e.g. can be resolved after the start of beta)

3 - Want for release 1

4 - Target for a future release of the spec

We should assign all P1's - if you see any bugs you would like to work on, please assign it to yourself

Some discussion on the support for tag values in Beta. We will raise this question in the call with prospective beta sites on Thursday.