date:20160804

RE: Net-SNMP License

2016-08-04 Thread Tom Incorvia

Hi Sam,

This conjunctive license is somewhat common.  SPDX does other conjunctive 
licenses such as the Python-2.0 License.

For my purposes (associating a license with a project), I typically have a 
single field to populate that is the declared license – I don’t have a spot for 
an expression.

A workaround for my need would be to create a license named “BSD-3-CLAUSE AND 
MIT-CMU”.

Anyway, let me know what the legal team decides.

Thanks,

Tom

Tom Incorvia; tom.incor...@microfocus.com; 
O: (512) 340-1336; M: (215) 500 8838; Shoretel (Internal): X27015; Time Zone: 
US Central (UK – 6 Hours)


From: Sam Ellis [mailto:sam.el...@arm.com]
Sent: Thursday, August 04, 2016 11:13 AM
To: Dennis Clark ; Tom Incorvia 
Cc: Spdx-legal@lists.spdx.org
Subject: RE: Net-SNMP License

The licenses in this file that look to me as if could be fully described with 
the expression: BSD-3-CLAUSE AND MIT-CMU. Are we seeing licenses in this file 
that are neither of these two, or are there other reasons that the combination 
deserves a separate identifier?

From: 
spdx-legal-boun...@lists.spdx.org 
[mailto:spdx-legal-boun...@lists.spdx.org] On Behalf Of Dennis Clark
Sent: 04 August 2016 16:49
To: Tom Incorvia
Cc: Spdx-legal@lists.spdx.org
Subject: Re: Net-SNMP License

Hi Tom and SPDX Legal Team,
Request for the Net-SNMP License added to

https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681
up at the top.  You can't miss it.
To be discussed in the legal team call on August 4, 2016.

Regards,
Dennis Clark
nexB Inc.

On Mon, Aug 1, 2016 at 7:04 PM, Tom Incorvia 
> wrote:
Hello SPDX Legal,

Would you please consider including the Net-SNMP license as an SPDX-vetted 
license?  Here is a reference in Dejacode:  
https://enterprise.dejacode.com/license_library/Demo/net-snmp/.  In terms of 
use in the wild, 273,000 hits on the text Net-SNMP and License; 3,500 hits on 
the specific string “Net-SNMP license”.

Thanks,

Tom

Tom Incorvia; tom.incor...@microfocus.com; 
O: (512) 340-1336; M: (215) 500 
8838; Shoretel (Internal): X27015; Time Zone: US 
Central (UK – 6 Hours)



___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

Click 
here
 to report this email as spam.
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

RE: call Thursday

2016-08-04 Thread Alan Tse

https://www.uberconference.com/spdxteam

Alan D. Tse
Associate General Counsel
Western Digital Corporation
3355 Michelson Dr., Suite 100, Irvine, CA 92612
T:  949-672-7759
F:  949-672-6604

-Original Message-
From: spdx-legal-boun...@lists.spdx.org 
[mailto:spdx-legal-boun...@lists.spdx.org] On Behalf Of Vidal, Thomas
Sent: Thursday, August 04, 2016 10:12 AM
To: Jilayne Lovejoy
Cc: SPDX-legal
Subject: Re: call Thursday

Do I have the wrong call-in information because nobody else is on the line I'm 
on.


On Aug 3, 2016, at 10:46 PM, J Lovejoy 
> wrote:

Hi all,

Reminder we have a legal team call Thursday - same bat time, same bat channel.  
http://wiki.spdx.org/view/Legal_Team

Agenda as follows:

1) any Business As Usual items - new license request, request for markup, etc. 
(see email threads, Dennis to lead :)

2) go over any flagged for review licenses in XML files

NOTE - last meeting we came up with a timeline for completing the review and 
conversation to XML format for the SPDX License List.  I've cut and pasted that 
from the meeting minutes below to make sure everyone remembers and we stay on 
track. :)

Jilayne




SPDX License List XML files - what needs to be done to get to release stage:

  1.  finish main review of licenses so that all can merged and other clean-up, 
