3 ms·
The solution seems quite simple: If you don't like the GPL, don't develop themes for WordPress.
by icey 16y ago
The solution seems quite simple: If you don't like the GPL, don't develop themes for WordPress.
- tzs 16y agoThe solution is if you don't like GPL, don't copy GPL code from WordPress when you make your theme.
- mseebach 16y agoThat's not at all simple. The corollary of that statement is "if you don't like the GPL, don't develop applications for GNU/Linux".
- pmjordan 16y agoIf you dislike it enough not to use any GPLed software, sure. The GPL specifically distinguishes between code running as part of the same "application" or not. In fact, the kernel itself has a clarification. GCC itself is GPL, but its libraries (along with glibc) have an exception that permits linking against non-GPL software.
- icey 16y agoWordPress states explicitly that it considers the PHP portion of themes to be GPLed. Seems pretty simple to me.
- slantyyz 16y agoWordPress states explicitly that it considers the PHP portion of themes to be GPLed. That they consider it a derivative work is their -legal opinion-. Remember their license still doesn't supercede local laws and a court could invalidate Wordpress' legal opinion of what a derivative work is.
- stoney 16y agoFurthermore, it doesn't matter what WordPress considers to be GPLed or not, what matters is what it says in the license.
- pmjordan 16y agoWhether non-copied code imported via PHP's include() statement is covered by the GPL is up to the lawyers to decide, but personally, I'd say if your code explicitly calls GPL'd functions (as opposed to via a callback or so) or subclasses GPL'd classes, you're asking for trouble. If your code happily runs outside WordPress, you have a much better argument.