Update to relicensing website with developments over the past few months.

[chandlerc]

Summary

• Corporate agreement details
• New file header
• Updated status and schedule

[lattner]

Looks great, thanks Chandler!

[hfinkel]

In D52929#1256622, @lattner wrote:

Looks great, thanks Chandler!

LGTM too!

foundation/relicensing/index.html

 <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:[e-mail]">LLVM Foundation Board</a> depending on the sensitivity of your email.
 </p>
 
-<div class="www_sectiontitle">Status and Documents</div>
+<div class="www_sectiontitle" id="status">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><a href="https://spdx.org/licenses/">SPDX License Identifier</a>: "Apache-2.0 WITH LLVM-exception"</li>
 <li>The license text itself.  This is <a href="LICENSE.txt">the expected LICENSE.TXT file</a>.</li>
 <li>The revised LLVM <a href="devpolicy.patch">developer policy patch</a>.</li>
 </ul>
+</p>
 
-That said, we still need to:
+<p>
+We also have worked with our legal counsel to build several more boring pieces:
 
 <ul>
-<li>Finalize the new top-of-file copyright header block.
+<li>A new top-of-file header block that is minimal and includes the relevant and important information about the new license.
+<li>A corporate agreement to relicense that is available for companies to sign and has begun to be distributed to some of the known and/or large contributors.
+</ul>
+</p>
+
+<p>
+That said, we still need to:
 
-<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>
+<ul>
+<li>Finalize the process and forms used for individuals to relicense past contributions under the new license structure. We believe 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>
+<div class="www_sectiontitle" id="header">New File Header</div>
+
+<p>
+The new file header will be:
+<pre>
+//===-- file/name - File description ----------------------------*- C++ -*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+//
+//===----------------------------------------------------------------------===//
+</pre>
+</p>
+
+<p>
+Some notable aspects of the new header:
+
+<ul>
+<li>There is no explicit copyright notice -- these had little value and tended to not be maintained.</li>
+<li>It is designed to be as compact and minimalist as possible while having the critical information: that it is part of LLVM, what license it is under, where to find that license, and the machine-scrapable SPDX markup to help people doing license audits.</li>
+</ul>
+</p>
+
+<div class="www_sectiontitle" id="corporate_agreement">Corporate Relicensing Agreement</div>
+
+<p>
+Corporations may sign an agreement to relicense their contributions to LLVM under the new license <a href="https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=5a2bb38c-41c4-4ce0-a26e-52a7eb8ae51c">with Docusign</a>. This is our preferred mechanism for collecting signatures. However, if your company requires it, you can print out <a href="https://drive.google.com/open?id=1FiHyH__qqr6Ki2RXDEAcP7SEYFhsawNo">this PDF of the agreement</a>, sign it, scan it, and send the signed version as a PDF attachment to the <a href="mailto:[e-mail]">LLVM Foundation Board</a>. Further, if your company has a specific concern or issue with the agreement, please reach out to the <a href="mailto:[e-mail]">the board</a> and we'll try to help.
+</p>
+
+<div class="www_sectiontitle" id="next_steps">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>~October 2018: We aim to have the individual license agreement approved, and have it posted prior to the US developer's meeting.  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" -->