Roads-and-Bridges-the-Unseen-Labor-Behind-Our-Digital-Infrastructure  ## Metadata - Author: [[fordfoundation.org]] - Full Title: Roads-and-Bridges-the-Unseen-Labor-Behind-Our-Digital-Infrastructure - Category: #articles - Document Note: - #opensource - #digitalinfrastructure - #funding Author: Nadia Eghbal Source: Ford Foundation report Reference: https://www.fordfoundation.org/wp-content/uploads/2016/07/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf date created: 2025-08-21 17:09 # Title: Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure ## Table of Contents: - [📚 Overview](#-overview) - [🧩 The Infrastructure Analogy](#-the-infrastructure-analogy) - [👩‍💻 Maintainers and Unpaid Labor](#-maintainers-and-unpaid-labor) - [💸 Funding Models and Incentives](#-funding-models-and-incentives) - [🏛️ Institutions, Policy, and Governance](#-institutions-policy-and-governance) - [🧰 Corporate Reliance and Risk](#-corporate-reliance-and-risk) - [🌱 Sustainability and Community Health](#-sustainability-and-community-health) - [🔧 Proposed Interventions](#-proposed-interventions) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items (Advocacy and OSPO Alignment)](#-action-items-advocacy-and-ospo-alignment) - [🧪 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) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: Include a list of sources consulted and cited in the article. - The report itself cites: Eric Raymond, Elinor Ostrom, Apache Foundation, Linux Foundation, npm, OpenSSL/Heartbleed incident coverage, GitHub data, and grantmaking literature. When quoting or teaching, consider linking out to primary orgs’ governance docs and incident postmortems. ## 📝 Summary: The report argues that open source software functions as critical public infrastructure—like roads and bridges—yet is maintained by a small number of underfunded, often unpaid individuals. It diagnoses misaligned incentives between widespread corporate reliance and minimal maintainership support, highlights the fragility of key dependencies (e.g., OpenSSL pre-Heartbleed), and proposes a portfolio of solutions: diversified funding, institutional backstops, better governance, and human-centered support for maintainers. The core message: sustainability requires recognizing software as a public good and building structures to fund, steward, and equitably share its costs and benefits. ## 📖 Main Content: - Infrastructure lens - Open source undergirds commerce, research, and national security. - Public-good characteristics: non-rivalrous and (functionally) non-excludable, creating free-rider problems. - Maintainers, not just code - The bottleneck is human attention: triage, reviews, security, social mediation. - Bus factor risks: a handful of individuals carry massive dependency graphs. - Funding models - Philanthropic grants, corporate sponsorships, foundations, consulting, dual licensing, SaaS complements, donations, bounties. - Tradeoffs: short-term vs. long-term, influence risks, admin overhead. - Governance and institutions - Role of foundations (Apache, Linux, Eclipse) in neutral IP, code of conduct, and legal scaffolding. - Need for lightweight yet explicit governance in smaller projects. - Market dynamics - Corporations optimize for local value capture; systemic resilience is a public good. - Procurement and compliance rarely compensate upstream. - Interventions - Funding pipelines, security audits, maintainer fellowships, OSPOs, upstream-first policies, ecosystem health metrics. Personal reflections and connections: - Aligns with WordPress’s dependency chain realities (PHP, OpenSSL, npm packages, Gutenberg). - Reinforces importance of Contributor Experience teams, mentorship, and non-code pathways (docs, triage). - OSPOs can normalize upstream time and compensate maintainers via contracts, foundations, or pooled funds. ### 🗒️ Notes - The metaphor: Roads/bridges = protocols, libraries, package registries; maintenance budgets ≈ maintainer time. - Free rider problem - Widespread consumption without proportional funding. - Incentive gap between individual/company benefit and collective maintenance needs. - Maintainer burnout - Issue queues as emotional labor; coordination costs compound with popularity. - Invisible work: security disclosures, release management, community moderation. - Fragility examples - Heartbleed revealed underfunded OpenSSL. - Left-pad incident showed ecosystem-level cascading failures. - Funding approaches - Corporate: sponsorships, dedicated headcount, upstream time. - Public/philanthropy: grants, fellowships, security initiatives (e.g., CII). - Community: donations, crowdfunding—helpful but unreliable. - Governance patterns - Meritocracy critiques; need for documented decision-making, CoC, onboarding paths. - Measurement - Beyond stars: look at review latency, single-maintainer hotspots, security posture. - Policy levers - Government procurement can require upstream support; SBOMs, criticality scores. - Equity and inclusion - Sustainability requires well-being, psychological safety, and accessible contributor ladders. ## 📖 References: - Ford Foundation: “Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure.” - OpenSSF and CII Best Practices badges for security and governance baselines. - Apache Foundation governance model; Linux Foundation funding mechanisms. - Heartbleed retrospectives; npm “left-pad” outage analyses. ## 🗣️ Paraphrase: - Original idea: Many companies depend on a tiny group of unpaid maintainers who shoulder disproportionate responsibility for security and stability. - Paraphrase: Corporate software stacks often rest on the shoulders of just a few volunteer developers, making enterprise reliability hinge on gift labor and creating systemic risk. - Original idea: Treating open source as infrastructure reframes obligations and unlocks institutional solutions. - Paraphrase: When we recognize open source as public infrastructure, we justify collective funding, governance, and policy tools that distribute costs and responsibilities more fairly. ## 📰 Newsletter: This week in web dev, we’re revisiting our foundations—literally. If your stack leans on open source (spoiler: it does), you’re driving on roads you didn’t pave. Nadia Eghbal’s landmark report for the Ford Foundation makes a compelling case that our digital “bridges” are kept standing by a handful of maintainers doing unseen labor. Takeaways for WordPress folks: invest upstream, normalize contributor time, and support projects you depend on. Want to help? Start with your dependency list and fund at least one maintainer whose work you ship every week. Bonus: check out OpenSSF’s guides to level up security governance. Useful links: - Read the report: Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure - Explore OpenSSF’s best practices for critical projects - Learn how to start an OSPO ## ✅ Action Items (Advocacy and OSPO Alignment): A prompt you can reuse per article: - Purpose: Explain how this article informs my work as a Developer Advocate at GoDaddy specializing in open source and WordPress, and my path toward an OSPO director role. - Frame: - Advocacy: Identify where the article exposes sustainability gaps (funding, governance, maintainer health) and propose at least two upstream interventions we can pilot with WordPress and its dependencies. - Contributor Engagement: Extract onboarding, mentorship, and triage practices that reduce maintainer load; outline a contributor journey from “first issue” to “release lead.” - Education: Translate concepts into curricula for PHP/JS/HTML/CSS/Git training, including modules on upstream etiquette, security disclosure, and documentation. - Funding Strategy: Map dependencies we rely on; classify by criticality; propose a diversified funding portfolio (direct sponsorships, founda - URL: https://www.fordfoundation.org/wp-content/uploads/2016/07/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf Full text of this document omitted because this document is a PDF [Download original file →](https://readwise.io/reader/document_raw_content/2272620), Roads-and-Bridges-the-Unseen-Labor-Behind-Our-Digital-Infrastructure, fordfoundation.org, 01jbhaga3411bfqcwd2vc6jrg3.