MartinMichlmayr: Convert to MediaWiki syntax

2013-03-06T10:59:20Z

Convert to MediaWiki syntax

Podence at 16:02, 8 January 2013

2013-01-08T16:02:19Z

New page

Attendance: 11Minutes of Nov 1 meeting approved.Lead by Phil OdenceSpecial Report on Open Compliance Summit, Japan - Adam<ul><li>Overview</li><ul><li>End of October. Great Event in General. </li><li>Surprising amount of awareness/interest in SPDX to help with recruitment</li><li>Adam/Mark Gisi (Windriver) pulled together a come all SPDX info meeting to help with recruitment</li><li>Chatham House rules, so sharing but no attribution of comments</li></ul><li>Unscheduled Roundtable</li><ul><li>Pulled together at last minute for end of first day</li><li>12 participants (surprisingly high)</li><li>Lots of interest and awareness. According to Adam, "the concept of SPDX sold itself)</li><li>Continued discussion with a number of participants the next day</li></ul><li>Flavor of discussion/inquiry</li><ul><li>Caution/Concern</li><li>Fear of Unknown</li><li>Language Issue</li><li>Fear of obligation- Worry that signing up is somehow a big commitment</li></ul><li>Concerns</li><ul><li>Language Issue</li><ul><li>More written materials would really help</li><li>English is OK (for written stuff) but looking for "User Manual" level documentation</li><li>The language of the Spec itself is difficult for non-English speakers</li></ul><li>Seems Complicated</li><ul><li>But MarkG was able to make folks understand it's not really</li><li>So a simple, written explanation would really help</li><li>Specific interest in understanding mandatory v. optional; what's the minimum</li><li>Kate had similar experience at U of Nebraska - Concern about complexity that went away after simple explanation.</li><li>So, all this is s general issue, but answer for Japan has to be written doc due to language.</li></ul><li>Obligation</li><ul><li>Concern that if you touch SPDX, you have to overhaul your entire compliance operation</li><li>Need to help folks understand, it's just a format and can fit your processes; it's a spec, not a business method</li></ul></ul><li>Current State</li><ul><li>A number of companies we didn't even know were aware are piloting internally</li><li>Some of these are not even on any mailing lists</li></ul><li>How we can help</li><ul><li>Written, user level doc</li><li>Help people understand how to dip a toe in</li><li>Lots of interest in understanding how to be just a consumer</li><li></li></ul></ul>Business Team Report - Jack<ul><li>Met with Matt and team at U of Nebraska</li><ul><li>Good progress with adding SPDX output capability to FOSSology</li><li>Turned up some issues with the existing tools which Gary is looking into</li><li>Discussion about creating tools for consuming SPDX</li><li>Looking at integrating with Git and Jack envisions an Eclipse-like plug-in framework</li></ul><li>Team understands need for a consumer guide- we need a resource to take that on</li><li>After first of year need to start planning F2F at Collboartion Summit</li><li>Steve Cropper is driving the idea of creating a model supply chain with different participants exchanging and compiling SPDX files.</li></ul>Tech Team Report -Kate <ul><li>Working on Modeling different approaches</li><li>Testing against use cases</li><li>Anticipated slowness due to holiday and as well as Ed's being somewhat tied up</li></ul><div>Legal Team Report - Jilayne<ul><li>Anticipating downtime over holidays.</li><li>Finishing up FSF license list additions to be included in LL 1.17</li><ul><li>Should be by end of year</li><li>Represents 30-40 new licenses</li></ul><li>Recent discussion has been about criteria or "filter" for license adds wiht a small group; needs broader input</li><li>Next meeting will discuss 2013 priorities</li></ul></div>Cross Functional Issues – Phil<ul><li>Web Site Update - Jack</li><ul><li>Framework is in place</li><li>Getting feedback from Core Team</li><li>WE NEED SOME VOLUNTEERS TO WORK ON THE TRANSITION AND ONGOING. HELP</li></ul></ul>Attendees<ul><li>Phil Odence, Black Duck</li><li>Jilayne Lovejoy, OpenLogic</li><li>Kamyar Emami, Protecode</li><li>Gary O'Neill, SourceAuditor</li><li>Kirsten Newcomer, Black Duck</li><li>Jason Buttura, Cisco</li><li>Pierre Laponte, nexB</li><li>Kate Stewart</li><li>Jack Manbeck, TI</li><li>Adam Cohn, Cisco</li><li>Scott Lamons, HP</li></ul>

