mycroft-core

ry a tool like this to generate that type commercial license: http://www.binpress.com/license/generator One of the real advantages of going open for you (the author) is getting help from other people. Often it is small things, but you can get help. Doing a Dual License complicates this. As long as you are the owner of the code you can freely re-license it. But once you accept a code contribution to your GPL code, you cannot legally or ethically just resell that contributed code under the commercial license. So you either: 1) Reject all contributions from other programmers 2) Have two independent branches that might end up diverging 3) Asking every code contributor to grant you a license to also use their code under your commercial license. To me, option #3 is questionable and probably won't fly well if your project takes off. We moved Mycroft (https://github.com/MycroftAI/mycroft-core) from GPLv3 to Apache 2.0. There were various reason for this, but for us the biggest was that business generally avoids GPL code, and in some cases there the regulatory system comes in conflict with the requirements of GPL. For example, if a car brake system has GPLv3 code you are REQUIRED to provide a mechanism so users can replace that code. Good luck getting approval of a car. Even if you did get it approved, the car manufacturers would be terrified of the court cases they'd have to defend -- win or lose. In short, if you don't think it is valuable enough to spend more than $100 on this, then just go with a well-known permissive open source license like MIT. If it takes off, you get famous and can command a high salary somewhere.