Re-Releasing, Re-Naming and Re-Writing Open Source GNU V3 Licensed software
<p><strong>MAIN QUESTION SUMMARY:</strong></p>

<p>Can someone with real world experience, who has actually <em>Modified, Re-Wrote, Re-Released and Re-Named Open Source GNU V3 Licensed software</em>; please share their experience on the subject?</p>

<p><strong>Background:</strong></p>

<p>I have been working on and debugging a plugin (for an OpenSource CMS system) for 4 years (about 500 hr per year) in order to make it work perfectly.</p>

<ul>
<li>The plugin is licensed as: <em>GNU General Public License</em> version 3 [or later]</li>
<li>The plugin clearly states: <em>free software: you can redistribute it and/or modify</em></li>
</ul>

<p><strong>Over that time the following things have happened:</strong></p>

<ul>
<li>The plugin developers have not supported the plugin very well or fast enough (in my opinion)</li>
<li>I have added major new functionality to the Plugin using "extensions"</li>
<li>I have patched the plugin repeatedly, for example:

<ul>
<li>Upgraded from PHP 5.4 => 7.0 => 7.2 (cleaned up errors, rewrites, removed lazy code like faulty output buffering and is_array checks - ect...)</li>
<li>Updated JS to modern web standards (Select2 3.5.3 => 4.0.2, jQuery 3.3, ect...)</li>
<li>Continually added notes into the @package declaration and changelog</li>
<li>Maintained and eventually modified the core plugin so much that its hardly even the same plugin anymore. (only 88 of 595 files are original plus 62 new files)</li>
</ul></li>
</ul>

<p>To conclude: the natural process of maintaining, debugging and enhancing has produced this 'different new thing'. </p>

<p><strong>Therefore: I am considering the following approach</strong> (because I do not want to confuse people, this plugin accomplished the same goal but is no longer the same software)</p>

<ol>
<li>Just rename the plugin</li>
<li>Honor the original developers by stating that this new plugin is "Based on the classic"</li>
<li>Keep the original License intact but in a separate .txt file</li>
<li>Keep the authors names listed as "Based on the work of"</li>
<li>Add a new GNU LICENSE declaration </li>
<li>Explain all modifications in a changelog</li>
<li>RE-RELEASE and RE-DISTRIBUTE the plugin under its new name</li>
<li>Go into the forum area where the original Plugin was distributed (where people are complaining) and tell them <em>"hey, I had the same problems, so I rewrote this plugin get it here for free, cheers"</em></li>
</ol>

<p><strong>I now have the following questions and concerns:</strong></p>

<ul>
<li>Is this acceptable and legal use of the GNU License? <em>[I assume yes]</em></li>
<li>Is this considered FauxPas or inappropriate? <em>[I assume no]</em></li>
<li>Should I <em>not</em> even mention the original name of the plugin? <em>[unsure]</em></li>
<li>Is keeping the authors names intact considered correct? <em>[I assume yes]</em></li>
<li>What is an honorable, noble and respectful way to handle naming? <em>[want a professional opinion]</em></li>
<li>How exactly does "Re-releasing GNU software after rewriting or heavy modification" work? <em>[I assume I just rename it and write a declaration that explains the history of the code]</em></li>
<li>Is there anyone with direct and specific experience in this exact same area that can share on the topic?</li>
<li>Should the original plugin developers "rise from the dead" and see what I have done- should I be concerned? (I imagine its 50/50, they either see it and say good job carry the torch, or they may become irate)</li>
</ul>

<p>IMPORTANT NOTE: some of the "extensions" for that plugin were not free, users had to pay to download them. I modified, maintained, updated and patches several of those as well. This explains some of my concerns here, there may be money involved on those extensions. These paid extensions also are listed as GNU, version 2 or later</p>

<p><strong>An example:</strong>
I remember when Joomla was Mambo... I feel that this situation might be similar?</p>

<p><strong>Research and notes:</strong>
I have examined the following, which helped me formulate some of my assumed answers.</p>

<ul>
<li><a href="https://opensource.org/licenses" rel="nofollow noreferrer">https://opensource.org/licenses</a></li>
<li><a href="https://www.gnu.org/licenses/gpl-3.0.en.html" rel="nofollow noreferrer">https://www.gnu.org/licenses/gpl-3.0.en.html</a></li>
<li><a href="http://www.gnu.org/licenses/" rel="nofollow noreferrer">http://www.gnu.org/licenses/</a></li>
<li><a href="https://odino.org/the-5-golden-rules-when-writing-open-source-software/" rel="nofollow noreferrer">https://odino.org/the-5-golden-rules-when-writing-open-source-software/</a>
<a href="https://opensource.guide/legal/" rel="nofollow noreferrer">https://opensource.guide/legal/</a></li>
<li><a href="https://www.gnu.org/licenses/gpl-faq.html" rel="nofollow noreferrer">https://www.gnu.org/licenses/gpl-faq.html</a></li>
<li><a href="https://stackoverflow.com/questions/9493786/gnu-gpl-license-terms-open-source-softwares">https://stackoverflow.com/questions/9493786/gnu-gpl-license-terms-open-source-softwares</a></li>
<li><a href="https://law.stackexchange.com/questions/3419/re-formatting-and-displaying-of-software-licenses-privacy-policy-impressum">(Re-)formatting and displaying of software licenses/privacy policy/impressum</a></li>
<li><a href="https://law.stackexchange.com/questions/30278/can-you-use-only-the-name-brand-of-gnu-open-source-software">Can you use only the name/brand of GNU open source software?</a></li>
<li><a href="https://law.stackexchange.com/questions/6136/law-and-open-source-project">Law and open-source project</a></li>
</ul>

<p>Thank you for your consideration in this matter.</p>

<p>I'm assuming that you are not seeking to change the license, and so it will remain GPLv3.  As long as you've built on the original software, that license still applies.  You also need to keep the previous copyright notices, including the names of the original people.</p>

<p>Assuming that, everything you're doing is legal, which is what's on topic here.  There is some etiquette around forks (which is what you're doing), which would be on topic at <a href="https://opensource.stackexchange.com/">the Open Source Stack Exchange</a>.</p>

<p>I'm puzzled by your desire to have a different license text.  You can't change the license from GPLv3, so that has to stay the same.  (If the original has GPLv3 "or, at your option, any later version", you can drop the any other version text if you like.)</p>

software open-source-software