Re: [new license request] The Open Group License

Hi Felicitas, thanks very much for your email. I've created an issue for your message in the repo at https://github.com/spdx/license-list-XML/issues/1026. Feel free to follow along and weigh in there as it is reviewed by the SPDX legal team participants. Best, Steve On Tue, May 12, 2020 at 8:31

[new license request] The Open Group License

Hi, while adding identifiers to licenses used in the BSP (note: i am a legal trainee, so wording may not be technical perfect), i stumbled upon the The Open Group License, which does not have an identifier yet. It is used in: xorg-app-iceauth, xorg-app-rgb, xorg-app-xauth, xorg- app-xdm,

Re: New License Request: Valgrind Client License

Hi Stefan, thanks for reaching out. It looks to me like this one is equivalent (for SPDX matching purposes) to bzip2-1.0.6 which is currently on the license list [1]. So I don't expect that this would lead to a new entry on the list, unless there are substantive differences under the SPDX matching

New License Request: CERN Open Hardware License v1.2

1. Provide a proposed Full Name for the license or exception. CERN Open Hardware License v1.2 2. Provide a proposed Short Identifier. CERN-OHL-1.2 3. Provide a functioning url reference to the license or exception text, either from the author or a community recognized source.

Re: New License Request: +CAL Software License

Thanks Sally, really interesting. I've created an issue here[1] where the SPDX legal team will assess the license, but in order to best make that assessment, we have a few questions in the meantime: 1. Can you point us to some examples of projects or works that are using this license? We try to

Re: New License Request: TU-Berlin

Hi ARW, Thank you for these license requests. They have been approved here and will be added to the next release of the SPDX License List. Best, Brad -- Brad Edmondson, *Esq.* 512-673-8782 | brad.edmond...@gmail.com On Fri, Apr 6, 2018 at

Re: New License Request: TU-Berlin

Hi Legal Team, For the record, the proposed license is currently recognized by ScanCode as tu-berlin. https://github.com/nexB/scancode-toolkit/blob/4e63a6775a895fdec5a3a53f96013399fa34b1b7/src/licensedcode/data/licenses/tu-berlin.yml Regards, Dennis Clark On Thu, Apr 5, 2018 at 6:09 PM, A.

New License Request: TU-Berlin

Proposed Full Name: Technische Universitaet Berlin License Permissive Technische Universitaet Berlin License [???] Proposed Short Identifier: TU-Berlin-1.0 TU-Berlin-2.0 URL references: 1.0: http://alpha.tmit.bme.hu/pub/audio/gsm-1.0/copyrigh

Re: New License Request: Linux-OpenIB

On Thu, Mar 22, 2018 at 11:47 AM, J Lovejoy wrote: > ok, great, that’s what we merged already. done :) > > On Mar 22, 2018, at 12:21 PM, Dennis Clark wrote: > > I think Linux-OpenIB is a perfect short identifier for this license. > > On Thu, Mar 22, 2018

Re: New License Request: Linux-OpenIB

ok, great, that’s what we merged already. done :) > On Mar 22, 2018, at 12:21 PM, Dennis Clark wrote: > > I think Linux-OpenIB is a perfect short identifier for this license. > > Regards, > Dennis > > On Thu, Mar 22, 2018 at 11:15 AM, J Lovejoy

Re: New License Request: Linux-OpenIB

On Thu, Mar 22, 2018 at 1:06 PM, Philippe Ombredanne wrote: > Kate: > > Thank you for this excellent background and research! > > On Thu, Mar 22, 2018 at 8:50 AM, Kate Stewart > wrote: > > > Provide a proposed Full Name for the license or

Re: New License Request: Linux-OpenIB

oh crikey, naming is so hard! the rationale for using “Linux-OpenIB” was to differentiate from the reality that OpenIB.org uses the real and full matching BSD-2-Clause - so some kind of such differentiation is good. Happy to add references to other examples in the Notes

Re: New License Request: Linux-OpenIB

Kate: Thank you for this excellent background and research! On Thu, Mar 22, 2018 at 8:50 AM, Kate Stewart wrote: > Provide a proposed Full Name for the license or exception > > Linux Kernel Variant of OpenIB.org license > > Provide a proposed Short Identifier. > >

Re: New License Request: Linux-OpenIB

