MartinMichlmayr: Convert to MediaWiki syntax

2013-03-05T17:40:41Z

Convert to MediaWiki syntax

Jlovejoy at 00:06, 27 January 2012

2012-01-27T00:06:10Z

New page

SPDX Legal Workstream Meeting Minutes - 25 January 2012In attendance:<ul><li>Jilayne Lovejoy, OpenLogic</li><li>Tom Incoriva, Microfocus</li><li>Mark Gisi, Windriver</li><li>Phil Odence, Black Duck</li><li>Peter Williams, OpenLogic</li><li>Mansour Ghomeshi, Motorola</li><li>Esteban Rockett, Motorola</li><li>Michael Herzog, NexB</li></ul>AGENDAI - update on CC-0 Preamble<ul><li>changed "copyrightable material" to "copyrightable work" in second and third paragraphs. </li></ul>ACTION ITEM: Jilayne to update this on SPDX wiki page with preambleII - Review draft License List Match Guidelines (templatizing)went through guideline document by section;  change focus from normalizing on guidelines - to just offering guidelines and let tools makers implementWhite Space<ul><li>if one sentence moves to another paragraph, it would be treated the same;  does this matter, can we find a use case where this would matter? could treat paragraph break as different than other whitespace breaks</li><li>seems okay to treat all white space the same; leave as is in guidelines</li></ul>Capitalization - okay as isPuncuation - okay as isBullets and Numbering<ul><li>as to bullets/numbers, just say ignore these</li><li>this would require flagging this text within licenses that have references </li><li>can we ignore the bullet/number/letter, but not "lose" that info (so you still see it later), otherwise it would be unreadable - really internal details for tools anyway</li><li>can we just start here and see how it goes?  Licenses that have internal references are less likely to have changes with numbering anyway</li><li>start here, and modify later if needed</li></ul>Varietal Word Spelling<ul><li>decision to re-word description re: British/American spelling to just equivalent spelling since geography is a non-issue</li><li>are there any words where there may be 3 different spelling? list only has two columns</li><ul><li>Can't think of any example, but would be same - not </li></ul><li>what about if a word is misspelled?  - slippery slope to try and deal with this; if misspelled consistently in license, then will just match on misspelling;  </li><ul><li>Can watch to see if this comes up/examples</li></ul></ul>Copyright Symbol<ul><li>okay as is - just say all three options are equivalent</li></ul>Copyright notice<ul><li>copyright notice line guideline:  is the copyright notice at the top of BSD really part of the license?</li><li>License is something that should be fixed; where does license notice fall in this?</li><li>Copyright notice applies to file; but license is the actual text, not the notice (which may say you have to reproduce the copyright notice)</li><li>Should we then strip the copyright notice out altogether in our license list?</li><li>Copyright notice for license itself is distinct, so keep - but most cases it would not be part of license itself</li><li>How does this impact our license list - e.g. "GPL or later" where there isn't really an "or later" license, but is really just a notice</li><li>Then raises question of how to deal with preambles and epilogue?</li></ul>→ next time pick up here with discussion and may tie into conversation re: headersACTION ITEM: update License List Match Guidelines and post on wiki page on spdx.org (current page posted is outdated)

