This is an archive of the discontinued LLVM Phabricator instance.

Differential D52960

Add a listing of companies that have agreed to the relicensing.
ClosedPublic

Authored by chandlerc on Oct 5 2018, 10:43 PM.

Details

Reviewers
hfinkel
lattner
Commits
rL343932: Add a listing of companies that have agreed to the relicensing.
Summary

Currently this is just Argonne, but hopefully will grow soon as I know
discussions are on-going at a *bunch* companies right now.

Diff Detail

Repository
rL LLVM

Event Timeline

chandlerc created this revision.Oct 5 2018, 10:43 PM
Herald added subscribers: llvm-commits, arphaman, mcrosier, sanjoy. · View Herald TranscriptOct 5 2018, 10:43 PM
Harbormaster completed remote builds in B23542: Diff 168561.Oct 5 2018, 10:43 PM
hfinkel accepted this revision.Oct 6 2018, 7:56 PM

LGTM

This revision is now accepted and ready to land.Oct 6 2018, 7:56 PM
Closed by commit rL343932: Add a listing of companies that have agreed to the relicensing. (authored by chandlerc). · Explain WhyOct 7 2018, 12:08 AM
This revision was automatically updated to reflect the committed changes.

Revision Contents

PathSize
www/
trunk/
foundation/
relicensing/
7 lines

Diff 168584

www/trunk/foundation/relicensing/index.html

Show First 20 Lines • Show All 83 Lines • ▼ Show 20 Lines
</p> </p>
<div class="www_sectiontitle" id="corporate_agreement">Corporate Relicensing Agreement</div> <div class="www_sectiontitle" id="corporate_agreement">Corporate Relicensing Agreement</div>
<p> <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:board@llvm.org">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:board@llvm.org">the board</a> and we'll try to help. 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:board@llvm.org">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:board@llvm.org">the board</a> and we'll try to help.
</p> </p>
<p>
Several corporations have already signed this agreement to relicense. A non-exhaustive list of companies already having signed:
<ul>
<li>Argonne National Laboratory</li>
</ul>
</p>
<div class="www_sectiontitle" id="next_steps">Next Steps and Schedule Estimate</div> <div class="www_sectiontitle" id="next_steps">Next Steps and Schedule Estimate</div>
<p> <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: 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> <ul>
<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>~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>
Show All 9 Lines