General Meeting/Minutes/2011-05-05 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-06T10:59:20Z

Convert to MediaWiki syntax

Podence at 20:11, 17 May 2011

2011-05-17T20:11:09Z

New page

<div style="background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #ffffff; margin: 8px;"><div style="background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #ffffff; margin: 8px;">Administrative Agenda    Attendance: 15     Minutes accepted Technical Team Report - BillGood ProgressOne specific blocking item/for spec and tools. The issue is has to do with set of terms to describe situation where a concluded license is not named. Team had been working with terms such as: None, No Assertion, Not Analyzed, Blank. They are working on a final proposal but are leaning towards two values one indcating that there has been a conclusion that there is no license and one indicating that there is no conclusion one way or the other.Team is asking for some ratification from the legal team, but proceeding on the two value path. Business Team Report - KimBeta kickoffs are scheduled.Final field names are getting merged into the training and tool docs by Kim and Kirsten resepctively.  Legal Team Report - RockettMetadata licensing issue still under discussionTeam is reviewing the need for including change tracking of SPDX docs in the spec. This will not hold up the beta. There was a discussion about how major a requirement this would be, i.e. would it necessarily hold up V1.0 past LinuxCon in August. The general sense from members of the Tech Team (which has been contemplating the issue) was that it would not by itself. Cross Functional Issues – PhilWebsite: A workign group of Kirsten, Pierre and Steve have been reviewing the website for usability. They are recommending the "three big buttons" approach to the home page for folks who are:<ul><li>New to SPDX and want to get up to speed</li><li>Familar and looking for official information on the spec and how to use</li><li>Interested in participating in development of the spec</li></ul>Their other major recommendation was to have drop down menus to give more visibility into the various sections of the website from the home page.There was lots of spirited discussion and opinions, but general agreement on the direction.The team will be developing and circulating mockups for subsequent feedback. Action Items• MartinM- Report back on # of people on respective mailing lists. ONGOING<ul class="ul1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><li><ul><li>spdx: 98</li><li>spdz-biz: 17</li><li>spdx-legal: 23</li><li>spdx-tech: 21</li></ul></li></ul>Attendees<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">Tom Incorvia, Microfocus</li><li class="li2">Gary O'Neall, Source Auditor</li><li class="li2">Jillayne Lovejoy, OpenLogic</li><li class="li2">Michael Herzog, NexB</li><li>Pierre Lapointe, NexB</li><li>Martin Michlmayr, HP</li><li>Bill Schineller, Black Duck Software</li><li>Kim Weins, Open Logic</li><li>Peter Williams, Open Logic</li><li>Mark Gisi, Wind River</li><li>Steve Cropper, Cisco</li></ul></div></div>

