WordPress Drama Timeline

WPisLoveOctober 21, 2024
Keep this handy—bookmark it for later!

The WordPress ecosystem has been a crucial platform for millions of websites, but recent events have revealed deep-rooted tensions and controversies that challenge its core principles. This timeline chronicles the significant moments in the ongoing conflict between Automattic, the company behind WordPress, and WP Engine, a leading managed hosting provider.

Beginning with the origins of WordPress, this timeline highlights key incidents and notable controversies that have shaped the community over the years. Join us as we navigate through this unfolding drama, reflecting on how these events may influence the future of one of the internet’s most popular content management systems.

Note: This timeline is regularly updated as new events come to light. If you would like to contribute, please submit news along with a source link for verification.

Timeline ToC

October 27-31, 2024

51. Tensions Rise in the WordPress Community. TechCrunch Interviewed Matt

Emails, Control, and Departures Highlight Ongoing Conflicts
  • October 27, 2024: In response to WP Engine’s recent motion, Automattic referred to WordPress.org as Matt Mullenweg’s personal website via X. This clarification confirms that WordPress.org is his property and not owned by the WordPress Foundation, a revelation that has taken the WordPress community by surprise.
  • October 27, 2024: Via Kellie Peterson on X – Emails revealed Automattic’s demands for WordCamp organizers to delete specific social media posts and surrender login credentials for their accounts.
  • October 28, 2024: Morten Rand-Hendricksen shared a personal story highlighting Matt Mullenweg’s long-standing control over WordCamp events since 2011.
  • October 28, 2024: The founder of WordCamp Asia expressed concerns on Reddit that new ticket purchase requirements, including mandatory WordPress.org account registration, could negatively affect attendance.
  • October 28, 2024: Jason Coleman, dev of the Paid Memberships Pro plugin claimed they received threats from Mullenweg regarding their listing on WordPress.org after they attempted to remove it. This claim was backed by screenshots confirmed by The Repository. They have now removed the plugin from WP repo
  • October 28, 2024: TheRegister published an article with title: WordPress forces user conf organizers to share social media credentials, arousing suspicions. It also mentions an incident in which WordCamp Sydney was asked to take down posts that said nice things about WP Engine
  • October 28, 2024: Chris Wiegman announced his departure from the WordPress community, criticizing the toxic environment fostered by Mullenweg and Automattic.
  • October 29, 2024: Carrie Dils publicly announced her decision to stop volunteering for the WordPress project due to dissatisfaction with Mullenweg’s actions.
  • October 30, 2024: Matt appeared in an interview with Connie Loizos, Editor-in-Chief, on Day 3 of TechCrunch Disrupt 2024. He stated that a fork would be “fantastic.” He added that the company, Automattic, is currently “very short-staffed.” Before the conflict began, Automattic had roughly 1,900 employees, but the headcount is now around 1,700.
  • October 30, 2024: In an article titled ‘Democratising publishing’, John O’Nolan says, the founder/CEO of Ghost said: “Having seen how things worked on the inside for several years, the conclusion I personally came to was that WordPress and Automattic were not truly about democratising publishing, after all. We build Ghost with a simple, permissive MIT license. No GPL drama.”. 
  • October 31, 2024: Matt Mullenweg recently appeared on TechCrunch Disrupt 2024, you can watch it on YouTube. In legal developments, Automattic has filed a motion to dismiss “Counts 1-6 and 9-11 of the Complaint” (Source: Court Listener). Additionally, Mullenweg submitted a declaration supporting Automattic’s motion to strike and oppose the preliminary injunction, detailing many actions he has taken in recent weeks from his perspective.
  • October 31, 2024: WordPress questioned Vinny Green about a broken post on FreeWP’s site, doubting the management of a fork while the site seemed dysfunctional. AspirePress replied, stating that FreeWP is not a fork and suggested ways to rebuild community trust. WordPress responded unprofessionally, saying, “We have lots of useful things to do with our funds; sending it to your “masturbatory governance” and repository work that won’t benefit users at all is a waste.” Many users criticized this comment, questioning how it reflects on the official account of an open-source project. The tweet was later deleted but a response from Matt is still live on a related screenshot. 
  • October 31, 2024: The head of Customer Success at WooCommerce, an Automattic-owned company, is reportedly cold-emailing WP Engine customers with offers for a buyout if they transition to Pressable. A (redacted) screenshot of one such email is included in the documentation and was also previously mentioned in Jason Teichman’s Declaration in Support of WPE’s Motion for Preliminary Injunction. The Verge has covered the latest developments, including the Motion to Dismiss.
October 27-31, 2024
October 22-26, 2024

50. Automattic confirms WordPress.org is Matt's own website.

BBC publishes a news article on the WordPress row
  • October 22, 2024: WordPress’ lawyers file their opposition to the motion, asserting that WordPress.org is Mullenweg’s personal site, which he controls independently of Automattic and the WordPress Foundation.
  • October 23, 2024: The court grants WP Engine’s motion for an expedited timeline regarding the preliminary injunction, setting key dates for responses and a hearing on November 26.
  • October 24, 2024: Reports emerge that Mullenweg attempted to hire Kendrick Lamar to create a diss track about WP Engine, revealed during an internal meeting.
  • October 25, 2024: WP Engine publishes a timeline detailing their efforts to ensure customer safety and continuity amid the ongoing dispute, while the BBC covers the conflict, highlighting its significance.
  • October 25, 2024: WordPress leadership has asked WordCamp organizers to disclose their social media accounts due to security concerns, prompting backlash from community organizers who see it as overreach.

    The situation has resulted in lower ticket sales for events, highlighting concerns about control and the historical context of Automattic’s actions against organizers, fueling fears of a hostile takeover within the community.
  • October 26, 2024: Core contributor Andy Fragen announces a hiatus from WordPress due to the ongoing drama affecting the community.
  • October 26, 2024: Bullenweg, a website which used to cover timeline of events related to the dispute is removed following legal threats from Matt Mullenweg. 
  • October 26, 2024: BBC published an article examining the implications of the dispute between WordPress and WP Engine on global businesses, especially small business owners. It highlighted the uncertainty and operational disruptions stemming from the conflict, emphasizing the potential ripple effects on the broader online economy.
October 22-26, 2024
October 22, 2024

49. WordPress.org is not WordPress

