k Gisi | Wind River | Director, Open Source & Software Assurance
Tel (510) 749-2016 | Fax (510) 749-4552
-Original Message-
From: m...@juniper.net [mailto:m...@juniper.net]
Sent: Saturday, December 24, 2016 7:57 PM
To: brad.edmond...@gmail.com
Cc: Gisi, Mark; spdx-t...@lists.spdx.org; SPDX-leg
Brad Edmondson writes:
> Thanks Mark,
>
> FWIW I believe that Mark Baushke looked at the current version of the
> net-SNMP package during our call today and found that its constituent parts
> all pointed to a single top-level license file that contained the license
> stack at issue. So while you
license stack v. using license expressions
Mark,
Would appreciate being looped into the package licensing discussions. I wrote
the current npm package licensing metadata spec, as well as the validating
implementation.
Very grateful for all the prior and continuing work of folks here on SPDX
Thanks Mark,
FWIW I believe that Mark Baushke looked at the current version of the
net-SNMP package during our call today and found that its constituent parts
all pointed to a single top-level license file that contained the license
stack at issue. So while your point is well-taken that the stack
Mark,
Would appreciate being looped into the package licensing discussions. I
wrote the current npm package licensing metadata spec, as well as the
validating implementation.
Very grateful for all the prior and continuing work of folks here on
SPDX. Mindful that the JavaScript community has used
http://net-snmp.sourceforge.net/about/license.html is not a license but a
license notice file. License expressions were initially designed to represent
the licensing of a single file whether it be a source file or a binary library
or program. They each represent a complete atomic integrated (de
