7 comments posted · 2 followers · following 2
"I used it because it was free at the time I bought it."
Bought it for free, huh? ;-)
My recent post Great Artists Still Steal
Off hand I think it is generally really expensive. Particularly, with ~3 releases a year. It also encourages some of passive development community to sit on older versions.
The WordPress 2.0 Legacy branch was a good experiment, but recently retired earlier than planned:
Having one supported version (+1 sometimes when new major version) is also most manageable for WordPress citizens.
Having said that was anyone:
* Providing details on how to do this effectively?
* Volunteering to take (some of) this on?
Linus Torvalds added an additional section to the Linux Kernel license that clarified that "This copyright does *not* cover user programs that use kernel services by normal system calls", but without that section that is not the interpretation of the GPL by the FSF as it applies to modules, and that is why the FSF also provide an LGPL license.
<a href="http://ftp.sunet.se/pub/os/Linux/kernels/COPYING" target="_blank">http://ftp.sunet.se/pub/os/Linux/kernels/COPYING
Your statement "That would mean a plugin would be a separate work, and would only have to be licensed under the GPL if it was distributed with WordPress itself." is close, but not quite right I think. Here is a clarified version:
That would mean a plugin would be a separate work, and would only have to be licensed under the GPL if it was distributed with WordPress *code*." Calls to WordPress functions is WordPress code. So, you can distribute (your code) the same code without the WordPress functions under any license you like -- seems obvious, but that is what that legalize is describing explicitly.