which also includes: (finish by end of August)
 *   opening and closing < SPDX > tag are not always same case - should be 
all upper-case
 *   discussion on what to do about some licenses that were flagged as 
having self-referring numbering - will save this data even tho not complete, 
just in case we want to go that route later; can be an attribute that is not 
"seen" at this point; don't merge these yet --> Kris will add attribute and 
merge.
 *   for those that are tagged as "requires acknowledgement" - reminder to 
not merge --> Kris to deal with those all at once
 *   Kris to do another pass to do some clean-up, including body tag to be 
removed
  2.  exceptions need to be added to XML - Kris will add to Github for review, 
will have own pull requests (Note from Gary: tools don't care whether in same 
or different directory)
  3.  same situation for deprecated licenses - Gary's point that need XML for 
tools (Gary and Kris were going back and forth on whether own XML files needed 
for this or not - to check on outcome of this)
  4.  review various webpages for updating --> Alan to do this (have first pass 
for review by group by mid-August)
 *   License matching guidelines page
 *   License list overview page; add info/explanation about XML tags (with 
input from Kris and Gary for tags)
  5.  define a new process for License List, i.e., how to request a new 
license, what kind of pull requests we want, underlying process etc. --> 
Jilayne to do this (end of August for review by group)
 *   check with Kate re: moving license list to Github primary (instead of 
LF Git and mirrored to Github)
  6.  Gary to update spdx-tools for new XML format (including website 
generation) - for 5 different formats (mid- to late- September)
 *   Gary already has basic structure in place; time frame such that he 
could do testing in mid- to end-September
 *   end-of September would aim to have preview of website so we can check 
