views:

691

answers:

3

Does anyone know a commonly used closed source license that allows non-commercial use of a library? I would like to provide a free (as in beer) version of the library but I don't want to release source code and I don't want people to make money with it without my permission.

The reason for not giving away the source code is because I don't want the library to start leading it's own life outside my control. If you have any good suggestions to avoid that, I'm interested as well.

+5  A: 

Check out BSD licences and see if these suite you. I personally like this, because it doesn't obligate me to release source code. Of course, if you own the copyright to the original you have even more free range. Also, many licenses can be described as "BSD-like", that is, they look like the BSD license, but have extra- or change some clauses.

Checking out the related link How to write a basic closed-source license for a software project?, Charlie Martin has a great suggestion, and it's the law. Legal advice can only be given by a licensed attorney ;-)

Update: On thinking of your desire for "people not to make money off of it", you may want to bookmark and look at the Creative Commons license builder. It seems like you can specify what you want out of it, and it fills in a template. I've come across a lot of projects, personally, that use some form of Creative Commons license, and they've undergone several revisions over the last several years. Check it out, see if it suits you. I'm guessing that you'll check "Non-commercial" and either "No-derivative" or "Share-alike".

maxwellb
Basic BSD allows the user to do almost anything: "allowing unlimited redistribution for any purpose as long as its copyright notices and the license's disclaimers of warranty are maintained". It doesn't match my "if you make money with it, so should I" requirement.
Ron
+1 for the Creative License Builder.
musicfreak
Thanks for the CC link. I will look into in detail and check the answer if it suits me. I'm bit puzzled about the derived work, since it's a library you should be allowed to make derived works I guess, but I better read the full text. At least the non-commercial part is covered.
Ron
Ron, check out each one individually, but also take a look at http://creativecommons.org/licenses/by-nc-sa/3.0/us/ for the Share-Alike version. This may be what you're looking for, too. This is also available through the license builder by selecting the appropriate option.After selecting a license you feel comfortable with, I would recommend reading the full text of whichever license you come across, and even have some peers let you know "if it makes sense to them", given your goals.Good luck!
maxwellb
A: 

If you own the library, simply release it under any terms you want.
You don't have to release the source code, normally a header and a .lib/.a or .so/.dll would be enough.

Martin Beckett
It's probably better to use one of the popular licenses out there for something like this because you don't want to create a loophole for yourself.
musicfreak
It's all my code so indeed I do whatever I want, but like musicfreak says, I'm really looking for a "popular" license.
Ron
+2  A: 

The Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 license sounds like what you want.

Iceman