Trust is lost forever. These are good times for Wordpress alternatives to shine.
Ghost.org seems pretty cool.
Ghost (and similar companies) probably can't believe their luck with this Wordpress debacle.
The ACF plugin on the WordPress directory has been taken over by WordPress.org
41–50 of 236 posts
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#42A lot of the comments seem to call out Matt (right or wrong). But that’s the easy thing to do. No one dares address the systemic issue of for profit corporations exploitatively (ab)using open source software. There is a social contract that people should contribute back, and while it’s largely unenforceable, as it should be, when it’s happening on a systemic level something has to be done. And we are all complicit if…
> No one dares address the systemic issue of for profit corporations exploitatively (ab)using open source software.
Calling out Matt and Automattic for their abusive behavior is addressing the systemic issue of for-profit corporations exploitatively abusing open source software.
We're talking about a company that released GPL software, waited a decade for another company to build their entire business around said GPL software, and then came at them with threats of going to "nuclear war" (their words) with them if they didn't agree to extremely exploitative terms on top of the GPL licensing under which the software was released.
That is the affront to Free Software that's happening here. WP Engine may or may not be a good company, but it is Matt who has given up on freedom. If you lure people in with a promise of Free Software and then hold a gun to their head when they take you up on it, you are the bad guy.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#43This is definitely going a bit too crazy. I sympathized with Wordpress a lot in the initial drama, but this is going downhill fast. Blocking somebody's access to the plugin repository, not accepting their patches, and then 'releasing' your own 'secure' version is just abuse, period.
It's not inherently abusive, consider NPM resurrecting an earlier version of leftpad against author's wish.
Who should provide security updates to an open source package when author no longer has access to the repository - voluntarily or otherwise?
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#44Matt has been busy being a tool https://bullenweg.com/ I feel for everyone that uses Wordpress.
Why on earth is Matt’s nosebleed on this? Making fun of peoples medical issues is tasteless, and makes me wonder about the motivation behind the rest of the page.
They are making a not-subtle insinuation that he’s engaging in stimulant drug abuse.
How that relates to an executive engaged in sudden extremely aggressive and over the top and highly personal scorched earth attack campaign over what appear to be fairly routine open source community squabbles is left as an exercise for the reader.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#45This is definitely going a bit too crazy. I sympathized with Wordpress a lot in the initial drama, but this is going downhill fast. Blocking somebody's access to the plugin repository, not accepting their patches, and then 'releasing' your own 'secure' version is just abuse, period.
It's not inherently abusive, consider NPM resurrecting an earlier version of leftpad against author's wish. Who should provide security updates to an open source package when author no longer has access to the repository - voluntarily or otherwise?
> updates to an open source package when author no longer has access to the repository
Give them the access. It's not like they forgot the password or are AWOL.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#46Calling it right now: If WP Engine is reading, fork WordPress now. Call it FreshPress. Put $25M into it, team up with other hosts, abandon the editor everyone hates, and relicense it to GPLv3 so Matt can’t have any of it. (Note that WordPress’s license specifically says GPLv2 or later.) Maybe support Composer like sane modern PHP projects. Maybe put the most important plugins like Woo into core and make it an all-in-…
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 free of Matt. There’s plenty of low hanging, long ignored gripes and opportunities for improvement. Offer a better, Matt-free product, and you’ll win.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#47A lot of the comments seem to call out Matt (right or wrong). But that’s the easy thing to do. No one dares address the systemic issue of for profit corporations exploitatively (ab)using open source software. There is a social contract that people should contribute back, and while it’s largely unenforceable, as it should be, when it’s happening on a systemic level something has to be done. And we are all complicit if…
> No one dares address the systemic issue of for profit corporations exploitatively (ab)using open source software. Calling out Matt and Automattic for their abusive behavior is addressing the systemic issue of for-profit corporations exploitatively abusing open source software. We're talking about a company that released GPL software, waited a decade for another company to build their entire business around said GPL…
[deleted]
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#48I Left wp development when gutenberg came out, it was clear that things would have turned for the worse.
Since then basically no new features only new bugs on an editor the majority didn't want and still doesn't.
Now this. It feels good to be right and see things turned even worse than expected but what a waste.
Wp could have improved so much and done so much more for entrepreneurs and startups.
Instead they are stuck in 2018
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#49Matt 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.
Re: The ACF plugin on the WordPress directory has been taken over by WordPress.org
#50This is definitely going a bit too crazy. I sympathized with Wordpress a lot in the initial drama, but this is going downhill fast. Blocking somebody's access to the plugin repository, not accepting their patches, and then 'releasing' your own 'secure' version is just abuse, period.
It's not inherently abusive, consider NPM resurrecting an earlier version of leftpad against author's wish. Who should provide security updates to an open source package when author no longer has access to the repository - voluntarily or otherwise?
That would be more compelling if the only change was the security patch itself. Maybe a link to the “only supported” fork.