For works that we are extremely fond of we’d likely not even choose a license that allows relicensing as GPL as that could create the potential that a downstream licensee might distribute a derivative of our original work that inherits all of the problems that we see above. And we do of course realize that as lengthy as this article has been, it only scratches the surface of the issues it raises, and likely oversimplifies some issues and gets some things wrong.
The above EllisLab comment means, you can’t distribute your CI based application under GPL, because EllisLab dislike GPL. Right?
I can’t understand well the last sentence, because of my poor English skill.
Yep, you understood that well. It means that they just screwed over their community and anyone using Code Igniter will not be able to use any GPL’ed code at all, not even a library based on GPL. Call that cutting of the branch you are already sitting on.
You’d guess they talk with their community first before making a change like that that. I have not seen a real dialogue with the community here. Not even after a week of all the complaints and not even the uservoice which jumped from 0 to 260 votes in just a few days ( http://codeigniter.uservoice.com/forums/40508-codeigniter-reactor/suggestions/2344554-gpl-compatible-non-copyleft-popular-licesne ) seems to be making an impression.
On the contrary, they first change the license, then employ lawyers to find out that they screwed up. But still try to tell us how great OSL is. “Do not take this as legal advice. Ask your lawyer if you want to be sure’. Yeah, right.
The kind of one-way ‘communication’ shown here (Top->down) seems to be typical. You want to discuss with us? We make announcements.
Lets see when the forums start being censored or people get attacked asking for a more compatible license than OSL.
All this just because someone said ‘I do not like GPL. Let’s make the new license deliberately incompatible, too’. Applause! (yes, I am being cynical).