Greenwashing - CourtneyR.dev's 2nd Brain

Greenwashing 🔗 **Source:** [Greenwashing](https://ma.tt/2025/10/greenwashing/) > [!note]+ Document Notes > tags: [open-source, governance, ethics] > author: [MISSING] > source: ma.tt > reference: [https://ma.tt/2025/10/greenwashing/] > date created: > > # 🏷️ Title: Greenwashing >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The post contrasts Patagonia’s stewardship with “greenwashing.” - It maps UN-style greenwashing tactics to open source “openwashing.” - Stakeholders include WordPress contributors, companies, and users. - Risk: firms buy goodwill while underfunding security and governance. - Bottom line: judge actions portfolio-wide, not isolated sponsorships. ## 📖 Main Content - The author attended a dinner celebrating David Gelles’ new book on Yvon Chouinard. See Dirtbag Billionaire by David Gelles for context: https://www.simonandschuster.com/books/Dirtbag-Billionaire/David-Gelles/9781797224256 - Patagonia’s structure aims at conservation; many firms only signal virtue. - The UN frames greenwashing as vague claims, weak plans, and minimal compliance. See the UN’s definition of greenwashing: https://www.un.org/en/climatechange/raising-ambition/renewable-energy/greenwashing - The post applies this to WordPress: firms “frack” OSS by extracting brand value while starving code and security. - The recommendation: evaluate total spend and net impact across actions. ### 🗒️ Notes ### [H1] Patagonia models mission-locked stewardship > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) by [[Matt]] via [[ma.tt]]. Published 2025-10-05. Accessed . > “how Yvon gave away all his equity and control in the company to ensure a focus on his lifelong goal of environmentalism and conservation.” Patagonia’s structure aligns control with mission. It contrasts with PR-first approaches. [view highlight](https://ma.tt/2025/10/greenwashing/) #xref #articleseed ID:rw_371591195-H1 ### [H2] UN-style greenwashing patterns recur in tech > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) by [[Matt]] via [[ma.tt]]. Published 2025-10-05. Accessed . > “Claiming that the company will achieve future environment milestones while not putting sufficient plans in place to do so.” Future claims without plans signal risk. Map to OSS roadmaps lacking investment. [view highlight](https://ma.tt/2025/10/greenwashing/) #xref ID:rw_371591195-H2 ### [H3] Vague virtue claims mask weak evidence > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) > “Being intentionally vague about operations or using vague claims that cannot be specifically proven (like saying they are ‘environmentally friendly’ or ‘green’).” In OSS, “supporting community” without metrics fits this pattern. [view highlight](https://ma.tt/2025/10/greenwashing/) #xref ID:rw_371591195-H3 ### [H4] Highlighting a lone good act distracts > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) > “Highlighting one thing the company does well regarding the environment while not doing anything else.” Single sponsorships can distract from systemic underinvestment. [view highlight](https://ma.tt/2025/10/greenwashing/) #xref ID:rw_371591195-H4 ### [H5] Minimum compliance framed as leadership > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) > “Promoting products that meet regulatory minimums as if peer products do not.” In WordPress, meeting baseline policies is not leadership proof. [view highlight](https://ma.tt/2025/10/greenwashing/) #xref ID:rw_371591195-H5 ### [H6] “Openwashing” extracts value and weakens code > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) > “our environmental crisis comes from companies that frack the open source software and brands… lack of investment in the code… or… tricking people into thinking they’re associated with the Good Open thing.” Brand parasitism plus security neglect harms the ecosystem. [view highlight](https://ma.tt/2025/10/greenwashing/) #articleseed #xref ID:rw_371591195-H6 ### [H7] Evaluate net impact, not isolated sponsorships > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) > “weigh that against the tens of millions they’re spending with their other hand to destroy the source of everything they’ve benefited from” Assess portfolios and incentives to avoid capture. [view highlight](https://ma.tt/2025/10/greenwashing/) #articleseed #share ID:rw_371591195-H7 ## 📚 References - Dirtbag Billionaire by David Gelles (publisher page): https://www.simonandschuster.com/books/Dirtbag-Billionaire/David-Gelles/9781797224256 - UN guidance on greenwashing: https://www.un.org/en/climatechange/raising-ambition/renewable-energy/greenwashing - Let My People Go Surfing by Yvon Chouinard: https://www.penguinrandomhouse.com/books/29633/let-my-people-go-surfing-by-yvon-chouinard/ ## 🗣️ Paraphrase - Patagonia aligns control with environmental mission using ownership design. - Some WordPress firms signal virtue while underfunding core and security. ## 📰 Newsletter - WordPress friends, watch for “openwashing.” Some firms sponsor events. Yet they underinvest in core and security. Evaluate net impact. Favor transparent budgets, contribution metrics, and long-term maintenance. Read the UN’s take on greenwashing patterns. Apply them to OSS decisions. See UN guidance on greenwashing: https://www.un.org/en/climatechange/raising-ambition/renewable-energy/greenwashing ## ✅ Action Items #### DevRel - Define “real support” metrics for sponsors — contribution hours, patches, CVEs closed. - Publish a sponsor scorecard template — PR vs. engineering inputs. - Add case studies showing net-positive patterns — before/after metrics. #### OSPO - Create an openwashing policy — disclosure, contribution floors, KPIs. - Require SBOM and vuln intake processes for partners. - Report quarterly upstream impact — commits, reviews, funding. #### Community - Run governance clinics on evaluating sponsorship portfolios. - Offer first-issue rotations tied to sponsor commitments. - Publish impact reports for events with sponsor contributions. #### WordPress - Core: track security backlog reduction per sponsor quarter. - Core Performance: define perf budgets and public dashboards. - Core AI: publish responsible AI guardrails and eval sets. - Core Program Team: set rituals for sponsor accountability. - Mobile: track telemetry and crash-free sessions targets. - Playground: add reproducible bug templates and labs. - Community: update WordCamp playbooks for sponsor metrics. - Training: add modules on OSS ethics and greenwashing. - Marketing: avoid vague claims; require evidence links. - Support: publish SLA adherence and escalation stats. - Design: add design tokens and accessibility audits cadence. - Documentation: examples-first patterns; evidence of freshness. - Photos/TV: improve captions and content indexing SLAs. - Polyglots: run translation sprints with measurable goals. - Accessibility: WCAG reviews and heatmaps of issues. - Meta: reliability SLOs for .org APIs and tools. - CLI: expand command coverage and smoke tests. - Hosting: standardize defaults; publish reliability telemetry. - Tide: clarify scoring and false-positive review loops. - Openverse: document ingestion and moderation policies. - Themes/Plugins: improve review throughput and provenance checks. #### The WPOCC - Programs: fund maintainer stipends with transparent ledgers. - Projects: governance clinics and documentation sprints. - Funding experiments: matched grants with milestone payouts. ### FAIR - Technical independence: signatures and provenance checks. - Policies: transparency covenants and anti-capture clauses. - Governance artifacts: public charters and operator agreements. ## 🧪 Hypotheses - Firms with transparent upstream KPIs have fewer security incidents. - Sponsorships paired with code funding yield faster issue closure. - Vague sponsor claims correlate with lower contributor retention. - Mission-locked entities produce higher net OSS benefits. ### 📊 Methodology - Collect sponsor KPIs across events; run difference-in-differences on issue closure. - Correlate transparency indices with security incident rates. - Audit sponsor claims vs. measurable contributions. ### ❓ Questions - Which KPIs best capture net OSS benefit? - How should WordPress weigh PR spend vs. engineering spend? - What minimums prevent openwashing without deterring sponsors? ### 🔮 Future Research - Study mission-locked structures applied to OSS foundations. - Evaluate matched grants vs. stipends for maintainer stability. ### 💡 Implications - Require contribution reporting with sponsorships. - Favor portfolios funding maintenance, not only marketing. - Adopt anti-capture guardrails in governance. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ≈ 9–10. #### 👀 Visual learners - Present: none. - Improve: dashboards and flow diagrams. #### 🔊 Aural learners - Present: none. - Improve: 3-minute audio brief. #### 🗣️ Verbal learners - Present: definitions and examples. - Improve: glossary of “openwashing” terms. #### 🧩 Kinesthetic learners - Present: none. - Improve: sponsor audit checklist. #### 🧠 Logical learners - Present: patterns and comparisons. - Improve: decision trees and KPIs. #### 🧑‍🤝‍🧑 Social learners - Present: community framing. - Improve: cohort review templates. #### 🧘‍♀️ Solitary learners - Present: reflection prompts implied. - Improve: self-audit worksheet. #### 🌿 Naturalistic learners - Present: sustainability analogy. - Improve: lifecycle impact mapping. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: headings on site likely exist. - Improve: consistent landmarks and alt text. #### Keyboard navigation - Present: unknown. - Improve: visible focus and skip links. #### Contrast and readability - Present: unknown. - Improve: 4.5:1 minimum and line-height checks. #### Text resizing and reflow - Present: unknown. - Improve: reflow at 200% and reduced motion. #### Media and captions - Present: minimal media. - Improve: captions and transcripts if adding video. #### Forms and interactions - Present: none. - Improve: standard accessible patterns. #### Standards reference - Map to WCAG 2.2 AA criteria. ### 🌍 DEIB Assessment #### Cultural breadth - Present: global OSS relevance. - Improve: multi-region examples. #### Inclusive language - Present: plain language mostly. - Improve: define “openwashing” explicitly. #### Neurodiversity support - Present: short paragraphs. - Improve: consistent structure and icons with text. #### Representation - Present: not applicable. - Improve: inclusive imagery if added. #### Psychological safety - Present: critical yet respectful tone. - Improve: community guidelines for discourse. ### ✅ Logical Validity #### Strong reasoning - Analogical mapping from greenwashing to openwashing is clear ([H2], [H6]). - Portfolio evaluation advice follows from incentive analysis ([H7]). #### Fallacies - Possible hasty generalization about “companies” in WordPress. Narrow scope by providing examples and data. #### Tone of voice - Cautious, critical, and values-driven. ### 🛡️ DARVO Analysis - Deny: none explicit. - Attack: critiques practices, not individuals. - Reverse victim/offender: warns against parasitism narratives, avoids reversal. ## 🎯 Conclusion - Evaluate sponsors by total net impact, not isolated acts. - Build policies, KPIs, and transparency to deter openwashing. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Patagonia models mission-locked stewardship > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) by [[Matt]] via [[ma.tt]]. Published 2025-10-05. Accessed . > “how Yvon gave away all his equity and control in the company to ensure a focus on his lifelong goal of environmentalism and conservation.” Two lines: mission-locking reduces value drift. Compare with OSS foundations. [view highlight](https://ma.tt/2025/10/greenwashing/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] UN-style greenwashing patterns recur in tech > [!quote] [Greenwashing](https://ma.tt/2025/10/greenwashing/) > “Claiming that the company will achieve future environment milestones while not putting sufficient plans in place to do so.” Use to assess OSS roadmaps and budgets. [view highlight](https://ma.tt/2025/10/greenwashing/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Mission-locking improves ecosystem-aligned decisions - When governance ties control to purpose. - Links: [[Governance-Design]] [[Foundation-Structures]] #### [Z2] Sponsor portfolios require net impact audits - Compare PR and engineering investments quarterly. - Links: [[Sponsorship-Policy]] [[OSS-KPIs]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft openwashing policy checklist — context/https://ma.tt/2025/10/greenwashing/ #fleeting #inbox - [F2] Build sponsor KPI dashboard mock — context/https://ma.tt/2025/10/greenwashing/ #fleeting #inbox - [F3] Propose The WPOCC matched grant pilot — context/https://ma.tt/2025/10/greenwashing/ #fleeting #inbox ---