← Older revision		Revision as of 10:59, 6 March 2013
Line 1:		Line 1:
−	~~<p> </p><p>~~Attendance: 11~~</p><p>~~Minutes of Nov 1 meeting approved.~~</p><p>~~Lead by Phil Odence~~</p><p><strong>~~Special Report on Open Compliance Summit, Japan - Adam~~</strong></p><ul><li>~~Overview~~</li><ul><li>~~End of October. Great Event in General.~~ </li><li>~~Surprising amount of awareness/interest in SPDX to help with recruitment~~</li><li>~~Adam/Mark Gisi (Windriver) pulled together a come all SPDX info meeting~~ ~~to help with recruitment~~</li><li>~~Chatham House rules, so sharing but no attribution of comments~~</li></ul><li>~~Unscheduled Roundtable~~</li><ul><li>~~Pulled together at last minute for end of first day~~</li><li>~~12 participants (surprisingly high)~~</li><li>~~Lots of interest and awareness. According to Adam, "the concept of SPDX sold itself)~~</li><li>~~Continued discussion with a number of participants the next day~~</li></ul><li>~~Flavor of discussion/inquiry~~</li><ul><li>~~Caution/Concern~~</li><li>~~Fear of Unknown~~</li><li>~~Language Issue~~</li><li>~~Fear of obligation- Worry that signing up is somehow a big commitment~~</li></ul><li>~~Concerns~~</li><ul><li>~~Language Issue~~</li><ul><li>~~More written materials would really help~~</li><li>~~English is OK (for written stuff) but looking for "User Manual" level documentation~~</li><li>~~The language of the Spec itself is difficult for non-English speakers~~</li></ul><li>~~Seems Complicated~~</li><ul><li>~~But MarkG was able to make folks understand it's not really~~</li><li>~~So a simple, written explanation would really help~~</li><li>~~Specific interest in understanding mandatory v. optional; what's the minimum~~</li><li>~~Kate had similar experience at U of Nebraska - Concern about complexity that went away after simple explanation.~~</li><li>~~So, all this is s general issue, but answer for Japan has to be written doc due to language.~~</li></ul><li>~~Obligation~~</li><ul><li>~~Concern that if you touch SPDX, you have to overhaul your entire compliance operation~~</li><li>~~Need to help folks understand, it's just a format and can fit your processes; it's a spec, not a business method~~</li></ul></ul><li>~~Current State~~</li><ul><li>~~A number of companies we didn't even know were aware are piloting internally~~</li><li>~~Some of these are not even on any mailing lists~~</li></ul><li>~~How we can help~~</li><ul><li>~~Written, user level doc~~</li><li>~~Help people understand how to dip a toe in~~</li><li>~~Lots of interest in understanding how to be just a consumer~~</li><li></li></ul></ul><p><strong>~~Business Team Report - Jack~~</strong></p><ul><li>~~Met with Matt and team at U of Nebraska~~</li><ul><li>~~Good progress with adding SPDX output capability to FOSSology~~</li><li>~~Turned up some issues with the existing tools which Gary is looking into~~</li><li>~~Discussion about creating tools for consuming SPDX~~</li><li>~~Looking at integrating with Git and Jack envisions an Eclipse-like plug-in framework~~</li></ul><li>~~Team understands need for a consumer guide- we need a resource to take that on~~</li><li>~~After first of year need to start planning F2F at Collboartion Summit~~</li><li>~~Steve Cropper is driving the idea of creating a model supply chain with different participants exchanging and compiling SPDX files.~~</li></ul><p><strong>~~Tech Team Report -Kate~~ </strong></p><ul><li>~~Working on Modeling different approaches~~</li><li>~~Testing against use cases~~</li><li>~~Anticipated slowness due to holiday and as well as Ed's being somewhat tied up~~</li></ul><div><p><strong>~~Legal Team Report - Jilayne~~</strong></p><ul><li>~~Anticipating downtime over holidays.~~</li><li>~~Finishing up FSF license list additions to be included in LL 1.17~~</li><ul><li>~~Should be by end of year~~</li><li>~~Represents 30-40 new licenses~~</li></ul><li>~~Recent discussion has been about criteria or "filter" for license adds wiht a small group; needs broader input~~</li><li>~~Next meeting will discuss 2013 priorities~~</li></ul></div><p><strong>~~Cross Functional Issues – Phil~~</strong></p><ul><li>~~Web Site Update - Jack~~</li><ul><li>~~Framework is in place~~</li><li>~~Getting feedback from Core Team~~</li><li>~~WE NEED SOME VOLUNTEERS TO WORK ON THE TRANSITION AND ONGOING. HELP~~</li></ul></ul><p class~~=~~"p1"><strong>~~Attendees~~</strong></p><ul><li>~~Phil Odence, Black Duck~~</li><li>~~Jilayne Lovejoy, OpenLogic~~</li><li>~~Kamyar Emami, Protecode~~</li><li>~~Gary O'Neill, SourceAuditor~~</li><li>~~Kirsten Newcomer, Black Duck~~</li><li>~~Jason Buttura, Cisco~~</li><li>~~Pierre Laponte, nexB~~</li><li>~~Kate Stewart~~</li><li>~~Jack Manbeck, TI~~</li><li>~~Adam Cohn, Cisco~~</li><li>~~Scott Lamons, HP~~</li></ul><p> </p>~~	+	* Attendance: 11
		+	* Minutes of Nov 1 meeting approved.
		+	* Lead by Phil Odence
		+
		+	== Special Report on Open Compliance Summit, Japan - Adam ==
		+
		+	* Overview
		+	** End of October. Great Event in General.
		+	** Surprising amount of awareness/interest in SPDX to help with recruitment
		+	** Adam/Mark Gisi (Windriver) pulled together a come all SPDX info meeting to help with recruitment
		+	** Chatham House rules, so sharing but no attribution of comments
		+	* Unscheduled Roundtable
		+	** Pulled together at last minute for end of first day
		+	** 12 participants (surprisingly high)
		+	** Lots of interest and awareness. According to Adam, "the concept of SPDX sold itself)
		+	** Continued discussion with a number of participants the next day
		+	* Flavor of discussion/inquiry
		+	** Caution/Concern
		+	** Fear of Unknown
		+	** Language Issue
		+	** Fear of obligation- Worry that signing up is somehow a big commitment
		+	* Concerns
		+	** Language Issue
		+	*** More written materials would really help
		+	*** English is OK (for written stuff) but looking for "User Manual" level documentation
		+	*** The language of the Spec itself is difficult for non-English speakers
		+	** Seems Complicated
		+	*** But MarkG was able to make folks understand it's not really
		+	*** So a simple, written explanation would really help
		+	*** Specific interest in understanding mandatory v. optional; what's the minimum
		+	*** Kate had similar experience at U of Nebraska - Concern about complexity that went away after simple explanation.
		+	*** So, all this is s general issue, but answer for Japan has to be written doc due to language.
		+	** Obligation
		+	*** Concern that if you touch SPDX, you have to overhaul your entire compliance operation
		+	*** Need to help folks understand, it's just a format and can fit your processes; it's a spec, not a business method
		+	* Current State
		+	** A number of companies we didn't even know were aware are piloting internally
		+	** Some of these are not even on any mailing lists
		+	* How we can help
		+	** Written, user level doc
		+	** Help people understand how to dip a toe in
		+	** Lots of interest in understanding how to be just a consumer
		+	**
		+
		+	== Business Team Report - Jack ==
		+
		+	* Met with Matt and team at U of Nebraska
		+	** Good progress with adding SPDX output capability to FOSSology
		+	** Turned up some issues with the existing tools which Gary is looking into
		+	** Discussion about creating tools for consuming SPDX
		+	** Looking at integrating with Git and Jack envisions an Eclipse-like plug-in framework
		+	* Team understands need for a consumer guide- we need a resource to take that on
		+	* After first of year need to start planning F2F at Collboartion Summit
		+	* Steve Cropper is driving the idea of creating a model supply chain with different participants exchanging and compiling SPDX files.
		+
		+	== Tech Team Report - Kate ==
		+
		+	* Working on Modeling different approaches
		+	* Testing against use cases
		+	* Anticipated slowness due to holiday and as well as Ed's being somewhat tied up
		+
		+	== Legal Team Report - Jilayne ==
		+
		+	* Anticipating downtime over holidays.
		+	* Finishing up FSF license list additions to be included in LL 1.17
		+	** Should be by end of year
		+	** Represents 30-40 new licenses
		+	* Recent discussion has been about criteria or "filter" for license adds wiht a small group; needs broader input
		+	* Next meeting will discuss 2013 priorities
		+
		+	== Cross Functional Issues – Phil ==
		+
		+	* Web Site Update - Jack
		+	** Framework is in place
		+	** Getting feedback from Core Team
		+	** WE NEED SOME VOLUNTEERS TO WORK ON THE TRANSITION AND ONGOING. HELP
		+
		+	== Attendees ==
		+
		+	* Phil Odence, Black Duck
		+	* Jilayne Lovejoy, OpenLogic
		+	* Kamyar Emami, Protecode
		+	* Gary O'Neill, SourceAuditor
		+	* Kirsten Newcomer, Black Duck
		+	* Jason Buttura, Cisco
		+	* Pierre Laponte, nexB
		+	* Kate Stewart
		+	* Jack Manbeck, TI
		+	* Adam Cohn, Cisco
		+	* Scott Lamons, HP
		+
		+	[[Category:General\|Minutes]]
		+	[[Category:Minutes]]

General Meeting/Minutes/2012-11-29 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

Podence at 16:02, 8 January 2013