Automattic's Response in WP Engine Legal Dispute clarifying Ownership of WordPress.org
On October 22, 2024, Automattic issued a response to the plaintiff in the ongoing legal dispute between WP Engine and Automattic/Matt Mullenweg. The statement emphasized that WordPress.org is solely Matt Mullenweg’s project, asserting that neither Automattic nor the WordPress Foundation exerts any influence over it. Automattic highlighted that WP Engine is responsible for building its business on top of WordPress.org.
This response drew significant reactions from the community. Douglas Karr (@douglaskarr) expressed strong concerns, stating, “No developer should ever contribute feedback or code to #Wordpress repositories again based on this admission by Matt’s attorneys. You’re just giving your work and intellectual property to him to use as he wishes.” Ryan Duff (@ryancduff) commented on the confusion stemming from the latest filings, stating, “If you weren’t confused before, you will be now. WordPress.org is not WordPress, nor is it Automattic, nor is it the WordPress Foundation.” This exchange further underscored the complexities and tensions surrounding ownership and governance within the WordPress ecosystem amidst ongoing legal disputes.
Reference: (1), (2), (3), (4)
 
October 22, 2024
October 21, 2024

48. Bjørn Johansen Announces Departure from WordPress Community

"Farewell to the WordPress Community"
On October 21, 2024, core contributor Bjørn Johansen published a heartfelt farewell titled “Farewell to the WordPress Community.” In his reflection, he recounted his journey within the community, emphasizing his contributions in organizing meetups, speaking at events, and facilitating Norwegian translations. Johansen expressed deep gratitude for the friendships and experiences he gained during his time in the community. However, he announced his decision to depart due to growing concerns about leadership transparency and collaboration within WordPress, specifically calling for Matt Mullenweg’s removal. He urged those seeking stability to consider alternatives outside of WordPress. His departure marked a significant moment, as it highlighted ongoing issues regarding governance and community dynamics amidst the escalating tensions in the WordPress ecosystem.
Source: (1), (2)
October 21, 2024
October 20, 2024

47. Mullenweg's "My Freedom of Speech" Blog Post

Framing WP Engine's Lawsuit as an Attack on First Amendment Rights
On October 20, 2024, Matt Mullenweg released a blog post titled “My Freedom of Speech,” asserting that WP Engine’s lawsuit against him and Automattic was an infringement on his First Amendment rights. He claimed the lawsuit, which included extensive legal documentation seeking an injunction, aimed to suppress his freedom of expression. He argues that WordPress.org shouldn’t be compelled to distribute WP Engine’s code and announces he’ll refrain from personally commenting on the case until a judge rules.  The community reacted critically, arguing that his interpretation misunderstood the amendment’s scope concerning private disputes. Critics also accused him of hypocrisy due to actions like banning users from WordPress Slack and enforcing new rules that limited the sharing of private communications. The response suggests growing frustration with Mullenweg’s handling of the situation and concern over his leadership approach.
Read more: (1), (2), (3), (4)
October 20, 2024
October 19, 2024

46. New Rule in Community Code of Conduct

WordPress.org Prohibits Publication of Private Messages
On October 19, 2024, WordPress.org revised its Community Code of Conduct to prohibit the publication of private messages without consent. This change aimed to safeguard private communications and enhance trust within the community. However, it faced backlash from some members who accused Matt Mullenweg of stifling whistleblowing and criticism amid ongoing tensions with WP Engine. Critics highlighted a contradiction between this rule and allegations regarding Mullenweg’s interest in accessing private Slack messages, raising concerns about transparency. Despite official claims that the rule was necessary for fostering a harassment-free environment, it underscored the challenges of balancing privacy and accountability in open-source governance.
Info Sources: (1), (2), (3)
 
October 19, 2024
October 18, 2024

45. WP Engine Files Motion for Preliminary Injunction

Escalation of Legal Dispute with Automattic and Mullenweg
On October 18, 2024, WP Engine intensified its legal conflict with Automattic and Matt Mullenweg by filing a motion for a preliminary injunction. The motion accused Automattic of extortionate demands, requiring WP Engine to pay hefty fees for trademark licensing and contribute more to WordPress development. It also claimed retaliatory actions, such as blocking WP Engine’s access to WordPress.org resources, which hindered updates to the Advanced Custom Fields (ACF) plugin and caused significant business harm. WP Engine alleged unauthorized takeover of the ACF plugin, rebranded as “Secure Custom Fields,” as part of a strategy to undermine its business. The filing indicated a 14% spike in cancellations, a 29% drop in new signups, and millions in lost business, linked to Mullenweg’s public criticisms. WP Engine sought court intervention to restore access and called for regulatory scrutiny over potential antitrust violations.  “Automattic vehemently denies WP Engine’s allegations — which are gross mischaracterizations of reality — and reserves all of our rights,” an Automattic spokesperson said.
DHH, the creator of Ruby on Rails, commented on this saying the request to return the ACF plugin listing and restore plugin update access as “immensely reasonable.” DHH praises the complaint’s presentation, calling it well-argued and well-written. He highlights how Automattic’s public statements, including interviews, tweets, and blog posts, provide ample evidence for WP Engine’s case.
References: (1), (2), (3), (4), (5)
October 18, 2024
October 17, 2024

44. WordPress.org Promotes Alternatives to WP Engine

Hosting Companies Offer Deals to Ex-WP Engine Customers
On October 17, 2024, WordPress.org published a post promoting a list of hosting companies that were offering special deals to customers leaving WP Engine. The announcement cited “legal attacks” against Matt Mullenweg as the catalyst for this initiative. Among the recommended hosts were Bluehost, Pressable, WordPress.com, and WordPress VIP, with offers ranging from free migrations to contract buyouts. This strategic move aimed to encourage WP Engine customers to switch providers, significantly escalating tensions within the WordPress ecosystem.
Info Sources: (1), (2)
 
October 17, 2024
October 14, 2024

43. Disruptions from ACF Plugin Takeover & Controversial Checkbox

WordPress.org Takes Control, Causing Widespread Issues
The WordPress community experienced significant disruptions following the takeover of the Advanced Custom Fields (ACF) plugin by WordPress.org. The abrupt implementation resulted in ACF’s slug being used in the repository, causing users searching for “ACF” to be redirected to the SCF page.
The takeover might led to widespread site breakages, as reported by Twitter user Hashim Warren, affecting approximately 2 million live sites. This unexpected change over a weekend frustrated many developers and site owners, with one user lamenting, “Thank you Matt Mullenweg for ruining my Sunday.”
Developers relying on ACF for client projects faced severe repercussions, with Reddit user u/mccoypauley reporting a lost $40,000 contract due to client concerns about WordPress’s stability amid ongoing tensions with WP Engine. Additionally, the use of ACF branding in SCF raised potential trademark violation issues, as WP Engine contested the takeover as unauthorized. Reports indicated that not all members of the WordPress Security Team were consulted before this decision, raising concerns about transparency and governance within the organization. Also, In a recent YouTube video, David McCam from WebTNG emphasizes that the conflict between Matt Mullenweg and WP Engine has far-reaching implications for millions of WordPress users. The inability to access support for various themes and plugins due to controversial checkbox requirement has created a challenging situation for many in the WordPress community.
Info Sources: (1), (2), (3), (4), (5) ,(6)
October 14, 2024
October 12-18, 2024

