MartinMichlmayr: Convert to MediaWiki syntax

2013-03-05T18:08:03Z

Convert to MediaWiki syntax

Jlovejoy at 16:33, 2 May 2012

2012-05-02T16:33:11Z

New page

SPDX Legal Work Group Meeting Minutes - 1 May 2012Attendees:<ul><li>David Wheeler</li><li>Mark Gisi</li><li>Michael Herzog</li><li>Peter Williams</li><li>Paul Madick</li><li>Tom Incorvia</li><li>Kevin Fleming</li><li>Adam Cohn</li></ul>1) Discuss status of Adding Licenses process<ul><li>decided to post proposal from 4/18 meeting on website and send to general mailing list for review and mention during tomorrow's General Meeting call (JILAYNE  to do)</li></ul>2) somewhat related and mildly circuitous discussion regarding license headers/notices, the standard header field on the license list<ul><li>suggestion floated to simply drop this field from the license list</li><li>another suggestion to change to "yes/no" - as in, yes, the license includes a suggested standard header, or no, it does not.  rationale being that where there is a standard header, it is merely cut and pasted from part of the license text anyway, so this is duplicitous</li><li>in meantime, may need to clarify/revise description of this field here - http://www.spdx.org/wiki/spdx-license-list</li><li>value of having standard header field is for identification purposes, an additional way to definitively identify it's Foo License besides matching on the entire license text (this is probably inline with license author's intent of including it!)</li><li>all agreed there are many "non-standard" headers in the wild, but trying to track those or create that list is another project that we can't do (at least not right now)</li></ul>3) statements on vision for: a) SPDX work groups, b) legal group specifically, and c) license list more specifically.  Adam proposed the following as to the first - did not have time to discuss, but would like to do so and then distribute to other groups.  need to draft items for b and c.Adam's proposed text:"To enable any party in the software supply chain, from the original author to the final end user, to accurately communicate and understand the licensing information for any piece of copyrightable material that such party may create, alter, pass on, or receive, and to make such information available in a consistent, understandable, and re-usable fashion, with the aim of facilitating license and other policy compliance."TASKS FOR NEXT CALL:<ol><li>Review Adam's proposed text to discuss on next call - ALL</li><li>draft vision/goals statement for legal group, distribute to group, so we can discuss on next call - PAUL</li><li>draft vision/goals statement for license list, distribute to group, so we can discuss on next call  - JILAYNE</li><li>review current to-do list (see: http://www.spdx.org/wiki/legal-team-current-issues-last-updated-april-6 ) and note anything that's missing (need to go over and prioritize on subsequent call) - ALL</li></ol>

← Older revision		Revision as of 18:08, 5 March 2013
Line 1:		Line 1:
−	~~<p><strong>SPDX Legal Work Group Meeting Minutes - 1 May 2012</strong></p><p>~~Attendees~~:</p><ul><li>~~David Wheeler~~</li><li>~~Mark Gisi~~</li><li>~~Michael Herzog~~</li><li>~~Peter Williams~~</li><li>~~Paul Madick~~</li><li>~~Tom Incorvia~~</li><li>~~Kevin Fleming~~</li><li>~~Adam Cohn~~</li></ul><p>~~1) Discuss status of Adding Licenses ~~process</p><ul><li>~~decided to post proposal from 4/18 meeting on website and send to general mailing list for review and mention during tomorrow's General Meeting call (JILAYNE ~~ ~~to do)~~</li></ul><p>~~2) somewhat related and mildly circuitous discussion regarding license headers/notices, the standard header field on the license list~~</p><ul><li>~~suggestion floated to simply drop this field from the license list~~</li><li>~~another suggestion to change to "yes/no" - as in, yes, the license includes a suggested standard header, or no, it does not. ~~ ~~rationale being that where there is a standard header, it is merely cut and pasted from part of the license text anyway, so this is duplicitous~~</li><li>~~in meantime, may need to clarify/revise description of this field here ~~- http://www.spdx.org/wiki/spdx-license-list</li><li>~~value of having standard header field is for identification purposes, an additional way to definitively identify it's Foo License besides matching on the entire license text (this is probably inline with license author's intent of including it!)~~</li><li>~~all agreed there are many "non-standard" headers in the wild, but trying to track those or create that list is another project that we can't do (at least not right now)~~</li></ul><p>~~3) statements on vision for: a) SPDX work groups, b) legal group specifically, and c) license list more specifically. ~~ ~~Adam proposed the following as to the first - did not have time to discuss, but would like to do so and then distribute to other groups. ~~ ~~need to draft items for b and c.~~</p><p>~~Adam's proposed text:~~</p><p class="p1"><em>~~"To enable any party in the software supply chain, from the original author to the final end user, to accurately communicate and understand the licensing information for any piece of copyrightable material that such party may create, alter, pass on, or receive, and to make such information available in a consistent, understandable, and re-usable fashion, with the aim of facilitating license and other policy compliance."~~</em></p><p class="p1"><strong>~~TASKS FOR NEXT CALL:~~</strong></p><ol><li>~~Review Adam's proposed text to discuss on next call - ALL~~</li><li>~~draft vision/goals statement for legal group, distribute to group, so we can discuss on next call - PAUL~~</li><li>~~draft vision/goals statement for license list,~~ ~~distribute to group, so we can discuss on next call~~  ~~- JILAYNE~~</li><li>~~review current to-do list (see: ~~http:~~/~~/www.spdx.org/wiki/legal-team-current-issues-last-updated-april-6~~ ) and note anything that's missing (need to go over and prioritize on subsequent call) - ALL~~</li></ol>~~	+	== Attendees ==
		+
		+	* David Wheeler
		+	* Mark Gisi
		+	* Michael Herzog
		+	* Peter Williams
		+	* Paul Madick
		+	* Tom Incorvia
		+	* Kevin Fleming
		+	* Adam Cohn
		+
		+	1) Discuss status of Adding Licenses proces
		+
		+	* decided to post proposal from 4/18 meeting on website and send to general mailing list for review and mention during tomorrow's General Meeting call (JILAYNE to do)
		+
		+	2) somewhat related and mildly circuitous discussion regarding license headers/notices, the standard header field on the license list
		+
		+	* suggestion floated to simply drop this field from the license list
		+	* another suggestion to change to "yes/no" - as in, yes, the license includes a suggested standard header, or no, it does not. rationale being that where there is a standard header, it is merely cut and pasted from part of the license text anyway, so this is duplicitous
		+	* in meantime, may need to clarify/revise description of this field here
		+	* value of having standard header field is for identification purposes, an additional way to definitively identify it's Foo License besides matching on the entire license text (this is probably inline with license author's intent of including it!)
		+	* all agreed there are many "non-standard" headers in the wild, but trying to track those or create that list is another project that we can't do (at least not right now)
		+
		+	3) statements on vision for: a) SPDX work groups, b) legal group specifically, and c) license list more specifically. Adam proposed the following as to the first - did not have time to discuss, but would like to do so and then distribute to other groups. need to draft items for b and c.
		+
		+	Adam's proposed text:
		+
		+	''"To enable any party in the software supply chain, from the original author to the final end user, to accurately communicate and understand the licensing information for any piece of copyrightable material that such party may create, alter, pass on, or receive, and to make such information available in a consistent, understandable, and re-usable fashion, with the aim of facilitating license and other policy compliance."''
		+
		+	'''TASKS FOR NEXT CALL:'''
		+
		+	# Review Adam's proposed text to discuss on next call - ALL
		+	# draft vision/goals statement for legal group, distribute to group, so we can discuss on next call - PAUL
		+	# draft vision/goals statement for license list, distribute to group, so we can discuss on next call - JILAYNE
		+	# review current to-do list (see: [[Legal_Team/Current_Projects_and_Issues]]) and note anything that's missing (need to go over and prioritize on subsequent call) - ALL
		+
		+	[[Category:Legal\|Minutes]]
		+	[[Category:Minutes]]

Legal Team/Minutes/2012-05-01 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

Jlovejoy at 16:33, 2 May 2012