<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Paul,<div><br></div><div>Thanks for your response! I think that you're right, and it would make sense for the LLVM Foundation to drive this kind of change to ensure this is done with correct legal compliance. I will close my patch and will reach out the Foundation instead.</div><div><br></div><div>I would like to offer a different perspective of why adding a top-level license file would benefit some downstream monorepo repositories. Yesterday, Apple published a prototype downstream monorepo that can be used for building Swift: <a href="https://github.com/apple/llvm-project-v1">https://github.com/apple/llvm-project-v1</a> . One of the issues we encountered before publishing was the lack of a top-level license file in LLVM's monorepo root SVN repo, as we created our own downstream fork for the monorepo root on Github as well (<a href="https://github.com/apple/llvm-monorepo-root">https://github.com/apple/llvm-monorepo-root</a>). Before we could publish it, we had to add a top-level LLVM LICENSE.txt file to our fork of the monorepo root, to ensure that the repository was licensed. And even though the monorepo root repository will go away once LLVM.org transitions to Github, we will still need a top-level license file in our downstream fork of llvm-project, to ensure that we aren't publishing files that appear to be unlicensed on Github (specifically the top-level config files in llvm-project).</div><div><br></div><div>Thanks,</div><div>Alex</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 17 Jul 2019 at 12:57, <<a href="mailto:paul.robinson@sony.com">paul.robinson@sony.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-7520850437449091314WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Yes, there are objections to adding a top-level LICENSE.txt, which I also mentioned in the review.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><a href="https://reviews.llvm.org/D64875" target="_blank">https://reviews.llvm.org/D64875</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">It's obvious from the .gitignore discussion that different downstream projects handle their additions to /llvm-project in different ways. If /llvm-project
adds a top-level LICENSE.txt file, that creates requirements on how downstream projects manage the licenses for their additions; specifically it requires a LICENSE.txt file in each directory added to the top level. And probably messes with how people have
to handle individual files added at the top level.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">While I understand your motivation is to simplify things, actually it doesn't; it changes how the license applies downstream, and that should not be done without
proper discussion and advance notice. In particular this is something the LLVM Foundation should initiate, if it feels this is appropriate, and AFAIK you are not part of the Foundation. Sorry if that sounds harsh, but legalities are a minefield.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">--paulr<u></u><u></u></span></p>
<p class="MsoNormal"><a name="m_-7520850437449091314__MailEndCompose"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></a></p>
<div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0in 0in 0in 4pt">
<div>
<div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"> llvm-dev [mailto:<a href="mailto:llvm-dev-bounces@lists.llvm.org" target="_blank">llvm-dev-bounces@lists.llvm.org</a>]
<b>On Behalf Of </b>Alex L via llvm-dev<br>
<b>Sent:</b> Wednesday, July 17, 2019 2:29 PM<br>
<b>To:</b> llvm-dev<br>
<b>Subject:</b> [llvm-dev] Adding the LLVM license file to the monorepo root<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">Hi,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The llvm-project monorepo (<a href="https://github.com/llvm/llvm-project" target="_blank">https://github.com/llvm/llvm-project</a>) is currently missing a top-level license file. It would be nice if there was one so that anyone unfamiliar with layout of
the monorepo could find it right away.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I have put up a patch that adds a LICENSE.txt file to the monorepo root:
<a href="https://reviews.llvm.org/D64875" target="_blank">https://reviews.llvm.org/D64875</a>. The file is copy of LICENSE.txt from the llvm/ directory. Are there any objections to adding it?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Alex<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote></div></div></div></div></div>