[PATCH] D56962: Remove FAQ entries about the legacy license structure and add the most obvious FAQ entry for the new one.

[Chandler Carruth via Phabricator via llvm-commits]

chandlerc created this revision.
chandlerc added reviewers: lattner, hfinkel.
Herald added subscribers: mcrosier, sanjoy.

Not sure what else we should be putting here, but I'm happy for anyone
to add questions they'd like answered here, and if I can, I'll add them
with an answer.

We could consider moving some of FAQ-like discussion from the developer
policy here or vice-versa if folks desire. Just let me know.


https://reviews.llvm.org/D56962

Files:
  llvm/docs/FAQ.rst


Index: llvm/docs/FAQ.rst
===================================================================
--- llvm/docs/FAQ.rst
+++ llvm/docs/FAQ.rst
@@ -9,11 +9,18 @@
 License
 =======
 
-Does the University of Illinois Open Source License really qualify as an "open source" license?
------------------------------------------------------------------------------------------------
-Yes, the license is `certified
-<http://www.opensource.org/licenses/UoI-NCSA.php>`_ by the Open Source
-Initiative (OSI).
+
+Why are there LLVM exceptions to the Apache 2.0 license?
+--------------------------------------------------------
+The LLVM exceptions address two potential issues users might have with using
+the Apache License 2.0. First, there are some concerns around combining code
+under Apache 2.0 with GPLv2 that the exceptions address. Second, the exceptions
+ensure LLVM-based runtime libraries don't impose Apache 2.0 notice requirements
+on software when you simply use LLVM as part of compiling that software. We
+designed this to be more flexible than usual because LLVM often shares code and
+technology between many different subsystems including runtime libraries and we
+don't want license terms to be a barrier to good engineering decisions around
+factoring out common logic.
 
 
 Can I modify LLVM source code and redistribute the modified source?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D56962.182675.patch
Type: text/x-patch
Size: 1348 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20190119/07c80aa6/attachment.bin>