News for hackers. Stuff that matters.

A comment on Wordpress.org bans WP Engine, blocks it from accessing its resources. Parent comment

Re:Wordpress.org bans WP Engine, blocks it from accessing it... by rpgbr on Thursday September 26, 2024 @03:09PM (#41662023)
Under GPLv2, WP Engine has no obligation of pay the ransom Matt is demanding no matter the revenue they make.
[ Parent | on HN ]
Re:Wordpress.org bans WP Engine, blocks it from accessing it... by teruakohatu on Thursday September 26, 2024 @04:03PM (#41662641)
But nor does the WordPress foundation need to WP Engine, or any user, access to the plugin library.

Chromium is Open Source, but Google is not required to allow Add On store access (even if they tolerate it from chromium forks).

[ Parent | on HN ]
Re:Wordpress.org bans WP Engine, blocks it from accessing it... by Touche on Friday September 27, 2024 @03:48AM (#41667462)
Requiring they pay the for-profit company to access non-profit resources seems problematic.
[ Parent | on HN ]
Re:Wordpress.org bans WP Engine, blocks it from accessing it... by sinkasapa on Thursday September 26, 2024 @04:01PM (#41662618)
As far as I could tell, they weren't denied use of the code, just a bunch of other services that are not covered by the GPLv2.
[ Parent | on HN ]
Re:Wordpress.org bans WP Engine, blocks it from accessing it... by tylermenezes on Thursday September 26, 2024 @04:04PM (#41662649)
GPLv2 licenses the Wordpress code, not trademarks or the right to use Automattic's APIs.
[ Parent | on HN ]
Re:Wordpress.org bans WP Engine, blocks it from accessing it... by ValentineC on Thursday September 26, 2024 @06:45PM (#41664344)
Before this week, I didn't realise that the WordPress.org servers and plugin repositories fell under Automattic, and not WordPress Foundation.

Some clarity would be nice.

[ Parent | on HN ]