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

Difference between revisions of "General Meeting/Minutes/2011-03-24"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
<p>&nbsp;</p><div style="background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #ffffff; margin: 8px;"><p style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Administrative Agenda</strong></p><p class="p1">&nbsp;&nbsp;&nbsp; Attendance: 15<br />&nbsp;&nbsp; &nbsp;Minutes accepted&nbsp;<span style="color: #0000ee;"><span style="text-decoration: underline;">http://www.spdx.org/wiki/20110224-general-meeting-minutes</span></span></p><p class="p1" style="padding-left: 90px;"><span style="color: #0000ee;"><span style="text-decoration: underline;">&nbsp;</span></span><span style="color: #0000ee;"><span style="text-decoration: underline;">http://www.spdx.org/wiki/20110311-general-meeting-minutes</span></span></p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Technical Team Report - Kate</strong></p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">After a great deal of effort, the team has converged on a consistent set of field names which will by synch'ed with all forms of spec shortly.</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">There are still a couple of areas of open issues which are dependent on the Legal Team, most having to do with who created the SPDX file.</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">Kate will be starting up a wiki page with an agenda for the upcoming Face to Face; participants should feel free to provide input.</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Business Team Report - Phil</strong></p><p class="p2" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">Beta training materials are not complete, but are in motion and should be fine for beta.</p><p class="p2" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">In the last meeting there was a lot of discussion about a process for requesting/evaluating/adding new licenses to the standard list. See <a href="http://www.spdx.org/wiki/business-team-meeting-agendaminutes-20110317">last Business Team meeting's minutes</a> for details.</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Legal Team Report - Rockett</strong></p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">SPDX Tool/Template Licensing- Done, we'll be using Apache 2.0</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">Metadata Licensing</p><ul><li>Stil active discussion delving in aspects of:<ul><li>Confidentiality</li><li>Trace ability and change logging</li><li>Copyright</li></ul></li><li>Rockett and Kate are having an offline discussion to pull it all together.</li></ul>Templatizing (defining what insubstantial variants are OK for a match to a standard license)<br /><div style="background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #ffffff; margin: 8px;"><ul><li>Proposal being reviewed within Legal Team</li><li>Ready for presentation to other teams in the next 1-2 months</li></ul></div><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">&nbsp;</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Cross Functional Issues – Phil</strong></p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>&nbsp;</strong>Collaboration Summit&nbsp;</p><ul class="ul2"><li class="li3"><span class="s2">Agenda has been posted:&nbsp;<a href="http://events.linuxfoundation.org/events/collaboration-summit/schedule"><span class="s3">http://events.linuxfoundation.org/events/collaboration-summit/schedule</span></a></span><ul class="ul3"><li class="li2">Tech Team meeting Thursday afternoon</li><li class="li2">Business Team meeting Friday,&nbsp;</li><li class="li2">1/2 day track on legal related issues Thursday morning</li></ul></li><li class="li2">anyone planning to attend should request an invite via the Linux Collaboration web site. (see link above)</li><li class="li2">Please RSVP for Face to Face sessions on <a href="http://www.spdx.org/wiki/linux-collaboration-summit">Wiki page</a></li></ul>Discussion about how to handle "Newbee" question that come in on lists&nbsp;<ul class="ul2"><li class="li2">Asking Business Team to take on providing guidelines to other teams and general&nbsp;</li><li class="li2">General feeling that we need a process to<ul><li class="li2">Respond in 24 hours</li><li class="li2">Provide answers that are consistent with "party line" but at the same time helpful</li><li class="li2">Ensure that good questions / answers get captured in FAQ</li></ul></li></ul><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Action Items</strong></p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">Most of the action items belong with the Teams. So, in addition to statusing, we will dispatch them to the respective teams and will not continue to track in this meeting. Action items for this meeting will be cross functional.</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">• Kate- Beta collateral: Examples in XML and spreadsheet form. PENDING&nbsp;</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">• MartinM- Report back on # of people on respective mailing lists. ONGOING</p><ul class="ul1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><li>&nbsp;<ul><li>spdx: 98</li><li>spdz-biz: 17</li><li>spdx-legal: 23</li><li>spdx-tech: 21</li></ul></li></ul><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">Phil O. - Capture a list of who will be at face to face meeting - DONE</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Attendees</strong></p><ul class="ul1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><li class="li2">Phil Odence, Black Duck Software</li><li class="li2">Kirsten Newcomer, Black Duck Software</li><li class="li2">Esteban Rockett, Motorola</li><li class="li2">Phil Koltun, Linux Foundation</li><li class="li2">Kate Stewart, Canonical</li><li class="li2">Tom Incorvia, Microfocus</li><li class="li2">Gary O'Neall, Source Auditor</li><li class="li2">Jillayne Lovejoy, OpenLogic</li><li class="li2">Karen Copenhaver, LF/Choate</li><li class="li2">Michael Herzog, NexB</li><li>Pierre Lapointe, NexB</li><li>Kamal Hassin, Protecode</li><li>Jilayne Lovejoy, Open Logic</li><li>Martin Michlmayr, HP</li><li>Bill Schineller, Black Duck Software</li></ul></div><p>&nbsp;</p>
+
* Attendance: 15
 +
