←back to thread

221 points michaelcampbell | 2 comments | | HN request time: 0.929s | source
Show context
dmje ◴[] No.41831511[source]
Long time WordPress agency owner here.

At the heart of this - if you consider it generously - is a principle that we can possibly all sign up to, namely that "large commercial entities" should (should from a moral, not legal standpoint) "pay back" to the open source software that makes them money.

The principle however has been totally undermined by MM's actions, which have been completely out of line. His behaviour has been abhorrent. I've been shocked (possibly naively) that a single individual could have such huge power over an open source project that they could literally turn it off (referring here to the update mechanism that WPEngine was using).

I've been even more shocked and appalled by this plugin takeover. ACF is a central piece of pretty much all WP developers' / agencies toolkit. Those of us who have been in this game a long time remember WP before it, and the breath of fresh air that it was to finally be able to define complex relationships between posts and provide our users with a GUI that actually worked well for complicated sites. ACF have pushed and supported this technology for years and years - firstly under the expertise of Elliot Condon, now under the aegis of WPEngine. I know some of the developer team at ACF personally - they're excellent people, making brilliant code, and most of them are putting huge efforts into WP as an open source project even aside from their efforts in maintaining and extending ACF.

The forking of a plugin is one thing. A fair way to do this would be to fork it, and start from zero installs. Automattic could have done that, promoted the hell out of "SCF" and got users in a way that was at least slightly (?) fair.

Simply switching the name and keeping the slug - and thus the 2+million sites - should be thought of as theft. It's outrageous, it's totally petty, and I so far haven't seen a single person being supportive of this (probably?) unilateral action by one - apparently increasingly unhinged - individual.

The wider problem of course is the effect this has on the vibrant WP ecosystem which as someone else in this thread has pointed out is a critical (erstwhile) open cornerstone of the web.

I am still hoping that this will subside into history and it'll all sort but it has left me and many WP devs I know with a pretty bitter taste.

replies(4): >>41831557 #>>41832228 #>>41834729 #>>41837993 #
1. lolinder ◴[] No.41832228[source]
The irony of this move is that his main argument to keep people on his side over this has been that WP Engine has not been contributing. He's been saying over and over that he's doing this because they're not giving back.

Now, when he's already failed to bring the community on board with his attacks, he decides that his next move is to make a big show of stealing something that had he done nothing many people would not have realized was a WP Engine property, with the net effect of reminding people that WP Engine has been responsible for maintaining what is widely considered to be the most essential plugin in the ecosystem.

But that doesn't count as giving back because... reasons.

replies(1): >>41832376 #
2. ValentineC ◴[] No.41832376[source]
> Now, when he's already failed to bring the community on board with his attacks, he decides that his next move is to make a big show of stealing something that had he done nothing many people would not have realized was a WP Engine property, with the net effect of reminding people that WP Engine has been responsible for maintaining what is widely considered to be the most essential plugin in the ecosystem.

> But that doesn't count as giving back because... reasons.

I haven't used WordPress in years, but I've seen recent comments saying that WP Engine has been using ACF to market their hosting packages, even giving customers a "4 month trial" — not something a hosting provider really wants to see.