Bug 1866472 - llvm: Incorrect License tag
Summary: llvm: Incorrect License tag
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: DevTools
Classification: Red Hat
Component: llvm
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 2019.3
Assignee: Tom Stellard
QA Contact: Tilmann Scheller
URL:
Whiteboard:
Depends On: 1866468
Blocks: 1866471
TreeView+ depends on / blocked
 
Reported: 2020-08-05 16:13 UTC by Florian Weimer
Modified: 2020-08-05 17:35 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1866468
Environment:
Last Closed: 2020-08-05 17:35:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Florian Weimer 2020-08-05 16:13:28 UTC
+++ This bug was initially created as a clone of Bug #1866468 +++

LLVM has been relicensed to ASL 2.0 with exceptions, so

License: NCSA

is no longer correct. There is a discussion here about the appropriate tag:

<https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org/message/4OT2CHT3UX7AYI7LDK4YFZEU3QIDZKPY/>

I think relicensings like this should also be announced on the devel list.

Comment 2 Tilmann Scheller 2020-08-05 17:35:58 UTC
There is an ongoing effort to relicense LLVM (and related projects) under the Apache 2.0 with LLVM Exception license (see https://llvm.org/foundation/relicensing), however that process will still take a long time to be completed. The assessment that LLVM has been relicensed already is incorrect. What has happened is that the LLVM contribution policy has changed a while ago to require any new contributions to be under both NCSA as well as Apache 2.0 with LLVM Exception (see https://llvm.org/docs/DeveloperPolicy.html#id32). This means that the entirety of LLVM is still under the NCSA license (details here: https://llvm.org/docs/DeveloperPolicy.html#id34) and as such the current license description in the spec file is still accurate. Since the completion of the relicensing is still far out in the future I'll go ahead and close this bug. Please let me know if you have any questions.


Note You need to log in before you can comment on or make changes to this bug.