|
|
|
|
|
by wreegab
4478 days ago
|
|
As a software developer, I want people to use my stuff. Once over the hurdle of writing something that people might find useful, I have to choose a license. When it's a library, I usually choose something without much restrictions, like MIT or Apache v2, or else developer will just go look elsewhere. However there is a project which is a full blown application, and I went GPLv3, because I want anybody to be able to use it, or fork it. However it would bother me if someone was using this project to earn money, as I personally forfeited deriving any income from this project (not even donations). Apparently GPLv3 allows commercial use (I didn't realize that when I picked the license). What license would best match my concerns? |
|
Probably the closest you can get in the form of commonly recognized license that meets those criteria is the Creative Commons Attribution-NonCommercial-ShareAlike license: http://creativecommons.org/licenses/by-nc-sa/4.0/. It was designed for creative works (books, movies, music, and so on) rather than software, so it doesn't address some technicalities that come up in the software field, but it is a license which allows modification and redistribution but not commercial use.
However, you have to ask yourself, why do you want to do this? Are you planning on selling the software commercially yourself? If someone else happens to make some money by adding features to your software and releasing them back to the community for anyone to use (which they are required to do under the terms of the GPL), does that actually hurt you? Or if they don't change it and just sell it straight, why would anyone buy that over the free version?
Why did you voluntarily forfeit making any money, even donations? Would you accept donations if offered? How about accept a contract to add a particular feature? If you won't accept that, why would you want someone else not to be able to accept such an offer to add a given feature? If your users are willing to pay for development, but you don't want to accept the money, should someone else not be able to accept the money, put the work in, and release their changes under the same license?
I would recommend sticking to the GPLv3. Most of the kinds of commercial use that are actually objectionable, like adding proprietary features and selling that version at a premium, are not possible under the GPLv3.