42. WordPress core contributor Scott Clark leaves project

Departure Cited Due to Inability to Support Mullenweg's Actions
On October 12, 2024, Scott Kingsley Clark, a notable contributor to the WordPress core, announced his resignation from the project. He stated that he could no longer make excuses for Matt Mullenweg’s actions as the reason for his departure, which he communicated in an update to the README file of the Fields API GitHub repository, a project he had led since 2016. Clark’s resignation, after over a decade of contributions, underscored rising tensions within the WordPress community regarding leadership and governance under Mullenweg.
Just days later, on October 18, 2024, Clark reported that his WordPress.org account had been unexpectedly disabled without explanation. This deactivation directly affected the Pods Framework project he led, as it hindered release processes that required WordPress.org login due to security protocols. Clark perceived this action as an attack against him and the Pods project, potentially linked to the ongoing conflict between Automattic and WP Engine.
Info Sources: (1), (2), (3), (4), (5)
October 12-18, 2024
October 12-19, 2024

41. WP Fusion Sent Cease and Desist to Automattic & Won

Trademark Infringement Allegations Over "WP Fusion Lite"
On October 12, 2024, WP Fusion sent a cease and desist letter to Automattic for trademark infringement concerning the “WP Fusion Lite” name on WordPress.com. Jack Arturo, founder of Very Good Plugins LLC, asserted ownership of the registered trademark for WP FUSION (U.S. Registration No. 6,052,437) and accused Automattic of brand confusion. The letter demanded the removal of “WP Fusion Lite” and a halt to similar trademark usage, with a warning of legal action for non-compliance.
On October 18, Automattic agreed to remove the plugin, despite disputing the trademark claim, seeking an amicable resolution. WP Fusion later voiced concerns about potential retaliation from Automattic and clarified that their Pro version was independent of the free version. This situation underscored ongoing issues regarding trademark protection and plugin management within the WordPress ecosystem.
Sources: (1), (2), (3), (4), (5)
 
October 12-19, 2024
October 12, 2024

40. WordPress.org launches SCF. Is it ACF Fork or hijacking?

WordPress.org Forks ACF, Launches "Secure Custom Fields"
On October 12, 2024, WordPress.org took control of the Advanced Custom Fields (ACF) plugin by renaming the plugin to SCF (Secure Custom Fields), of course without permission from WP Engine and making some security changes. Matt Mullenweg announced the fork, citing security concerns and the need to eliminate commercial upsells associated with ACF Pro.
The forking aimed to address a vulnerability in ACF that mishandled unfiltered data. While some developers welcomed SCF for its improved security, others were worried about losing advanced features from ACF Pro. WP Engine opposed the takeover, calling it unprecedented, and began providing updates for users directly from their server who wanted to continue using ACF.
Info Sources: (1), (2), (3), (4), (5)
 
October 12, 2024
October 12, 2024

39. Sorry! Who are you? Says WordPress - Laura Elizabeth, the founder of Client Portal

Tensions Highlighted Amidst Ongoing WP Engine Conflict
On October 12, 2024, a notable Twitter exchange occurred between WordPress and Laura Elizabeth, founder of Client Portal, revealing tensions over the WP Engine conflict. Laura tweeted about he inability to log into WordPress.org because of her connection to WP Engine as a customer. The official @WordPress account replied dismissively, asking, “Sorry, who are you?” which many interpreted as sarcastic.
The community largely condemned Mullenweg’s response, seeing it as a sign of larger governance issues within WordPress. Arvid Kahl, the author of Zero to Sold, criticized this behavior as harmful to both the community and the software’s legacy.
Source: (1)
October 12, 2024
October 11, 2024

38. Fireship's Viral Video on WordPress & the Twitter Poll

Fireship asks which is worse: Automattic or WP Engine. Voters say - Automattic.
On October 11, 2024, Fireship, a prominent tech YouTuber with 3.4 million subscribers, released a viral video titled “The WordPress ecosystem has lost its mind.” The 7-minute video quickly gained traction, amassing 8.4 million views. On the same day, Fireship conducted a poll asking viewers to choose which entity was worse: Automattic or WP Engine. The poll garnered over 5,900 votes, with 64% of respondents indicating that Automattic and Matt Mullenweg were perceived as worse. Suprisingly it was retweeted by @WordPress handle, likely expecting it to reflect positive community sentiment towards WordPress. However, the outcome was contrary to his expectations, prompting him to remove the retweet amid negative feedback.
Info Sources: (1), (2), (3)
October 11, 2024
October, 2024

37. Mullenweg Bans Prominent Contributors Amid Controversy Over WP Engine Checkbox

Tensions Rise in the WordPress Community Following Legal Precautions
Tensions in the WordPress community intensified as Matt Mullenweg banned several long-term contributors for questioning a new login requirement on WordPress.org. This controversial checkbox required users to confirm they were not affiliated with WP Engine, which Mullenweg justified as necessary due to potential legal risks arising from WP Engine’s lawsuit against WordPress.org.
The bans, which included prominent contributors like Javier Casares and Andrew Hutchings, sparked significant debate within the community. Many viewed Mullenweg’s actions as an overreach that could stifle open dialogue and discourage contributions. Mullenweg defended his decision by stating it was a protective measure for WordPress.org and its contributors. The bans raised concerns about governance and inclusivity, particularly affecting key individuals crucial to the development of WordPress as well as regular users.
Info Sources:  (1), (2), (3), (4)
 
October, 2024
October 9, 2024

36. WordPress.org Introduces Controversial Checkbox Targeting WP Engine Affiliates

New Requirement Marks Escalation in Ongoing Conflict
On October 9, 2024, WordPress.org introduced a controversial checkbox on its login page requiring users to confirm they are not affiliated with WP Engine. This move escalated the ongoing conflict between WordPress.org/Automattic and WP Engine. Users had to check a box stating, “I am not affiliated with WP Engine in any way.” CEO Matt Mullenweg defended the measure as a response to WP Engine’s lawsuit, which he claimed posed legal risks to the WordPress.org ecosystem.
The checkbox sparked confusion and concern among users, with some unable to access their accounts without checking it. WP Engine clarified on Twitter that their users should not be deemed affiliates. Many community leaders expressed worries about the implications for participation and governance within the WordPress ecosystem, highlighting the growing tensions between the two entities.
Read more: (1), (2), (3), (4)
October 9, 2024
October 8-15, 2024

35. DHH (Ruby on Rails) vs Matt (Automattic)