* Minutes accepted [[General_Meeting/Minutes/2011-02-24]] and [[General_Meeting/Minutes/2011-03-11]]
 +
 
 +
== Technical Team Report - Kate ==
 +
 
 +
After a great deal of effort, the team has converged on a consistent set of field names which will by synch'ed with all forms of spec shortly.
 +
 
 +
There are still a couple of areas of open issues which are dependent on the Legal Team, most having to do with who created the SPDX file.
 +
 
 +
Kate will be starting up a wiki page with an agenda for the upcoming Face to Face; participants should feel free to provide input.
 +
 
 +
== Business Team Report - Phil ==
 +
 
 +
Beta training materials are not complete, but are in motion and should be fine for beta.
 +
 
 +
In the last meeting there was a lot of discussion about a process for requesting/evaluating/adding new licenses to the standard list. See [[Business_Team/Minutes/2011-03-17|last Business Team meeting's minutes]] for details.
 +
 
 +
== Legal Team Report - Rockett ==
 +
 
 +
SPDX Tool/Template Licensing- Done, we'll be using Apache 2.0
 +
 
 +
Metadata Licensing
 +
 
 +
* Stil active discussion delving in aspects of:
 +
** Confidentiality
 +
** Trace ability and change logging
 +
** Copyright
 +
* Rockett and Kate are having an offline discussion to pull it all together.
 +
 
 +
Templatizing (defining what insubstantial variants are OK for a match to a standard license)
 +
 
 +
* Proposal being reviewed within Legal Team
 +
* Ready for presentation to other teams in the next 1-2 months
 +
 
 +
== Cross Functional Issues – Phil ==
 +
 
 +
Collaboration Summit:
 +
 
 +
* Agenda has been posted: http://events.linuxfoundation.org/events/collaboration-summit/schedule
 +
** Tech Team meeting Thursday afternoon
 +
** Business Team meeting Friday,
 +
** 1/2 day track on legal related issues Thursday morning
 +
* anyone planning to attend should request an invite via the Linux Collaboration web site. (see link above)
 +
* Please RSVP for Face to Face sessions on [[Old/Linux_Collaboration_Summit_2011|Wiki page]]
 +
 
 +
Discussion about how to handle "Newbee" question that come in on lists
 +
 
 +
* Asking Business Team to take on providing guidelines to other teams and general
 +
* General feeling that we need a process to
 +
** Respond in 24 hours
 +
** Provide answers that are consistent with "party line" but at the same time helpful
 +
** Ensure that good questions / answers get captured in FAQ
 +
 
 +
== Action Items ==
 +
 
 +
Most of the action items belong with the Teams. So, in addition to statusing, we will dispatch them to the respective teams and will not continue to track in this meeting. Action items for this meeting will be cross functional.
 +
 
 +
* Kate- Beta collateral: Examples in XML and spreadsheet form. PENDING
 +
* MartinM- Report back on # of people on respective mailing lists. ONGOING
 +
** ** spdx: 98
 +
** spdz-biz: 17
 +
** spdx-legal: 23
 +
** spdx-tech: 21
 +
* Phil O. - Capture a list of who will be at face to face meeting - DONE
 +
 
 +
== Attendees ==
 +
 
 +
* Phil Odence, Black Duck Software
 +
* Kirsten Newcomer, Black Duck Software
 +
* Esteban Rockett, Motorola
 +
* Phil Koltun, Linux Foundation
 +
* Kate Stewart, Canonical
 +
* Tom Incorvia, Microfocus
 +
* Gary O'Neall, Source Auditor
 +
* Jillayne Lovejoy, OpenLogic
 +
* Karen Copenhaver, LF/Choate
 +
* Michael Herzog, NexB
 +
* Pierre Lapointe, NexB
 +
* Kamal Hassin, Protecode
 +
* Jilayne Lovejoy, Open Logic
 +
* Martin Michlmayr, HP
 +
* Bill Schineller, Black Duck Software
 +
 
 +
[[Category:General|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 11:44, 6 March 2013

Technical Team Report - Kate

After a great deal of effort, the team has converged on a consistent set of field names which will by synch'ed with all forms of spec shortly.

There are still a couple of areas of open issues which are dependent on the Legal Team, most having to do with who created the SPDX file.

Kate will be starting up a wiki page with an agenda for the upcoming Face to Face; participants should feel free to provide input.

Business Team Report - Phil

Beta training materials are not complete, but are in motion and should be fine for beta.

In the last meeting there was a lot of discussion about a process for requesting/evaluating/adding new licenses to the standard list. See last Business Team meeting's minutes for details.

Legal Team Report - Rockett

SPDX Tool/Template Licensing- Done, we'll be using Apache 2.0

Metadata Licensing

  • Stil active discussion delving in aspects of:
    • Confidentiality
    • Trace ability and change logging
    • Copyright
  • Rockett and Kate are having an offline discussion to pull it all together.

Templatizing (defining what insubstantial variants are OK for a match to a standard license)

  • Proposal being reviewed within Legal Team
  • Ready for presentation to other teams in the next 1-2 months

Cross Functional Issues – Phil

Collaboration Summit:

Discussion about how to handle "Newbee" question that come in on lists

  • Asking Business Team to take on providing guidelines to other teams and general
  • General feeling that we need a process to
    • Respond in 24 hours
    • Provide answers that are consistent with "party line" but at the same time helpful
    • Ensure that good questions / answers get captured in FAQ

Action Items

Most of the action items belong with the Teams. So, in addition to statusing, we will dispatch them to the respective teams and will not continue to track in this meeting. Action items for this meeting will be cross functional.

  • Kate- Beta collateral: Examples in XML and spreadsheet form. PENDING
  • MartinM- Report back on # of people on respective mailing lists. ONGOING
    • ** spdx: 98
    • spdz-biz: 17
    • spdx-legal: 23
    • spdx-tech: 21
  • Phil O. - Capture a list of who will be at face to face meeting - DONE

Attendees

  • Phil Odence, Black Duck Software
  • Kirsten Newcomer, Black Duck Software
  • Esteban Rockett, Motorola
  • Phil Koltun, Linux Foundation
  • Kate Stewart, Canonical
  • Tom Incorvia, Microfocus
  • Gary O'Neall, Source Auditor
  • Jillayne Lovejoy, OpenLogic
  • Karen Copenhaver, LF/Choate
  • Michael Herzog, NexB
  • Pierre Lapointe, NexB
  • Kamal Hassin, Protecode
  • Jilayne Lovejoy, Open Logic
  • Martin Michlmayr, HP
  • Bill Schineller, Black Duck Software