Which license should I use for my open source project?

Question

I have an open source project that I am working on and am trying to figure out which liscense will be the best. In fact, my project is the foundation that developers will use to create their own projects.

The vision I received for licensing the project (in plain English):

• The user should not sell the source code or any derivatives.
• The user should not sell the framework or any derivatives.
• The user has the right to sell a program that uses the framework.

Basically, I just don’t want anyone to abuse the open source aspect of the project, take what I did, turn around and sell it.

Any suggestions for a good license to use for this?

thanks

Answer 1

You described something similar to LGPL .

I DO NOT LOVE

---

Under LGPL you can associate yourself with the library, and the rest of your application should not be distributed with the LGPL license - it can be any license you want, but the source code of the library should remain available under LGPL, However, if you change the library and distribute it The new modified library should also be LGPLed.

Technically, someone could sell a derivative work, but once this work was distributed to even one person, that person could freely distribute it to everyone they want.

Answer 2

Look to increase the license .
It is small, easy to read, accepted by sourceforge and fits your vision. His goals, copied directly from the page linked to above, are as follows:

• It should be easy to read and understand.
• Must provide permission without charging fees for copying, using and modifying software for any use (commercial and non-commercial).
• The license must appear with all copies [including redistributions] of the software source code.
• You do not need to require the license to be displayed with executable files or other binary uses of the library.
• It is not necessary to require that the source code is available for execution or other binary uses of the library.