This was moved to github https://github.com/spdx/license-list-XML/issues/620 On Thu, Mar 22, 2018 at 10:50 AM, Kate Stewart wrote: > > *Background:In 2004 an industry association called Open Infiniband or > "OpenIB" was founded to consolidate and upstream into

New License Request: Linux-OpenIB

*Background:In 2004 an industry association called Open Infiniband or "OpenIB" was founded to consolidate and upstream into Linux what is today drivers/infiniband.That group of companies mutually agreed to use a "dual GPL and BSD license" scheme and the membership agreement obligated the member

Re: New License Request: FB-Patents-2.0

On Thu, Aug 10, 2017 at 10:53:47AM -0400, Wheeler, David A wrote: > Based on feedback from W. Trevor King (thank you!!), here is round 2. Cross-linking round 1 [1]. > Here I propose this Facebook rider as a new *license* instead of > separate license *exception*… I had proposed the name >

New License Request: FB-Patents-2.0

Based on feedback from W. Trevor King (thank you!!), here is round 2. Here I propose this Facebook rider as a new *license* instead of separate license *exception*. The proposal is below; I'm including a modified "INTRODUCTION" to give context. INTRODUCTION: Many Facebook projects, including the

Re: New License Request: The Glasgow Haskell Compiler License

riginal Message - From: "W. Trevor King" <wk...@tremily.us> To: "David A Wheeler" <dwhee...@ida.org> Cc: "Richard Fontana" <rfont...@redhat.com>, "J Lovejoy" <opensou...@jilayne.com>, "SPDX-legal" <spdx-legal@lists.spdx.org&

RE: New License Request: The Glasgow Haskell Compiler License

Richard Fontana: > The way I read the matching guidelines this license does not actually match > to BSD-3-Clause, even though it obviously should. I think the problem is > that I am reading the matching guidelines more literally than they may be > intended to be read, but given that this is

Re: New License Request: The Glasgow Haskell Compiler License

To: "David Wheeler" <dwhee...@ida.org> Cc: "SPDX-legal" <spdx-legal@lists.spdx.org>, "David Parrish" <daveparr...@tutanota.com> Sent: Thursday, June 1, 2017 12:02:03 AM Subject: Re: New License Request: The Glasgow Haskell Compiler License H

Re: New License Request: The Glasgow Haskell Compiler License

Hi David (P), David W is right - this is the same license as BSD-3-Clause. The only difference is in the “replaceable” text (i.e., the names) as per the license matching guidelines and which you can see visually in the red text on the license webpage here:

RE: New License Request: The Glasgow Haskell Compiler License

David Parrish: > 1. Provide a proposed Full Name for the license or exception. > The Glasgow Haskell Compiler License > 2. Provide a proposed Short Identifier. > ghc >3. Provide a functioning url reference to the license or exception text, >either from the author or a community recognized source.

New License Request: The Glasgow Haskell Compiler License

1. Provide a proposed Full Name for the license or exception. The Glasgow Haskell Compiler License 2. Provide a proposed Short Identifier. ghc 3. Provide a functioning url reference to the license or exception text, either from the author or a community recognized source.

Re: New License Request: Zero Clause BSD

Hi Everyone, I have added BSD-0-Clause to our Licenses under Consideration worksheet (worksheet Row 11): https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 I am afraid that our format does not really handle the extensive discussion

RE: New License Request: Zero Clause BSD

@lists.spdx.org Subject: New License Request: Zero Clause BSD Submission Requirements: Provide a proposed Full Name for the license or exception. BSD 0-clause Public Domain Equivalent License. Provide a proposed Short Identifier. BSD-0-Clause Provide a functioning url reference

New License Request

Hi, I would like to propose the addition of SGI’s GLX license to the SPDX license list, as follows: Short name: SGI-GLX-1.0 Long name: SGI GLX Public License v1.0 URL: http://fedoraproject.org/wiki/Licensing/GLX_Public_License License specimen: attached to this email OSI approved: no Evidence

Re: New License Request

Hi Maciej, As per discussion on the SPDX Legal Call today, this license will be added to the next version of the SPDX License List. Thanks for your request! Cheers, Jilayne SPDX Legal Team co-lead opensou...@jilayne.com On Apr 1, 2014, at 4:07 AM, Maciej Wereski

Re: New License Request

