Earlier this year, I posted a message about my goal: I want to run a business or entity (or whatever) where developers come when THEY want to build stuff. It's paraphrasing a bit, but that's because I worded things in that post a little strangely. But what has been holding me back? Is it my code, or... what?
Back in the day, when I open-sourced a bunch of my code, I had to make some arbitrary decisions regarding licensing. I didn't know how I should license these libraries, or how I was going to use them, I just knew they needed to get out into the light of day. At the time, it seemed like the best licensing scheme was to go with the GNU Public License (or "GPL").
To be honest, I haven't really thought about that decision much for many, many years, until just recently. At work, I've been working with a new client to build an application for them. Suffice it to say, it was determined that this particular application would be a PHP-based web application. I was very excited, as I very much love to build web applications in PHP... that's when it hit me.
We talked about some implementation concerns, about implementing frameworks, when Darkman revealed that we wouldn't be able to use frameworks that were GPL'ed (that is, licensed under the GNU Public License). I realized immediately that this meant I couldn't use my own code the way it was, and we agreed to use CakePHP... and that my libraries would probably never be used for any commercial application if they remained under the GPL.
During the course of reading about CakePHP, I realized that it was their licensing that lead to such seemingly wide-spread adoption: they used the MIT license. It's a very open license, which allows it to be used for commercial applications without having to be open sourced themselves.
And finally we get to the point: I've dual-licensed my core libraries/frameworks: both under the GPL and MIT licenses. That means they can be used in commercial applications and wider adoption.
Without further ado, here are the libraries and the corresponding versions that have been dual-licensed (more will be updated in the future):