DHH Critiques Automattic's Revenue Demand
David Heinemeier Hansson (DHH), the creator of Ruby on Rails, sharply criticized Automattic in two blog posts regarding its demand for 8% of WP Engine’s revenues. In his first post, “Automattic is doing open source dirty,” DHH argued that this demand constitutes a violation of open-source principles and the GPL license, threatening the integrity of open-source licensing. He emphasized that such revenue demands are not permissible based on a project’s success. In a follow-up post titled “Open source royalty and mad kings,” DHH raised further concerns about Mullenweg’s actions in the ongoing WordPress conflict, addressing the revenue demand, the WordPress.org login oath, and the takeover of WP Engine’s ACF plugin. He warned against the misuse of open-source code registries. In response, Mullenweg questioned DHH’s expertise and defended Automattic’s trademark stance. This confrontational approach faced significant backlash, prompting Mullenweg to remove the original post and publish a more measured apology, clarifying that the conflict primarily revolves around trademark issues rather than GPL violations and defending the ACF plugin takeover as a necessary security measure.
DHH responded to Mullenweg’s removal of the controversial blog post, expressing approval of this decision. He shared advice he had given privately, suggesting two steps to resolve the conflict between Automattic and WP Engine: returning the ACF plugin repository and dropping the demand for a share of WP Engine’s revenues. DHH stressed that open-source contributions should be voluntary and criticized requiring a paid license to avoid trademark confusion.
Read all related posts: (1), (2), (3), (4), (5)
October 8-15, 2024
October 5, 2024

34. Mullenweg's Actions Spark Controversy Over ACF Alternatives

Matt Mullenweg asks for alternatives to ACF
On October 5, 2024, tensions within the WordPress community intensified as Matt Mullenweg made significant moves concerning the Advanced Custom Fields (ACF) plugin. He called for alternatives to ACF on Twitter, suggesting that many users would soon seek substitutes, which sparked speculation about ACF’s future. Automattic also publicly disclosed a vulnerability in ACF, a move that WP Engine claimed violated Intigriti’s Code of Conduct for responsible disclosure, raising ethical questions about vulnerability communication within the community.
Additionally, Mullenweg joined an Automattic alumni Slack instance and offered to pay for access, leaving his true motivations unclear and prompting curiosity among community members.
Sources: (1), (2), (3)
 
October 5, 2024
October 3-17, 2024

33. Mass Employee Exodus After Mullenweg's "Alignment Offer"

Significant Departures Amid Ongoing Conflict with WP Engine

October 3, 2024: Automattic CEO Matt Mullenweg announced an Alignment Offer for employees to resign by 20:00 UTC on that day. Those who accepted would receive either $30,000 or six months of salary, losing access to the company immediately and becoming ineligible for re-hire. As a result, 159 employees (approximately 8.4% of staff) chose to leave. Mullenweg noted that the remaining employees collectively gave up $126 million in severance to stay. Among those who left, a majority were male, and many earned over $200,000 annually. This situation raised concerns about internal tensions and the future impact on Automattic and the WordPress project. On this same day, Executive Director Josepha Haden leaves Automattic.

October 17, 2024: Mullenweg released another alignment offer providing nine months of severance, but employees only had four hours to respond. The number of employees who accepted this second offer remains unclear.

In a recent interview, Mullenweg revealed that Automattic’s employee count dropped from around 1,900 to approximately 1,700 since the beginning of the conflict. He confirmed that despite the turmoil, Automattic hired 26 new employees in October.

October 3-17, 2024
October 3, 2024

32. Former Automattic Employee Accuses Mullenweg of Bullying

Kellie Peterson's Claims Raise Concerns About Leadership and Power Dynamics
Kellie Peterson, a former Automattic employee, publicly tweeted about Mullenweg’s offer for employees who disagreed with him to leave with a severance package. In response, she received a direct message from Mullenweg that she perceived as a threat of legal action. Kellie views Mullenweg’s behavior as bullying, contrasting it with his public image. While she acknowledges his kindness at times, she criticizes his dismissive leadership style and its negative impact on Automattic and the WordPress community. She spoke out to highlight actions she believes harm open source and WordPress’s growth, giving a voice to others who fear repercussions. Kellie urges Automattic’s investors to hold Mullenweg accountable for his actions, raising critical questions about leadership and power dynamics within WordPress.
Her medium post: (1)
October 3, 2024
October 3, 2024

31. Automattic Responds Strongly to WP Engine's Lawsuit

Legal Battle Escalates in the WordPress Ecosystem
On October 3, 2024, Automattic strongly rebutted WP Engine’s lawsuit, calling the allegations “gross mischaracterizations” and “flawed.” They hired Neal Katyal and his firm Hogan Lovells, showing a commitment to a robust defense. Automattic expressed confidence in vigorously fighting the “absurd filing” and hinted at possible counterclaims. Katyal deemed the complaint meritless, reaffirming Automattic’s mission to protect WordPress’s integrity and setting the stage for a protracted legal battle over governance and trademark usage in the open-source ecosystem.
Info Sources: (1), (2), (3)
October 3, 2024
October 2, 2024

30. WP Engine Files Federal Lawsuit Against Automattic and Mullenweg

Legal Action Marks Major Escalation in WordPress Conflict
On October 2, 2024, WP Engine filed a federal lawsuit against Automattic and its CEO, Matt Mullenweg, escalating the ongoing conflict within the WordPress ecosystem. The lawsuit accuses Mullenweg and Automattic of extortion and misusing power, claiming they violated open-source principles.
Key allegations include that Automattic demanded “tens of millions of dollars per year” for trademark usage and that Mullenweg threatened to “go to war” if WP Engine did not agree to a licensing deal. The lawsuit also claims that Mullenweg concealed his control over the WordPress Foundation for personal gain.
Info Sources: (1), (2), (3), (4), (5), (6)
October 2, 2024
October 1, 2024

29. Cloudflare CEO Offers to Host WordPress.org for Free

A Potential Solution Amidst Ongoing Conflict
On October 1, Matt Mullenweg emphasized the need for independently wealthy entities to support WordPress.org, which handles significant traffic (30,000 requests per second) and requires substantial resources. To everyone’s surprise, Matthew Prince from Cloudflare expressed his willingness to donate resources to support WordPress.org and indicated an interest in discussing how their services could enhance its infrastructure. Matt has also responded positively to Matthew’s comment, but there are no further reports on this. Another user suggested that Matthew should only proceed with the donation if there is a clause forbidding Matt from cutting off access to anyone in the community. In response, Matthew Prince said, and I quote: “It’s Matt’s project; he can do what he wants with it.”
Source: (1)
October 1, 2024
October 1, 2024

28. WordPress.org Reinstates Ban on WP Engine

Ongoing Conflict Escalates as Access to Resources Blocked Again
On October 1, 2024, WordPress.org reinstated its ban on WP Engine, blocking the hosting provider’s access to plugin and theme updates. This intensified the conflict between WordPress.org/Automattic and WP Engine. After a temporary reprieve expired on September 27, WP Engine announced via Twitter that they had deployed a solution to restore access globally by mirroring WordPress.org repositories.
The WordPress community remained divided over the dispute’s implications. WP Engine updated its website to lessen the use of “WordPress” and clarify trademark usage, while offering minimal explanations. Matt Mullenweg publicly criticized WP Engine and invited Lee Wittlinger of Silver Lake to debate, highlighting ongoing tensions and raising questions about trademark usage and power dynamics in the WordPress ecosystem.
Info Sources: (1), (2)
 
October 1, 2024
September 27, 2024

27. WordPress.org Temporarily Lifts WP Engine Ban

A Brief Respite Amid Ongoing Conflict with Automattic
On September 27, 2024, WordPress.org temporarily lifted its ban on WP Engine, marking a significant shift in the ongoing conflict between Matt Mullenweg and the hosting provider. The ban was lifted until October 1, 2024, at 12:00 AM UTC, just two days after its implementation. In a post on WordPress.org, Mullenweg expressed regret for the impact on WP Engine customers but continued to criticize the company and its private equity investor, Silver Lake, blaming them for the situation and noting that it saddened him that customers were affected by their commercial decisions. Lifting the ban allowed WP Engine users to update plugins and themes, addressing immediate security concerns. However, Mullenweg reiterated that WP Engine had ignored attempts to resolve their differences and establish a commercial licensing agreement. The WordPress community remained divided, with some praising the temporary solution while others criticized the handling of the situation. This event highlighted unresolved issues, including trademark disputes and contributions to the WordPress ecosystem, leaving users uncertain about the future after October 1 and raising questions about governance amid commercial interests.
Info Sources: (1), (2), (3), (4)
September 27, 2024
September 26, 2024

26. Pressable Launches Aggressive Campaign Targeting WP Engine Customers

Strategic Move Following WordPress.org Ban Amid Ongoing Controversy
On September 26, 2024, Pressable, a WordPress hosting company owned by Automattic, launched a marketing campaign targeting WP Engine customers after the WordPress.org ban. The campaign aimed to assist users facing access issues with updates and plugins.
Key elements included immediate launch after the ban and financial incentives, offering a $100 credit per site (up to $10,000) for agencies migrating clients from WP Engine or Flywheel. Pressable also promised to cover the remaining time on existing WP Engine contracts, avoiding extra costs for customers. Emphasizing its connection to Automattic, Pressable positioned itself as a reliable alternative. The campaign utilized social media platforms like Twitter (X) and featured a limited-time offer expiring on November 30, 2024, encouraging swift action.
The timing and nature of this campaign underscored the intense competition in the WordPress hosting market and reflected how quickly companies were moving to capitalize on the unfolding situation, further complicating the dynamics between WordPress.org, Automattic, and WP Engine.
Info Sources: (1), (2), (3)
September 26, 2024
September 25, 2024

25. WordPress.org Bans WP Engine: A Dramatic Escalation in the Conflict

Access Blocked Amid Ongoing Dispute Between Automattic and WP Engine
On September 25, 2024, WordPress.org banned WP Engine from accessing its resources, escalating the conflict between Matt Mullenweg’s Automattic and the hosting provider. This significant move prevented WP Engine customers from installing or updating themes and plugins from the WordPress.org repository. Mullenweg announced the ban, citing alleged trademark violations and WP Engine’s inadequate contributions to the open-source project as justifications. As a result, thousands of WP Engine customers faced security risks due to unpatched vulnerabilities. WP Engine responded by assuring customers that site performance and security remained unaffected while they worked on a solution. The decision drew widespread criticism within the WordPress community, with concerns raised about the impact on innocent users.
Info Sources: (1), (2), (3), (4)
September 25, 2024
September 23, 2024

24. WP Engine Issues Cease-and-Desist to Automattic: Escalation of the WordPress Conflict

Legal Battle Looms as Tensions Rise Between WP Engine and Matt Mullenweg
On September 23, 2024, WP Engine sent a cease-and-desist letter to Automattic and Matt Mullenweg, marking a critical point in their ongoing conflict. The letter demanded Mullenweg retract his critical comments and accused him of making threats against WP Engine, mentioning a “scorched earth nuclear approach” if his demands were not met. WP Engine defended its use of the WordPress trademark, citing a prior policy from the WordPress Foundation that allowed “WP” in company names. The letter also claimed Mullenweg had made an “astronomical and extortionate monetary demand” for a share of WP Engine’s revenue. WP Engine denied any wrongdoing regarding trademark usage and contributions to the WordPress community. The letter hinted at potential legal action for tortious interference and unfair business practices and requested Automattic to preserve all relevant documents. This cease-and-desist transformed the public dispute into a possible legal battle, highlighting tensions between open-source ethics and commercial interests.
Read more: (1), (2), (3)
September 23, 2024
September 21, 2024

23. Mullenweg Labels WP Engine a "Cancer to WordPress"

Escalation of Conflict with Serious Accusations
On September 21, 2024, Matt Mullenweg published a controversial post on WordPress.org that heightened tensions with WP Engine. He called WP Engine a “cancer to WordPress,” stressing that “WP Engine is not WordPress”, as even his mother confused it for an official entity. Mullenweg accused WP Engine of profiting from the WordPress brand without proper licensing and criticized its lack of contributions to the community, particularly regarding the Five for the Future initiative. He also claimed that WP Engine disabled key features like the revision system to cut costs, which he argued undermined user trust. Mullenweg urged users to reconsider their hosting choices, highlighting their power as customers. This post intensified the conflict and sparked broader discussions about the responsibilities of commercial entities within open-source projects.
Read more: (1), (2)
 
September 21, 2024
September 20, 2024

22. Mullenweg's Controversial Keynote Speech at WordCamp US 2024

Public Criticism of WP Engine Escalates Ongoing Conflict
On September 20, 2024, Matt Mullenweg delivered a controversial keynote at WordCamp US 2024 in Portland, where he criticized WP Engine.  He highlighted the large gap in contributions to the WordPress project, noting that Automattic pledged 3,900 hours per week to the “Five for the Future” initiative, while WP Engine only contributed 40 hours. Mullenweg expressed concerns about WP Engine’s ownership by Silver Lake, a private equity firm, suggesting their focus on profits conflicted with open-source values. He urged the community to “vote with your wallet” and reconsider supporting companies that do not contribute enough. Mullenweg implied that WP Engine customers should rethink their choices at contract renewal. His remarks were especially shocking as WP Engine sponsored the event, escalating tensions and sparking debates about commercial involvement in open-source projects.
Sources: (1), (2), (3), (4)
September 20, 2024
September 20, 2024

21. Automattic Sends Trademark License Agreement to WP Engine

