Resources to follow WordPress drama

[WhizBee]

You are likely already aware of the WordPress drama that began when Automattic sent a trademark license agreement to WP Engine, followed by WP Engine issuing a cease-and-desist to Automattic.


If you want to stay updated on ongoing events, these resource links may be beneficial:

1. https://mattisnotwp.com/ - There are dedicated pages for WordPress drama timeline, affected plugins, and impacts on other stakeholders (who owns what, who said what, and who got what).
2. https://wpvswpe.report/ (The Timeline is the website )
3. https://gist.github.com/adrienne/aea9dd7ca19c8985157d9c42f7fc225d ( By AlienneLeigh , covering updated news related to the Mullenweg/WPE Thing )
4. https://duerrenberger.dev/blog/2024/10/08/timeline-of-the-wordpress-drama/ (By Lukas Dürrenberger)

If you are aware of any such resources which can be helpful, please suggest in the comment section.

 

[Dopious]

Resources are always nice, nice job collecting.

 

[Megaverse]

Who knows how long this drama gonna last?
I'm becoming irritated with the whole shit..

 

[V]

Who knows how long this drama gonna last?
I'm becoming irritated with the whole shit..

I've been away from the forum for a while. Can you please give me a quick rundown of what all this drama is about? Too drunk and tired to go through all the resources above.

 

[WhizBee]

Major incidents:

• Tensions Emerge: Significant conflicts arise in the WordPress ecosystem, particularly between Automattic (the parent company of WordPress) and WP Engine, a major hosting provider.
• Ownership Clarification: On October 27, 2024, Automattic clarified that WordPress.org is Matt Mullenweg’s personal site, not owned by the WordPress Foundation, surprising many in the community.
• Controversial Emails: Automattic requested that WordCamp organizers delete specific social media posts and surrender login credentials, raising concerns about their control over the community.
• Community Backlash: Key figures like Chris Wiegman and Carrie Dils announced their exit from the WordPress community due to dissatisfaction with Mullenweg's leadership.
• Legal Filings: Automattic filed a motion to dismiss various counts in WP Engine’s lawsuit, asserting their position in ongoing legal disputes.
• ACF Plugin Controversy: WordPress.org took control of the Advanced Custom Fields (ACF) plugin and renamed it Secure Custom Fields (SCF) without WP Engine's consent, leading to widespread issues.
• Community Code of Conduct Revised: A new rule was established prohibiting the publication of private messages without consent, which led to accusations of stifling whistleblowing.
• Mass Employee Exodus: Following Mullenweg's "Alignment Offer," 159 employees departed from Automattic.
• DHH's Critique: David Heinemeier Hansson criticized Automattic's demand for 8% of WP Engine’s revenue, calling it a breach of open-source principles.
• Bans on Contributors: Mullenweg banned several long-term contributors for questioning a new login requirement, raising concerns regarding governance.
• Controversial Checkbox Introduced: A new login requirement asked users to confirm they were not affiliated with WP Engine, further escalating tensions.
• WP Engine's Legal Action: WP Engine initiated a federal lawsuit against Automattic, alleging extortion and misuse of power.
• Public Criticism at WordCamp: Mullenweg criticized WP Engine during WordCamp US 2024 for its low contributions to the project, intensifying the conflict.
• Temporary Lifting of Ban: On September 27, 2024, WordPress.org temporarily lifted its ban on WP Engine but reinstated it shortly after, causing operational issues for affected customers.
• Community Reactions: Members expressed deep concerns regarding Mullenweg's comments and actions, viewing them as harmful to the ecosystem.
• Internal Disputes: Several core contributors left the project due to dissatisfaction with Mullenweg's leadership style and governance issues.
• Promotion of Alternative Hosts: WordPress.org promoted alternative hosting companies providing deals to WP Engine customers amid ongoing disputes.
• Mullenweg's Freedom of Speech Argument: Mullenweg framed WP Engine’s lawsuit as an attack on his First Amendment rights, which faced critical backlash from the community.
• Cloudflare's Offer: Cloudflare CEO Matthew Prince offered resources to support WordPress.org free of charge amidst the conflicts.
  

Detailed timeline: https://mattisnotwp.com/wordpress-drama-timeline/

 

[drehdinho]

Wordpress CEO is acting in contravention of basic law of contract that regulate technology ownership and intellectual property and fundamental right to freedom of privacy in WP engine.

If there had been a business renegotiation controversy between the two companies, he shouldn’t have resulted into self help.

Self help will destroy his case and he may run the risk of multiple damages awarded against him personally.

 

[Megaverse]

I've been away from the forum for a while. Can you please give me a quick rundown of what all this drama is about? Too drunk and tired to go through all the resources above.

I guess you should go check Deleted member 752298 thread

 

[V]

I guess you should go check Deleted member 752298 thread

I know about that case, but this one between WP Engine and whoever? This is the first time I've heard about it!

 

[Megaverse]

I know about that case, but this one between WP Engine and whoever? This is the first time I've heard about it!

That's the genesis of the whole issues. A lot of folks are caught in the middle of it.

 

[UnusualSubstance]

This just got more juicer than a steak.

Damn.

Where's the popcorn at?

 

[Dopious]

Concerned of your WordPress privacy, check this plugin out. Test it on a dev site first.
https://github.com/wp-privacy/wp-api-privacy