[llvm-dev] Relicensing: Revised Developer Policy

Daniel Berlin via llvm-dev llvm-dev at lists.llvm.org
Fri Aug 11 13:49:00 PDT 2017


On Fri, Aug 11, 2017 at 1:07 PM, Rafael Avila de Espindola via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Chris Lattner <clattner at llvm.org> writes:
> >>> 2. The Apache CLA is the only widely available one, but it is
> unsuitable for LLVM’s goals because it allows a project to relicense
> contributions.
> >>> 3. Some contributors are significantly concerned with the Apache CLA,
> partially because of #2, but there are other concerns.  Losing contributors
> would be unfortunate.
> >>> 4. We do not want a novel legal device (e.g. a new or significantly
> hacked up CLA).
> >>
> >> We are proposing moving to modified Apache license. Why is a modified
> >> license less troublesome than a modified CLA?
> >
> > The proposal is not a modified apache license.  It is an apache license
> that has some exceptions which can be completely ignored by a user of LLVM
> if they choose, and the exceptions are carefully scoped by many lawyers to
> ensure they are bounded in the right ways.
>
> The code is then effectively dual licensed. It is both Apache and
> Apache+exceptions.
>

This is not correct.  It is apache + additional permissions.
That is not a dual license, in theory or practice, any more than if i said
"My code is GPLv2, but you are free to ignore section 2" is dual licensed.

>
> Could it be Apache+MIT for example?
>

Folks went through almost every possibility you can think of before
arriving at this choice.
Dual licensing has the horrible outcome that you must choose which of the
two licenses you are using, and you will get very different rights
depending on your choice.  You don't get to use it under both
simultaneously - It is not the quantum superposition of licenses.


> Since every contributor would be agreeing with both, we would still get
> section 3 (the grant of patents), and could drop our current patent
> wording.
>

This is not correct, as i stated, you have to choose which you are using it
under.
If i choose MIT, you are welcome to sue me for patents without fear you
will lose something.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170811/fc22f4e9/attachment.html>


More information about the llvm-dev mailing list