it, probably then one more pass at tools, etc.
  7.  need new tool to take text of new license and convert to XML file (to do 
so by hand is a bit tedious). Will still need human review before finalizing. 
(doesn't have to be done for release stage)


SPDX Legal Team co-lead
opensou...@jilayne.com


___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal




***CONFIDENTIALITY NOTICE***
This email contains confidential information which may also be legally 
privileged and which is intended only for the use of the recipient(s) named 
above. If you are not the intended recipient, you are hereby notified that 
forwarding or copying of this email, or the taking of any action in reliance on 
its contents, may be strictly prohibited. If you have received this email in 
error, please notify us immediately by reply email and delete this message from 
your inbox.

___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal
Western Digital Corporation (and its subsidiaries) E-mail Confidentiality 
Notice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or 
legally privileged information of WDC and/or its affiliates, and are intended 
solely for the use of the individual or entity to which they are addressed. If 
you are not the intended recipient, any disclosure, copying, distribution or 
any action taken or omitted to

RE: call Thursday

2016-08-04 Thread Sam Ellis

I am dialed in using: 857-216-2871 / pin 38633.

> -Original Message-
> From: spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal-
> boun...@lists.spdx.org] On Behalf Of Vidal, Thomas
> Sent: 04 August 2016 18:12
> To: Jilayne Lovejoy
> Cc: SPDX-legal
> Subject: Re: call Thursday
>
> Do I have the wrong call-in information because nobody else is on the line
> I'm on.
>
>
> On Aug 3, 2016, at 10:46 PM, J Lovejoy
> > wrote:
>
> Hi all,
>
> Reminder we have a legal team call Thursday - same bat time, same bat
> channel.  http://wiki.spdx.org/view/Legal_Team
>
> Agenda as follows:
>
> 1) any Business As Usual items - new license request, request for markup,
> etc. (see email threads, Dennis to lead :)
>
> 2) go over any flagged for review licenses in XML files
>
> NOTE - last meeting we came up with a timeline for completing the review
> and conversation to XML format for the SPDX License List.  I've cut and
> pasted that from the meeting minutes below to make sure everyone
> remembers and we stay on track... :)
>
> Jilayne
>
>
>
>
> SPDX License List XML files - what needs to be done to get to release stage:
>
>   1.  finish main review of licenses so that all can merged and other 
> clean-up,
> which also includes: (finish by end of August)
>  *   opening and closing < SPDX > tag are not always same case - should be
> all upper-case
>  *   discussion on what to do about some licenses that were flagged as
> having self-referring numbering - will save this data even tho not complete,
> just in case we want to go that route later; can be an attribute that is not
> "seen" at this point; don't merge these yet --> Kris will add attribute and
> merge.
>  *   for those that are tagged as "requires acknowledgement" - reminder to
> not merge --> Kris to deal with those all at once
>  *   Kris to do another pass to do some clean-up, including body tag to be
> removed
>   2.  exceptions need to be added to XML - Kris will add to Github for review,
> will have own pull requests (Note from Gary: tools don't care whether in
> same or different directory)
>   3.  same situation for deprecated licenses - Gary's point that need XML for
> tools (Gary and Kris were going back and forth on whether own XML files
> needed for this or not - to check on outcome of this)
>   4.  review various webpages for updating --> Alan to do this (have first 
> pass
> for review by group by mid-August)
>  *   License matching guidelines page
>  *   License list overview page; add info/explanation about XML tags (with
> input from Kris and Gary for tags)
>   5.  define a new process for License List, i.e., how to request a new 
> license,
> what kind of pull requests we want, underlying process etc. --> Jilayne to do
> this (end of August for review by group)
>  *   check with Kate re: moving license list to Github primary (instead 
> of LF
> Git and mirrored to Github)
>   6.  Gary to update spdx-tools for new XML format (including website
> generation) - for 5 different formats (mid- to late- September)
>  *   Gary already has basic structure in place; time frame such that he 
> could
> do testing in mid- to end-September
>  *   end-of September would aim to have preview of website so we can
> check it, probably then one more pass at tools, etc.
>   7.  need new tool to take text of new license and convert to XML file (to do
> so by hand is a bit tedious). Will still need human review before finalizing.
> (doesn't have to be done for release stage)
>
>
> SPDX Legal Team co-lead
> opensou...@jilayne.com
>
>
> ___
> Spdx-legal mailing list
> Spdx-legal@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx-legal
>
>
> 
>
> ***CONFIDENTIALITY NOTICE***
> This email contains confidential information which may also be legally
> privileged and which is intended only for the use of the recipient(s) named
> above. If you are not the intended recipient, you are hereby notified that
> forwarding or copying of this email, or the taking of any action in reliance 
> on
> its contents, may be strictly prohibited. If you have received this email in
> error, please notify us immediately by reply email and delete this message
> from your inbox.
>
> ___
> Spdx-legal mailing list
> Spdx-legal@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx-legal

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

___
Spdx-legal mailing list

Re: call Thursday

2016-08-04 Thread Vidal, Thomas

Do I have the wrong call-in information because nobody else is on the line I’m 
on.


On Aug 3, 2016, at 10:46 PM, J Lovejoy 
> wrote:

Hi all,

Reminder we have a legal team call Thursday - same bat time, same bat channel.  
http://wiki.spdx.org/view/Legal_Team

Agenda as follows:

1) any Business As Usual items - new license request, request for markup, etc. 
(see email threads, Dennis to lead :)

2) go over any flagged for review licenses in XML files

NOTE - last meeting we came up with a timeline for completing the review and 
conversation to XML format for the SPDX License List.  I’ve cut and pasted that 
from the meeting minutes below to make sure everyone remembers and we stay on 
track… :)

Jilayne




SPDX License List XML files - what needs to be done to get to release stage:

  1.  finish main review of licenses so that all can merged and other clean-up, 
which also includes: (finish by end of August)
 *   opening and closing < SPDX > tag are not always same case - should be 
all upper-case
 *   discussion on what to do about some licenses that were flagged as 
having self-referring numbering - will save this data even tho not complete, 
just in case we want to go that route later; can be an attribute that is not 
"seen" at this point; don't merge these yet --> Kris will add attribute and 
merge.
 *   for those that are tagged as "requires acknowledgement" - reminder to 
