Difference between revisions of "Technical Team/Minutes/2012-09-04"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
<p><span style="font-family: Calibri; font-size: medium;">Minutes 9/4/2012</span></p><p><span style="font-family: Calibri; font-size: medium;">Attendees:</span></p><p><span style="font-family: Calibri; font-size: medium;">Gary O’Neall,&nbsp;</span><span style="font-family: Calibri; font-size: medium;">Bill Schineller,&nbsp;</span><span style="font-family: Calibri; font-size: medium;">Kate Stewart,&nbsp;</span><span style="font-family: Calibri; font-size: medium;">Jack Manbeck, Michael Herzog,&nbsp;</span><span style="font-family: Calibri; font-size: medium;">Ed Warnicke,&nbsp;</span><span style="font-family: Calibri; font-size: medium;">Peter Williams,&nbsp;</span><span style="font-family: Calibri; font-size: medium;">Kirsten Newcomer, Marshall Clow</span></p><p>&nbsp;</p><p><span style="font-family: Calibri; font-size: medium;">Agenda:</span></p><ul><li><span style="font-family: Calibri; font-size: medium;">Re-cap of Linux Con discussions</span></li><li><span style="font-family: Calibri; font-size: medium;">Discussion of recent blog post expressing confusion about SPDX</span></li><li><span style="font-family: Calibri; font-size: medium;">Ed Warnicke proposal / demo of 'Watermarking' &nbsp;</span></li></ul><div><span style="font-family: Calibri; font-size: medium;">Re-cap of Linux Con discussions</span></div><div><ul><li><span style="font-family: Calibri; font-size: medium;">Kate: 1.1 spec draft and rdf got in sync, releaseable</span></li><li><span style="font-family: Calibri; font-size: medium;">Fossology intent to provide Agent to produce 1.1 SPDX announced</span></li><li><span style="font-family: Calibri; font-size: medium;">Deferred modeling discussions while at Linux Con</span></li><li><span style="font-family: Calibri; font-size: medium;">Ed W. socialized idea of 'Watermarking' approach</span></li></ul><div><span style="font-family: Calibri; font-size: medium;"><br /></span></div><div><span style="font-family: Calibri; font-size: medium;">Discussion sparked by recent blog post:</span></div><div><ul><li><span style="font-family: Calibri; font-size: medium;">http://www.murrayc.com/blog/permalink/2012/08/31/generating-spdx-files-with-licensecheck/</span></li><li><span style="font-family: Calibri; font-size: medium;">Jack: idea for validation suite - future agenda item?</span></li><li><span style="font-family: Calibri; font-size: medium;">Kate: need to update examples - volunteer to do 'time' package</span></li><li><span style="font-family: Calibri; font-size: medium;">Kate: idea for "plug fest" at next Linux Collab summit - encourage those who support/produce SPDX to do so for same package and compare results?</span></li></ul><div><span style="font-family: Calibri; font-size: medium;">Watermarking Proposal / Demo (Ed Warnicke)</span></div><div><ul><li><span style="font-family: Calibri; font-size: medium;">Source files and their compiled output are the "leaves" of hierarchies of copyrightable 'things', so can SPDX specify a watermarking approach to put licensing information&nbsp;</span><span style="font-family: Calibri; font-size: medium;">directly in source files?</span></li><li><span style="font-family: Calibri; font-size: medium;">Reqts: Machine-readable, close to leaf, flows through hierarchy</span></li><li><span style="font-family: Calibri; font-size: medium;">Demonstrated for the C language an spdx.h defining a macro SPDX_INFO. &nbsp;Including this header, then compiling results in an introspectable compiled output</span></li></ul><span style="font-family: Calibri; font-size: medium;">Reactions to demo:&nbsp;</span><br /><ul><li><span style="font-family: Calibri; font-size: medium;">Peter - "ship it"? !</span></li><li><span style="font-family: Calibri; font-size: medium;">Ed: our 'one chance' to get it right with upstream providers, don't rush it</span></li><li><span style="font-family: Calibri; font-size: medium;">Michael: let's decouple the spec from its 'enabling technologies"</span></li><li><span style="font-family: Calibri; font-size: medium;">Issues: concern about the SIZE compiling strings into object code adds to the distros.&nbsp;</span></li><li><span style="font-family: Calibri; font-size: medium;">Let's determine what's 'acceptable' size bloat (none!...) and think about other languages too</span></li></ul></div></div><div><span style="font-family: Calibri; font-size: medium;"><br /></span></div></div><div><span style="font-family: Calibri; font-size: medium;"><br /></span></div><p>&nbsp;</p>
+
== Attendees ==
 +
 
 +
