Help me choose an Open-Source license

Posted by Spartan-117A on Programmers See other posts from Programmers or by Spartan-117A
Published on 2011-02-20T23:49:47Z Indexed on 2011/02/23 7:33 UTC
Read the original article Hit count: 276

Filed under:
|
|
|
|

So I've done lots of open-source work. I have released many projects, most of which have fallen under GPL, LGPL, or BSD licensing.

Now I have a new project (an implementation library), and I can't find a license that meets my needs (although I believe one may exist, hence this question).

This is the list of things I'm looking for in the license.

  1. Appropriate credit given for ALL usage or derivative works.
  2. No warranty expressed or implied.
  3. The library may be freely used in ANY other open-source/free-software product (regardless of license, GPL, BSD, EPL, etc).
  4. The library may be used in closed-source/commercial products ONLY WITH WRITTEN PERMISSION.

GPL - Useless to me, obviously, as it completely precludes any and all closed-source use, violating requirement (4).

BSD/LGPL/MIT - Won't work, because they wouldn't require closed-source developers to get my permission, violating requirement (4). If it wasn't for that, BSD (FreeBSD in particular) would look like a good choice here.

EPL/MPL - Won't work either, as the code couldn't be combined with GPL-code, therefore violating requirement (3). Also I'm pretty sure they allow commercial works without asking permission, so they don't meet (4) either.

Dual-licensing is an option, but in that case, what combination would hold to all four requirements?

Basically, I want BSD minus the commercial use, plus an option to use in commercial/closed-source as long as the developer has my written permission.

EDIT: At the moment, thinking something like multiple-licensing under GPL/LGPL plus something else for commercial?

© Programmers or respective owner

Related posts about library

Related posts about open-source