Grow the ecosystem, not just yourself  🔗 **Source:** [Grow the ecosystem, not just yourself](https://dri.es/grow-the-ecosystem-not-just-yourself) > [!note]+ Document Notes > tags: [open-source-ecosystems, drupal-governance, competitive-dynamics, commons-stewardship, social-contracts, vendor-behavior] > author: Dries Buytaert > source: dries.es > reference: [https://dri.es/grow-the-ecosystem-not-just-yourself] > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Grow the ecosystem, not just yourself > <!-- deep-read:sections start --> ## 🧭 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) ## 📝 Summary - Dries Buytaert addresses competitive dynamics in the Drupal ecosystem, specifically criticizing Pantheon's attacks on Acquia around private equity ownership. - He argues that open source companies have dual responsibilities: compete on product merits while stewarding shared commons (code, community, reputation). - Acquia contributed 26,331 weighted issue credits vs Pantheon's 243 in the past year, demonstrating different levels of ecosystem investment. - The piece calls for establishing social contracts that prioritize ecosystem growth over vendor attacks. - Bottom line: Competition should focus on building better products and growing adoption, not undermining other vendors through misleading messaging. ## 📖 Main Content ### Core Framework: Dual Responsibility Model Buytaert articulates a fundamental tension in open source business models. Unlike proprietary software where companies compete independently, open source vendors depend on shared infrastructure: codebase, community trust, documentation, security, and adoption momentum. This creates what he calls a "different kind of responsibility" - companies must simultaneously compete and collaborate. The license provides the legal floor (what companies are permitted to do), but sustainable ecosystems require a social contract above that floor. This social contract encompasses voluntary stewardship activities: code contributions, security work, maintainer support, documentation, events, and adoption marketing. ### The Pantheon-Acquia Dispute The immediate trigger is Pantheon's marketing strategy targeting Acquia's private equity ownership. Buytaert argues this represents energy misdirection - attacking ownership models rather than competing on product features, support quality, or pricing. He notes customers choose platforms based on functionality and reliability, not financial structure. The contribution data provides concrete evidence: Acquia's 26,331 weighted issue credits versus Pantheon's 243 represents roughly a 100x difference in measurable code contributions. While acknowledging credits don't capture all contribution forms, the gap illustrates different approaches to ecosystem stewardship. ### Social Contract Evolution Buytaert positions his response as standard-setting rather than corporate defense. He argues that what communities "let pass" becomes normalized behavior, shaping acceptable practices for years. This mirrors how social norms evolve through public boundary-setting moments. His reluctance to engage in ongoing debate reflects a strategic choice to avoid escalation while establishing clear expectations. The focus remains on building and contributing rather than defending or attacking. ## 🗒️ Notes ### Ecosystem Economics - Open source creates "commons" dependency: software, community, reputation, adoption work - Companies must balance competitive advantage with collective stewardship - Social contract operates above legal license requirements through voluntary contributions ### Contribution Metrics - Drupal.org credits provide public accountability for ecosystem investment - Acquia: 26,331 weighted issue credits + 164 security credits (past year) - Pantheon: 243 weighted issue credits + 2 security credits (same period) - Community contributions exceed any single company's involvement ### Marketing Strategy Critique - Attacking competitors' ownership models diverts energy from product improvement - Customers prioritize functionality, support, and platform reliability over financial structure - Vendor attacks create noise rather than customer value in open source contexts ### Leadership Philosophy - Reluctant to engage in public competitor disputes but willing when ecosystem health is threatened - Focuses on building/contributing rather than defending/attacking - Uses founder authority to establish behavioral norms for the broader community ## 📚 References - [Drupal.org](https://drupal.org) - Contribution credit tracking system - [LinkedIn discussion](https://linkedin.com) - Follow-up conversation thread ## 🗣️ Paraphrase Dries Buytaert argues that open source software creates unique competitive dynamics where companies must balance individual success with collective stewardship of shared resources. Using the Drupal ecosystem as an example, he criticizes Pantheon's marketing attacks on Acquia's private equity ownership as counterproductive energy that could be better spent improving products and growing adoption. The piece establishes a framework distinguishing between legal permissions (what the license allows) and social contracts (what healthy ecosystems require). While no one enforces contribution requirements, sustainable open source projects depend on voluntary stewardship activities like code contributions, security work, documentation, and community support. Buytaert supports his argument with concrete contribution data showing Acquia's significantly higher investment in Drupal development compared to Pantheon. Rather than defending his company, he positions the response as ecosystem standard-setting - establishing norms that prioritize collaborative growth over vendor attacks. The underlying message advocates for competition focused on product merit, customer service, and ecosystem strengthening rather than misleading messaging about ownership models that customers don't prioritize when choosing platforms. ## 📰 Newsletter **Open Source Economics: When Competition Meets Collaboration** Drupal founder Dries Buytaert published a thoughtful piece this week about the unique challenges of competing in open source ecosystems. Unlike traditional software markets, open source vendors depend on shared infrastructure - code, community trust, security, documentation - that requires collective stewardship even as companies compete for customers. The immediate context involves marketing tensions between Drupal hosting companies Acquia and Pantheon, but the underlying principles apply broadly to WordPress, PHP, and other open source communities. Buytaert's key insight: healthy ecosystems need social contracts that operate above legal license requirements, encouraging voluntary contributions that benefit everyone. For WordPress professionals, this raises important questions about how we balance individual business success with community investment. Whether you're an agency, plugin developer, or hosting company, consider how your marketing and contribution strategies support the broader ecosystem that enables your business. The piece includes concrete contribution data and practical examples of ecosystem stewardship that could inform WordPress community discussions about vendor responsibility and competitive practices. **Read more:** [Grow the ecosystem, not just yourself](https://dri.es/grow-the-ecosystem-not-just-yourself) ## ✅ Action Items #### Community - **Ecosystem Standards:** Draft contribution expectations for WordPress hosting companies and major vendors - **Metrics Development:** Explore public contribution tracking similar to Drupal.org's credit system for WordPress.org involvement - **Social Contract Documentation:** Create explicit guidelines for competitive behavior within WordPress vendor community #### WordPress - **Meta:** Evaluate contribution tracking and public accountability systems for ecosystem participants - **Community:** Develop frameworks for addressing vendor conflicts that affect ecosystem health - **Marketing:** Create guidelines for competitive messaging that promotes ecosystem growth #### DevRel - **Community management:** Develop playbooks for managing competitive tensions while maintaining collaborative culture - **Developer advocacy:** Articulate the business case for open source ecosystem investment beyond legal requirements - **Education:** Create content explaining dual responsibility models for open source businesses ## 🧪 Hypotheses - **Social Contract Enforcement:** Public accountability and founder/leader intervention can effectively establish behavioral norms in open source communities without formal governance structures - **Contribution Transparency:** Making ecosystem contributions publicly measurable (like Drupal.org credits) encourages higher levels of voluntary stewardship investment - **Marketing Strategy Impact:** Vendor attacks in open source contexts create negative-sum outcomes that harm adoption and community health more than they benefit the attacking company - **Ownership Model Irrelevance:** Customer platform choices prioritize functionality and support over corporate ownership structure, making ownership-based attacks ineffective marketing strategies ### 📊 Methodology - **Longitudinal Contribution Analysis:** Track contribution patterns before and after public accountability initiatives across multiple open source projects - **Customer Decision Factor Surveys:** Measure relative importance of product features, support quality, and ownership models in platform selection decisions - **Community Health Metrics:** Develop composite indicators measuring the relationship between competitive behavior and ecosystem vitality (adoption rates, contributor retention, project velocity) - **Comparative Case Studies:** Analyze vendor conflict resolution approaches across different open source ecosystems (Drupal, WordPress, Linux distributions, JavaScript frameworks) ### ❓ Questions - How can open source communities establish and enforce social contracts without formal governance overhead? - What contribution tracking and transparency mechanisms most effectively encourage ecosystem stewardship? - When should project leaders intervene in vendor disputes, and what intervention strategies preserve community cohesion? - How do competitive dynamics differ between open source ecosystems with different governance models and commercial structures? ### 🔮 Future Research - **Cross-Platform Comparative Analysis:** Study social contract formation and enforcement mechanisms across major open source ecosystems - **Economic Impact Modeling:** Quantify the relationship between ecosystem investment and individual vendor success in open source markets - **Community Governance Innovation:** Explore hybrid approaches that balance contributor autonomy with accountability for ecosystem stewardship - **Marketing Strategy Evolution:** Track how competitive messaging strategies adapt to open source contexts and community feedback ### 💡 Implications **Practice:** Open source businesses need explicit strategies balancing competitive advantage with ecosystem investment, potentially requiring new metrics and accountability structures. **Policy:** Open source communities may need governance frameworks that address competitive behavior without stifling innovation or creating regulatory overhead. **Education:** Business education should include open source economics principles, particularly the dual responsibility model and social contract concepts. **Funding:** Investment and ownership models should account for ecosystem stewardship requirements, not just traditional competitive dynamics. ### 🧠 Learning Styles Assessment - **Reading level estimate:** Flesch-Kincaid Grade Level 12.8 - sophisticated vocabulary and complex sentence structures requiring college-level reading skills. #### 👀 Visual learners - **Present:** Clear section headers, structured argumentation flow - **Improve:** Ecosystem relationship diagrams, contribution comparison charts, social contract vs. legal requirement visual framework #### 🔊 Aural learners - **Present:** Strong authorial voice, conversational tone in explanations - **Improve:** Audio version, podcast discussion format exploring the competitive dynamics concepts #### 🗣️ Verbal learners - **Present:** Well-defined terminology (commons, stewardship, social contract), concrete examples - **Improve:** Glossary of open source economics terms, comparison with traditional business model analogies #### 🧩 Kinesthetic learners - **Present:** Concrete contribution data and specific examples - **Improve:** Interactive contribution tracking tools, hands-on exercises for evaluating ecosystem health #### 🧠 Logical learners - **Present:** Clear cause-and-effect reasoning, data-driven arguments, structured problem analysis - **Improve:** Decision trees for competitive behavior, quantitative frameworks for measuring ecosystem impact #### 🧑‍🤝‍🧑 Social learners - **Present:** Community-focused framing, discussion of social norms and collective responsibility - **Improve:** Facilitated discussion guides, collaborative exercises for developing social contracts #### 🧘‍♀️ Solitary learners - **Present:** Reflective tone, leadership philosophy, individual responsibility emphasis - **Improve:** Self-assessment tools for ecosystem contribution, personal reflection prompts on competitive ethics #### 🌿 Naturalistic learners - **Present:** Ecosystem metaphors, organic community growth concepts - **Improve:** Biological ecosystem analogies, environmental sustainability parallels in open source stewardship ### 📊 Accessibility Assessment #### Screen reader semantics - **Present:** Clear heading hierarchy, structured content organization - **Improve:** More descriptive link text than generic "LinkedIn discussion," alt text for any embedded images #### Keyboard navigation - **Present:** Standard web navigation structure - **Improve:** Skip links for main content, visible focus indicators for interactive elements #### Contrast and readability - **Present:** Good text contrast on white background - **Improve:** Verify color contrast ratios meet 4.5:1 minimum, test with various color blindness simulations #### Text resizing and reflow - **Present:** Responsive design accommodating text scaling - **Improve:** Ensure content reflows properly at 200% zoom without horizontal scrolling #### Media and captions - **Present:** Text-only content, no multimedia requiring captions - **Improve:** If audio/video versions are created, include full transcripts and captions #### Forms and interactions - **Present:** Simple subscription form with clear labeling - **Improve:** Error handling for form validation, accessible confirmation messages ### 🌍 DEIB Assessment #### Cultural breadth - **Present:** Universal open source principles applicable across regions - **Improve:** Examples from non-Western open source communities, consideration of different business culture approaches to competition #### Inclusive language - **Present:** Professional, gender-neutral terminology throughout - **Improve:** Define technical jargon (weighted issue credits, private equity) for broader accessibility #### Neurodiversity support - **Present:** Clear section structure, consistent formatting - **Improve:** Summary bullet points, simplified version of complex concepts #### Representation - **Present:** Focus on corporate behavior and ecosystem health - **Improve:** Acknowledge diverse stakeholder perspectives (individual contributors, small companies, international participants) #### Psychological safety - **Present:** Respectful tone even when criticizing competitive behavior - **Improve:** Explicit acknowledgment of legitimate business pressures that create competitive tensions ### ✅ Logical Validity #### Strong reasoning - **Dual Responsibility Framework (opening):** Deductively sound argument that shared infrastructure creates shared responsibility - logically connects premise (commons dependency) to conclusion (stewardship obligation) - **Data-Driven Evidence (contribution section):** Strong inductive reasoning using concrete metrics (26,331 vs 243 credits) to support claims about differential ecosystem investment - **Social Contract Theory (middle section):** Solid analogical reasoning comparing open source community norms to established social contract concepts from political theory #### Fallacies - **Ad Hominem Avoidance:** Successfully separates criticism of marketing strategy from personal attacks on Pantheon leadership ("I have no quarrel with Pantheon's products or the people who build them") - **Cherry-Picking Concern:** Acknowledges limitation of credit metrics ("Credits don't capture every form of contribution") but gap is substantial enough to support broader point - **Authority Position:** Could be seen as argument from authority given Buytaert's founder status, but reasoning stands independently of position #### Tone of voice - **Measured Authority:** Combines confidence with restraint ("I don't usually write publicly about competitors. It's not how I want to spend my voice") - **Constructive Criticism:** Focuses on behaviors and impacts rather than personal or corporate character assassination - **Strategic Disengagement:** Explicitly avoids escalation ("I won't turn this into an ongoing debate") while establishing clear position ### 🛡️ DARVO Analysis No DARVO patterns detected in this content. The piece demonstrates the opposite approach: - **Accountability:** Buytaert acknowledges his company's position and potential bias ("The fact that Acquia is the company being attacked made me slower to respond") - **Evidence-Based Response:** Provides concrete data rather than deflecting criticism - **Constructive Framework:** Proposes positive standards rather than attacking accusers - **Victim-Offender Clarity:** Maintains focus on ecosystem health rather than claiming victim status The rhetoric emphasizes shared responsibility and collaborative solutions, characteristic of healthy conflict resolution rather than manipulative deflection tactics. ## 🎯 Conclusion Dries Buytaert's response to competitive tensions in the Drupal ecosystem articulates a sophisticated framework for understanding business dynamics in open source software. His core insight - that companies must balance individual competition with collective stewardship of shared infrastructure - has broad applicability beyond Drupal to any commons-dependent business model. The piece succeeds in establishing behavioral standards through measured leadership intervention rather than defensive corporate messaging. By providing concrete contribution data while acknowledging its limitations, Buytaert demonstrates how transparency can encourage accountability without creating adversarial dynamics. For WordPress and other open source communities, this offers a template for addressing vendor conflicts while maintaining collaborative culture. The emphasis on social contracts operating above legal requirements suggests pathways for community self-governance that don't require heavy-handed enforcement mechanisms. The practical next step involves translating these principles into actionable guidelines for competitive behavior, contribution expectations, and conflict resolution within open source ecosystems that depend on voluntary cooperation for long-term sustainability. ## 🔄 Refactor Appendix — Grow the ecosystem, not just yourself ### 📚 Literature Atoms (H3) #### Open source vendors share commons dependency unlike proprietary competitors > [!quote] ID:ecosystem_commons > Companies compete through their own products and services, but they all depend on the same commons: the software, the community, the project's reputation, and the shared work that helps people trust and adopt it. **Context & use**: - Opening framework establishing dual responsibility model - Distinguishes open source competitive dynamics from traditional business models - Foundation for arguing stewardship obligations beyond legal requirements **Tags**: #xref #competitive-dynamics **Source**: Article introduction <!-- atomicity: 1 idea ✓ --> #### Social contracts operate above license requirements in healthy ecosystems > [!quote] ID:social_contract > An Open Source license defines what companies are allowed to do. It sets the floor. Contribution is not required. Above that floor is a social contract. No one enforces it, but every healthy Open Source ecosystem depends on it. **Context & use**: - Distinguishes legal permissions from community expectations - Explains voluntary nature of ecosystem stewardship - Supports argument for contribution accountability without formal enforcement **Tags**: #xref #governance **Source**: Mid-article framework section <!-- atomicity: 1 idea ✓ --> #### Public boundary-setting shapes acceptable community behavior over time > [!quote] ID:boundary_setting > What we let pass now will shape what is acceptable in Drupal years from now. Communities like ours evolve their social contract through moments like this, when we say in public what we expect of each other. **Context & use**: - Explains leadership intervention rationale - Demonstrates how norms evolve through public accountability moments - Justifies standard-setting rather than defensive corporate response **Tags**: #governance #leadership **Source**: Response justification section <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### Open source businesses must balance individual competition with collective stewardship **Claim**: Companies built on open source infrastructure face dual responsibilities that don't exist in proprietary software markets - they must simultaneously compete for customers while investing in shared commons that benefit all participants. **Evidence pointer**: [[#Open source vendors share commons dependency unlike proprietary competitors]] **Scope & conditions**: - Applies to any business model dependent on shared infrastructure - Breaks down when commons are captured or when legal enforcement replaces social contracts - Requires transparency mechanisms for accountability **Links**: - [[Social contracts in decentralized systems]] — because extends governance concepts - [[Commons-based business models]] — because applies-in various open source contexts - [[Competitive dynamics in platform ecosystems]] — because contrasts with proprietary competition <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - Investigate WordPress vendor contribution tracking systems similar to Drupal.org credits - Research social contract formation in other open source communities (Linux, Apache, Mozilla) - Analyze the relationship between ownership models and ecosystem stewardship across different projects ### → Things 3 (max 2 actions) - [ ] Draft proposal for WordPress vendor contribution guidelines — community team #things - [ ] Research Drupal.org credit system implementation for potential WordPress adaptation — meta team #things <!-- deep-read:sections end --> ## Highlights - Companies compete through their own products and services, but they all depend on the same commons: the software, the community, the project's reputation, and the shared work that helps people trust and adopt it. - Note: 📚 Open source vendors share commons dependency unlike proprietary competitors · - Opening framework establishing dual responsibility model - Distinguishes open source competitive dynamics from traditional business models - Foundation for arguing stewardship obligations beyond legal requirements **Source**: Article introduction · #atom/literature/h1 - An Open Source license defines what companies are allowed to do. It sets the floor. Contribution is not required. Above that floor is a social contract. No one enforces it, but every healthy Open Source ecosystem depends on it. - Note: 📚 Social contracts operate above license requirements in healthy ecosystems · - Distinguishes legal permissions from community expectations - Explains voluntary nature of ecosystem stewardship - Supports argument for contribution accountability without formal enforcement **Source**: Mid-article framework section · #atom/literature/h2 - What we let pass now will shape what is acceptable in Drupal years from now. Communities like ours evolve their social contract through moments like this, when we say in public what we expect of each other. - Note: 📚 Public boundary-setting shapes acceptable community behavior over time · - Explains leadership intervention rationale - Demonstrates how norms evolve through public accountability moments - Justifies standard-setting rather than defensive corporate response **Source**: Response justification section · #atom/literature/h3 - Open source businesses must balance individual competition with collective stewardship - Note: Applies to any business model dependent on shared infrastructure · - [[Social contracts in decentralized systems]] — because extends governance concepts · #atom/zettel/z1 - ** Successfully separates criticism of marketing strategy from personal attacks on Pantheon leadership ("I have no quarrel with Pantheon's products or the people who build them") - Note: 🔍 Fallacy: Ad Hominem #fallacy/ad-hominem