How to abide by software license when forking source code
<p>I am forking a source code repository. The repository contains a file, LICENSE.TXT, which reads:</p>
<p>&quot;MIT License</p>
<p>Copyright (c) 2021 Microsoft</p>
<p>[...]</p>
<p>The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.</p>
<p>[...]&quot;</p>
<p>What is the common practice here?
It seems I must keep a copy of this license in my repository and also publish it when deploying my software. I also want to provide my own license (also under MIT), but I can't sign it using 'Microsoft'. Should I perhaps rename Microsoft's LICENSE.TXT to something else, then create my own LICENSE.TXT and put my name in it?</p>
<p>Basically, I want to abide by the existing license and to publish my own license (which incidentally will be identical but not signed by 'Microsoft' as I am not employed by that company).</p>

<p>It seems it's <em>the license itself</em> that is under Microsoft's copyright. So if you copy the license, you should leave Microsoft's copyright notice intact. And please, please don't create your own license. It just leads to legal trouble. And Microsoft hasn't given you any permission to modify the license. (Same with the GPL licenses, you are free to copy them, but they will get VERY angry if you modify a GPL license).</p>
<p>Next you look at the copyright for the actual code. The original has one or more copyright holders. If you modify it, you will be an additional copyright holder. So don't write a license that claims you are the sole copyright holder.</p>

open-source-software