* Gary O’Neall
 +
* Bill Schineller
 +
* Kate Stewart
 +
* Jack Manbeck
 +
* Michael Herzog
 +
* Ed Warnicke
 +
* Peter Williams
 +
* Kirsten Newcomer
 +
* Marshall Clow
 +
 
 +
== Agenda ==
 +
 
 +
* Re-cap of Linux Con discussions
 +
* Discussion of recent blog post expressing confusion about SPDX
 +
* Ed Warnicke proposal / demo of 'Watermarking'
 +
 
 +
== Re-cap of Linux Con discussions ==
 +
 
 +
* Kate: 1.1 spec draft and rdf got in sync, releaseable
 +
* Fossology intent to provide Agent to produce 1.1 SPDX announced
 +
* Deferred modeling discussions while at Linux Con
 +
* Ed W. socialized idea of 'Watermarking' approach
 +
 
 +
== Discussion sparked by recent blog post ==
 +
 
 +
* http://www.murrayc.com/blog/permalink/2012/08/31/generating-spdx-files-with-licensecheck/
 +
* Jack: idea for validation suite - future agenda item?
 +
* Kate: need to update examples - volunteer to do 'time' package
 +
* Kate: idea for "plug fest" at next Linux Collab summit - encourage those who support/produce SPDX to do so for same package and compare results?
 +
 
 +
== Watermarking Proposal / Demo (Ed Warnicke) ==
 +
 
 +
* Source files and their compiled output are the "leaves" of hierarchies of copyrightable 'things', so can SPDX specify a watermarking approach to put licensing information directly in source files?
 +
* Reqts: Machine-readable, close to leaf, flows through hierarchy
 +
* Demonstrated for the C language an spdx.h defining a macro SPDX_INFO. Including this header, then compiling results in an introspectable compiled output
 +
 
 +
== Reactions to demo ==
 +
 
 +
* Peter - "ship it"? !
 +
* Ed: our 'one chance' to get it right with upstream providers, don't rush it
 +
* Michael: let's decouple the spec from its 'enabling technologies"
 +
* Issues: concern about the SIZE compiling strings into object code adds to the distros.
 +
* Let's determine what's 'acceptable' size bloat (none!...) and think about other languages too
 +
 
 +
[[Category:Technical|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 13:40, 6 March 2013

Attendees

  • Gary O’Neall
  • Bill Schineller
  • Kate Stewart
  • Jack Manbeck
  • Michael Herzog
  • Ed Warnicke
  • Peter Williams
  • Kirsten Newcomer
  • Marshall Clow

Agenda

  • Re-cap of Linux Con discussions
  • Discussion of recent blog post expressing confusion about SPDX
  • Ed Warnicke proposal / demo of 'Watermarking'

Re-cap of Linux Con discussions

  • Kate: 1.1 spec draft and rdf got in sync, releaseable
  • Fossology intent to provide Agent to produce 1.1 SPDX announced
  • Deferred modeling discussions while at Linux Con
  • Ed W. socialized idea of 'Watermarking' approach

Discussion sparked by recent blog post

Watermarking Proposal / Demo (Ed Warnicke)

  • Source files and their compiled output are the "leaves" of hierarchies of copyrightable 'things', so can SPDX specify a watermarking approach to put licensing information directly in source files?
  • Reqts: Machine-readable, close to leaf, flows through hierarchy
  • Demonstrated for the C language an spdx.h defining a macro SPDX_INFO. Including this header, then compiling results in an introspectable compiled output

Reactions to demo

  • Peter - "ship it"? !
  • Ed: our 'one chance' to get it right with upstream providers, don't rush it
  • Michael: let's decouple the spec from its 'enabling technologies"
  • Issues: concern about the SIZE compiling strings into object code adds to the distros.
  • Let's determine what's 'acceptable' size bloat (none!...) and think about other languages too