A Software License That's Libre But Not Gratis?
duncan bayne writes "My company is developing some software using Ruby. It's proprietary software — decidedly not free-as-in-beer — but I don't want to tie my customers down with the usual prohibitions on reverse engineering, modification, etc. After all, they're licensing the product from us, so I think they should be able to use it as they see fit. Does anyone know of an existing license that could be used in this case? Something that gives the customer the freedom to modify the product as they want, but prohibits them from creating derivative works, or redistributing it in any fashion?"
IANAL, but if you are not imposing a EULA, you shouldn't need any kind of license. End-user licenses restrict what can be done with the copy of the software that is owned. Licenses like the GPL restrict what can be done when redistributing the software, but impose nothing on the end-users. If you are not wanting to permit your end-users to redistribute, simple copyright is enough to protect your rights without the need for an additional license. If the software is not being redistributed and you aren't requiring a EULA, then the end-users are free to modify the software as they see fit (or do anything with it, except redistribute) under existing copyright law. So it seems copyright law as-is protects you from redistribution and permits your users the ability to modify the software, without the need of any license.
I have come here to chew memory and kick ass... and malloc() is returning a null pointer.
um, like, hire a real lawyer. really, dude.
which was the name of Microsoft's family of "not quite open source" licenses a few years back. Several products allowed you to examine the source code but do little else. I don't think they even allowed you to modify and recompile it in those days, but they've since replaced it (IIRC) with the "Microsoft Permissive License" which might be less restrictive.
One product I remember was Rotor, a sample implementation of the .Net Common Language Runtime (similar to Mono but not as comprehensive). Another was the WTL Win32 GUI framework, which was an alternative to MFC based on ATL (Active Template Library).
Slashdot was even more heavily anti-MS a few years ago and there used to be withering sarcasm at any mention of "Shared Source"... not so sure about today.
gives the customer the freedom to modify the product as they want, but prohibits them from creating derivative works
Modifying the product is creating a derivative work.
My company is developing some software using Ruby. It's proprietary software â" decidedly not free-as-in-beer â" but I don't want to tie my customers down with the usual prohibitions on reverse engineering, modification, etc. After all, they're licensing the product from us, so I think they should be able to use it as they see fit.
Look into selling them a copy of your software, instead of a license to use a copy of your software. US copyright law does permit people who actually own a copy of software to make certain kinds of modifications (don't recall what exactly), make the needed copies to actually use it (disk -> ram, etc), and such.
It is unlikely that the person licensing the software is their sole customer, or that they paid for all or even a majority of the software development. When you are a small company who has any interest in building some "equity" from the work you get, you will be constantly be operating in a mode that is neither simply selling shrink-wrapped software or being paid to write software as work-for-hire but a mix of the two. I've never been directly involved in this sort of work, but from what I've seen on the outside, the terms and rights appear to be handled more through contracts than licenses.
Something that gives the customer the freedom to modify the product as they want, but prohibits them from creating derivative works, or redistributing it in any fashion?"
This question shows a total lack of understanding for what "libre" software is.
A license along those lines would not be "libre but not gratis". Being freely redistributable and allowing derived works are core parts of "libre" software.
All the common definitions of "libre" software (OSF, DFSG, etc) include statements like:
"Free Redistribution
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale."
and:
"The license must allow modifications and derived works"
rage, rage against the dying of the light
When I wrote:
I meant to imply the redistribution of derivative works there.
Obviously, modifying the software in-house counts as a derivative work, and I'm okay with that - just not with the idea that customers would then onsell or give away the modified product to other potential customers.
I hate replying to car analogies, but here goes:
You can buy a car and do whatever you want with it, but this will void the warranty and the manufacturer will not support you if it breaks down.
You can sell the car, but NO WAY are you allowed to copy the car and sell those copies. Say if you own a car factory, you're not allowed to buy one Ford F100, then reverse-engineer it and sell identical copies as Ford F100s. Nor are you allowed to change, say, the colour of the upholstery, then sell the whole thing as your own work. No way. It's not just the electronic media that has these restrictions.
sustainable living
Radiator (a commercial Radius server) is provided with source code. Their license is at http://www.open.com.au/license.html. I just read it (again), and the legalese seems rather complete, you just have to remove the sentence saying that derivative works are not permitted, and replace it with something saying that the Licensee is permitted to modify the work for his own use as he sees fit but that any such modifications are to be considered part of the licensed work and may not be distributed to anyone except back to the Licensor . . . but since your company's money is involved you should go ask your local copyright lawyer what he thinks :-0