My take
A public project can attract users faster than it can attract maintainers. Who benefits, who does the work, and how that work is supported are part of the product’s design.
What is Working in Public: The Making and Maintenance of Open Source Software about?
Open source is often described as a large crowd building together. Eghbal shows why many projects instead depend on a small number of people, and examines the labor and support needed to keep shared software working.
Who should read Working in Public: The Making and Maintenance of Open Source Software?
Maintainers, software teams, open source funders, platform builders, and creators deciding how much public work they can sustain.
Key ideas from Working in Public: The Making and Maintenance of Open Source Software
- Look at who maintains a project, not only who contributes
- Community size does not show how work is distributed
- Dependency and user growth create ongoing support costs
Is Working in Public: The Making and Maintenance of Open Source Software worth reading?
Teams that depend on public software need to understand its maintenance costs and the people carrying them. The same questions apply to online communities and creator-led products.
Best for
Open source maintainers, product leads, community builders, and teams planning to depend on or fund public infrastructure.
Not ideal for
Readers looking for a technical guide to writing software or a step-by-step open source launch checklist.
What materially matters
- How open source projects change as they grow
- The work and costs of software maintenance
- Who creates and supports online work
Practical use cases
- Map the people and unpaid work behind a critical dependency.
- Review whether a community project has a realistic maintenance plan.
Pros
- Connects community structure to the work required to maintain a product.
- Uses interviews and project examples rather than treating contributors as an abstraction.
Limitations
- The project examples reflect the platforms and open source landscape examined in the book.
- It explains the problem more than it prescribes a single funding model.
Working in Public: The Making and Maintenance of Open Source Software FAQ
Is this a programming book?
No. It examines the organization, economics, and maintenance of open source projects; it does not teach a programming language.
Who should read it first?
Start here if your team depends on open source, maintains a public project, or is planning a contribution program.
Continue · Strategy
