licensing
What (combination of) licenses is popular for public/shared proprietary software (“Feel free to contribute, but only we can make commercial use”)?
<p>A software product (a web service) is being developed.</p>

<p>In essence, I want the software code to be hosted publicly on GitHub. Anyone should be able view, download, modify, use for personal use, and contribute back with improvements as they want, meaning most of the "open source" principles - but not all, as...</p>

<p>...Only I may make commercial usage of the software code.</p>

<p>But the more I search on the Internet, the more confused I get about this topic. According to me, <strong>this situation has to be a common desire by developers or organizations</strong>, but yet it seems hard to find a clear answer to exactly how an organization can achieve this.</p>

<p>I have a hard time believing that each person or organization has to call in a lawyer that writes a custom license each time, right?  In other words, reinventing the wheel all the time.</p>

<p>Isn't there a straightforward, popular, or common license or license model that achieves this?</p>

<p>Perhaps "dual licensing" is the only way to achieve this? If so, are there any examples of GitHub projects that do this?</p>

<p>You're not going to find an <a href="https://opensource.org/licenses" rel="nofollow noreferrer">OSI-approved</a> or <a href="https://www.gnu.org/licenses/license-list.html" rel="nofollow noreferrer">FSF-approved</a> license that meets your needs because these licenses comply with the <a href="https://opensource.org/osd" rel="nofollow noreferrer">OSI definition</a> or <a href="https://www.gnu.org/philosophy/free-sw.html" rel="nofollow noreferrer">FSF definition</a> of open-source software, and your requirements don't.</p>

<p>Looking at your requirements, it looks like you want a license where users can modify the software and use it for private use, but cannot use it for commercial use. I ran <a href="https://tldrlegal.com/search?reverse=true&amp;can%5B%5D=52c65c9c09728f9723000012&amp;can%5B%5D=52e5822181519e003b00000d&amp;cannot%5B%5D=52c0d009a1ddc9766c00000a" rel="nofollow noreferrer">a search on TL;DR Legal</a> to see what licenses match. There are some one-off licenses that appear to be written by individuals or groups or written by companies that explicitly call out a particular software package. <a href="https://tldrlegal.com/license/trackingteam-licence" rel="nofollow noreferrer">One appears to be a modification of the Apache License</a>. I wouldn't recommend simply using one of these without not only reading them thoroughly yourself, but also consulting a lawyer - just because they started with a license that is trusted doesn't mean that a change they made didn't cause problems if it were to be challenged.</p>

<p>For a project hosted on GitHub, it doesn't need to be open-source. You can upload a project that is all rights reserved, but by using GitHub, you do need to <a href="https://help.github.com/articles/github-terms-of-service/#f-copyright-and-content-ownership" rel="nofollow noreferrer">allow others to view and fork your repository</a>. However, I wouldn't expect many outside contributors. Why should I give you my hard work if you're just going to turn around and make money on it? That's essentially free labor.</p>

<p>I'm not aware of any listing of vetted licenses that are designed for commercial use of software, like how the OSI and FSF maintain lists of licenses. There is a <a href="http://www.binpress.com/license/generator" rel="nofollow noreferrer">Binpress license generator</a>, but again, it's not a vetted license. How much stake you put into license generator or some random license you find on the Internet is up to you and the level of risk that you find acceptable.</p>

<p>If you want to make money on your open-source software, you may want to rethink your approach.</p>

<p>In my experience, I've usually seen dual licensing achieve this. One license is a custom written commercial license while the other is a very strong copyleft license, like <a href="https://www.gnu.org/licenses/gpl-3.0.en.html" rel="nofollow noreferrer">GPL</a> or <a href="https://www.gnu.org/licenses/agpl-3.0.en.html" rel="nofollow noreferrer">AGPL</a> (depending on how you intend your software to be used), which forces companies to also open-source their software if they use yours. It doesn't explicitly prevent commercial usage, but many companies will either look for an alternative that has a more permissive license or purchase the commercial license to prevent their software from being required to be open-source as well.</p>

<p>You may also be interested in questions on Open Source about how to <a href="https://opensource.stackexchange.com/questions/tagged/monetization?sort=votes&amp;pagesize=50">monetize open-source projects</a>. There are options out there - selling support and maintenance or related services or selling additional documentation or examples. Under this model, all of your software is free and open source under any of the well-known open-source software licenses, but you make money supporting users of the software.</p>

<p>@Thomas Owens already explained that your license is not a FOSS license because non-commercial is an incompatible restriction.</p>

<p>But note that while it <a href="https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software" rel="nofollow">isn't recommended to use them for software</a>, <a href="http://creativecommons.org/" rel="nofollow">creative commons</a> has <a href="https://wiki.creativecommons.org/wiki/NonCommercial_interpretation" rel="nofollow">non-commercial licenses</a>. </p>

<p>As you want to use a license that doesn't allow commercial use and do the commercial use yourself: this is a dual license situation if the commercial use is along the lines of having customers who buy the software: they need a license as well, and they'll naturally want to have something in addition to the free-to-use version.</p>

<p>A dual licensing strategy with a similar non-commercial software license plus you selling the commercial license could meet your needs. </p>

<p>Note however,</p>

<ul>
<li>that dual licensing has a bad taste at least to part of the FOSS community - you probably need to strike a very delicate balance between asking for contributions and exploiting the result commercially.</li>
<li><p>"commercial" has different meanings in different legislations. E.g. in Germany, courts have decided that a private web page becomes commercial as soon paid ads ads are put on it - even if the income through those ads is negligible. The non-commercial CC licenses are therefore considered to be difficult in the sense that they may not exactly do what you (or your user) thinks it does, and they may scare eligible users away because they are not sure. </p></li>
<li><p>Similarly, while you may have an idea what you'd call private use, it may be much more difficult to define this in a legally sound way. E.g. I'm researcher, and also privately interested in similar questions. E.g. I answer on SE-sites. Is that private use? Or is it marketing of my professional skills and thus commercial? Can the very same use far outside working hours be private if I'm an employee but commercial if I'm freelancer? Depending on the type of software, this gray zone may be a large part of your users.</p></li>
</ul>

<hr>

<blockquote>
  <p>I have a hard time believing that each person or organization has to call in a lawyer that writes a custom license each time, right? With other words, reinventing the wheel all the time.</p>
</blockquote>

<p>You are not required to hire a lawyer to get a license text - you could even write it yourself. More to the point, you can buy model contracts (even with explanations) for all kinds of purposes, including for selling/licensing software. These often have choices where you just tick and fill in the options you need.</p>

<p>Somewhat naturally however, you typically have to buy commercial model license texts whereas the FOSS crowd has made their licenses freely available.</p>
