They either have some of the best or worst legal counsel; or they just ignore the legal counsel.
They also have the worst social media team I have ever seen:
WordPress.org's latest move involves taking control of a WP Engine plugin
11–20 of 222 posts
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#12You make an opensource project, provide hosting services, then others take your project, modify it for their needs, cut into your hosting market share and then you try to get rid of them.
...What was the end game plan?
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#13> It’s not clear what security problem Mullenweg is referring to in the post. Where is the CVE? What risk is there continuing to use the original plugin? No details at all. This results in fear: we don't know if the original is safe to use. > Going forward, Secure Custom Fields is now a non-commercial plugin Does this imply that Wordpress is potentially going after a revenue stream from WPEngine? If the plugin had Pr…
> Where is the CVE? What risk is there continuing to use the original plugin?
Here’s the diff showing what has changed: https://plugins.trac.wordpress.org/changeset?new=3167679%40a...
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#14They either have some of the best or worst legal counsel; or they just ignore the legal counsel.
While the situation is much less problematic, I think WordPress management could listen to their lawyers more
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#15Earlier quoted context omitted.
Some people just think they're above the law. This Matt guy has gone mental.
Yeah, but pretty sure some of the employees/volunteers are in on it or "just following orders."
Yes, no one stopped the co-funder and it's unlikely he did the fork and the change of ownership only by himself. Other people at Automattic are responsible too.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#16> It’s not clear what security problem Mullenweg is referring to in the post. Where is the CVE? What risk is there continuing to use the original plugin? No details at all. This results in fear: we don't know if the original is safe to use. > Going forward, Secure Custom Fields is now a non-commercial plugin Does this imply that Wordpress is potentially going after a revenue stream from WPEngine? If the plugin had Pr…
> If the plugin had Pro options* then are those closed source and so not available to Wordpress in their fork of the codebase? It's not clear.
Because WordPress is licensed under the GPL, all plugins must be licensed under GPL-compatible licenses. This applies to ACF Pro as well.
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#17[dead]
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#18You make an opensource project, provide hosting services, then others take your project, modify it for their needs, cut into your hosting market share and then you try to get rid of them. ...What was the end game plan?
[dead]
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#19Mullenweg is hijacking existing users with supply chain attack.
> supply chain attack.
Where's the "attack" part? I thought that was a crucial part in the definition
Re: WordPress.org's latest move involves taking control of a WP Engine plugin
#20They either have some of the best or worst legal counsel; or they just ignore the legal counsel.
They also have the worst social media team I have ever seen: https://x.com/WordPress/status/1845121130207535524
This is wild. Surely Matt isn't tweeting from the official account - marketing would not allow that, right?