Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal Summary

1. Open source maintenance relies on solo developers, not communal collaboration
2. Modern creators face unsustainable attention demands from public work
3. GitHub’s architecture shifted open source from collaboration to isolated maintenance
4. Corporate funding prioritizes critical code over community-driven open source projects
5. “One-way mirror governance” balances public visibility with contributor control
6. Maintainers trade personal bandwidth for software’s societal impact and reputation
7. Open source parallels influencer economies through reputation-based labor systems
8. The “passion economy” model fails to scale for infrastructure maintenance
9. Successful projects manage contributor influx through automated quality filters
10. Maintainers face emotional labor comparable to social media content creators
11. Babel’s maintenance crisis exemplifies open source’s hidden sustainability costs
12. Platforms monetize community labor while offloading support burdens to creators

『Working in Public』の著者について

Nadia Eghbal, author of Working in Public: The Making and Maintenance of Open Source Software, is a leading researcher and writer on digital infrastructure and online collaboration. A former senior developer-relations researcher at GitHub, Eghbal combines hands-on experience with incisive analysis to explore the economics, governance, and social dynamics of open-source ecosystems.

Her work bridges technical insights with broader themes of community sustainability and the creator economy, influenced by her roles at Protocol Labs and Substack, where she studied decentralized systems and creator-driven platforms.

Eghbal first gained recognition for Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure, a Ford Foundation-published report that reframed open-source code as critical public infrastructure requiring systemic support. Her writing and TEDx talks have been featured in The New York Times, Wired, and tech industry forums, establishing her as a trusted voice on digital public goods. Working in Public has been translated into 12 languages and cited in over 200 academic papers, underscoring its relevance to contemporary discussions about internet governance and collaborative innovation.

『Working in Public』に関するよくある質問

What is Working in Public by Nadia Eghbal about?

Working in Public examines the evolution of open-source software, highlighting the shift from collaborative development to maintenance by a small group of overburdened creators. It explores how platforms like GitHub transformed code production and draws parallels between open-source maintainers and modern digital creators (e.g., YouTubers). The book analyzes governance, funding challenges, and the "attention economy" impacting sustainable development.

Who should read Working in Public?

This book is essential for software developers, open-source contributors, and digital creators interested in sustainable online collaboration. It also appeals to those studying internet economics, platform dynamics, or community-driven projects. Nadia Eghbal’s insights bridge technical and non-technical audiences, making it accessible to policymakers and tech enthusiasts.

Is Working in Public worth reading?

Yes, Working in Public offers a groundbreaking analysis of open-source sustainability and creator economies. Eghbal’s research, including interviews with hundreds of developers, provides actionable frameworks for managing projects and understanding digital labor. It’s praised for connecting niche software practices to broader internet trends.

What are the main ideas in Working in Public?

Key concepts include:

• The "one-way mirror": Public project discussions with limited participation to reduce maintainer burnout.
• Creator-maintainer parallels: Open-source developers face similar attention/funding challenges as influencers.
• Platform impact: GitHub’s infrastructure centralizes code but fragments contributor accountability.

How does Working in Public compare to Producing Open Source Software?

Karl Fogel’s 2005 guide focuses on collaborative best practices, while Eghbal’s work analyzes modern solo maintainers and platform-driven dynamics. Working in Public highlights systemic issues like funding gaps and attention scarcity absent in earlier open-source literature.

What critiques exist about Working in Public?

Some argue Eghbal overemphasizes individual maintainers’ roles, underplaying corporate contributions to projects like Linux. Others note limited solutions for systemic funding issues beyond patronage models.

How does Nadia Eghbal address sustainability in open source?

Eghbal advocates for balancing community growth with maintainer well-being, suggesting tools like modular governance and "benevolent dictatorships." She critiques unrealistic expectations of infinite collaboration, urging recognition of maintenance as critical labor.

What quotes are notable in Working in Public?

• “We’re all maintainers now”: Highlights the universal burden of curating digital content.
• “The cost of production is maintenance”: Emphasizes overlooked labor in sustaining projects.

How does Working in Public relate to the creator economy?

Eghbal argues open-source developers are proto-creators, navigating attention scarcity and monetization before platforms like Patreon. Both groups face sustainability challenges despite producing public goods.

What is the "one-way mirror" concept in Working in Public?

This framework describes projects where discussions are publicly visible but participation is restricted to core maintainers. It reduces noise from casual contributors, letting teams focus on high-impact work—a strategy used by projects like Babel.

Why is Working in Public relevant in 2025?

As AI-generated code increases, maintainers face new challenges vetting contributions. Eghbal’s insights into scalable governance and funding remain critical for open-source ecosystems adapting to automation.

Are there case studies in Working in Public?

Yes, Eghbal analyzes Bootstrap (73% of commits by three developers), Linux’s maintainer hierarchy, and solo projects like Babel. These examples illustrate varying governance models and maintenance burdens.