Category: Exclusive

  • WordCamp Asia 2026 Handover Sparks Tensions Between Organizers and WordCamp Central

    WordCamp Asia 2026 Handover Sparks Tensions Between Organizers and WordCamp Central

    WordCamp Asia is set to return in 2026 — but not without behind-the-scenes tension.

    Organizers of the 2025 event say they were sidelined in choosing the next host city, shut out before a proper handover was complete, and “flushed out.” WordCamp Central, meanwhile, says it stepped in to keep the flagship event from losing momentum after the 2025 team suggested skipping 2026.

    Accounts from WordCamp Asia organizers (including some who spoke on condition of anonymity), WordPress Community Team program managers, and project leadership point to a breakdown in communication, complicated by cultural misunderstandings, competing interpretations, and lingering mistrust after a turbulent year for WordPress.

    [yarpp]

    Conflicting accounts and a rushed Mumbai bid

    Tokyo was initially the front-runner to host WordCamp Asia 2026 but withdrew after seven months of stalled venue negotiations, which organizers say were exacerbated by delays and a lack of support from WordCamp Central. The local team was left “exhausted and demoralised,” according to one organizer.

    The failed bid prompted a new call for host city applications in November 2024, but “basically got none,” in stark contrast to the eight applications received for the 2025 event. So organizers reached out to cities that had previously applied — including from Nepal, Malaysia, and India — to gauge interest.

    “We reached out, saying, ‘Hey, you guys applied back in 2024. Do you still want to host?’ And they all said, ‘With what’s going on, we don’t want to host it,’” another organizer said, referring to tensions in the WordPress community following co-founder Matt Mullenweg’s contentious keynote at WordCamp US 2024.

    The 2025 team turned to WordCamp Central for help, proposing two options: return to the community to find a new host city, or skip 2026. Soon after, Automattic-sponsored Program Manager Rocío Valdivia informed them that Mumbai had been chosen as the 2026 host city and a new lead appointed.

    “We asked for guidance, not for them to make the decision for us,” one organizer said.

    Valdivia, who served as a mentor for the 2025 team, confirmed reaching out to organizers in Mumbai but said it was “with the awareness and support of the 2025 leads.” She said that other regional program managers assisted, and cited precedent, pointing to WordCamp Europe 2015 being awarded to Seville, Spain, after a direct invitation.

    Five people pose together in a restaurant, smiling at the camera.
    Local leads Andrew Garcia and JC Palmes, Community Team Program Manager Rocío Valdivia, and global leads Yuli Yang and Shusei Toda. Image: WordCamp Asia 2025.

    Adding to the differing accounts, Executive Director Mary Hubbard, who’s employed by Automattic, said the 2025 team had indicated they wanted to pause the event in 2026 due to burnout, prompting mentors and program managers to begin scouting cities and leads before planning fell too far behind.

    “So yes, the process looked different from previous years, but that was because we were working from a different starting point,” Hubbard said. “The goal was never to bypass anyone, but rather to avoid a leadership vacuum that could have resulted in the event being skipped altogether.”

    But the 2025 organizers insist skipping 2026 was just one idea under discussion, not a decision. “We weren’t abandoning the event, we just needed support to figure out a way forward,” one said.

    While two Indian cities had originally applied to host WordCamp Asia, Mumbai wasn’t one of them. Its proposal was submitted just three weeks before WordCamp Asia 2025, following what 2025 organizers described as a rushed and incomplete vetting process. According to organizers, Aditya Kane, who coordinated with local organizers in Mumbai, initially refused to submit an application, citing that WordCamp Central had already selected Mumbai and a formal submission was unnecessary.

    Hubbard said Mumbai was the only city to submit a “complete, eligible application.” “The local team was strong, experienced, and responsive, and their proposal was shared with the 2025 leads before any final decision was made,” she said. “In fact, after meeting with the prospective organizers, the 2025 leads agreed to proceed with Mumbai just days before [WordCamp Asia 2025].”

    Kane said the Community Team had approached him, asking for his help to identify if any Indian cities were ready and willing to host WordCamp Asia. He acknowledged the tight timeline but said there was no pressure from WordCamp Central. “We applied as a host city for the event formally after making sure a couple of dozen community organizers from around the country were onboard with Mumbai,” he said.

    Still, the selection left some former organizers reeling. One described the decision as “top-down,” said they felt “gas-lit,” and were told to “just accept” Mumbai. Another added, “There was no sense of accountability or explanation. It just happened.”

    A group of four speakers on stage at WordCamp Asia 2025, with a podium and presentation behind them.
    WordCamp Asia 2026 Global Lead Regan Khadgi with local leads Vachan Kudmule, Meher Bala, and Aditya Kane. Image: WordCamp Asia 2025.

    Community Team steps in as leadership confusion escalates

    In the weeks following WordCamp Asia 2025, confusion over leadership roles between outgoing and incoming organizers played out on WordCamp Asia Slack.

    Ahead of the event, members of the 2025 team had met with former leads, program managers, and Hubbard to resolve tensions around the global and local lead roles. Several people on the call told The Repository a path forward had been agreed by all. But at the conference in Manila, a slide mix-up during Mumbai’s host city announcement meant only Nepali organizer Regan Khadgi was named as global lead, adding to the leadership confusion.

    In Slack messages viewed by The Repository, Khadgi said he had agreed to the role on the understanding that he would be one of three global leads. He said Kane had proposed merging the global and local roles. While open to the change, Khadgi wanted assurance that the leadership team would reflect geographic diversity, rather than be dominated by organizers from one country. “… there is a possibility of similar thought processes influencing key decisions,” he wrote. “As the only Global Lead at the moment, I am concerned that this could create an imbalance when making collective decisions.”

    WordCamp Asia co-founder Jon Ang, Director of Enterprise Strategy at Human Made, responded that two additional global leads were still being confirmed and suggested outgoing leads Shusei Toda and Yuli Yang could temporarily support Khadgi, as had been done in previous years.

    Tensions came to a head on April 3, when Automattic-sponsored Community Team Program Manager Isotta Peira posted in the Slack channel, asking Ang to “stop interfering,” directed Toda and Yang to complete wrap-up tasks, and informed the 2025 team they would be removed from Slack.

    “@Jon Ang, we truly appreciate your efforts and willingness to help, despite not having an official role within the WCAsia 2025 team,” Peira wrote. “However, at this stage, your continued involvement is disrupting the handover process. I kindly ask you to stop interfering and allow the 2026 team to begin their work independently from the 2025 team.”

    Peira confirmed that she posted the message, which followed an earlier email from Hubbard asking the 2025 team to step aside. She claimed Ang’s behavior included asserting influence over key decisions, undermining new leadership in private channels and DMs, and framing the transition as a “power grab” by WordCamp Central, despite previously indicating he was stepping back.

    She said that some members of the 2025 team were removed from specific organizing channels, but only after the handover to the 2026 team was complete.

    Ang said the 2025 team had asked for his help managing tensions between the 2025 and 2026 leads and mentors. “My Slack messages were focused on encouraging open dialogue, addressing concerns already raised by the 2026 global lead, and offering continuity and support,” he said. “I made it clear the 2025 team stood ready to assist with ongoing discussions around venue, dates, and budget. This kind of transition support has always been part of how flagship events have successfully evolved.”

    Several organizers confirmed that the 2025 team had asked Ang to assist and pushed back against the idea that he had interfered.

    “Yes, we did ask Jon to help bridge things. He’s been involved since the beginning and has all the context,” said JC Palmes, a local lead for WordCamp Asia 2025. “I’ve been helping organize WordCamp Asia alongside Jon and Shusei since 2019, so we’ve all worked closely enough to know when to step in and when to step back. Jon was there to support us, and he’s always been diplomatic and level-headed in tense situations.”

    Past global lead Andy Saw, COO of Exabytes, also disagreed with Peira’s characterization. “Not really, I don’t really feel [he was disruptive], because I was in those Slack channels,” he said.

    Saw noted that in past years, WordCamp Central had been more collaborative, calling out Naoko Takano, an Automattic-sponsored community manager based in Japan, for her years of support. This year, he said, there was a “clear change” and claimed past organizers were “flushed out” and the 2025 leads were left in the dark during the transition, hindering continuity. “Things were happening in the background that were not transparent to the outgoing team,” he said.

    Other organizers told The Repository they were concerned that without the support and institutional knowledge of the 2025 team and other past organizers, the 2026 leads would be “reinventing the wheel” — left to figure out team dynamics and budgets without the support of past organizers, as had been the norm in previous years. Others said they stepped back from 2026 out of concern that all their unpaid work could be dismissed, and instead of building on past contributions, organizers could simply be shut out.

    Four individuals stand on stage, engaged in a presentation.
    WordCamp Asia 2024 global and local leads Huanyi Chuang, Andy Saw, Yuli Yang, and Jon Ang. Image: Susumu.

    Code of Conduct concerns

    Tensions weren’t confined to online. During WordCamp Asia 2025, Toda was involved in a public confrontation with Valdivia. According to multiple witnesses, Valdivia approached Toda in a busy hallway and began yelling at him, prompting other organizers to intervene.

    Local lead JC Palmes, who stepped in to help de-escalate the situation, described the confrontation as “tense, emotional, and difficult to ignore.”

    The altercation is understood to have stemmed from disagreements over the location of the keynote sessions. According to Toda, the exchange left him feeling unsafe. “The tone used during this altercation was nowhere near ‘advice.’ I felt attacked and that I was not taken seriously as she started laughing,” he said.

    Valdivia disputed Toda’s account. “I would never laugh at someone who expresses that they feel unsafe,” she said. “But I was surprised by the comment. I value respectful communication and teamwork, and took immediate steps to clarify the situation and move the conversation forward constructively.”

    Toda also pointed to the blurred lines between Rocío’s role as the 2025 team’s mentor and her employment at Automattic, noting that the conflict centered on decisions involving Automattic CEO Matt Mullenweg. Valdivia responded: “Mentors come from various companies or work independently, and we’re all expected to maintain a clear separation between our professional roles and our responsibilities as community mentors. My priority has always been the event’s success and the community’s well-being.”

    Ang claimed that Valdivia, who was on the WordPress Incident Response Team until recently, was assigned to handle a Code of Conduct complaint that Toda submitted about the incident. However, Executive Director Mary Hubbard disputed this, stating the complaint was handled appropriately and denying that Valdivia was involved in the investigation.

    Four months later, the complaint remains unresolved. Toda said he still hadn’t received a resolution to his complaint, and that replies to his emails to the Incident Response Team were averaging 7–9 days.

    Miscommunication, mistrust and moving forward

    The friction over Mumbai’s selection, the 2026 handover, and the Code of Conduct complaint that followed didn’t happen in a vacuum. Organizers and program managers say they reflect deeper, unresolved tensions around communication, trust, and control in the WordPress community.

    As one program manager put it, “At the time, it felt like a combination of miscommunication and scepticism towards anything Automattic people do, plus concerns about gatekeeping, that all contributed to the situation.” Cultural differences and contrasting communication styles also compounded the tension.

    Peira cited a similar mismatch: “Some miscommunication likely came from the expectation mismatch between what was initially communicated (skipping 2026) and what some individuals later demanded (continued control or influence).”

    Ang, meanwhile, said the WordCamp Asia team had lost its autonomy over the event and called on Hubbard to investigate and reinstate the team.

    “We had previously received alignment from the Executive Director that WordCamp Asia would retain autonomy over its leadership and future iterations, a model we’ve upheld since 2020. Yet despite a successful 2025 event, the entire organizing team was removed shortly after, even after offering to support a full handover. That decision remains difficult to understand,” Ang said.

    “I strongly urge [Mary Hubbard] to look into what has happened, and to consider reinstating this highly experienced and decorated team to ensure that the 2026 organizing team receives the support it deserves.”

    Feature image: WordCamp Asia 2025.

  • New FAIR Project Aims to Decentralize WordPress.org Services, Backed by Linux Foundation and Hundreds of Contributors

    New FAIR Project Aims to Decentralize WordPress.org Services, Backed by Linux Foundation and Hundreds of Contributors

    A coalition of WordPress contributors, open source organizations and businesses have launched a project they hope will reshape how WordPress sites connect to the wider ecosystem — and remove dependency on WordPress.org while securing the project’s future.

    Known as FAIR — Federated and Independent Repositories — the project is essentially a plugin that can be installed on any WordPress site, allowing users and hosting companies to connect to decentralized repositories for core, theme, and plugin updates, translations, news feeds, and other hard-coded services that typically rely on WordPress.org — a site owned and controlled by WordPress co-founder Matt Mullenweg.

    FAIR was launched today at Alt Ctrl Org, an independently organized event held alongside WordCamp Europe 2025 in Basel, Switzerland.

    While FAIR’s launch is no surprise — Yoast founder Joost de Valk first proposed the idea in December 2024 in response to Mullenweg’s public attacks following WordCamp US 2024 — what’s surprising is the scale of support behind it. The project has been developed over the past six months by a team of up to 300 people, including many veteran core committers and contributors. 

    Notably, the coalition includes the 20 anonymous contributors who signed an open letter to Mullenweg in December calling for governance reform.

    The effort is being coordinated by de Valk and Crowd Favorite CEO Karim Marucchi, in partnership with the Linux Foundation, which is providing neutral infrastructure and governance support. It’s also being overseen by a three-person technical steering committee comprising longtime contributors Carrie Dils, Mika Epstein, and Ryan McCue.

    “We’ve worked hard to ensure this isn’t just another vanity project,” de Valk told The Repository. “It has structure, transparency, and people with real experience guiding it.”

    “This is about future-proofing the ecosystem,” added Marucchi. “We’re creating the infrastructure that should’ve existed already, and doing it in a way that puts power in the hands of the community.”

    [yarpp]

    A new plugin designed to give users control

    Dils, Epstein, and McCue say the plugin prioritizes transparency, privacy, and security. It removes unnecessary data sharing with WordPress.org, supports cryptographic signing, and introduces Decentralized Identifiers (DIDs) that help developers retain control over distribution, even if a plugin or theme changes hands or their repository is no longer trusted. Each package must also provide a security contact, a requirement aligned with the EU’s upcoming Cyber Resilience Act.

    FAIR also addresses long-standing limitations in the WordPress plugin directory. It allows premium plugins to appear directly in the WordPress dashboard, surfaces details when plugins have been closed or removed, and gives hosts and enterprises tools to filter packages by PHP compatibility or block known vulnerabilities.

    “The idea of a single canonical repo doesn’t match the reality of how WordPress is used today,” said McCue, the creator of the WordPress REST API. “We’ve built FAIR to unify what’s already happening, and to give users more secure, flexible options.”

    CDN company Fastly is powering FAIR’s central infrastructure. According to the company’s Fast Forward Lead Tracy Hinds, “Fastly is proud to champion the FAIR Package Manager project’s efforts to build an ever more vibrant and decentralized WordPress ecosystem. By powering the package manager, we’re supporting the open source principles that drive creativity, collaboration, and the sustained growth of the open internet’s most impactful builders.”

    Built in private, now public

    FAIR has been developed in secret over the past several months to protect contributors from backlash. Today, many of those contributors have revealed who they are, appearing with de Valk and Marucchi during the project’s launch.

    Mullenweg has previously reacted strongly to challenges to his leadership: in January, he banned de Valk and Marucchi from WordPress.org after the pair publicly called for an end to his benevolent dictator for life (BDFL) leadership of the project.

    In December, core committers and contributors urged Mullenweg to pursue “community-minded” governance solutions in an open letter. In November, core committers raised concerns about a “culture of fear” in the project, citing Mullenweg’s “outsized control” and the potentially career-ending risks of speaking out.

    de Valk and Marucchi said they hope FAIR will become a neutral, sustainable foundation for future infrastructure — regardless of whether WordPress leadership supports it. They also emphasized that it’s not a fork.

    “We didn’t build this to divide the community,” said Marucchi. “We built it because the community needs better tools, and because governance should not be controlled by a single entity.”

    Despite past tensions, both said they would welcome Mullenweg and Automattic to join the project. “There’s nothing stopping him from joining,” de Valk said. “If he sees the value in what we’ve built, FAIR could benefit everyone — including WordPress.org.”

    Backed by open source leaders

    FAIR has the backing of the Linux Foundation, a highly respected nonprofit that hosts more than 1,000 open source projects across industries and provides neutral governance frameworks for initiatives like Kubernetes and Node.js.

    “The FAIR Package Manager project paves the way for the stability and growth of open source content management, giving contributors and businesses additional options governed by a neutral community,” said Jim Zemlin, Executive Director of the Linux Foundation. ”We look forward to the growth in community and contributions this important project attracts.”

    Mike Dolan, SVP of Legal & Strategic Programs at the Linux Foundation, also told The Repository that in the short-term, the foundation would support the FAIR project to establish governance, a charter, and security infrastructure and communication tools. In the long-term, support will include events, communications and marketing, release management, best practices, and other help focused on running infrastructure, and the ability to recruit financial support to underwrite the cost of infrastructure and other activities. 

    FAIR has also gained support from other open source leaders, including Chris Aniszczyk, CTO of the Cloud Native Computing Foundation, who called FAIR “a progressive shift toward establishing an independent foundation for plugin distribution” in WordPress. Robin Bender Ginn, Executive Director of the OpenJS Foundation, described it as “critical, community-led infrastructure that strengthens the open source web.”

    While several hosting companies are already testing FAIR and preparing to run it, others are watching closely to see how Mullenweg responds.

    Mullenweg is scheduled to appear at WordCamp Europe 2025 in a closing fireside chat with WordPress Executive Director Mary Hubbard tomorrow. Whether or not he will engage with FAIR remains to be seen, but the coalition behind it has made clear that the door is open.

    The FAIR repository is live on GitHub and accepting contributions.

  • Joost de Valk Banned From WordCamp Asia as Matt Mullenweg Brands Him “Persona Non Grata”

    Joost de Valk Banned From WordCamp Asia as Matt Mullenweg Brands Him “Persona Non Grata”

    WordPress co-founder Matt Mullenweg has banned Joost de Valk from attending WordCamp Asia 2025, publicly branding him “persona non grata” in a fiery social media post. The decision follows a tense private exchange between the pair, where de Valk invited Mullenweg to dinner—only to have the invitation met with accusations of betrayal and a total severing of ties.

    In private messages exchanged last Tuesday on WordPress Slack, viewed by The Repository, de Valk invited Mullenweg to dinner in Manila, where the pair were set to attend WordCamp Asia next week. However, the following day, Mullenweg rejected de Valk’s invitation, telling him, “You stabbed me while I was down” and “I can’t imagine a bigger betrayal.”

    Mullenweg told de Valk that his WordCamp Asia ticket would be rescinded, his access to WordPress.org wrapped up, and his WordPress Slack access revoked. He also asked de Valk not to attend future WordCamps. Shortly after, Mullenweg took to X to amplify his condemnation in a public post.

    “I have given him hundreds of hours of my time and more access than almost anyone in the WP community, including admin access on Google Analytics, a marketing leadership position, and more. This trust was betrayed,” Mullenweg wrote, referring to de Valk’s former role as WordPress’s Marketing Lead.

    “His previous contributions do not ‘make up’ for this behavior, nor has he apologized or taken any conciliatory action. This deeply saddens me. Because of this, I will not interact with him any further or participate with anything he’s involved with, he’s persona non grata.”

    Mullenweg also challenged de Valk’s repeated assertions that he has no plans to fork WordPress, highlighting key phrases—albeit out of context—from an announcement de Valk published on December 20, 2025, calling for an end to Mullenweg’s role as WordPress’ Benevolent Dictator for Life (BDFL).

    The WordCamp Asia ban is the latest in a series of actions Mullenweg has taken against de Valk since December.

    In January, Mullenweg published a post on WordPress.org, claiming that de Valk and Crowd Favorite CEO Karim Marucchi were forking WordPress. In the post, laced with sarcasm, he dismissed their experience and contributions, mockingly referring to their supposed fork as “JKPress.” Mullenweg announced that he was deactivating both of their WordPress.org accounts “to make this easy and hopefully give this project the push it needs to get off the ground.”

    de Valk, who founded the popular Yoast SEO plugin, had been scheduled to speak at WordCamp Asia on the topic “Launching or Finding a WordPress Product in 2025.” He was also tentatively slated to participate in a panel discussion on managing WordPress.

    Progress Planner, a product launched by de Valk’s investment firm, Emilia Capital, last year, has also been banned from sponsoring both WordCamp Asia and WordCamp Europe.

    Speaking to The Repository, de Valk called the decision to ban him “sad” but acknowledged that his push for WordPress governance reform was always “going to go wrong.” de Valk also exchanged messages with Mullenweg the day after his December post and the conversation, also viewed by The Repository, was civil. Mullenweg made no mention of feeling upset or betrayed by de Valk’s actions.

    “I’ve been trying to keep the conversation open because, honestly, what I want to do is figure out what’s best for the community… I think that [Mullenweg] should not be the sole leader,” de Valk said.

    “I’ve been contributing to WordPress for about 20 years now. I just want what’s good for the community, and I think what’s good for the community is if we get governance and start taking things a bit more seriously.

    “I also foresee significant challenges. With WordPress governance in its current state, navigating new European regulations will be very difficult.”

    Following Mullenweg’s messages last Friday, de Valk said Executive Director Mary Hubbard informed him that it would be best if he did not attend WordCamp Asia in the interest of community cohesion. Hubbard confirmed de Valk’s account, telling The Repository:

    “This decision was made with careful consideration and is rooted in maintaining trust and cohesion within the WordPress community—both of which are critical to the project’s health.

    “WordPress has always welcomed healthy debate, differing perspectives, and constructive criticism. However, Joost has indicated that he is working to separate the community rather than engage within it. When actions actively undermine community cohesion, it is appropriate to reassess participation in official events.

    “This decision was communicated directly to Joost, and the necessary steps have already been taken, including a ticket refund, session removal, and sponsorship refund processing.”

    de Valk and his wife and business partner, Marieke van de Rakt, recently made headlines when they acquired Post Status, a popular business community for WordPress professionals, and converted it into a Dutch nonprofit. In March 2024, their investment firm, Emilia Capital, became an investor in Automattic.

    Feature image credit: Fede Padilla.

  • WordPress Contributors and Community Leaders Call for Governance Reform in Rare Open Letter

    WordPress Contributors and Community Leaders Call for Governance Reform in Rare Open Letter

    A group of WordPress contributors, including long-time core committers and community leaders, has issued a rare call for changes to the governance of the open-source project. The group is urging co-founder Matt Mullenweg to work with the community instead of continuing to act unilaterally.

    In an open letter titled “Dear WordPress community: We stand with you,” the contributors raise objections about governance, transparency, and decision-making processes. They highlight concerns about “double standards,” including Mullenweg’s lack of accountability under the project’s Code of Conduct and the executive director’s direct employment by Automattic.

    The letter comes amid Mullenweg’s ongoing legal battle with WP Engine. On Tuesday, WP Engine won a preliminary injunction against Mullenweg and his company, Automattic. The court ordered Mullenweg and Automattic to stop blocking WP Engine’s access to WordPress.org and interfering with its plugins.

    The group provided The Repository with first access to the letter. To protect the signatories—who fear retaliation if named publicly—their identities and roles have not been disclosed publicly. The Repository has verified each of the 18 20 signatories in the group, which comprises senior and influential figures across the WordPress project and the community.

    Read the full text of the open letter at the bottom of this article.

    A call to action amid fear and uncertainty

    The letter was coordinated by a long-time core committer who told The Repository they felt compelled to act after WordCamp US 2024.

    “Never before has the project been dragged into such disputes. Many of us did not have a specific motivation to speak out at any one time, but these actions make it impossible not to,” the committer said. “Matt has also taken drastic actions against people for just disagreeing with him—and communities can only operate effectively with a degree of free speech amongst themselves.”

    Signatories took significant steps to protect their anonymity, even from each other, using single-use aliases and anonymous email addresses. “There is such a great culture of fear that no one trusted anyone,” the committer said. “Ensuring anonymity allowed us to speak freely and openly.”

    Asked why the signatories continue contributing to WordPress despite their frustrations, the committer explained: “Many people have jobs, businesses, and careers tied to the project, and the project is more important than any one person. Many of us have contributed in spite of Matt’s leadership of the project, because it is important.”

    The letter’s key points

    The two-page letter acknowledges the recent turmoil surrounding Mullenweg’s war with WP Engine and the group’s broader concerns about how the WordPress project operates as a community and ecosystem.

    The letter objects to the current governance model, highlighting Mullenweg’s consolidation of power, the ongoing lack of transparency in project decision-making, and the opaque handling of trademark licensing and hosting recommendations. They also object to Mullenweg’s control over all WordPress infrastructure.

    The letter points to the WordPress Foundation’s minimal role in governance, describing it as largely administrative and lacking community oversight. It also takes issue with “continued misrepresentations by Matt Mullenweg of the community and its contributor teams’ efforts.”

    “We believe there has been a major breakdown in trust between Matt Mullenweg and the WordPress community stemming from actions he’s taken since WordCamp US 2024,” the letter states. It adds, “the volatility of the self-governing BDFL (benevolent dictator for life) model has become clearer than ever.”

    The letter concludes with a call for constructive dialogue: “We implore Matt Mullenweg to meditate on these objections and propose community-minded solutions.”

    The signatories encourage others in the WordPress community to share the letter, spread its message, and join the conversation. “We are all part of the WordPress community. We stand together,” the letter states.

    Culture of fear and hope for the future

    Several signatories shared their motivations for signing the letter and the challenges they faced if their names were to be revealed. Their comments shed light on the culture of fear within the WordPress community and the extraordinary measures taken to protect their identities.

    One signatory, a core committer, said they signed the letter because they believe in WordPress’s importance to the open internet. “I’m signing because I still believe the WordPress project is the most important organization for sustaining a human-centered internet,” they said. “But I fear we will waste the opportunity without better governance and more transparent decision-making processes going forward. To quote Matt himself, ‘What got us here won’t get us there.’”

    Another long-time core committer pointed to the emotional and practical toll of recent events on contributors. “I signed largely because of the lack of public recognition by WordPress leadership of the impact to the WordPress project and hurt that Matt’s actions have caused to the folks, largely volunteers, who help to make WordPress,” they said. “Matt’s pattern of actions, and how they’ve been affecting the community, are not new, and I’m glad that changes for project governance are being more openly discussed. My hope is that, more than just objection, the letter will create conversations to find ways forward, to make the WordPress project a safer, more inclusive, and sustainable place.”

    Others raised concerns about the personal risks of speaking out, including potential repercussions such as being blocked from contributing to WordPress, which would impact livelihoods. In November, The Repository reported on this “culture of fear” and the potential career-ending consequences of opposing Mullenweg, particularly for sponsored contributors.

    “I think it’s a situation that’s been building for a while,” another core committer said. “The letter is the culmination of events over the past 12–18 months that have reached a tipping point with the WP Engine situation—that was the hay bale that broke the camel’s back.”

    The committer who organized the letter said they hoped Mullenweg would deeply reflect on the concerns raised. “I’d like him to consider whether any of this truly supports the mission of democratizing publishing or creating a stable platform for future generations.”


    The full text of the open letter:

    Dear WordPress community: We stand with you

    To the WordPress community,

    In light of the recent turmoil between Matt Mullenweg as project leader and Automattic CEO, and WP Engine, we have written this joint statement expressing our concerns with how WordPress operates as a community and an ecosystem.

    This letter is not about picking a side in the case before the courts, rather it is about surfacing the issues—as we see them—to drive the project forward to a better future.

    We are:

    • Core committers and contributors
    • Make/WordPress team elders and contributors
    • Others serving in various community roles

    We are you.

    Our anonymity is a shield against retaliation by Matt Mullenweg or others. Our names and roles within the project have been independently verified by Rae Morey from The Repository.

    We object:

    We object to the status quo, and believe the WordPress project’s current internal operating structure threatens the health and sustainability of the project and its community.

    On governance:

    • We object to the continued opaqueness of the WordPress governance model.
    • We object to one person, Matt Mullenweg, controlling all official infrastructure, including the project’s website, email systems, support forums, core, plugin, and theme repositories, update systems, security tools, communication channels, and other technical assets.
    • We object to major decisions being made without community input, advice, or support.
    • We object to a project model where influence granted can overrule influence earned.
    • We object to the WordPress Foundation playing no meaningful role in the governance of the WordPress project outside of administering meetups and WordCamps via its PBC subsidiary, WordPress Community Support.

    On transparency:

    • We object to continued misrepresentations by Matt Mullenweg of the community and its contributor teams’ efforts.
    • We object to the WordPress Foundation continuing to lack community participation or oversight.
    • We object to the continued lack of transparency around all licensing and sub-licensing of the WordPress trademarks.
    • We object to the lack of transparency around how recommended hosts are determined.

    On double standards:

    • We object to project leader Matt Mullenweg not being accountable to the project’s own Code of Conduct policy.
    • We object to WordPress having an executive director who is employed by Automattic—not the WordPress Foundation—and who is therefore accountable only to Matt Mullenweg in his role as Automattic’s CEO.
    • In summary, we object to the continued absence of an official Conflict of Interest policy and the notion that it’s possible for one person, Matt Mullenweg, to have simultaneously served in several key positions of power (project leader, Automattic CEO, and WordPress Foundation board member) for so long.

    We believe:

    1. We believe there has been a major breakdown in trust between Matt Mullenweg and the WordPress community stemming from actions he’s taken since WordCamp US 2024.
    2. We believe the volatility of the self-governing BDFL model has become clearer than ever.
    3. We believe the unchecked disrespect from Matt Mullenweg towards contributors, community members, and members of the public is unacceptable.
    4. We believe continuing to contribute to WordPress over these objections will ultimately be a personal decision for us all, as well as an economic one for those whose contributions are a source of their livelihood.

    We want to work together:

    We implore Matt Mullenweg to meditate on these objections and propose community-minded solutions.

    If you are a contributor or community member who finds our objections resonate with you, please share this letter within your networks and help us spread the word.

    We are all part of the WordPress community. We stand together.

    Sincerely,
    The contributors

  • Core Contributors Voice Concerns Over Mullenweg’s Control and “Culture of Fear” in WordPress Community

    Core Contributors Voice Concerns Over Mullenweg’s Control and “Culture of Fear” in WordPress Community

    Veteran WordPress core committers and contributors have described a “culture of fear” within the project, driven by co-founder Matt Mullenweg’s “outsized control” and the potentially career-ending consequences of opposing him. Many say the lack of formal governance has left them vulnerable to the whims of Mullenweg, whose recent actions have raised questions about the future direction of WordPress.

    Bans of prominent voices critical of Mullenweg’s leadership, like WordPress REST API creator Ryan McCue, highlight what they describe as an unhealthy power dynamic, where speaking out risks livelihoods. “Angering Matt has the potential to render our ability to make a living as contributors moot,” according to one committer. “That’s scary as hell.”

    In recent weeks, The Repository has spoken with numerous long-time committers and contributors who requested anonymity out of fear of retaliation. While many agree that WP Engine should contribute more to WordPress—but aren’t required to do so, under the GPL—they disapprove of Mullenweg’s “nuclear” approach, which one committer described as “unnecessarily divisive.” As another contributor explained, “We can agree with Matt’s goals, but the way he’s treating people who disagree with him is unacceptable.”

    Mullenweg’s “War” with WP Engine — and the Community

    In September, Mullenweg declared a self-described “war” with WP Engine, a competitor to his company Automattic, calling it a “cancer to WordPress” and accusing it of trademark infringement and failing to contribute enough to the project. WP Engine responded by filing legal action, alleging abuse of power, extortion, and anti-competitive behavior.

    Since then, Mullenweg has blocked WP Engine and its employees—including prominent community members like StudioPress founder Brian Gardner—from WordPress.org. Other actions, such as banning contributors who questioned his decisions, adding a checkbox on WordPress.org with vague legal implications, and publicly disclosing a vulnerability in Advanced Custom Fields (ACF) before taking it over, have left contributors concerned about the project’s stability and direction. For contributors whose careers depend on WordPress, these actions, and the ways in which Mullenweg has antagonized contributors, have raised serious concerns, highlighting the risks of an unchecked, “benevolent dictator for life” governance model.

    One committer described his shock at seeing “private Matt” on the stage at WordCamp US 2024, as opposed to the affable “public Matt” the WordPress community is more familiar with. “For a lot of us who have gotten to know Matt in various capacities over the years, the sentiment itself (WP Engine not contributing enough) was not really news. But private Matt and public Matt are very different personalities, and in some ways it was shocking to see private Matt show his face in public with how he called out WP Engine,” they said.

    Another contributor said they were upset that former Executive Director Josepha Haden Chomphosy and key members of the WordPress Community team had left the project, including Naoko Takano, who quit in protest after 14 years at Automattic.

    Growing Fear Amongst Contributors

    “The fear of retribution from Matt for even seemingly innocuous feedback is very real at the moment. It’s very telling that so many high-level contributors aren’t speaking out,” said one committer, who has been instructed by their employer not to engage in public discussions about the WordPress “drama.”

    Another said they feared losing their job: “The thing I have most to lose is Matt reaching out to [my employer] and saying, ‘Hey, get rid of [name removed].’ That’s the thing I worry about the most, really, is retaliation. Because I’ve heard he’s done that before.”

    Contributors said they felt stuck, as publicly disagreeing with Mullenweg could result in a ban from WordPress.org, potentially ending their involvement with the project, but not speaking out was stifling meaningful discussion about how to move the open-source project forward.

    “I know plenty of people who are working at various companies because of their level of influence in whatever area of WordPress. Absent that influence, their employability could be questionable though,” said one committer. And that all feeds right back into this pervasive fear. Matt holds an outsized amount of power over this community and he’s currently flexing it to silence a lot of people, intentionally or otherwise.”

    Another committer said following WordCamp US 2024, it “quickly became apparent that Matt was doing ‘alignment’ in the community,” referring to Automattic’s recent buyout offers.

    “We’re not speaking out because we fear retribution. We saw it with Ryan McCue being blocked—people are understandably cautious,” they said. “The culture of WordPress in the past few weeks has become a culture of fear among senior and established contributors.”

    High-profile Contributors Step Back, Others Stuck

    While many core contributors are keeping a low profile, others “who can afford to be brave,” as one committer described, have been vocal about stepping away from the project, including Colin Stewart, Tonya Mork, Andy Fragen, and Scott Kingsley Clark. Their departures last month followed McCue’s shock ban. McCue, a high-profile core committer, was instrumental in enabling WordPress to be used in custom and enterprise applications via the WordPress REST API.

    McCue voiced his opposition to Mullenweg and Automattic’s trademark claims and offered ideas for how the WordPress Foundation could govern the project in two blog posts. It’s widely believed these posts led to his ban.

    Many committers and contributors The Repository spoke to have already cut back their contributions or are contemplating leaving the project, questioning whether their continued involvement is sustainable under Mullenweg’s control. At least one has already quietly quit.

    Others need to keep a roof over their head, as one committer put it. Some who hold influential roles feel they have no choice but to stay because leaving and starting again, potentially outside of the WordPress ecosystem, isn’t a possibility they want to entertain.

    Unease Over Mullenweg’s Control

    For many, the project’s historical governance model—or lack thereof—has long been accepted. But contributors agree that Mullenweg’s power has gone largely unchecked, and his recent actions, despite his informal title as the project’s BDFL, have escalated concerns. They now want proper governance and believe it’s the only way forward if the WordPress community is to survive the current crisis intact.

    “Everything in WordPress hummed along mostly fine under this governance model for years, with the occasional, mostly inconsequential tantrum from Matt,” one committer said. “But now, sensibility has been thrown out the window. This governance model is no longer viable for me as a contributor.” Another echoed this sentiment: “Without governance, it’s just Matt’s will. It’s not a community-driven project.”

    Many contributors expressed feeling disenfranchised. “Some of us feel we’re just here to execute [Mulleweg’s] vision, not shape it,” said one committer. “For people who have dedicated years, sometimes decades, to WordPress, that’s hard to accept. We’re invested in this project, but we have no control.”

    Some contributors highlighted WordPress’s “bus factor of one” — meaning the entire project’s stability relies on Mullenweg alone — as a significant risk. “What if Matt’s no longer around?” one said. “He’s built the project in such a way that we’re dependent on him — it’s not sustainable.”

    Another contributor also highlighted the lack of succession planning, noting that Mullenweg had not trained anyone to take over his role should he ever step back. This absence of a clear plan, they said, left the project vulnerable and unable to operate independently of Mullenweg’s influence.

    In an interview with The Repository on September 30, 2024, Mullenweg was asked about his succession plans for WordPress in the event of his death. He cryptically replied, “I have thought about these things deeply and make plans in decades.”

    Contributors Contemplate Project’s Future

    One contributor summed up the stakes: “For some people, WordPress is their whole life, and it’s hard to watch what’s happening now. It makes you question if you’re putting all this effort in only for someone else to have the final say on everything.”

    As Mullenweg’s war with WP Engine continues—and could go on for at least two years—the concerns of committers and contributors have raised questions about the project’s long-term sustainability and the need for more balanced governance. Contributors worry that without structural changes, the project’s collaborative spirit has been put at risk, with many saying they no longer want to be involved unless there’s change.

    “If anything, the fear is increasing each week as this whole thing goes on and it’s only been seven weeks,” one committer said. “I feel like I’ve made a promise to other contributors for the time being, but I’m reevaluating where and how I contribute and whether I want to contribute to core as much as I do.”

    These concerns come a day before Core Days, a two-day event in Rome dedicated to WordPress core developers. With contributors gathering amid ongoing uncertainty, recent tensions may overshadow this opportunity to focus on technical contributions.”

    Image credit: John Carlo Pattaguan.

  • [Updated] Mullenweg Threatens To Take Over Paid Memberships Pro

    [Updated] Mullenweg Threatens To Take Over Paid Memberships Pro

    Update, November 3, 2024: WordPress co-founder Matt Mullenweg says he would like to discuss “misunderstandings” over his apparent threat to takeover over Paid Memberships Pro with its CEO, Jason Coleman.

    Responding to questions from The Repository, Mullenweg said: “I’d love to talk to Jason directly but he hasn’t responded to me. I think there are some misunderstandings.”


    Matt Mullenweg has threatened to take over Paid Memberships Pro (PMPro) in the WordPress.org plugin repository, according to private messages between the WordPress co-founder and PMPro CEO Jason Coleman.

    Mullenweg messaged Coleman in Making WordPress Slack on October 18, writing that he wanted to “check in” with Coleman about his announcement two days earlier that from version 3.3 onward, PMPro would be hosted on the company’s own license server instead of WordPress.org.

    Mullenweg warned Coleman: “because [sic] if you go down that path, next step is for us to take over your listing and make it a community plugin like we did to ACF.

    “is [sic] that what you want? you [sic] can’t have it both ways, you’re violating the directory guidelines right now.”

    Coleman, who showed the messages to The Repository during a video call, said he sought legal advice before deciding not to respond to Mullenweg’s messages. Mullenweg later emailed Coleman to check that he had seen the Slack messages, but Coleman also chose not to reply.

    Mullenweg’s threat to takeover PMPro follows WordPress.org’s recent controversial takeover of WP Engine’s popular Advanced Custom Fields (ACF) plugin. It also comes amid ongoing conflict between WP Engine and Automattic, with WP Engine filing legal action against Mullenweg and Automattic earlier this month, alleging abuse of power, attempted extortion, and anti-competitive practices.

    In his announcement on October 16, Coleman said Paid Membership Pro’s premium plugins, and several free ones, had been served from his company’s own license server for many years. Downloads and updates for the company’s free, core version of Paid Membership Pro would be available from the server from version 3.3 onwards, he said.

    PMPro was permanently closed in the repository on October 17. Coleman said he had contacted the WordPress Plugin Review Team to have the plugin removed, and the team had quickly responded and complied with his request.

    PMPro, which launched on WordPress.org in July 2011, had an average rating of 4.3 out of five stars at the time of its removal.

    In a follow-up post published yesterday, Coleman revealed Mullenweg’s threat and shared more about the company’s decision to pull PMPro from WordPress.org, citing concerns over potential user disruptions.

    “We began seriously thinking about these issues in early 2023 and decided that PMPro would have to move off the .org site eventually. We planned on a longer transition, but when Matt started blocking long time .org contributors for petty reasons and took over the Advanced Custom Fields plugin, we decided that it was best for our users to start updating PMPro from our own server while we still had the most control over how that would happen,” Coleman said.

    He hoped that Mullenweg would let PMPro “leave the repository without further disruption.”

    “Taking over the ‘paid-memberships-pro’ slug and hosting a forked version would only create confusion,” he said. “There’s no good reason for Matt and his team to attempt this takeover.”

    Paid Memberships Pro powers 60,000-90,000 sites, most of which are small businesses or nonprofits, Coleman said, and any “tampering with the PMPro listing [on WordPress.org] could cause confusion and damage.”

    Coleman addressed concerns about potential retaliation from Mullenweg, writing, “The fact that we even have to consider this possibility is why we had to make this move.”

    Speaking to The Repository, he speculated that Mullenweg may not have been aware that PMPro had already been removed from the repository the day before he issued his threat on Slack.

    “Hopefully, he’ll realize there’s no point in pursuing it further,” Coleman said. “But if he does, we’re ready, we’re able to continue serving PMPro without disruption to our customers.”

    PMPro is among several plugins that have been pulled from the WordPress.org plugin repository in recent weeks amid growing concerns that WordPress.org is no longer a secure place to host plugins.

    Mullenweg was contacted for comment.

  • Mullenweg threatens corporate takeover of WP Engine

    Mullenweg threatens corporate takeover of WP Engine

    Automattic CEO Matt Mullenweg has rescinded an 8% licensing deal offered to WP Engine in September, suggesting that escalating tensions between the two companies could lead to a corporate acquisition by Automattic.

    In an interview with The Repository, Mullenweg said Automattic now wanted more than 8% of WP Engine’s annual revenue, or an equivalent of resources invested into the WordPress project—or a combination of both—in exchange for the use of its “WordPress” and “WooCommerce” trademarks.

    “That deal’s not on the table anymore. We’re seeking more, not 8%,” Mullenweg said. “I don’t want to speculate on what the deal might be… In July it was less than 8%, it was smaller. In September it was 8%. The deal they have to do next could be taking over the company, they have no leverage.”

    Mullenweg’s latest comments come as Automattic and WP Engine remain locked in a tense stand-off more than a week after he called the rival hosting company a “cancer to WordPress,” accusing it of profiting off the WordPress project and violating trademarks.

    While WP Engine has remained tight-lipped over the past week, Mullenweg has ramped up his public criticism of WP Engine through social media, interviews, and livestreams, following years of private negotiations that he says failed to reach an agreement.

    “I didn’t wake up one day and suddenly decide to do this,” he said. “I was taken advantage of for so many years. The only way to deal with a bully is to fight,” he said.

    “[WP Engine is] a half-a-billion dollar company. [WP Engine’s main investor] Silver Lake has disrupted the ecosystem. I’m fighting for my life’s work.”

    Mullenweg said his public attacks would continue, adding “I have a lot to work with.”

    Silver Lake used to hold this asset (WP Engine) on their books for $2 billion… They stand to lose billions [in the event of a corporate takeover].”

    Mullenweg’s comments come after he posted in Making WordPress Slack on Saturday about potentially bringing ACF Pro, the premium version of WP Engine’s Advanced Custom Fields (ACF) plugin, into WordPress core.

    How the conflict started

    Mullenweg blew up WordCamp US 2024 when he called out WP Engine’s apparent minimal contributions to WordPress and Five for the Future in his keynote address on September 20.

    According to Five for the Future, WP Engine currently sponsors 11 contributors for a total of 40 hours per week across five teams. By contrast, Automattic, sponsors 116 contributors for a total of 3,948 hours per week across 22 teams. Both companies, as Mullenweg highlighted in WordCamp US & Ecosystem Thinking ahead of his keynote, are roughly the same size with revenue in the ballpark of half a billion.

    During his keynote, he also took aim at WP Engine’s main investor, Silver Lake, and specifically its Managing Director, Lee Wittlinger. He acused the private equity firm of maximizing profits over fostering open source values since investing in WP Engine in 2018.

    Mullenweg urged the WordPress community to “vote with your wallet,” urging folks to support companies that invest back into WordPress rather than those that prioritize extracting value from the ecosystem without giving back.

    In a follow up post on WordPress.org, WP Engine is not WordPress, Mullenweg doubled down on his talk, describing Silver Lake as “hollowing out” the open source WordPress project.

    He highlighted WP Engine’s long-time practice of turning off revisions to support his claims, describing the company as “strip-mining the WordPress ecosystem, giving our users a crappier experience so they can make more money.”

    “What WP Engine gives you is not WordPress, it’s something that they’ve chopped up, hacked, butchered to look like WordPress, but actually they’re giving you a cheap knock-off and charging you more for it,” Mullenweg wrote.

    “This is one of the many reasons they are a cancer to WordPress, and it’s important to remember that unchecked, cancer will spread. WP Engine is setting a poor standard that others may look at and think is ok to replicate. We must set a higher standard to ensure WordPress is here for the next 100 years.”

    WP Engine fires back

    WP Engine quickly hit back, their legal counsel sending Automattic a cease and desist letter on September 23. In the letter, WP Engine claims that in the days leading up to Mullenweg’s keynote address, Automattic suddenly began demanding large sums of money—”a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis,” according to the letter — and if it didn’t, “Automattic would wage a war against WP Engine.”

    “This demand was accompanied by allegations about WP Engine’s business that were not only baseless but also bore no rational relation to the payment demand,” the letter claims.

    The letter also contains several examples of text messages that WP Engine says demonstrate how Mullenweg attempted to pressure the company into giving into Automattic’s financial demands.

    WP Engine also defends its contributions to WordPress, highlighting the “tens of millions of dollars” it gives back through events, sponsorships, and the development of educational resources, including WordCamps, its DE{CODE} conference, as well as maintaining popular projects including ACF, WPGraphQL, and faust.js.

    Automattic reveals trademark disputes

    The same day, September 23, Automattic’s legal counsel issued its own cease and desist letter, revealing a critical piece of the puzzle missing from Mullenweg’s WCUS keynote: Automattic’s claims that WP Engine is violating the “WordPress” and “WooCommerce” trademarks.

    In the letter, Automattic claims WP Engine has developed a business generating annual revenue of over $400 million, which has been “based entirely on extensive and unauthorized uses of the trademarks.”

    The letter states that Automattic remains exclusive commercial rights to the trademarks from the WordPress Foundation, and WP Engine needs a license to use them.

    As well as ceasing all unauthorized uses of the trademarks, Automattic demands compensation for its lost licensing revenue, suggesting an 8% royalty on WP Engine’s $400 million in annual revenue, or $32 million.

    Mullenweg has since clarified that the 8% deal offered was for a percentage of WP Engine’s annual revenue, an equivalent in contributions to the WordPress project, or a combination of both.

    In a post accompanying the cease and desist letter, Automattic claims it tried “for years” to get WP Engine to obtain a commercial license for trademark use and contribute to the WordPress project, but the hosting company had repeatedly declined to partner or give back.

    Shortly after the letter was published, the WordPress Foundation—of which Mullenweg is one of three board members—changed its Trademark Policy page, calling out WP Engine for allegedly confusing users:

    Previously, the text stated:

    The abbreviation “WP” is not covered by the WordPress trademarks and you are free to use it in any way you see fit.

    The updated text states:

    The abbreviation “WP” is not covered by the WordPress trademarks, but please don’t use it in a way that confuses people. For example, many people think WP Engine is “WordPress Engine” and officially associated with WordPress, which it’s not. They have never once even donated to the WordPress Foundation, despite making billions of revenue on top of WordPress.

    It was also revealed last week that the foundation filed trademark applications for “managed WordPress” and “hosted WordPress” in July. The revelation has sparked fears among developers and business owners that if these trademarks are granted, they could be used against them.

    Mullenweg escalates attacks

    In an apparent attempt at hiding Mullenweg’s recent posts on WordPress.org, WP Engine removed the news widget from its users’ dashboards on September 24, reportedly breaking thousands of sites in the process.

    The following day, Mullenweg further escalated things when he banned WP Engine from accessing WordPress.org and its resources. The move blocked WP Engine-powered sites from plugin and theme updates, also breaking sites.

    In Post Status Slack, developer Brian Coords accused Matt Mullenweg of “weaponizing” developers:

    In response to the ban, WP Engine accused Mullenweg of misusing his control of WordPress to interfere with WP Engine customers’ access to WordPress.org.

    Matt Mullenweg’s unprecedented and unwarranted action interferes with the normal operation of the entire WordPress ecosystem, impacting not just WP Engine and our customers, but all WordPress plugin developers and open-source users who depend on WP Engine tools like ACF. We are taking immediate steps to remediate the impact of this action. We remain steadfastly committed to supporting WP Engine customers, users, and the entire WordPress community,” WP Engine posted on X.

    Mullenweg hit back, accusing WP Engine of failing to resolve “Stripe issues.” He later clarified in an interview with ThePrimeTime that WP Engine had been siphoning “tens of millions” of dollars away from Woo’s revenue share partnership with Stripe into its own coffers. It’s understood WP Engine has been swapping out WooCommerce’s Stripe Connect Account information for its own when a user installs WooCommerce.

    On September 27, the WordPress.org ban was temporarily lifted to allow WP Engine to access resources until October 1, giving the company a brief window of time to find a workaround.

    In an interview with YouTuber Theo Browne on September 29, Mullenweg said he had disabled the WP Engine developer account on WordPress.org, blocking the company from accessing and deploying code to their plugins, including ACF.

    On September 30, WP Engine updated its site footer to clarify its use of the WordPress, WooCommerce and Woo trademarks, and that it’s not directly affiliated with the WordPress Foundation or WooCommerce, Inc.:

    WP Engine is a proud member and supporter of the community of WordPress® users. The WordPress® trademark is the intellectual property of the WordPress Foundation, and the Woo® and WooCommerce® trademarks are the intellectual property of WooCommerce, Inc. Uses of the WordPress®, Woo®, and WooCommerce® names in this website are for identification purposes only and do not imply an endorsement by WordPress Foundation or WooCommerce, Inc. WP Engine is not endorsed or owned by, or affiliated with, the WordPress Foundation or WooCommerce, Inc.

    The company has also changed its plan names from “Essential WordPress,” “Core WordPress,” and “Enterprise WordPress” to “Essential,” “Core,” and “Enterprise.”

    On October 1, WP Engine posted on X that it had deployed a solution allowing its customers to again access plugins and theme updates:

    It’s not clear what WP Engine’s solution is—whether they’ve mirrored WordPress.org repositories—and if the solution is temporary or permanent, or how the company plans to prevent future disruptions.

    What next?

    When asked what his legal counsel has advised regarding his speaking out publicly, Mullenweg told The Repository, “When you’re right, you can talk. When you’re wrong, [the lawyers] tell you to shut up. My lawyers are fine, they’re like, ‘go for it!’”

    He said he hadn’t spoken to Wittlinger since his text messages ahead of his WCUS keynote. On Saturday, Mullenweg challenged Wittlinger to debate with him publicly.

    As tensions escalate, Mullenweg shows no signs of backing down, leaving open the possibility of a corporate takeover or legal battle to resolve the dispute.