Escalation of Conflict with Substantial Financial Demands
On September 20, 2024, a major development arose in the Automattic and WP Engine controversy when Automattic proposed a seven-year trademark license agreement to WP Engine, requiring significant financial commitments. The agreement allowed WP Engine to use the WordPress and WooCommerce trademarks if they adhered to trademark guidelines and offered three compensation options: an 8% monthly royalty fee based on gross revenue, allocating 8% of revenue for salaries of employees working on core WordPress features, or a combination of the first two options. It also prohibited WP Engine from modifying any software from Automattic and granted Automattic full audit rights over WP Engine’s financial reports. This demand, made just before Mullenweg’s keynote at WordCamp US 2024, raised concerns in the community, as many considered the 8% royalty excessive given WP Engine’s annual revenue exceeding $400 million, while the audit rights were viewed as intrusive.
Read further: (1), (2), (3)
September 20, 2024
September 17, 2024

20. Mullenweg's Controversial Post during WordCamp US

Tensions with WP Engine Erupt in the WordPress Ecosystem
On September 17, 2024, at WordCamp US, Matt Mullenweg, co-founder of WordPress and CEO of Automattic, ignited controversy by criticizing companies profiting from WordPress without contributing to the project, specifically targeting WP Engine. He highlighted a stark contrast in contributions: Automattic provided 3,786 hours per week to the Five for the Future initiative, while WP Engine reported only 47 hours.
Mullenweg accused some companies of benefiting without giving back and introduced the “Ecosystem Thinking” framework, emphasizing the need for learning and nurturing in open-source communities.
Read more: (1), (2), (3)
 
September 17, 2024
July 12, 2024

19. WordPress Foundation Files Trademark Applications

Attempt to Trademark "Managed WordPress" and "Hosted WordPress"
On July 12, 2024, the WordPress Foundation filed trademark applications for “Managed WordPress” and “Hosted WordPress” with the U.S. Patent and Trademark Office, covering web hosting services and content management systems. If approved, these trademarks could restrict other companies from using these terms. This has heightened tensions between WordPress, led by Matt Mullenweg, and hosting firms like WP Engine. Many independent providers fear marketing limitations. The move has sparked debate within the community about trademarking common industry terms. Concerns also arise about Automattic’s enforcement of these trademarks, recalling past conflicts with hosting companies. This situation complicates discussions on governance, commercial interests, and open-source values in the WordPress ecosystem.
Sources: (1), (2), (4)
July 12, 2024
Late February 2024

18. Mullenweg's Public Feud with Tumblr User

Controversy Over Content Moderation and LGBTQ+ Issues
In late February 2024, a feud erupted between Matt Mullenweg and a transgender Tumblr user after her ban on February 22 for voicing frustrations about transmisogynistic harassment. Known as “predstrogen,” she made a violent comment wishing for Mullenweg’s death, which he deemed a threat to Tumblr staff despite being on sabbatical.
Mullenweg publicly responded on his blog and X (formerly Twitter), disclosing private details about her side blogs and raising privacy concerns. This led to accusations of transphobia and criticism of Tumblr’s moderation practices. On February 26, transgender employees from Tumblr and Automattic condemned Mullenweg’s actions as “unwarranted and harmful,” asserting he did not represent their views and arguing the user’s comment was not a real threat.
The incident highlighted issues in content moderation, CEO responsibilities, and the challenges LGBTQ+ users face online, sparking discussions about Tumblr’s practices and communication within the company.
Sources: (1), (2)
 
Late February 2024
January 14, 2024

17. Mullenweg's Statement on Ownership of WordPress.org

Controversy Over Governance and Transparency in the WordPress Community
On January 14, 2024, Matt Mullenweg stirred controversy in the WordPress community by declaring in a Slack channel that he personally owns WordPress.org, contradicting the belief that the WordPress Foundation manages it. His statement raised governance and transparency concerns, as community members worried about potential conflicts of interest due to his dual role in Automattic. This revelation sparked debates about the sustainability and future direction of the WordPress project, particularly amid rising tensions with hosting companies like WP Engine. The incident highlighted ongoing discussions about power dynamics within the WordPress community and the interplay between commercial interests and open-source principles, significantly influencing events and governance debates throughout 2024.
Info Sources: (1), (2), (3), (4)
January 14, 2024
September 14, 2023

16. WordPress Plugin Showdown: .com vs .org

Developers worry that WordPress.com plugin listings are outranking those on WordPress.org in Google search results.

John Blackbourn, a WordPress core developer, expressed concerns about WordPress.com plugin listings outranking WordPress.org in Google search results, suggesting that this competition is unhealthy for the open-source community. SEO consultant Rebecca Gill pointed out that the duplicate content between WordPress.com and WordPress.org confuses both users and search engines, advocating for a noindex strategy for .com content to prioritize .org. Matt Mullenweg, CEO of Automattic, defended the cloned plugin directory on WordPress.com, arguing that it provides greater distribution opportunities for plugin authors despite concerns about ambiguity. Plugin developers expressed frustration over not having access to install statistics for their plugins listed on WordPress.com, which impacts their understanding of user bases (Read more about this on WPTavern)

September 14, 2023
June 24, 2022

15. Mullenweg's Criticism of GoDaddy

Public Conflict Raises Questions About Contributions to WordPress
The conflict between Matt Mullenweg and GoDaddy became public on June 24, 2022, when Mullenweg criticized GoDaddy in a series of tweets, labeling the company as a “parasitic” entity and “an existential threat to WordPress’ future.” He argued that GoDaddy was not contributing sufficiently to WordPress and WooCommerce relative to the revenue generated from these open-source projects. Mullenweg also condemned GoDaddy’s investment in proprietary website solutions, suggesting that this conflicted with their support for WordPress. He expressed concern about the future of WordPress if GoDaddy continued to succeed at the expense of the ecosystem, contrasting their approach with Bluehost’s long-standing support since 2003.
The community reacted with mixed responses; some supported Mullenweg, while others defended GoDaddy. The incident sparked debates about what constitutes adequate contributions from companies benefiting from open-source projects. GoDaddy responded on June 30, emphasizing shared goals and their active participation in WordPress events, including a commitment to invest significantly in WordCamps in 2022.
Following the controversy, Mullenweg deleted his tweets, but discussions continued regarding the relationship between commercial entities and open-source projects, focusing on fair contribution and support. This event highlighted the complexities within the WordPress ecosystem and raised critical questions about the sustainability of open-source initiatives in a commercial landscape.
Info Sources: (1), (2), (3)
June 24, 2022
August 16, 2021

14. Controversy Over "WP" in Plugin Names