← Older revision		Revision as of 17:40, 5 March 2013
Line 1:		Line 1:
−	~~<p><strong>SPDX Legal Workstream Meeting Minutes - 25 January 2012</strong></p><p>In attendance:</p><ul><li>~~Jilayne Lovejoy, OpenLogic~~</li><li>~~Tom Incoriva, Microfocus~~</li><li>~~Mark Gisi, Windriver~~</li><li>~~Phil Odence, Black Duck~~</li><li>~~Peter Williams, OpenLogic~~</li><li>~~Mansour Ghomeshi, Motorola~~</li><li>~~Esteban Rockett, Motorola~~</li><li>~~Michael Herzog, NexB~~</li></ul><p><strong>AGENDA</strong></p><p><span style~~=~~"text-decoration: underline;">I -~~ update on CC-0 Preamble~~</span></p><ul><li>~~changed "copyrightable material" to "copyrightable work" in second and third paragraphs.~~ </li></ul><p>~~ACTION ITEM: Jilayne to update this on SPDX wiki page with preamble~~</p><p><span style~~=~~"text-decoration: underline;">II -~~ Review draft License List Match Guidelines (templatizing)~~</span></p><p>~~went through guideline document by section~~; &nbsp~~;change focus from normalizing on guidelines - to just offering guidelines and let tools makers implement~~</p><p>~~White Space~~</p><ul><li>~~if one sentence moves to another paragraph, it would be treated the same~~;&nbsp~~; does this matter, can we find a use case where this would matter?~~ ~~could treat paragraph break as different than other whitespace breaks~~</li><li>~~seems okay to treat all white space the same; leave as is in guidelines~~</li></ul><p>~~Capitalization - okay as is~~</p><p>~~Puncuation - okay as is~~</p><p>~~Bullets and Numbering~~</p><ul><li>~~as to bullets/numbers, just say ignore these~~</li><li>~~this would require flagging this text within licenses that have references~~ </li><li>~~can we ignore the bullet/number/letter, but not "lose" that info (so you still see it later), otherwise it would be unreadable - really internal details for tools anyway~~</li><li>~~can we just start here and see how it goes? ~~ ~~Licenses that have internal references are less likely to have changes with numbering anyway~~</li><li>~~start here, and modify later if needed~~</li></ul><p>~~Varietal Word Spelling~~</p><ul><li>~~decision to re-word description re: British/American spelling to just equivalent spelling since geography is a non-issue~~</li><li>~~are there any words where there may be 3 different spelling? list only has two columns~~</li><ul><li>~~Can't think of any example, but would be same - not~~ </li></ul><li>~~what about if a word is misspelled? ~~ ~~- slippery slope to try and deal with this; if misspelled consistently in license, then will just match on misspelling; ~~ </li><ul><li>~~Can watch to see if this comes up/examples~~</li></ul></ul><p>~~Copyright Symbol~~</p><ul><li>~~okay as is - just say all three options are equivalent~~</li></ul><p>~~Copyright notice~~</p><ul><li>~~copyright notice line guideline: ~~ ~~is the copyright notice at the top of BSD really part of the license?~~</li><li>~~License is something that should be fixed; where does license notice fall in this?~~</li><li>~~Copyright notice applies to file; but license is the actual text, not the notice (which may say you have to reproduce the copyright notice)~~</li><li>~~Should we then strip the copyright notice out altogether in our license list?~~</li><li>~~Copyright notice for license itself is distinct, so keep - but most cases it would not be part of license itself~~</li><li>~~How does this impact our license list - e.g. "GPL or later" where there isn't really an "or later" license, but is really just a notice~~</li><li>~~Then raises question of how to deal with preambles and epilogue?~~</li></ul><p>~~→ next time pick up here with discussion and may tie into conversation re: headers~~</p><p>~~ACTION ITEM: update License List Match Guidelines and post on wiki page on spdx.org (current page posted is outdated)~~</p><p style="text-indent~~: ~~-28px;"><span style="font-family~~: ~~Calibri;"><span style="font-size: 15px;"><br /></span></span></p>~~	+	== Attendees ==
		+
		+	* Jilayne Lovejoy, OpenLogic
		+	* Tom Incoriva, Microfocus
		+	* Mark Gisi, Windriver
		+	* Phil Odence, Black Duck
		+	* Peter Williams, OpenLogic
		+	* Mansour Ghomeshi, Motorola
		+	* Esteban Rockett, Motorola
		+	* Michael Herzog, NexB
		+
		+	== update on CC-0 Preamble ==
		+
		+	* changed "copyrightable material" to "copyrightable work" in second and third paragraphs.
		+
		+	ACTION ITEM: Jilayne to update this on SPDX wiki page with preamble
		+
		+	== Review draft License List Match Guidelines (templatizing) ==
		+
		+	went through guideline document by section; change focus from normalizing on guidelines - to just offering guidelines and let tools makers implement
		+
		+	White Space
		+
		+	* if one sentence moves to another paragraph, it would be treated the same; does this matter, can we find a use case where this would matter? could treat paragraph break as different than other whitespace breaks
		+	* seems okay to treat all white space the same; leave as is in guidelines
		+
		+	Capitalization - okay as is
		+
		+	Puncuation - okay as is
		+
		+	Bullets and Numbering
		+
		+	* as to bullets/numbers, just say ignore these
		+	* this would require flagging this text within licenses that have references
		+	* can we ignore the bullet/number/letter, but not "lose" that info (so you still see it later), otherwise it would be unreadable - really internal details for tools anyway
		+	* can we just start here and see how it goes? Licenses that have internal references are less likely to have changes with numbering anyway
		+	* start here, and modify later if needed
		+
		+	Varietal Word Spelling
		+
		+	* decision to re-word description re: British/American spelling to just equivalent spelling since geography is a non-issue
		+	* are there any words where there may be 3 different spelling? list only has two columns
		+	** Can't think of any example, but would be same - not
		+	* what about if a word is misspelled? - slippery slope to try and deal with this; if misspelled consistently in license, then will just match on misspelling;
		+	** Can watch to see if this comes up/examples
		+
		+	Copyright Symbol
		+
		+	* okay as is - just say all three options are equivalent
		+
		+	Copyright notice
		+
		+	* copyright notice line guideline: is the copyright notice at the top of BSD really part of the license?
		+	* License is something that should be fixed; where does license notice fall in this?
		+	* Copyright notice applies to file; but license is the actual text, not the notice (which may say you have to reproduce the copyright notice)
		+	* Should we then strip the copyright notice out altogether in our license list?
		+	* Copyright notice for license itself is distinct, so keep - but most cases it would not be part of license itself
		+	* How does this impact our license list - e.g. "GPL or later" where there isn't really an "or later" license, but is really just a notice
		+	* Then raises question of how to deal with preambles and epilogue?
		+
		+	→ next time pick up here with discussion and may tie into conversation re: headers
		+
		+	ACTION ITEM: update License List Match Guidelines and post on wiki page on spdx.org (current page posted is outdated)
		+
		+	[[Category:Legal\|Minutes]]
		+	[[Category:Minutes]]

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

MartinMichlmayr: Convert to MediaWiki syntax

Jlovejoy at 00:06, 27 January 2012