← Older revision		Revision as of 10:59, 6 March 2013
Line 1:		Line 1:
−	<p><div style="background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #ffffff; margin: 8px;"><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" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">    Attendance: 15~~<br />    ~~Minutes accepted~~ </p><p class~~=~~"p1" style~~=~~"color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>~~Technical Team Report - Bill~~</strong></p><p class~~=~~"p1" style~~=~~"color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">~~Good Progress~~</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">~~One specific blocking item/for spec and tools. The issue is has to do with set of terms to describe situation where a concluded license is not named. Team had been working with terms such as: None, No Assertion, Not Analyzed, Blank. They are working on a final proposal but are leaning towards two values one indcating that there has been a conclusion that there is no license and one indicating that there is no conclusion one way or the other.~~</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">~~Team is asking for some ratification from the legal team, but proceeding on the two value path.~~</p><p class~~=~~"p1" style~~="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"> </p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong>Business Team Report - Kim~~</strong></p><p class~~=~~"p2" style~~=~~"color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">~~Beta kickoffs are scheduled.~~</p><p class="p2" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">~~Final field names are getting merged into the training and tool docs by Kim and Kirsten resepctively.~~ </p><p class~~=~~"p2" style~~="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"> </p><p class="p2" 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;">~~Metadata licensing issue still under discussion~~</p><p class="p1" style="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;">~~Team is reviewing the need for including change tracking of SPDX docs in the spec. This will not hold up the beta. There was a discussion about how major a requirement this would be, i.e. would it necessarily hold up V1.0 past LinuxCon in August. The general sense from members of the Tech Team (which has been contemplating the issue) was that it would not by itself.~~</p><p class~~=~~"p1" style~~="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"> </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;">~~Website: A workign group of Kirsten, Pierre and Steve have been reviewing the website for usability. They are recommending the "three big buttons" approach to the home page for folks who are:~~</p><ul><li>~~New to SPDX and want to get up to speed~~</li><li>~~Familar and looking for official information on the spec and how to use~~</li><li>~~Interested in participating in development of the spec~~</li></ul><p>~~Their other major recommendation was to have drop down menus to give more visibility into the various sections of the website from the home page.~~</p><p>~~There was lots of spirited discussion and opinions, but general agreement on the direction.~~</p><p>~~The team will be developing and circulating mockups for subsequent feedback.~~</p><p class~~=~~"p1" style~~="color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px;"><strong><br /></strong></p><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;">•~~ 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><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;"><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">~~Tom Incorvia, Microfocus~~</li><li class="li2">~~Gary O'Neall, Source Auditor~~</li><li class="li2">~~Jillayne Lovejoy, OpenLogic~~</li><li class="li2">~~Michael Herzog, NexB~~</li><li>~~Pierre Lapointe, NexB~~</li><li>~~Martin Michlmayr, HP~~</li><li>~~Bill Schineller, Black Duck Software~~</li><li>~~Kim Weins, Open Logic~~</li><li>~~Peter Williams, Open Logic~~</li><li>~~Mark Gisi, Wind River~~</li><li>~~Steve Cropper, Cisco~~</li></ul></div></p></div></p>~~	+	* Attendance: 15
		+	* Minutes accepted
		+
		+	== Technical Team Report - Bill ==
		+
		+	Good Progress
		+
		+	One specific blocking item/for spec and tools. The issue is has to do with set of terms to describe situation where a concluded license is not named. Team had been working with terms such as: None, No Assertion, Not Analyzed, Blank. They are working on a final proposal but are leaning towards two values one indcating that there has been a conclusion that there is no license and one indicating that there is no conclusion one way or the other.
		+
		+	Team is asking for some ratification from the legal team, but proceeding on the two value path.
		+
		+	== Business Team Report - Kim ==
		+
		+	Beta kickoffs are scheduled.
		+
		+	Final field names are getting merged into the training and tool docs by Kim and Kirsten resepctively.
		+
		+	== Legal Team Report - Rockett ==
		+
		+	Metadata licensing issue still under discussion
		+
		+	Team is reviewing the need for including change tracking of SPDX docs in the spec. This will not hold up the beta. There was a discussion about how major a requirement this would be, i.e. would it necessarily hold up V1.0 past LinuxCon in August. The general sense from members of the Tech Team (which has been contemplating the issue) was that it would not by itself.
		+
		+	== Cross Functional Issues – Phil ==
		+
		+	Website: A workign group of Kirsten, Pierre and Steve have been reviewing the website for usability. They are recommending the "three big buttons" approach to the home page for folks who are:
		+
		+	* New to SPDX and want to get up to speed
		+	* Familar and looking for official information on the spec and how to use
		+	* Interested in participating in development of the spec
		+
		+	Their other major recommendation was to have drop down menus to give more visibility into the various sections of the website from the home page.
		+
		+	There was lots of spirited discussion and opinions, but general agreement on the direction.
		+
		+	The team will be developing and circulating mockups for subsequent feedback.
		+
		+	== Action Items ==
		+
		+	* MartinM- Report back on # of people on respective mailing lists. ONGOING
		+	** spdx: 98
		+	** spdz-biz: 17
		+	** spdx-legal: 23
		+	** spdx-tech: 21
		+
		+	== Attendees ==
		+
		+	* Phil Odence, Black Duck Software
		+	* Kirsten Newcomer, Black Duck Software
		+	* Esteban Rockett, Motorola
		+	* Phil Koltun, Linux Foundation
		+	* Tom Incorvia, Microfocus
		+	* Gary O'Neall, Source Auditor
		+	* Jillayne Lovejoy, OpenLogic
		+	* Michael Herzog, NexB
		+	* Pierre Lapointe, NexB
		+	* Martin Michlmayr, HP
		+	* Bill Schineller, Black Duck Software
		+	* Kim Weins, Open Logic
		+	* Peter Williams, Open Logic
		+	* Mark Gisi, Wind River
		+	* Steve Cropper, Cisco
		+
		+	[[Category:General\|Minutes]]
		+	[[Category:Minutes]]