The core contributor posted a follow up to their comments to say that they’re not seeing anything positive yet.
“It should be crystal clear in Matt’s mind that what’s happening right now can’t continue. How he chooses to act on that knowledge is anyone’s guess. Unfortunately, what I’m seeing in his messages through all communication channels so far doesn’t show signs of anything positive, yet (as I said in my earlier comment, we’re all watching very, very closely).”
Social Media Reaction
An overwhelming number of the posts on X (formerly Twitter) express disappointment with Mullenweg’s actions and are supportive of WP Engine.
Technology writer Robert Scoble posted:
“WordPress at war. So sad.
I was one of the first to use WordPress. I didn’t see this coming. I read hundreds of posts about what @photomatt did and almost none of them are on his side.
Never seen a decision so universally hated in tech. Lots of my old friends are in pain tonight.”
Typical reaction on X:
“This is absolutely insane and such a disgusting abuse of power by @photomatt. I have clients using @wpengine and now they can’t easily install plugins or update themes. #WordPress”
Another WordPress user posted:
“Gotta say, I’m with WP Engine on this. Not saying they are the “good guys” but if we all have to pay Automattic for using the word “WordPress” in our marketing, then we’re all in trouble. This sets a dangerous precedent.”
Read Mullenweg’s post on WordPress.org
WP Engine is banned from WordPress.org
Read the WP Engine Incident Report:
Plugin and Theme Update Restrictions
Featured Image by Shutterstock/Wirestock Creators