Greenwashing original post: [[3. Resources/Readwise/Full Document Contents/Articles/Greenwashing|Greenwashing]] Greenwashing summarized post: [[3. Resources/Readwise/Articles/Greenwashing|Greenwashing]] WCEU chat summary about sustainability [[3. Resources/Readwise/Podcasts/Fireside chat with Q&A Mary Hubbard and Matt Mullenweg|Fireside Chat With Q&A Mary Hubbard and Matt Mullenweg]] WCEU chat transcript sustainability [[3. Resources/Readwise/Full Document Contents/Articles/Fireside chat with Q&A Mary Hubbard and Matt Mullenweg|Fireside chat with Q&A Mary Hubbard and Matt Mullenweg]] # The Weaponization of Environmental Rhetoric: Matt Mullenweg's Sustainability Hypocrisy The discovery of Matt Mullenweg's October 4, 2025 blog post "Greenwashing" transforms what appeared to be simple hypocrisy into something far more troubling. Matt didn't write about environmental greenwashing to critique corporate environmental claims. Instead, he appropriated the serious concept of greenwashing and its associated environmental terminology as rhetorical weapons in his ongoing business dispute with WP Engine. This appropriation occurred just months after he disbanded WordPress's Sustainability Team, revealing a pattern where environmental concerns matter to him only when they serve as useful metaphors for business conflicts, not when they require actual commitment or resources. <!-- atomicity: 1 idea ✓ --> ## The post that reveals everything Matt's blog post begins promisingly enough, attending a dinner honoring David Gelles' book about Patagonia founder Yvon Chouinard. Matt positions himself as someone who understands and values genuine environmental commitment, referencing Chouinard's 2018 book "Let My People Go Surfing" and expressing admiration for how Chouinard gave away his company equity to ensure environmental focus. He then provides the United Nations definition of greenwashing, which includes claiming future environmental milestones without sufficient plans, being intentionally vague about operations, highlighting one environmental achievement while ignoring others, and promoting minimal regulatory compliance as exceptional. But then the post pivots sharply. Matt writes that "in WordPress and open source our environmental crisis comes from companies that frack the open source software and brands." This isn't environmental language being used carefully as analogy. This is environmental terminology being hijacked wholesale. He describes lack of code investment as software "falling fallow," uses "frack" to describe business practices, and calls companies "parasitic cancers" that attach to brands while "tricking people." He coins the term "openwashing" to describe what he sees as companies appearing to support open source while allegedly undermining it. The target becomes clear when Matt writes about companies hiring "a good person" or sponsoring events representing "hundreds of thousands of dollars of investment" while supposedly spending "tens of millions" to "destroy the source of everything they've benefited from." This is his ongoing attack on WP Engine, dressed in borrowed environmental language. The entire sophisticated framework of greenwashing analysis exists not to examine actual environmental issues but to weaponize environmental concepts against a business competitor. ## Why this appropriation matters deeply When Jaap Wiering stood before Matt at WordCamp Europe 2025 in Basel and pleaded for the Sustainability Team's reinstatement, he opened with "Tomorrow is World Ocean Day. Our oceans are in danger and have immense influence on our climate." He was speaking about actual environmental reality. The oceans are genuinely in danger. Climate change represents an existential threat to planetary systems. The WordPress Sustainability Team wanted to address how a platform powering forty-three percent of all websites could reduce its environmental footprint. Matt's response was to question whether WordPress was even the right place to focus on environmental impact. He demanded evidence of return on investment from unpaid volunteers. He suggested sustainability should simply be "embedded in everything" rather than having a dedicated team, despite WordPress maintaining dedicated teams for accessibility, performance, and numerous other cross-cutting concerns that also need to be "embedded everywhere." Yet just months later, Matt publishes a blog post where "environmental crisis" means trademark disputes, where "fracking" describes business practices, where "greenwashing" becomes "openwashing" to attack competitors. The contrast couldn't be starker. Real environmental concerns warranted dismissal and demands for ROI metrics from volunteers. Metaphorical environmental language warranted a carefully crafted blog post leveraging UN definitions and prestigious environmental figures like Yvon Chouinard. This reveals that environmental concepts matter to Matt only as rhetorical devices, not as subjects worthy of substantive work. The WordPress community members who tried to create carbon footprint measurement tools, sustainable event guidelines, and performance optimization frameworks paired with consumption reduction strategies now see their dismissed concerns transformed into business attack metaphors. Charlotte Bax organized a petition with three to four hundred signatures requesting the team's reinstatement. That actual environmental work was deemed insufficiently productive. But environmental language proved quite productive when weaponized against WP Engine. ## The dissolution that preceded the appropriation Understanding the full scope of this hypocrisy requires examining what happened to the WordPress Sustainability Team. On January 8, 2025, Matt Mullenweg sent a Slack message that read: "Today I learned that we have a sustainability team. Thank you Thijs Buijs for your effort in this area, looking at results of the team so far, and the ROI of time invested, it's probably a good time to officially dissolve the team entirely." He immediately archived the sustainability Slack channel, ending eighteen months of official operations and two years of community organizing. This message contained three layers of problematic reasoning. First, claiming ignorance about an official WordPress team with elected representatives, published roadmaps, and regular meetings for eighteen months suggests either genuine disconnection from the project or deliberate minimization of inconvenient work. Neither reflects well on leadership. Second, demanding ROI from unpaid volunteers working in spare time sets an impossible standard, particularly when those same volunteers received zero organizational resources, budget, or dedicated support. Third, the suggestion that sustainability work might lack sufficient value to continue came from someone whose company simultaneously publishes sustainability reports and environmental claims. The team's actual accomplishments were substantial by any reasonable volunteer standard. They created the Sustainable Events Handbook for WordCamp organizers, translated into Spanish and French. They collaborated with the Performance team on code optimization. They developed integration plans with diversity, equity, inclusion and Five for the Future initiatives. They published roadmaps with GitHub project tracking. Active work at the time of dissolution included a WordPress carbon footprint plugin, sustainability guidelines for WordPress websites, contributor dashboard initiatives, and funding sustainability research through GitHub Sponsors and Open Collective. These were concrete deliverables from unpaid volunteers working on a project affecting hundreds of millions of websites. The team had approximately two hundred Slack channel members and four elected representatives, all self-sponsored. Nahuai Badiola, a team co-founder, later explained that "the team was formed mainly by self-sponsored people so the pace of task completion was much slower than we would have liked it to be. We were doing the best we could with what we had." Matt provided no resources, then criticized insufficient output. This represents a classic management failure, like refusing to fund a department while demanding it match well-funded competitors' productivity. ## Automattic's parallel environmental claims While Matt disbanded volunteer sustainability efforts, his company Automattic maintains active environmental claims and sustainability reporting. The company's sustainability page, last updated in 2021, states: "We spend our days making the internet a better place and recognize that our planet's survival is essential to the continued existence of the web." The page reports eighteen hundred fifty tons of annual carbon dioxide emissions from data centers, approximately fifty percent renewable energy usage as of 2020, and carbon offset purchases totaling sixteen hundred thirty tons from UN programs and three hundred seventy tons from BeZero in 2021. Automattic's 2020 blog post "Toward zero: Reducing and offsetting our data center power emissions" announced an internal employee resource group focused on sustainability and claimed that "servers running WordPress.com, WordPress VIP, Tumblr, and other Automattic services contribute net zero carbon emissions." The company employs paid staff to calculate emissions, purchase offsets, publish sustainability reports, and maintain this internal Automattician Resource Group dedicated to environmental work. The contradiction crystallizes when we recognize that Automattic resources paid employees for environmental work that serves corporate reputation management while Matt disbanded community volunteers attempting parallel work for the broader WordPress ecosystem. The ROI he questioned for volunteers apparently doesn't apply to Automattic's own sustainability reporting, which generates positive press and corporate credentials rather than measurable environmental impact. What's the actual ROI of Automattic's sustainability page? It provides exactly what the Sustainability Team could have delivered for WordPress.org at massive scale: credibility, guidance, and frameworks for addressing environmental concerns. ## The UN greenwashing criteria applied Matt helpfully provides the United Nations greenwashing definitions in his blog post. Examining his own behavior against these criteria reveals the depth of contradiction. The UN warns against claiming future environmental milestones while not putting sufficient plans in place. Automattic's 2020 announcement of net zero carbon emissions and an internal sustainability group occurred while Matt later disbanded the community team that could have created WordPress-wide sustainability frameworks and tools. The plans existed only as corporate PR, not as substantive ecosystem-wide commitment. The UN cautions against being intentionally vague or using claims that cannot be proven. Automattic's sustainability page makes broad statements about planetary survival being "essential to the continued existence of the web" while providing limited specific data beyond 2021 carbon calculations. There's no indication of how these corporate-level efforts translate to the broader WordPress ecosystem or what ordinary WordPress users should do about their environmental impact. The UN identifies highlighting one thing done well regarding the environment while not doing anything else. Automattic emphasizes remote work's climate benefits and data center carbon offsets while refusing to support broader sustainability work across an ecosystem powering nearly half of all websites. The narrow focus on Automattic's own operations ignores the vastly larger environmental footprint of the entire WordPress ecosystem, which the Sustainability Team was attempting to address. This represents textbook greenwashing behavior. Automattic makes environmental claims sufficient for corporate reputation management while actively preventing the substantive work that would address WordPress's actual environmental impact at scale. The framework Matt uses to attack WP Engine for "openwashing" applies with devastating accuracy to his own relationship with environmental sustainability. ## The WordCamp Europe confrontation At WordCamp Europe 2025 in Basel, the WordPress community attempted to reverse the dissolution decision. Charlotte Bax organized a spontaneous petition collecting three to four hundred signatures calling for team reinstatement. During the final question and answer session, contributor Jaap Wiering made a public plea that included the World Ocean Day reference and concluded: "Please, could you reactivate the Sustainability Team so we can make WordPress more environmentally friendly?" The audience applauded enthusiastically. Both WordPress Executive Director Mary Hubbard and Matt Mullenweg declined to reinstate the team. Matt's explanation revealed fundamental misunderstandings about sustainability work. He stated: "We need to measure results. I talked to a number of people on the team, I read some reports, I reviewed, I think, twelve months of blog posts. And I don't think the sustainability team had that output culture, if I'm really candid." He suggested sustainability should be "embedded in everything we do" rather than having a dedicated team, then questioned whether WordPress was even appropriate for environmental focus: "It's an area I've spent a ton of time on, on a number of environmental non-profits over the years. I deeply care about this. I also feel like, it doesn't feel like WordPress, at least for me, is the place to have the biggest impact in the world there." These responses fail on multiple levels. The output culture criticism ignores that the team received zero resources while being compared to well-funded corporate sustainability teams. The "embedded everywhere" argument contradicts WordPress's own structure, where the Accessibility Team exists specifically to ensure accessibility gets embedded across WordPress, and the Performance Team coordinates performance optimization without people questioning why it isn't just "embedded everywhere." Sustainability requires coordination, specialized knowledge, and dedicated attention, exactly what the team provided. The suggestion that WordPress isn't the right place for environmental impact is particularly absurd coming from someone leading a platform powering over forty percent of all websites. WordPress has enormous leverage to influence web sustainability. The Sustainable Events Handbook alone affects hundreds of WordCamps annually. The carbon footprint plugin in development could help millions of site owners understand and reduce environmental impact. If WordPress isn't the right place for Matt to focus environmental efforts, why does Automattic maintain a sustainability page and publish carbon offset claims? The logic is fundamentally inconsistent, revealing that sustainability matters for Automattic's corporate reputation but not enough to support community-led work on identical issues. ## Expert analysis of the leadership failure Hannah Smith, Director of Operations at Green Web Foundation and former Sustainability Team supporter, published detailed analysis explaining why WordPress leadership should prioritize this work. She identified three concrete reasons, starting with legal requirements. Europe's Corporate Sustainability Reporting Directive mandates that companies representing approximately eighty percent of European GDP report Scope 3 greenhouse gas emissions, which includes cloud services and data center usage. WordPress hosts and agencies need sustainability data to comply with these regulations. The Sustainability Team was developing exactly the frameworks and tools that would help WordPress businesses meet these legal obligations. Smith's second reason addressed competitive pressure. Competitors like Umbraco CMS and Wagtail CMS provide sustainability guidance through dedicated teams. Former Automattic employees report that winning WordPress VIP contracts in regulated industries increasingly requires satisfactory sustainability responses to requests for proposals. Corporate clients want evidence of environmental responsibility, and WordPress lacks the coordinated sustainability framework that competitors provide. The Sustainability Team was building this competitive advantage, which Matt dismissed as lacking ROI despite its clear business value. Smith's third reason involved Jevons paradox, which demonstrates that performance optimization alone doesn't reduce overall resource consumption. As systems become more efficient, people use them more, leading to greater total resource consumption. Making WordPress more efficient simply enables more sites, more features, and greater overall resource use unless efficiency gains are explicitly paired with sustainability frameworks that consider supply chains, energy sources, manufacturing impacts, and total system effects. Matt's suggestion to focus solely on performance metrics instead of sustainability shows he fundamentally misunderstands the distinction between efficiency and sustainability. They are not the same thing. A car with better gas mileage isn't automatically sustainable if it uses fossil fuels, was manufactured with conflict minerals, and encourages more driving through induced demand. Smith concluded: "WordPress leadership have an opportunity to get on the right side of this and start building bridges to the people with the knowledge and passion to help. Also without some humility and accountability from Matt, no-one is going to stop talking about how WordPress leadership needs to change." Six months after dissolution, that accountability hasn't materialized. Instead, Matt doubled down at WordCamp Europe while simultaneously publishing blog posts appropriating environmental language for business disputes. ## The rhetorical structure of appropriation Matt's greenwashing blog post follows a sophisticated rhetorical structure that makes the appropriation particularly effective and particularly cynical. He begins by establishing environmental credentials through the Patagonia dinner, positioning himself as someone who understands and values genuine environmental commitment. He references reading Yvon Chouinard's book in 2018 and expresses admiration for someone who gave away company equity to ensure environmental focus. This opening creates the impression of someone deeply engaged with environmental issues who can recognize authentic commitment versus superficial gestures. He then provides the United Nations greenwashing definition, demonstrating familiarity with official frameworks for identifying misleading environmental claims. This positions him as knowledgeable about how greenwashing works, capable of identifying when companies make environmental claims without backing them up with substantive action. The setup is complete: Matt appears as an informed environmental advocate who can distinguish real commitment from corporate window dressing. The pivot comes abruptly. After establishing environmental bona fides and definitional rigor, Matt declares that "in WordPress and open source our environmental crisis comes from companies that frack the open source software and brands." This isn't careful analogy where environmental language illuminates business practices. This is wholesale appropriation where serious environmental terminology gets repurposed as business attack vocabulary. "Environmental crisis" no longer means climate change threatening planetary systems. It means trademark disputes and business model conflicts. "Fracking" no longer refers to extractive fossil fuel practices damaging ecosystems. It describes companies that don't contribute code in ways Matt approves of. The appropriation serves multiple rhetorical purposes. It imports the moral urgency of environmental issues into business disputes, suggesting that failing to contribute to WordPress core in Matt's preferred manner carries the same ethical weight as contributing to climate catastrophe. It allows him to position critics as equivalent to polluters and extractive industries, deserving similar condemnation. It creates a framework where business disagreements become existential threats requiring immediate action. The environmental language transforms mundane commercial conflicts into battles for survival. ## The pattern across multiple contexts The Sustainability Team dissolution didn't occur in isolation. It's part of a broader pattern of controversial decisions during 2024 and 2025 that reveal concerning leadership trends. In September 2024, Matt's public feud with WP Engine began when he called them "a cancer to WordPress" and banned their access to WordPress.org resources. The inflammatory rhetoric and unilateral action set the tone for subsequent conflicts. In October 2024, one hundred fifty-nine Automattic employees, representing eight point four percent of the workforce, accepted buyout packages to leave the company amid the WP Engine dispute. A second buyout offer gave employees only four hours to respond and threatened those who spoke to press with termination. In December 2024, a preliminary injunction was issued against Mullenweg and Automattic requiring them to cease blocking WP Engine's access to WordPress.org, suggesting courts found their actions legally problematic. In January 2025, five community members had WordPress.org accounts deactivated without clear process, and the Sustainability Team was disbanded. In February 2025, a class action lawsuit was filed against Automattic and Mullenweg by WP Engine customers. By June 2025, the community petition with three to four hundred signatures requesting Sustainability Team reinstatement was rejected at WordCamp Europe. This pattern reveals declining accountability, increasing centralization of power, and dismissiveness toward community input. The Sustainability Team dissolution exemplifies these trends perfectly. Volunteers working within official WordPress structures for eighteen months were summarily dismissed without consultation, warning, or transition planning. The decision came from Matt personally, though he later claimed it involved "a number of people" when pressed for accountability. The community organized, petitioned, and made public appeals, all of which were rejected. The message was clear: community input matters only when it aligns with leadership preferences. The high-profile nature of some criticism underscores the severity. Veteran tech journalist Kara Swisher, co-founder of Recode and All Things D, posted on Threads calling Matt's behavior "bizarrely heinous" and "stone cold asshole." Swisher isn't a WordPress insider with axes to grind. She's a respected journalist with decades of technology industry coverage. Her public statement reflects how the incidents appeared to informed outside observers: gratuitously cruel and counterproductive. When someone of Swisher's stature and experience makes such harsh assessments, it suggests the problems extend beyond internal community disagreements into genuinely concerning leadership failures. ## The cost of metaphorical environmental language By using environmental terminology metaphorically for business disputes, Matt trivializes actual environmental work and degrades the language available for discussing genuine environmental challenges. When "environmental crisis" can mean either climate change threatening human civilization or companies that compete with your business model, the term loses its specific urgency and meaning. When "fracking" describes both extractive fossil fuel practices destroying ecosystems and business practices you disapprove of, the word's power to identify genuinely destructive behavior dissipates. This degradation has practical consequences for the WordPress community members who wanted to work on actual sustainability issues. They now see their dismissed concerns about carbon footprint measurement, sustainable event guidelines, and performance optimization paired with consumption reduction transformed into metaphors for trademark disputes. The language they would use to advocate for environmental work has been colonized for entirely different purposes. How can they argue that WordPress faces an "environmental crisis" requiring urgent attention when Matt uses identical language to mean something completely different? The appropriation also demonstrates a troubling hierarchy of values. Environmental concepts prove valuable enough to structure an entire blog post when they serve as rhetorical weapons against competitors. The sophisticated framework of greenwashing analysis, the reference to prestigious environmental figures like Yvon Chouinard, the careful invocation of United Nations definitions—all of this intellectual infrastructure gets deployed for business conflicts. But actual environmental work by community volunteers warranted dismissal, demands for ROI metrics, and questions about whether WordPress is even the appropriate venue for environmental focus. Charlotte Bax, who organized the WordCamp Europe petition, must experience particular frustration watching environmental concepts weaponized for business purposes after being told actual environmental work lacks sufficient return on investment to warrant support. The volunteers who spent hundreds of unpaid hours developing sustainability frameworks now see their core concerns reduced to metaphorical ammunition. The message couldn't be clearer: environmental issues matter to Matt only when they're useful for attacking others, not when they require supporting community initiatives. ## Charitable interpretations and their failures Thorough analysis requires considering whether Matt's position could be defended charitably. Perhaps the team genuinely wasn't producing enough tangible results to justify organizational overhead. This defense fails because the team received zero organizational resources, no budget, no paid staff, no dedicated support. Comparing their output to well-resourced corporate sustainability teams like Automattic's own is fundamentally unfair. The proper comparison is to other volunteer Make WordPress teams, many of which operate with similar resource constraints and slower timelines. By the volunteer standard, the Sustainability Team's output was substantial. Perhaps sustainability should be embedded across all teams rather than siloed, as Mary Hubbard argued at WordCamp Europe. This excuse contradicts WordPress's own structure. The Accessibility Team exists as a dedicated team ensuring accessibility is embedded across WordPress. Nobody suggests disbanding it because "accessibility should be in everything we do." The Performance Team coordinates performance optimization across the project without people questioning why it isn't just "embedded everywhere." Sustainability requires coordination, specialized knowledge, and dedicated attention exactly like accessibility and performance. Dissolving the team doesn't embed sustainability thinking throughout WordPress. It eliminates sustainability focus entirely. Perhaps Matt has limited time and attention and genuinely didn't realize the team's full scope of work, making his "today I learned" comment honest rather than dismissive. This excuse actually makes things worse. If Matt is so disconnected from official WordPress teams that he can be unaware of one operating for eighteen months with elected representatives, published roadmaps, and regular meetings, that represents a governance failure of stunning magnitude. Leaders can't effectively manage projects they don't understand. Ignorance of official team operations is an indictment, not an excuse. Perhaps performance optimization fundamentally addresses sustainability, making a separate team redundant. This demonstrates fundamental misunderstanding of what sustainability requires. Hannah Smith explained clearly that performance optimization addresses energy efficiency but ignores supply chains, manufacturing impacts, social sustainability, economic sustainability for contributors, event sustainability, and systemic resource consumption patterns. These are different domains requiring different expertise. A more efficient system isn't automatically sustainable if the efficiency enables greater total consumption, if the hardware manufacturing process is destructive, if the social structures are exploitative, or if the economic models are extractive. None of these charitable interpretations successfully resolve the contradictions. Each explanation either fails on its own terms or reveals additional problems with Matt's leadership and decision-making. The actions remain indefensible when examined rigorously from any angle. ## The openwashing framework turns inward Matt's central accusation against WP Engine is "openwashing," which he describes as hiring good people or sponsoring events while supposedly spending more to destroy open source. His evidence is that visible good actions mask contradictory behavior. Apply this exact framework to Matt and Automattic's relationship with environmental sustainability, and the parallel becomes devastating. Visible good actions include Automattic publishing sustainability reports, calculating carbon emissions, purchasing offsets, maintaining a sustainability page claiming net zero data center emissions, and highlighting an internal Automattician Resource Group for sustainability. These are the equivalent of hiring good people and sponsoring events—the publicly visible gestures that create an impression of commitment. Hidden contradictory actions include Matt disbanding the community Sustainability Team, providing zero resources to volunteer environmental work, dismissing environmental concerns as potentially irrelevant to WordPress, and questioning the ROI of unpaid volunteers working on climate issues. The appearance created is that Automattic cares about environmental responsibility and sustainability. The reality is that environmental work matters only when it serves corporate reputation management, not when it requires supporting community-led initiatives. This is definitionally the behavior Matt condemns in his blog post. He accuses WP Engine of showing one face publicly while doing something different privately. Yet his own actions regarding sustainability follow the exact pattern he identifies as washing. The framework even extends to the spending comparison. Matt criticizes companies for spending "hundreds of thousands" on visible good actions while spending "tens of millions" to allegedly destroy open source. Automattic presumably spends money on sustainability reporting, carbon offset purchases, and internal sustainability groups—the visible environmental actions. Meanwhile, Matt provides zero budget to the community Sustainability Team while presumably spending significantly more on corporate priorities that don't include supporting volunteer environmental work. The resource allocation reveals true priorities just as clearly as the spending patterns he criticizes. The term "openwashing" itself represents an appropriation of "greenwashing," just as Matt appropriates environmental language throughout the post. But the appropriation reveals more than he intended. By creating a framework to identify when companies make superficial gestures while behaving contradictorily, he inadvertently provided the perfect analytical tool for examining his own behavior. The openwashing critique he levels at WP Engine describes his own relationship with environmental sustainability with remarkable precision. The pot isn't just calling the kettle black. The pot is describing in sophisticated detail exactly how kettles deceive people, while being completely blind to its own identical deception. ## What accountability would require Understanding what's missing helps clarify the depth of the problem. Accountability would require Matt acknowledging that disbanding the Sustainability Team while Automattic maintains environmental claims represents a contradiction. It would mean recognizing that demanding ROI from unpaid volunteers while corporate sustainability reporting faces no such scrutiny reveals unjustifiable double standards. It would involve admitting that questioning whether WordPress is the right place for environmental work while appropriating environmental language for business disputes demonstrates that he values environmental concepts only as rhetorical tools. Accountability would require reversing the dissolution decision, providing actual resources to sustainability work, and acknowledging the community members who tried to do this work. It would mean apologizing to Charlotte Bax for rejecting her petition, to Jaap Wiering for dismissing his public plea, to Nahuai Badiola and the other team founders for characterizing their volunteer efforts as lacking output culture, and to the hundreds of Slack channel members who engaged with this work. Accountability would require examining why environmental concerns warrant sophisticated blog posts when they serve as business attack metaphors but warrant dismissal when they require supporting volunteer initiatives. It would mean confronting the uncomfortable reality that his behavior exhibits the same washing pattern he condemns in others—making claims without substantive backing, highlighting minimal efforts as exceptional, and creating false impressions of commitment. None of this accountability has materialized. Instead, six months after dissolution, Matt published a blog post appropriating the very environmental concepts he deemed insufficiently valuable to support. The community response demonstrates what genuine commitment looks like. Charlotte Bax stated she would "get some great work done with the team, and show Matt and Mary what a big mistake they have made by closing us down." Two external organizations offered resources to continue work outside official WordPress channels. Contributors are moving forward independently, emphasizing that "sustainability should be a core value of WordPress." Volunteers are doing the work Matt won't support but his company claims credit for. That's the essence of greenwashing, and now we can add that it's the essence of openwashing too. The framework Matt created to attack competitors describes his own behavior with devastating accuracy. ## The definitive hypocrisy Your instinct that this represents the pot calling the kettle black was absolutely correct, but the actual blog post reveals something even more cynical than standard hypocrisy. Matt isn't simply failing to live up to standards he applies to others, though that's certainly present. He's actively exploiting environmental concepts he demonstrably doesn't value as rhetorical ammunition in business disputes. The WordPress Sustainability Team tried to do real environmental work and was disbanded for lacking ROI. Meanwhile, Matt writes blog posts using environmental language as metaphor, and Automattic publishes sustainability reports as corporate PR. The priorities couldn't be clearer. Environmental concerns matter to Matt only when they serve his immediate rhetorical or reputational needs, not when they require actual commitment or support for community-led initiatives. This isn't just hypocrisy. It's a particularly cynical form where serious global challenges become mere rhetorical devices in service of business feuds. The framework for identifying washing behavior that he applies to competitors describes his own actions with perfect precision. The UN greenwashing definitions he quotes apply to his company's environmental claims paired with community team dissolution. The concept of openwashing he invented captures his relationship with sustainability perfectly. The appropriation of environmental language while dismissing actual environmental work represents a form of intellectual dishonesty that's particularly galling to community members who tried to address genuine climate concerns. They wanted to measure WordPress's carbon footprint, create sustainable event guidelines, develop tools for site owners, and build frameworks for an ecosystem affecting billions of page views daily. Matt told them this work lacked sufficient value. Then he used their language—environmental crisis, greenwashing, planetary impact—to attack business competitors. The message is unmistakable: environmental concepts are valuable rhetorical weapons but not worthy of substantive support. This is the pot calling the kettle black, but with full awareness of the irony. Matt understands greenwashing well enough to quote UN definitions and identify the pattern in others. He just can't or won't recognize it in himself, even as he creates new washing terminology that describes his own behavior. The WordPress Sustainability Team dissolution stands as Exhibit A in a case study of corporate environmental hypocrisy, now joined by Exhibit B: a blog post weaponizing the very environmental concepts he refused to support when they required actual commitment. The contradiction isn't just present. It's the entire structure of his relationship with environmental issues. ## Links - [[3. Resources/Permanent Notes/Concentrated Authority Without Accountability Produces the Same Failure Patterns Across Religious and Software Ecosystems]] — applies-in: concentrated project authority can dismiss community sustainability work while redeploying its language without an independent accountability check - [[3. Resources/Permanent Notes/Impact-Over-Truth Is the Self-Justifying Engine of Platform-Centered Church Abuse]] — extends: public impact and rhetorical usefulness become substitutes for whether the underlying institutional claim is true or consistently practiced - [[3. Resources/Permanent Notes/Trust Erosion in Concentrated Systems Is Slow to Build and Fast to Manifest]] — evidence-for: the gap between stated environmental concern and treatment of sustainability work accumulates as another trust-eroding contradiction - [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] — applies-in: repeated founder-level contradictions can become platform risk when trust is part of the adoption layer ### Critical Timeline - August 27, 2025: Weston announces joining WP Engine. - October 4, 2025: Matt publishes "Greenwashing" post. ### The Specific Passage That Raises Eyebrows > Matt writes about companies hiring **“a good person”** or sponsoring events representing “hundreds of thousands of dollars of investment” while supposedly spending “tens of millions” to “destroy the source of everything they’ve benefited from.” ### Now, Weston Ruter Is - A decade-long core committer. - Former lead of the Core Performance Team. - Widely respected in the WordPress community. - Explicitly hired by WP Engine to continue full-time core contribution. - Someone who directly addressed the drama, saying his hiring was “not related in any way to the current WP drama.” ### The Case for This Being About Weston 1. **Timing is suspicious.** The post comes 5–6 weeks after Weston’s very public announcement. 2. **“A good person” fits perfectly.** If you wanted to describe Weston without naming him, this phrase works. 3. **It neutralizes Weston’s contribution.** Weston’s post emphasized WP Engine’s commitment to giving back and his continued core work. Matt’s framework preemptively dismisses this as “openwashing.” 4. **The dollar amounts align.** A principal engineer salary at WPE could easily represent “hundreds of thousands of dollars.” ### What Makes This Particularly Cynical If True Matt’s framework suggests that *even legitimate core contribution from WP Engine employees* is somehow performative or illegitimate—just window dressing while they “destroy” WordPress. This effectively: - Undermines Weston’s genuine decade of contributions. - Poisons any good-faith contribution from WPE employees. - Creates a catch-22: WPE gets attacked for not contributing, but when they hire respected contributors, that’s also “openwashing.” ### Questions to Consider - What do you make of the timing and that specific “good person” phrase? - Does anything else in either post jump out at you as potentially connected? - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists this note under Connected Permanent Notes (synthesis 2026-07-21 — run 17).