not merge --> Kris to deal with those all at once
 *   Kris to do another pass to do some clean-up, including body tag to be 
removed
  2.  exceptions need to be added to XML - Kris will add to Github for review, 
will have own pull requests (Note from Gary: tools don't care whether in same 
or different directory)
  3.  same situation for deprecated licenses - Gary's point that need XML for 
tools (Gary and Kris were going back and forth on whether own XML files needed 
for this or not - to check on outcome of this)
  4.  review various webpages for updating --> Alan to do this (have first pass 
for review by group by mid-August)
 *   License matching guidelines page
 *   License list overview page; add info/explanation about XML tags (with 
input from Kris and Gary for tags)
  5.  define a new process for License List, i.e., how to request a new 
license, what kind of pull requests we want, underlying process etc. --> 
Jilayne to do this (end of August for review by group)
 *   check with Kate re: moving license list to Github primary (instead of 
LF Git and mirrored to Github)
  6.  Gary to update spdx-tools for new XML format (including website 
generation) - for 5 different formats (mid- to late- September)
 *   Gary already has basic structure in place; time frame such that he 
could do testing in mid- to end-September
 *   end-of September would aim to have preview of website so we can check 
it, probably then one more pass at tools, etc.
  7.  need new tool to take text of new license and convert to XML file (to do 
so by hand is a bit tedious). Will still need human review before finalizing. 
(doesn't have to be done for release stage)


SPDX Legal Team co-lead
opensou...@jilayne.com


___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal




***CONFIDENTIALITY NOTICE***
This email contains confidential information which may also be legally 
privileged and which is intended only for the use of the recipient(s) named 
above. If you are not the intended recipient, you are hereby notified that 
forwarding or copying of this email, or the taking of any action in reliance on 
its contents, may be strictly prohibited. If you have received this email in 
error, please notify us immediately by reply email and delete this message from 
your inbox.

___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

wrong encoding in two licenses

2016-08-04 Thread Zavras, Alexios

Hi Gary and Jilayne,

I can't make it to the SPDX Legal call today, but I just want to report that 
two licenses in the git repo are stored with wrong encoding (i.e., they're not 
in utf-8).
I'm talking about OSL-2.1.txt and RPSL-1.0.txt in git.spdx.org/license-list.git.

Running
recode iso8859-1..utf8 OSL-2.1.txt
recode iso8859-1..utf8 RPSL-1.0.txt
should fix the issue.


-- zvr -

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

Re: Net-SNMP License

2016-08-04 Thread Dennis Clark

Hi Tom and SPDX Legal Team,

Request for the Net-SNMP License added to

https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681


up at the top.  You can't miss it.

To be discussed in the legal team call on August 4, 2016.

Regards,
Dennis Clark
nexB Inc.


On Mon, Aug 1, 2016 at 7:04 PM, Tom Incorvia 
wrote:

> Hello SPDX Legal,
>
>
>
> Would you please consider including the Net-SNMP license as an SPDX-vetted
> license?  Here is a reference in Dejacode:  https://enterprise.dejacode.
> com/license_library/Demo/net-snmp/.  In terms of use in the wild, 273,000
> hits on the text Net-SNMP and License; 3,500 hits on the specific string
> “Net-SNMP license”.
>
>
>
> Thanks,
>
>
>
> Tom
>
>
>
> *Tom Incorvia; *tom.incor...@microfocus.com; *O: (512) 340-1336
> <%28512%29%20340-1336>; M: (215) 500 8838 <%28215%29%20500%208838>;
> Shoretel (Internal): X27015; Time Zone: US Central (UK – 6 Hours)*
>
>
>
>
>
> ___
> Spdx-legal mailing list
> Spdx-legal@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx-legal
>
>
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

RE: Net-SNMP License

RE: call Thursday

RE: call Thursday

Re: call Thursday

wrong encoding in two licenses

Re: Net-SNMP License

6 matches

Site Navigation

Mail list logo

Footer information