Licensing software opensource but keeping reputation as the creator
<p>I am building a web application for a client of mine.  I will likely wish to use the software with other clients.  My client has no expectations that they will have exclusive rights to the software, but also doesn't want to be stranded if I get out of the business and licencing prevents them from being able to modify the source code.  I am strongly involved in creating the application, but am paying someone to write much of the script.  I wish to be seen as the main contributor of this software as it will help me from a marketing standpoint.</p>

<p>My thoughts are to do the following:</p>

<ol>
<li>Licence the software opensource.  Probably GNU General Public License (GPL), GNU Library or "Lesser" General Public License (LGPL), or MIT license, but I am not sure which one.  Maybe more than one?</li>
<li>Add to the HTML of each page of the application "Created by MyCompany under the XYZ opensource licence".</li>
</ol>

<p>Is this an applicable approach?  Which opensource license might be most applicable?  If the individual I am paying to write much of the script is okay with me putting my name as the author, is this okay?  What else should I be doing?</p>

<p>You don't create software "under a license". You create software, then you own the copyright, and as the copyright owner, you license the software with whatever license you want. </p>

<p>Since you want to use the software with more clients, and your client wants to use it as well, you could just add</p>

<pre><code>Copyright 2017 by user1032531
Unlimited, non-exclusive license granted to TheirCompany
</code></pre>

<p>In other words, they can do whatever they like, except that you are the copyright holder. So they can't stop you from doing anything, and they can't sue someone who makes illegal copies of the code (only you can). GPL has restrictions that they might not like. </p>

<p>In many countries, you can't claim you're the author if you are not the author. You may be the copyright owner, but to be the author, you must have written it yourself. </p>

<p>GPL restrictions: If you give GPL licensed software to anyone, you have to give the source code to them at the same time. OR you have to give the source code to anyone (and I mean anyone) who asks for it. </p>

<p>Let's say your client hires me to add to your software. And I don't want my code to end up GPL licensed. Then your client has to find someone else to do the work. </p>

software licensing open-source-software