This is an archive of the discontinued LLVM Phabricator instance.

Differential D54018

Update the relicensing website to better explain the list of companies, and update the list as some more signatures have come in.
ClosedPublic

Authored by chandlerc on Nov 1 2018, 5:52 PM.

Details

Reviewers
hfinkel

Diff Detail

Event Timeline

chandlerc created this revision.Nov 1 2018, 5:52 PM
Herald added subscribers: llvm-commits, arphaman, mcrosier, sanjoy. · View Herald TranscriptNov 1 2018, 5:52 PM
Harbormaster completed remote builds in B24492: Diff 172289.Nov 1 2018, 5:54 PM
hfinkel accepted this revision.Nov 2 2018, 7:52 AM

LGTM

This revision is now accepted and ready to land.Nov 2 2018, 7:52 AM
chandlerc updated this revision to Diff 174153.Nov 14 2018, 8:58 PM

Reorganize the company listing and add UIUC as signed.

Based on the discussion in the board meeting, this seems like an improved
structure. We may still move to a direct and comprehensive list.

Updating D54018: Update the relicensing website to better explain the list of companies, and

update the list as some more signatures have come in.

Harbormaster completed remote builds in B25033: Diff 174153.Nov 14 2018, 8:58 PM
chandlerc closed this revision.Nov 14 2018, 9:00 PM

Revision Contents

PathSize
foundation/
relicensing/
42 lines

Diff 174153

foundation/relicensing/index.html

Show First 20 Lines • Show All 102 Lines • ▼ Show 20 Lines
<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> <p>
A non-exhaustive list of companies that have been contacted about relicensing or have already signed the agreement is below. This is primarily intended to avoid duplicate work within these companies trying to get things signed and set up. A non-exhaustive list of companies that have been contacted about relicensing or have already signed the agreement is below. This is primarily intended to avoid duplicate work within these companies trying to get things signed and set up.
</p>
<p>
<b>Signed:</b>
<ul> <ul>
<li>Access Softek: contacted</li> <li>Argonne National Laboratory</li>
<li>AMD: contacted</li> <li>Google</li>
<li>ARM: contacted</li> <li>Microsoft</li>
<li>Apple: contacted</li> <li>UIUC</li>
<li>Argonne National Laboratory: signed</li> <li>lowRISC</li>
<li>Azul: contacted</li> </ul>
<li>Google: signed</li> </p>
<li>IBM: contacted</li>
<li>Intel: contacted</li> <p>
<li>Linaro: contacted</li> <b>Contacted:</b>
<li>lowRISC: signed</li> <ul>
<li>Microsoft: signed</li> <li>AMD</li>
<li>Nvidia: contacted</li> <li>ARM</li>
<li>Qualcomm: contacted</li> <li>Access Softek</li>
<li>Sony: contacted</li> <li>Apple</li>
<li>UIUC: contacted</li> <li>Azul</li>
<li>IBM</li>
<li>Intel</li>
<li>Linaro</li>
<li>Nvidia</li>
<li>Qualcomm</li>
<li>Sony</li>
</ul> </ul>
</p> </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:
Show All 11 Lines