Disheartening actions by a petulant child.
The ACF plugin on the WordPress directory has been taken over by WordPress.org
81–90 of 236 posts
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#82Disheartening actions by a petulant child.
You're giving him too much credit.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#83It's very funny that Matt's original complaint was that WPEngine didn't contribute enough, and he has now banned them from contributing and stolen what they had previously provided
Do you think they were all of the sudden going to dramatically start contributing? I see this more as symbolically shutting them out. Nothing in this ongoing situation is about more than optics now
They were already contributing as evidenced by the existence of ACF.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#84This is the press release explaining the move - https://wordpress.org/news/2024/10/secure-custom-fields/
the linked site[1] got deleted.
[1]: https://wordpress.org/support/topic/future-updates-for-acf-a...
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#85Matt has been busy being a tool https://bullenweg.com/ I feel for everyone that uses Wordpress.
He's never really been a good person or savvy in general and IMO people put him on pedestal before recently. This is the guy who bought tumblr and hasn't done anything of merit with it after all.
I thought Tumblr given its 'content' is beyond any redemption.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#86Earlier quoted context omitted.
What is the significance of going from GPL v2 to v3 here?
GPLv3 code can’t go into a GPLv2 project - but “GPLv2 or later” licensed code can go into a GPLv3 project. The main reason is that Matt wouldn’t be able to freeload without relicensing WordPress - which would be a massive headache for him and his partners to go through; and the reason would be patently and embarrassingly obvious. The goal I described earlier is not to make a WordPress clone that just happens to be fr…
> GPLv3 code can’t go into a GPLv2 project - but “GPLv2 or later” licensed code can go into a GPLv3 project.
Has this been proven in court, not implying the legality would be respected in this case though.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#87Matt you've lost the plot, time to step down or put independent governance in-place. How can you expect any developer to devote time to writing a plugin if the dictatorship of Matt can rug pull it at any time.
This action is astonishing in its malignity. At this point I'm simply hoping for Matt Mullenweg to be excruciated in court.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#88Does anyone want to play armchair internet psychologist with me to speculate as to Matt's thinking here? My guess is that he was focused on these facts: 1) I own Wordpress 2) WPEngine is profiting from Wordpress and I'm not benefiting 3) This is unfair And it was stuck in his mind like a thorn, irritating him whenever the thought arose, and never went away. Commercializing open source is hard for myriad reasons, but…
I hate to speculate, especially from a distance. But I do wonder:
- Why now? What snapped? Clearly WPE didn't go to "billions" over night. So why go nuclear now?
- Doesn't he have a close and immediate circle of advisors and confidants? Are they speaking to him and he's not listen? Or has he locked himself in a room so to speak and is completely unapproachable? Either way, not good.
- Is he trying to force WPE to fork WP and then maintain their own version? Does he believe they can't do it? What if WPE's hosting peers unite and abandon what is effectively Automattic's version?
Am I the only one who can't imagine a good outcome from all this?