Proposed license accepted in v1.20. Because of significant differences in license terms, it was decided by the SPDX legal team to call this license the Caldera License (Caldera) rather than BSD 4-clause Caldera License (BSD-4-Clause-Caldera), even though the text is generally structured in a

New License Request

Dear Ladies and Gentleman, I'm not sure weather this should be considered BSD 4-Clause, so I've decided to submit request. Full Name of License: BSD 4-clause Caldera License License Identifier (aka SPDX Short Identifier): BSD-4-Clause-Caldera Source/url: http://www.lemis.com/grog/UNIX/

RE: New license request

] Sent: Wednesday, March 05, 2014 8:17 PM To: Tom Incorvia Cc: Oliver Fendt; SPDX-legal Subject: Re: New license request Hi Oliver, Tom, Just to clarify on Tom's points - the normal process is to review based on the OSD as a starting point, although for a license to be on the SPDX License List

AW: New license request

...@microfocus.com] Gesendet: Donnerstag, 6. März 2014 13:39 An: J Lovejoy Cc: Fendt, Oliver; SPDX-legal Betreff: RE: New license request Hi Jilayne, Thanks for pointing out the possible flexibility in the license list; Oliver, thanks again for taking the time to submit this license. I'll

Re: AW: New license request

@lists.spdx.org spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Subject: AW: New license request Hi Jilayne, hi Tom Thank you for the feedback. I will try to make it to be in the telco. This is a very interesting discussion. From a practical point of view we need a standard to provide

AW: AW: New license request

@lists.spdx.org spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Subject: AW: New license request Hi Jilayne, hi Tom Thank you for the feedback. I will try to make it to be in the telco. This is a very interesting discussion. From a practical point of view we need a standard to provide

Re: AW: AW: New license request

: AW: New license request We have definitely gone beyond the OSI list and even beyond the OSI definition, but have tried, for now, to keep it to open source-like licenses. See http://spdx.org/spdx-license-list/license-list-overview for a complete explanation of how we decide to include

New license request

Hi all, We have found a license which is currently not available in the SPDX license list and I did not find it in the list licenses under consideration, due to this I want to request that it will be included in the SPDX license list. Please find below the required information for inclusion.

Re: New License Request

On 05/03/2014 11:56 AM, J Lovejoy wrote: If you have any other questions, please do not hesitate to ask! That's fine. "BSD-3-Clause" is a perfectly good answer. Thanks everyone for all the help! -- Mike Milinkovich

RE: New license request

-boun...@lists.spdx.org] On Behalf Of Fendt, Oliver Sent: Wednesday, March 05, 2014 10:31 AM To: spdx-legal@lists.spdx.org Subject: New license request Hi all, We have found a license which is currently not available in the SPDX license list and I did not find it in the list licenses under

Re: New license request

@lists.spdx.org Subject: New license request Hi all, We have found a license which is currently not available in the SPDX license list and I did not find it in the list “licenses under consideration”, due to this I want to request that it will be included in the SPDX license list. Please find

Re: New license request

Oliver, Legal Team, New license request added to http://wiki.spdx.org/view/Legal_Team/License_List/Licenses_Under_Consideration#Licenses_Under_Consideration Regards, Dennis Clark On Mon, Feb 10, 2014 at 7:34 AM, Fendt, Oliver oliver.fe...@siemens.comwrote: Hi all, We have found a license

New License Request

Hello, I would like to submit a new license request. The information is given below: 1. Full Name for the license: Artistic License (Perl) 1.0 2. Proposed License Short Identifier: Artistic-Perl-1.0 3. URL reference to the license text: http://dev.perl.org/licenses

RE: New License Request

6850 -Original Message- From: spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal-boun...@lists.spdx.org] On Behalf Of Till Jaeger Sent: Friday, March 01, 2013 3:09 AM To: Jilayne Lovejoy Cc: SPDX-legal Subject: Re: New License Request Hi Jilayne, Thanks for your quick evaluation. Just

Re: New License Request

Thanks Till! We will begin review of this license on the next SPDX Legal call, which is this Thursday. Cheers, Jilayne Lovejoy SPDX Legal Team co-lead Corporate Counsel | OpenLogic, Inc. jlove...@openlogic.com | 720 240 4545 On 2/25/13 11:10 AM, Till Jaeger jae...@jbb.de wrote: Dear