Relicensing software under GPLv2+ without all contributors
<p>I have software licensed under GPLv2, which I would like to relicense under GPLv2+.  Unfortunately, I an unable to contact some of the contributors.  Can I proceed, or am I stuck?</p>

<p>Since licensing can only be done by the copyright holder, you generally need individual permission from each copyright holder to change the license of their code. (If the project is being re-licensed to the GPL from a <a href="http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean" rel="noreferrer">compatible license</a>, then no re-licensing from the copyright holder is necessary; however, versions 2 and 3 of the GPL are not compatible with one another.)</p>
<p>Ways around this are:</p>
<ul>
<li><p>Remove or replace all code written by the unreachable contributors.</p>
</li>
<li><p>Have contributors assign copyright to a person or legal entity that controls the project, so that there is exactly one copyright holder. (This is a <em>preventive</em> measure. If you have not done this already, it's too late when you cannot track down a contributor.)</p>
</li>
</ul>
<p>But if you can't do either of those things, what do you do?</p>
<p>Historically, re-licensing of software without explicit approval from all contributors <em>has</em> been done before, under the advice of legal professionals. However, the legal mechanics of it are unclear and have never been tested in court. The two prominent examples appear to be:</p>
<ul>
<li><p><a href="http://www-archive.mozilla.org/MPL/relicensing-faq.html" rel="noreferrer">Mozilla relicensed</a> from the MPL to a triple-licensed MPL/GPL/LGPL scheme</p>
</li>
<li><p>The <a href="https://dolphin-emu.org/blog/2015/05/25/relicensing-dolphin/" rel="noreferrer">Dolphin emulator relicensed</a> from GPLv2 to GPLv2+.</p>
</li>
</ul>
<p>The Dolphin project <a href="https://dolphin-emu.org/blog/2015/05/25/relicensing-dolphin/" rel="noreferrer">produced a report about the process</a>, but it lacks any specifics about <em>how</em> the legal mechanics of the switch work. They say (emphasis mine):</p>
<blockquote>
<p>Out of all [200 contributors], we managed to contact all or take care of the code of all but 10 of those developers. Considering that many of those accounts are now dead and the people seemingly vanished from the Internet, finding the rest is akin to squeezing blood out of a stone.</p>
<p>That's when research provided us some much needed relief when it seemed as though relicensing was an impossibility. In 2003, <strong>Free Software lawyers consulted for Mozilla's relicensing project and stated that relicensing with the permission of just 95% of contributors was fine, as long as there were no objections in the remaining 5%</strong>.</p>
<p>[...]</p>
<p>[...] Instead of simply asking all of our active developers and relicensing, we made a very strong effort to get a hold of every single developer. Despite this, it simply wasn't feasible to make contact with every single person who worked on Dolphin.</p>
<p>[...] We definitely would love to hear support from those that we were unable to contact, and if there are any concerns we will gladly address them in a prompt fashion.</p>
</blockquote>
<p>That posts links to a <a href="http://blogs.fsfe.org/ciaran/?p=58" rel="noreferrer">post from Ciaran O'Riordan</a>:</p>
<blockquote>
<p>Someone who works with many lawyers on free software copyright issues later told me that it is not necessary to get permission from 100% of the copyright holders. It would suffice if there was permission from the copyright holders of 95% of the source code and no objections from the holders of the other 5%. This, I’m told, is how Mozilla was able to relicense to the GPL in 2003 despite years of community contributions.</p>
</blockquote>
<p>There is no information available about <em>why</em> Mozilla's lawyers believed it was acceptable to re-license without each copyright holder's permission. It's also unclear if any factors apply to Mozilla specifically that might apply less strongly to anyone else in a similar situation.</p>
<p>In sum, we know only that:</p>
<ul>
<li><p>You need the permission of every contributing copyright holder to re-license a work</p>
</li>
<li><p>Mozilla's lawyers believed (for unspecified reasons) it would be acceptable for Mozilla to make a good-faith effort to contract all contributors and then re-license, even if 5% of the contributors were unreachable (and none of the contributors disapproved).</p>
</li>
</ul>

<p>As far as I know, you are stuck unless you can somehow track the pieces of code written by every single developer, and remove those written by those you can't reach.</p>

<p>For obvious reasons, this is seldom doable.</p>

copyright licensing gpl