Beyls: Wrapping up LLVM's relicensing effort
Kristof Beyls has published a summary to the LLVM discussion forum to announce that the project is declaring success and bringing its relicensing…
Why am I seeing this Ranked on source trust — LWN
It ranks mainly on source trust: LWN is the most reliable outlet we track on this subject, and is the only one on the story so far.
Single-sourced. No second organisation has confirmed it yet.
Link-outLink-out, because only one organisation carries it and no first-party source is on it and the subject could not be identified from the text. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroboration | 0.35 | 0.39 | +0.135 29% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trustleads | 0.25 | 0.85 | +0.212 45% | LWN is the highest-trust source on this story. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.63 | +0.125 26% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.
LLVM has concluded its eight-year relicensing initiative, with over 99.5% of contributed code now covered by Apache-2.0 WITH LLVM-exception or falling outside copyright scope. The project began requesting relicensing from past contributors in 2018, with new contributions automatically falling under the Apache license starting January 19, 2019. Code predating that cutoff required explicit permission from authors to migrate from LLVM's original UIUC/NCSA and MIT licenses.
The project determined that pursuing the remaining fraction of code was impractical and decided to close the effort rather than continue indefinitely. Contributors whose work predates January 19, 2019 can still contact LLVM if they wish to ensure their code receives proper SPDX license identifiers or if they object to the relicensing of their contributions.
This marks the formal completion of a licensing transition that affected the entire LLVM codebase. Developers upgrading to current LLVM versions should be aware that the vast majority of the project now operates under the unified Apache-2.0 WITH LLVM-exception license.
What happened
Kristof Beyls has published a summary to the LLVM discussion forum to announce that the project is declaring success and bringing its relicensing effort to a close after eight years. We've been asking past contributors to relicense their work since 2018. New contributions have come in under Apache-2.0 WITH LLVM-exception since January 19, 2019. Code contributed before that date was under LLVM's earlier licenses (UIUC/NCSA, plus MIT for some runtime libraries), so we needed permission from its authors to move it over. Today, more than 99.5% of all lines of code ever contributed to LLVM are either covered by the new license, too small for copyright to apply, or no longer in the repository.
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Lwn first seen Beyls: Wrapping up LLVM's relicensing effort
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.