Communication Breakdown and Trademark Concerns
On August 16, 2021, the WordPress community reacted strongly to news that Joe Youngblood’s plugin had been rejected due to the use of “WP” in its name. This decision, implemented in May 2021 without prior announcement, caused confusion and frustration among developers. The change aimed to prevent trademark violations, as some developers submitted plugins with “WP” in the name and later changed it to “WordPress,” which is a trademarked term.
Concerns arose when the community discovered that Automattic could still use “WP” in plugin names, raising fairness issues. While plugins using “WP” were not outright banned, many faced manual reviews or automatic rejections, adding to the confusion. Developers demanded transparency regarding the impact on existing plugins and businesses centered around “WP”-prefixed products.
On August 17, Mika Epstein from the Plugin Team clarified that the change was part of a broader discussion about trademark misuse. She noted that “WP” itself is not a trademarked term and that the WordPress Foundation was not actively pursuing its trademark. This controversy underscored significant communication issues between WordPress leadership and developers, highlighting the need for clearer guidelines on trademark usage and more transparent decision-making processes within the WordPress ecosystem.
Dive deep: (1), (2), (3), (4)
 
August 16, 2021
August 11, 2020

13. Changes to Plugin and Theme Guidelines on WordPress.org

Updates Implemented with WordPress 5.5
On August 11, 2020, WordPress 5.5 was released, introducing significant changes to plugin and theme guidelines on WordPress.org. A key feature was the implementation of automatic updates for plugins and themes, allowing site administrators to opt-in for updates on a per-plugin and per-theme basis. This new functionality shifted responsibilities onto developers, who were now accountable for ensuring their code was compatible with auto-updates. The updated Plugin Guidelines emphasized developer responsibility for all contents of their plugins, requiring compliance with licensing for all included files. New rules also aimed to prevent excessive notifications in the admin dashboard and mandated that plugin version numbers be incremented for each release to trigger user notifications. Additionally, guidelines discouraged frequent commits to the SVN repository, reinforcing its role as a release repository. These changes sparked debate within the community, with some developers concerned about the increased responsibilities and potential risks associated with auto-updates. Discussions focused on balancing user convenience with developer control over plugins and the impact of stricter guidelines on communication and rapid iterations. The Plugin Review Team continued to enforce these guidelines while supporting developers in adapting to the new framework. Overall, these changes marked a significant shift in the management of plugins and themes, aiming to enhance security and user experience while holding developers to higher standards of code quality and compliance.
More info: (1), (2)
August 11, 2020
January 4, 2018

12. WP Engine Secures $250 Million Investmentt; Automattic exits

A Major Milestone and Shift in Corporate Strategy
On January 4, 2018, WP Engine announced a significant milestone by securing a $250 million investment from Silver Lake, a prominent technology investment firm. This investment coincided with WP Engine reporting over $100 million in annual recurring revenue and a customer base exceeding 75,000 globally, achieving a 30% year-over-year growth in customers. As part of this transaction, Automattic exited its earlier investment in WP Engine. The funding aimed to accelerate innovation on WP Engine’s Digital Experience Platform and support future international expansion. Following the investment, Silver Lake’s Greg Mondre, Lee Wittlinger, and Mark Gillett joined WP Engine’s Board of Directors. Heather J. Brunner, Chairwoman and CEO of WP Engine, highlighted the alignment of core values between WP Engine and Silver Lake as pivotal for the partnership. This event marked a major shift in WP Engine’s corporate relationships and financial backing, underscoring its rapid growth and solidifying its position in the WordPress ecosystem. With WP Engine powering around 5% of all internet visits, this investment was viewed as a strong endorsement of its business model and potential for further expansion in the global market.
Dive Deeper: (1), (2), (3), (4), (5)
January 4, 2018
Late 2014

11. Acquisition of Thesis.com by Matt Mullenweg

A Controversial Purchase and Its Implications
In late 2014, Matt Mullenweg, representing Automattic, acquired the domain thesis.com for $100,000 from Larry Fische, a domain expert at Getyourdomain. This acquisition garnered attention due to Mullenweg’s prior conflict with Chris Pearson, the creator of the Thesis theme. Pearson initially negotiated with Larry but found the $150,000 asking price too high and offered only $37,500 at most.
In November 2014, Larry informed Chris Pearson that Matt Mullenweg had made a $100,000 offer. He then gave Pearson a chance to purchase the domain for $115,000, which Pearson declined. Later that month, during a Q&A session at WordCamp San Francisco, Mullenweg revealed his ownership of the domain. Following the purchase, Automattic redirected thesis.com to themeshaper.com, a blog focused on WordPress themes.
Pearson viewed the acquisition as retaliatory, considering their history of public disputes over the GPL licensing of the Thesis theme dating back to 2010. In response, Pearson filed a cybersquatting complaint with the National Arbitration Forum in 2015. However, on July 3, 2015, the panel ruled that the domain would remain with Automattic. This event reignited tensions between Pearson and Mullenweg, highlighting the ongoing complexities of balancing commercial interests with open-source principles in the WordPress ecosystem.
Dive deep: (1), (2), (3), (4), (5), (6), (7), (8)
Late 2014
December 2012 - July 2013

10. Envato Marketplace Controversy and WordCamps

Licensing Disputes Lead to Ban on ThemeForest Authors
The controversy surrounding Envato marketplace authors and WordPress began in late 2012 and continued into 2013. On December 1, 2012, Matt Mullenweg announced that authors selling themes on ThemeForest would be banned from speaking, sponsoring, or volunteering at official WordCamps due to licensing disagreements with Envato. WordPress requires that themes be 100% GPL-compliant, while Envato utilized a split license model, keeping PHP code under GPL but making other assets proprietary.
This decision impacted many developers, forcing them to choose between participating in WordCamps or selling on Envato’s platform. The WordPress community responded strongly, arguing it was unfair to penalize individual developers for Envato’s policies. A notable case involved Jake Caputo, who was removed from the speaker lineup at WordCamp Chicago in 2013 because of his association with ThemeForest.
On March 22, 2013, Envato announced a policy change allowing authors to opt for 100% GPL licensing. However, the ban was not lifted until July 2013, when the WordPress Foundation updated its guidelines. This controversy highlighted the complexities of open-source licensing and the significant impact of leadership decisions on individual developers within the WordPress ecosystem.
Sources: (1), (2)
December 2012 - July 2013
November 15, 2011

9. WP Engine Secures $1.2 Million Series A Funding

Milestone Investment and Collaboration with Automattic
On November 15, 2011, WP Engine announced the successful closure of a $1.2 million Series A funding round, marking an important milestone in its growth. The funding was led by Silverton Partners from Austin, Texas, and included prominent angel investors such as Eric Ries, Loic Le Meur, and Automattic, the company behind WordPress.com. This investment aimed to scale the product, recruit top talent, and strengthen relationships with elite WordPress service providers.
Coinciding with the funding announcement, Automattic launched its VIP Support for Web Hosts program, naming WP Engine as its first partner. At that time, WP Engine had already established a substantial install base of over 30,000 WordPress blogs. Founder and CEO Jason Cohen emphasized the company’s commitment to customer service and its dedication to expanding the platform.
Read more: (1), (2)
November 15, 2011
January 17, 2011

