[www] r330125 - Put all the tidbits about the current state of relicensing into one place so it is generally findable without scrubbing through lots of email. There is nothing revolutionary here, other than an attempt at a schedule estimate.

Tue Apr 17 14:03:05 PDT 2018

I will once again point out that no one has explained why a contributor
agreement would not have the desired effect without a license change and
until someone does I will not agree to relicense.

Cheers,
Rafael

Chris Lattner via llvm-commits <llvm-commits at lists.llvm.org> writes:

> Author: lattner
> Date: Mon Apr 16 07:12:55 2018
> New Revision: 330125
>
> URL: http://llvm.org/viewvc/llvm-project?rev=330125&view=rev
> Log:
> Put all the tidbits about the current state of relicensing into one place so it is generally findable without scrubbing through lots of email.  There is nothing revolutionary here, other than an attempt at a schedule estimate.
>
> Added:
>     www/trunk/foundation/relicensing/index.html   (with props)
>
> Added: www/trunk/foundation/relicensing/index.html
> URL: http://llvm.org/viewvc/llvm-project/www/trunk/foundation/relicensing/index.html?rev=330125&view=auto
> ==============================================================================
> --- www/trunk/foundation/relicensing/index.html (added)
> +++ www/trunk/foundation/relicensing/index.html Mon Apr 16 07:12:55 2018
> @@ -0,0 +1,70 @@
> +<!--#include virtual="../header.incl" -->
> +
> +<div class="www_sectiontitle">LLVM Relicensing Effort</div>
> +
> +<p>
> +The LLVM relicensing effort aims to modernize the LLVM Licensing structure and developer policy.  The high level goals of the relicensing effort are to:
> +
> +<ul>
> +<li>Encourage ongoing contributions to LLVM by preserving a low barrier to entry for contributors.</li>
> +<li>Protect users of LLVM code by providing explicit patent protection in the license.</li>
> +<li>Protect contributors to the LLVM project by explicitly scoping their patent contributions with this license.</li>
> +<li>Eliminate the schism between runtime libraries and the rest of the compiler that makes it difficult to move code between them.</li>
> +<li>Ensure that LLVM runtime libraries may be used by other open source and proprietary compilers.</li>
> +</ul>
> +
> +This project involves sensitive legal issues and has been a multi-year effort.  The primary public discussions have included these mailing list threads:
> +
> +<ul>
> +<li>October 19, 2015: <a href="http://lists.llvm.org/pipermail/llvm-dev/2015-October/091536.html">Initial license draft proposal</a>.</li>
> +<li>September 12, 2016: <a href="http://lists.llvm.org/pipermail/llvm-dev/2016-September/104778.html">Second license draft</a>, resolving GPL2 compatibility concerns.</li>
> +<li>April 17, 2017: <a href="http://lists.llvm.org/pipermail/llvm-dev/2017-April/112142.html">Third license draft</a>, which resolved concern about use of LLVM runtimes with proprietary toolchains.</li>
> +<li>August 7, 2017: <a href="http://lists.llvm.org/pipermail/llvm-dev/2017-August/116266.html">LLVM Developer Policy wording</a>.</li>
> +</ul>
> +
> +Beyond that, these topics have also been discussed by, and include contributions from, over a dozen lawyers and key LLVM contributors, and have been discussed informally with hundreds of people in the LLVM Developer Meeting BoFs.  The effort has been overseen by Heather Meeker, who is the LLVM Foundationâs legal counsel.  If you have questions or concerns about the content of this document, please email the <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">llvm-dev mailing list</a> or the <a href="mailto:board at llvm.org">LLVM Foundation Board</a> depending on the sensitivity of your email.
> +</p>
> +
> +<div class="www_sectiontitle">Status and Documents</div>
> +
> +<p>
> +At this point, we have achieved community consensus on:
> +
> +<ul>
> +<li>The goals of the relicensing effort.</li>
> +<li>License Full Name: "Apache 2.0 with LLVM Exception"</li>
> +<li>SPDX License Identifier: "Apache-2.0 WITH LLVM-exception"</li>
> +<li>The license text itself.  This is the expected LICENSE.TXT file.</li>
> +<li>The revised LLVM developer policy text.</li>
> +</ul>
> +
> +That said, we still need to:
> +
> +<ul>
> +<li>Finalize the new top-of-file copyright header block.
> +
> +<li>Finalize the process and forms used for corporations and individuals to relicense past contributions under the new license structure.  We currently believe that the corporate relicensing form will be a paper form, and that the individual contributor agreement will be a click-through web form.</li>
> +<li>Decide a date upon which all new contributions will be under both the new and old license agreements.</li>
> +<li>Decide upon and enact a process for getting 100% of existing code relicensed under the new agreement (using the aforementioned forms) or rewrite/remove the code.</li>
> +<li>Drop the old license when the entire codebase is covered under the new license.</li>
> +</ul>
> +</p>
> +
> +<div class="www_sectiontitle">Next Steps and Schedule Estimate</div>
> +
> +<p>
> +
> +Our goal is to openly and transparently communicate our process, including the expected next steps and a timeframe that can be used for planning.  That said, we are dealing with a lot of unknowns, so while we believe the following schedule is achievable, this is not a guarantee:
> +
> +<ul>
> +<li>~May 2018: We aim to have the corporate agreement (to relicense prior contributions) approved by the LLVM Foundation board and LLVM legal counsel, and will post it on this web page.  At this point, we will ask corporate contributors (e.g. through email to llvm-dev) to bring it to their company legal team.  We aim to get sign-off from as many companies as possible starting at this point.</li>
> +<li>~June 2018: We aim to have the individual license agreement approved, and have the web interface for it implemented prior to the LLVM 7.0 release.  We will add details about that to this web page, release notes, and will solicit individual contributors to relicense their prior contributions (e.g. on llvm-dev).</li>
> +<li>~January 2019: Coincident with the final release branch date for LLVM 8.0, we will install the new developer policy.  To ensure that all contributors have agreed to the terms of the new developer policy, we will recind commit access from all contributors who are not covered by a corporate or individual agreement at that point.  We will develop a policy for affected contributors to regain commit access.</li>
> +</ul>
> +
> +When these steps are done, all new contributions will be under the new license structure, and we expect that a significant amount of prior contributions will be relicensed under the new structure.  At that point, we will scope and define the process for chasing down the long tail of prior contributions that are not covered and resolve them on a case-by-case basis.
> +
> +</p>
> +
> +<!-- *********************************************************************** -->
> +<!--#include virtual="../footer.incl" -->
>
> Propchange: www/trunk/foundation/relicensing/index.html
> ------------------------------------------------------------------------------
>     svn:executable = *
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits