Working in Public

1. Open source software has evolved from community-driven to individual-centric projects

There is no "open source community," really, anymore than there is an "urban community."

From collective to individual. Open source software has transformed from large, community-driven projects to smaller, individual-centric endeavors. This shift reflects broader changes in online content creation and distribution. The early days of open source were characterized by massive collaborative efforts like Linux, but today's landscape is dominated by smaller projects maintained by one or a few dedicated individuals.

Diverse project types. Open source projects now span a spectrum:

• Federations: Large, community-driven projects (e.g., Linux, Node.js)
• Clubs: Niche projects with overlapping contributors and users
• Toys: Personal projects with minimal user base
• Stadiums: Widely-used projects maintained by few individuals

This diversity challenges traditional notions of open source as inherently collaborative, highlighting the need for new models of understanding and supporting these projects.

2. GitHub revolutionized open source development by standardizing workflows

GitHub had a meteoric impact on open source. It crashed through the roof of the Church of Free and Open Source Software and landed on the pews, crushing everything beneath.

Standardization and accessibility. GitHub transformed open source development by providing a centralized platform with standardized tools and workflows. This dramatically lowered the barrier to entry for new contributors and made it easier for projects to manage contributions. Key features include:

• Unified interface for code hosting, issue tracking, and pull requests
• Social features like user profiles and project starring
• Built-in version control with Git

Cultural shift. GitHub's impact went beyond technical improvements, fundamentally changing open source culture:

• Emphasis on individual developers over projects
• Increased visibility for maintainers and contributors
• Normalization of open source participation for commercial developers

This standardization has made open source more accessible but also introduced new challenges in managing increased participation.

3. Maintenance, not creation, is the primary challenge for open source projects

Software is frequently characterized as "zero marginal cost," meaning that it can be distributed for nearly nothing, regardless of how many additional people consume it.

Hidden costs of maintenance. While creating and distributing open source software may have low marginal costs, maintaining it over time incurs significant hidden expenses:

• Responding to user support requests and bug reports
• Updating documentation and managing dependencies
• Reviewing and merging contributions
• Ensuring compatibility with evolving technologies

Burnout risk. The burden of maintenance often falls on a small number of individuals, leading to burnout and project abandonment. This challenge is exacerbated by:

• Expectations of continuous support from users
• Difficulty in monetizing maintenance work
• Lack of recognition for ongoing maintenance efforts

Addressing these maintenance challenges is crucial for the long-term sustainability of open source projects.

4. The economics of open source are shifting from collaborative to solo endeavors

If creators, rather than communities, are poised to become the epicenters of our online social systems, we need a much better understanding of how they work.

Centralized communities. The open source landscape is increasingly dominated by projects centered around individual maintainers rather than large collaborative communities. This shift mirrors trends in other online content creation spaces, where individual creators build audiences around their work.

New economic models. This change necessitates new approaches to valuing and supporting open source work:

• Focus on maintainer reputation and social capital
• Exploration of funding models that support individual creators
• Rethinking contribution dynamics to manage maintainer workload

The challenge lies in balancing the benefits of open collaboration with the need to support and sustain individual maintainers.

5. Managing over-participation is crucial for project sustainability

A tragedy of the commons occurs not from consumers over-appropriating the content itself, but from consumers over-appropriating a creator's attention.

Attention as a limited resource. As open source projects gain popularity, maintainers often struggle with an overwhelming influx of user requests, bug reports, and contributions. This "over-participation" can lead to burnout and project abandonment if not managed effectively.

Strategies for managing demand:

• Automation of routine tasks (e.g., continuous integration, bots for issue triage)
• Clear contribution guidelines and templates
• Selective engagement with high-value contributions
• Distributing support tasks to the user community

Balancing openness with sustainable practices is key to long-term project health and maintainer well-being.

6. Reputation and social capital are becoming central to open source economics

Historically, producers charge customers to access content. But today, producers can make content free to read, while instead charging for "write access": meaning, the ability to appropriate attention from producers.

Reputation as currency. In the new open source economy, a maintainer's reputation and social capital are becoming increasingly valuable. This shift parallels trends in other online content creation spaces, where creators build personal brands and monetize their audience relationships.

Implications:

• Increased focus on personal branding for open source developers
• Potential for monetization through sponsorships and patronage
• Tension between project-based and individual-based funding models

This emphasis on reputation challenges traditional notions of open source as purely altruistic, introducing new dynamics of value creation and capture.

7. Funding models for open source are evolving to support individual maintainers

Can we imagine telling Tfue, who rose to fame by livestreaming himself playing Fortnite Battle Royale on Twitch, that the most he could hope for was to get hired by ESPN?

Beyond corporate funding. Traditional funding models for open source, often relying on corporate sponsorship or foundation support, are being supplemented by new approaches that directly support individual maintainers:

• Crowdfunding and patronage platforms (e.g., Patreon, GitHub Sponsors)
• Paid support and consulting services
• Dual licensing models

Challenges and opportunities:

• Balancing open source ethos with individual monetization
• Developing sustainable funding streams for less visible but critical projects
• Navigating potential conflicts between personal and project interests

These evolving funding models offer new possibilities for sustaining open source work but also introduce complex ethical and practical considerations.

8. The future of open source lies in balancing public access with controlled participation

When production is a one-way mirror, creators are shielded from distraction, building things in public view but without the expectation that they engage with unhelpful contributors.

Rethinking participation. The future of open source may involve a shift towards models that maintain public access to code while limiting direct participation. This approach aims to address the challenges of over-participation while preserving the benefits of open source.

Potential strategies:

• Tiered access models for contributions
• Increased use of automation and AI for issue triage and support
• Development of new platform features to manage user interactions

The challenge lies in finding the right balance between openness and sustainability, ensuring that open source continues to thrive while supporting the needs of maintainers and users alike.

Last updated: November 19, 2024