[llvm-foundation] Status of re-license?

Chris Lattner via llvm-foundation llvm-foundation at lists.llvm.org
Sun Aug 2 17:37:42 PDT 2020


Hi Zachary,

We ask that all new contributions be contributed under the terms of both the new and the old license.  This allows people to use it under the old license during the transition, but allows us to eventually get to the new one.

Our intention is to eventually drop the old license.  However, if we drop it at revision X, people could still use the codebase as of revision X-1 under the old license if they want to.

There is no CLA required for this sort of thing.  A CLA is required when you want to change the license of a contribution post-facto, which is something that many contributors are not willing to agree to.

-Chris


> On Jul 28, 2020, at 4:13 PM, Zachary Turner via llvm-foundation <llvm-foundation at lists.llvm.org> wrote:
> 
> What does this mean in terms of new contributors?  In order to be licensed under both old and new license, there should be some kind of CLA involved I’m assuming.  But I don’t see anything.  What do i tell my legal department?
> 
> On Tue, Jul 28, 2020 at 5:52 AM Robinson, Paul <paul.robinson at sony.com <mailto:paul.robinson at sony.com>> wrote:
> The process is still in progress. The online documentation is accurate.
> 
> Well, except for the January 2019 date.  It would be good to update that to a more sensible target.
> 
> --paulr
> 
>  
> 
> From: llvm-foundation <llvm-foundation-bounces at lists.llvm.org <mailto:llvm-foundation-bounces at lists.llvm.org>> On Behalf Of Hal Finkel via llvm-foundation
> Sent: Tuesday, July 28, 2020 1:51 AM
> To: Zachary Turner <zturner at roblox.com <mailto:zturner at roblox.com>>; llvm-foundation at lists.llvm.org <mailto:llvm-foundation at lists.llvm.org>
> Subject: Re: [llvm-foundation] Status of re-license?
> 
>  
> 
>  
> 
> On 7/24/20 8:35 PM, Zachary Turner via llvm-foundation wrote:
> 
> Hi, I'd like to make a contribution.  As it is currently written, I do not understand the requirements for being able to contribute a patch.
> 
>  
> 
> This page <https://urldefense.com/v3/__https:/llvm.org/docs/DeveloperPolicy.html*relicensing__;Iw!!JmoZiZGBv3RvKRSx!tTB6fptPB67Jr1XkdBJ1hFHiXdGmACITgQwclIU7qFlG5RHS61Gh0seceHmtxqQ5FQ$> seems to suggest that all contributions are currently being licensed under both the old and new license.
> 
>  
> 
> > In the interim, all contributions to the project will be made under the terms of both the new license and the legacy license scheme (each of which is described below). 
> 
>  
> 
> And there is no indication that this has been completed.  On this page <https://urldefense.com/v3/__https:/llvm.org/foundation/relicensing/__;!!JmoZiZGBv3RvKRSx!tTB6fptPB67Jr1XkdBJ1hFHiXdGmACITgQwclIU7qFlG5RHS61Gh0seceHmd_yEI8g$>, at the bottom, it says that the aim is to have this completed by January 2019.  If it has been completed, I don't think it has been communicated well, because all public facing documentation still refers to it being in progress.
> 
>  
> 
> The process is still in progress. The online documentation is accurate.
> 
>  -Hal
> 
>  
> 
>  
> 
> Could you offer some guidance on what the current status of the re-license is and how I should communicate this to my company's legal department?
> 
> 
> 
> 
> _______________________________________________
> llvm-foundation mailing list
> llvm-foundation at lists.llvm.org <mailto:llvm-foundation at lists.llvm.org>
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-foundation <https://urldefense.com/v3/__https:/lists.llvm.org/cgi-bin/mailman/listinfo/llvm-foundation__;!!JmoZiZGBv3RvKRSx!tTB6fptPB67Jr1XkdBJ1hFHiXdGmACITgQwclIU7qFlG5RHS61Gh0seceHmX9Q7zxg$>
> -- 
> Hal Finkel
> Lead, Compiler Technology and Programming Languages
> Leadership Computing Facility
> Argonne National Laboratory
> _______________________________________________
> llvm-foundation mailing list
> llvm-foundation at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-foundation

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-foundation/attachments/20200802/0d0e67ca/attachment.html>


More information about the llvm-foundation mailing list