8. The "Coward" Controversy

Allegations of Attempted Censorship in the WordPress Community
On January 17, 2011, Ben Cook published a post titled “Matt Mullenweg: The Coward” on WPBlogger.com, detailing a troubling incident involving Matt Mullenweg, co-founder of WordPress. Cook alleged that in December 2010, Mullenweg contacted his employer, GoDaddy, in an attempt to get him fired due to Cook’s critical posts about WordPress and Automattic. Mullenweg reportedly pressured GoDaddy by threatening to sever business ties, but the company refused to terminate Cook, stating that his personal blog was unrelated to his work.
Cook characterized Mullenweg’s actions as “cowardly” and “childish,” expressing disappointment in someone he once admired. This incident raised concerns about the abuse of power within the WordPress community and its potential chilling effect on open discourse. It sparked discussions about ethics, free speech, and the responsibilities of leadership in open-source environments, highlighting the need for professional boundaries and respect for differing opinions.
Find the archived link of this blog post: (1)
January 17, 2011
September 13, 2010

7. Concerns Over WordPress Trademark Transfer

Warnings About Accountability and Control
On September 13, 2010, a blog post on WordPress raised significant concerns regarding the transfer of the WordPress trademark from Automattic to Matt Mullenweg. The author questioned the celebration surrounding this transfer, highlighting potential issues with accountability and transparency under the new WordPress Foundation that would manage the trademark. There were worries that the Foundation might use trademark violations to suppress non-GPL code, referred to as a “weapon in the GPL jihad.” Additionally, the post expressed skepticism about the lack of checks on Mullenweg’s authority without Automattic’s board to temper his decisions.
Dive deep: (1), (2)
September 13, 2010
July 2010

6. Thesis Theme Controversy

Dispute Over Licensing and Open Source Principles
The Thesis Theme Controversy started in July 2010 between Matt Mullenweg, co-founder of WordPress, and Chris Pearson, creator of the popular Thesis theme. The dispute reignited after Pearson’s interview on Mixergy, where he stated that Thesis generated approximately $1.2 million in just 16-18 months. A heated exchange on X (previously Twitter) led to a live debate, during which Mullenweg argued that since Thesis was built on WordPress, it must adhere to the GPL license. In contrast, Pearson claimed it was an original creation exempt from GPL requirements.
In response to the controversy, Mullenweg offered alternatives for Thesis users and removed associated themes from WordPress.com. Ultimately, Pearson released a split-license version of Thesis, with the PHP code under GPL and other components retained under a proprietary license. This dispute highlighted the significance of open-source principles, influenced the rise of competing themes like Genesis, and emphasized the need for clear licensing guidelines within the WordPress community.
Dive Deep: (1), (2), (3), (4), (5), (6)
July 2010
1st March 2010

5. Founding of WP Engine

A New Standard in Premium WordPress Hosting
WP Engine was founded by Jason Cohen and Ben Metcalfe in March 2010 to fill a significant gap in the WordPress hosting market. The idea was inspired by Cohen’s challenges with his blog, “A Smart Bear,” which faced issues like server crashes, slow load times, and security problems. Unable to find a suitable premium hosting option, Cohen validated his concept by discussing it with over 50 bloggers.
This led to the creation of WP Engine, which promised Speed, Scale, Security, and Service. Initially bootstrapped, the company experienced steady growth and ultimately raised around $300 million in funding within a decade, establishing itself as a leader in managed WordPress hosting.
Read more: (1), (2), (3), (4) , (5)
 
1st March 2010
March 11, 2008

4. WordPress vs. Movable Type Controversy

Public Dispute Highlights Competition in Blogging Platforms
On March 11, 2008, a public dispute arose between WordPress and Six Apart’s Movable Type, initiated by Anil Dash, Six Apart’s Chief Evangelist. In a blog post intended as an upgrade guide for WordPress 2.5, Dash suggested that users consider switching to Movable Type instead of upgrading. This statement drew a sharp rebuke from WordPress founder Matt Mullenweg, who accused Six Apart of being “desperate and dirty.” In response, Dash challenged Mullenweg to point out any inaccuracies in his post.
This incident highlighted the fierce competition in the blogging platform market and the challenges faced by users. It also foreshadowed the emergence of new content management systems that would further disrupt the landscape.
Read more here: (1), (2), (3)
March 11, 2008
August 2005

3. Automattic Founded to Power WordPress.com

Matt Mullenweg's Company Introduces Hosted WordPress Service
In August 2005, Matt Mullenweg founded Automattic, a company established to support and expand the WordPress ecosystem. Based in San Francisco, Automattic has always focused on open-source solutions, primarily powering WordPress.com, a freemium blogging service. The company’s name cleverly combines Mullenweg’s first name with the word “automatic.”
Automattic soon became a major contributor to the WordPress open-source project, developing popular plugins like Akismet and later acquiring services such as Gravatar. From the beginning, the company has embraced a flexible work model, allowing employees to work from anywhere. The formation of Automattic marked a significant advancement in the professionalization of WordPress development and set the stage for the platform’s remarkable growth in the years that followed.
Learn more: (1), (2), (3), (4), (5), (6)
 
August 2005
2004

2. WordPress Adopts GPL, Sparking Licensing Debate

Community Divided Over Implications for Commercial Themes and Plugins
In 2004, WordPress officially adopted the GNU General Public License (GPL), a decision that ignited substantial debate within the community. The GPL’s “copyleft” rule required that all new works, like themes and plugins, also be shared under the same license. This worried some commercial developers about how it would affect their proprietary code and business models. Supporters loved it and believed the GPL encouraged software freedom and teamwork, while critics thought it could make it harder to find ways to make money. The main point of discussion was whether themes and plugins were considered derivative works of WordPress and had to follow the GPL, leading to ongoing discussions about open-source values versus business interests.
Dive deep: (1), (2), (3), (4)
2004
January 24, 2003

1. Launch of WordPress

A New Era in Blogging
This is a date that should be celebrated as one of the happiest moments in the history of internet blogging: the birth of WordPress!  It originated as a fork of b2/cafelog, which had been abandoned by its creator, Michel Valdrighi, in 2002. On January 24, 2003, Matt Mullenweg excitedly shared his plan to create a new version, with the wonderful support of developer Mike Little. The first version, WordPress 0.7, was launched on May 27, 2003, focusing on improving the code and following web standards. Even though some people were unsure about it and there were other similar projects, Matt’s passion for connecting with the community helped WordPress thrive and become a beloved choice for open-source blogging. I personally can’t thank Matt enough for creating WordPress! It has truly empowered us to express ourselves and be the content artists, even if we don’t know anything about coding.
Sources: (1), (2), (3), (4), (5)
January 24, 2003
Know someone who needs to see this? Share it now!

1 comment

Leave your comment

Explore More