Quote from NevcairielThe GPL does in no way limit what you do inside your own addon. I would really be interested in the part that you claim limits us to use any non-open library in our code?
GPL Module Licensing
If I add a module to a GPL-covered program, do I have to use the GPL as the license for my module?
The GPL says that the whole combined program has to be released under the GPL. So your module has to be available for use under the GPL.
But you can give additional permission for the use of your code. You can, if you wish, release your program under a license which is more lax than the GPL but compatible with the GPL. The license list page gives a partial list of GPL-compatible licenses.
Yeah, your new license doesn't look to be compatible.
Further to the issue..
If a library is released under the GPL (not the LGPL), does that mean that any program which uses it has to be under the GPL or a GPL-compatible license?
Yes, because the program as it is actually run includes the library.
Quote from NevcairielThats like saying you cannot use non-free software on linux..
Uh, no. That's like saying you need to actually read and understand the GPL.
Anyways, IANAL, but it seems pretty clear to me that you're invalidating existing authors licenses with your changes.