Matt Mullenweg deactivates WordPress accounts of contributors planning a fork

This isn’t unexpected; I’ve been deactivated on Slack since very early in this dispute, and later banned from the issue tracker as well. I’ve been contributing for 20 years to the project, am a committer, and built several large parts of WordPress including the REST API.

Matt is banning anyone who speaks out at all, even when they agree with points he’s made. A large group of contributors felt they had to make an anonymous statement from fear of the same retribution I suffered: https://www.therepository.email/core-contributors-voice-conc...

(I am a less active direct contributor these days, so I’m still able to contribute even while blocked - but many people’s livelihoods depend on it, as sponsored contributors.)

Honest question from an outsider. WordPress is open source, so why hasn't the project been replaced with one that doesn't include him?

WordPress is a lot more than it's core code. There's a whole ecosystem of plugins, for example, and the usual place to share them (wordpress.org/plugins) is, essentially, controlled by one guy. It's not so easy to fork that.

Then start with a new place to share plugins.

The first people to take this step will most likely have their plugins stolen, just as Matt did with ACF. This means taking this step is a massive danger for the first contributors - those with the highest impact are those with the most to lose.

What do you exactly mean with „stolen“? Honest question.

Matt's company will fork your project, replace your original plugin listing and claim all your reviews as theirs, while also stopping you from distributing security updates to force people to switch to their fork.

Imagine if you make your money from selling your plugin, and Matt does this to you. Every WP plugin developer has to live in fear of this happening at any moment, and you can be certain it will happen if you show any kind of resistance towards Matt.

I'd suggest guerilla-scraping the entire plugin site under the radar, unbeknownst to them. Go live with a new site that simply has all the same directory data as the existing site and additional mirror site links for each plugin, And create a process for plugin authors to claim the existing page in the directory.

Matt may be able to fork plugins, but they won't be able to fork every single plugin in the directory, as it isn't very feasible.

It also would then not necessarily be obvious to Matt which plugin listings in the new directory have been claimed, and which plugins are being updated by other people from the community.

Sounds fun. You would only have to provide listing editing if the plugin is not on the other site.

If anyone fills a complaint and can prove ownership a redirect can be provided.

Could maybe perhaps train an llm on a plugin and have it assist.making a free or not bloated version of some popular ones.