This is an archive of the discontinued LLVM Phabricator instance.

Differential D54566

Reorganize the company listing and add UIUC as signed.
ClosedPublic

Authored by chandlerc on Nov 14 2018, 9:01 PM.

Details

Reviewers
hfinkel
Commits
rL346976: Reorganize the company listing and add UIUC as signed.
Summary

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

Diff Detail

Repository
rL LLVM

Event Timeline

chandlerc created this revision.Nov 14 2018, 9:01 PM
Herald added subscribers: llvm-commits, arphaman, mcrosier, sanjoy. · View Herald TranscriptNov 14 2018, 9:01 PM
Harbormaster completed remote builds in B25034: Diff 174154.Nov 14 2018, 9:01 PM
hfinkel accepted this revision.Nov 15 2018, 4:48 AM

LGTM

This revision is now accepted and ready to land.Nov 15 2018, 4:48 AM
Closed by commit rL346976: Reorganize the company listing and add UIUC as signed. (authored by chandlerc). · Explain WhyNov 15 2018, 10:30 AM
This revision was automatically updated to reflect the committed changes.

Revision Contents

PathSize
www/
trunk/
foundation/
relicensing/
42 lines

Diff 174246

www/trunk/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