News for hackers. Stuff that matters.

A comment on WordPress.org's latest move involves taking control of a WP Engine plugin.

Re:WordPress.org's latest move involves taking control of a ... by shdon on Sunday October 13, 2024 @04:26AM (#41826178)
Mullenweg calls it a fork. I could see that being somewhat okay if it's indeed for security fixes, but removing the upsells is petty at the very least. But a fork doesn't take control of the original, so I wonder what they did there? Perhaps a redirect from the ACF entry to SCF?

To be honest, none of this makes WordPress look good... It just seems like a douche move.

[ Parent | on HN ]
Re:WordPress.org's latest move involves taking control of a ... by k1kingy on Sunday October 13, 2024 @06:54AM (#41826910)
It can hardly be called a fork when you wipe every mention of the original dev team in the codebase, and start a fresh changelog with 'Patched security fixes' whilst thanking his team. It's an absolute takeover not a fork.
[ Parent | on HN ]
Re:WordPress.org's latest move involves taking control of a ... by mananaysiempre on Sunday October 13, 2024 @07:28AM (#41827048)
The thanks come from the upstream release notes for 6.3.8, FWIW.
[ Parent | on HN ]