Everyone knows that the GPL is being commonly violated by companies that just don't care and developers who don't understand it. Any US legal precedent around GPL would be welcome.
Everyone knows that the GPL is being commonly violated by companies that just don't care and developers who don't understand it. Any US legal precedent around GPL would be welcome.
[1] https://github.com/WordPress/WordPress/blob/master/index.php
[2] https://www.gnu.org/licenses/gpl-howto.en.html
[3] https://github.com/WordPress/WordPress/blob/master/license.t...
[4] https://github.com/WordPress/WordPress/blob/master/wp-conten...
[5] https://www.gnu.org/licenses/gpl-2.0.html See term 7.
As it stands there semm to be two readings from this: 1) the plugin is not part of the GPL code and de-facto unlicensed ("All rights reserved"), meaning the plugin can not be included in GPL redistributions of Wordpress; or 2) the plugin is part of the code and the code is therefore not eligible to be distributed under the GPL in the first place.
The existence of non-GPL plugins without a proper exemption however might be problematic for re-distribution of the bundle in other GPL software. It could be argued that the plugin in question isn't part of the code covered by the GPL but then the official Wordpress distribution itself is obviously also not entirely GPL and can't be redistributed fully under the GPL.
For an example of partially GPL-compatible software re-distributed under GPL consider the program formerly known as IceWeasel: https://en.wikipedia.org/wiki/GNU_IceCat (a modified version of Firefox minus the proprietary branding).
¹ Only 15% of works were renewed after its initial 28 years of protection, which just goes to show the insanity of the current default duration.
I guess a big part of the reason is that suing in Germany is costly, but not "you'll be poor for the rest of your life" costly.