# Maintainer Attention Is the Scarce Resource in Open Source The conventional framing asks: how do we get more people to write open source code? Eghbal flips this: what if software is actually overproduced, and the real scarcity is maintainer attention? The bottleneck in open source isn't code supply. It's the human capacity to review, triage, merge, document, and support what already exists. Every issue filed, every PR submitted, every support question asked -- each one costs maintainer attention. And unlike code, attention doesn't scale. You can't fork it, distribute it, or automate the judgment calls it requires. A maintainer reviewing a PR needs to understand the project's architecture, the contributor's intent, edge cases, backward compatibility, and documentation implications. That's skilled cognitive work that only a few people in any project can do. This reframes the "sustainability" conversation. Most funding proposals target code production: grants for features, bounties for bugs, sponsorships for releases. But the work that actually burns maintainers out isn't writing code. It's the coordination overhead: answering questions, reviewing contributions from people who didn't read the guidelines, explaining why a PR doesn't fit the roadmap, managing expectations from users who treat free software like a paid product. The implication: protecting maintainer attention matters more than attracting contributors. Saying no to a well-intentioned but low-context PR isn't gatekeeping -- it's resource management. Building triage automation, enforcing contribution standards, and limiting the surface area of a project are all forms of attention conservation. <!-- atomicity: 1 idea ✓ --> ## Why This Matters If you want to support open source sustainability, stop asking "how do we get more contributors?" and start asking "how do we protect the people who are already doing the work?" Fund their time, reduce their interrupts, and respect their no. ## Links - [[3. Resources/Permanent Notes/Stability Is the Precondition for Formation Across Domains]] — applies-in: stable participation lets maintainer knowledge and trust accumulate instead of repeatedly spending attention on reorientation - [[3. Resources/Permanent Notes/Stewardship Invests in Contributor Capacity Not Just Cash]] — extends: stewardship relieves the attention bottleneck by forming more people who can carry triage, review, documentation, and mentoring work - [[3. Resources/Permanent Notes/Real Standards Adoption Means Implementing the Draft and Pushing the Gaps Upstream]] — applies-in: a precise gap report plus reference implementation turns private adoption work into an efficient request for scarce maintainer attention - [[3. Resources/Permanent Notes/Open-Source Design Tools Reach Parity Through Community-Contribution Velocity]] — constrains: community contribution becomes parity only when maintainers have enough attention to review, integrate, and sustain the incoming work. - [[Auditing the Build Not the Install Is What Makes Personal-Scale Coverage Possible]] — contrasts: content-addressed audit compute can be deduplicated across installs, unlike the maintainer judgment that remains irreducibly scarce. - [[AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — extends: deliberate apprenticeship consumes the maintainer attention that automated entry-tier work no longer funds indirectly. - [[3. Resources/Permanent Notes/A Project Is the Community Not the Code]] — extends; if the community is the durable project asset, maintainer attention is the scarce input that keeps it coherent. - [[3. Resources/Permanent Notes/The Stadium Is the Dominant Open Source Pattern]] — the production pattern that leaves a small maintainer core absorbing attention from a large user crowd - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — attention scarcity persists because the work consuming it receives little status or funding - [[3. Resources/Permanent Notes/The Inverse Commons]] — both notes explain why open participation can concentrate costs on a small group - [[3. Resources/Permanent Notes/DevRel Burnout Is Structural Not Personal]] — maintainer overload is the open-source form of role-level structural burnout - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] — the source analysis that grounds maintainer attention as the binding resource - [[3. Resources/Permanent Notes/AI Compresses the Knowledge-Worker Pipeline From Both Ends]] — added 2026-05-28; if AI is compressing the junior-tier work that historically fed the maintainer pipeline, the maintainer-attention scarcity gets worse, not better, even as individual senior maintainers get more leverage from AI tools - [[3. Resources/Literature Notes/Deliberate Mentoring Accelerates OSS Onboarding - Literature Note]] — added 2026-05-28; Pinto et al. empirical data on deliberate mentoring as a counter to the maintainer-pipeline problem this note names — structured onboarding measurably accelerates newcomer activation, but requires up-front maintainer-attention investment - [[3. Resources/Literature Notes/The Importance of Setting Boundaries and Saying "No"]] — applies-in: explicit limits and honest refusals turn finite maintainer attention into predictable commitments instead of an unreliable queue of automatic yeses - [[3. Resources/Permanent Notes/Open Source Project Market Share Tracks Founder Trust]] — added 2026-05-28; project-level downstream effect when the maintainer-attention scarcity manifests as concentrated founder-trust risk - [[3. Resources/Permanent Notes/Zet · Rapid weaponization outpaces manual update workflows]] — machine-scale vulnerability reporting adds a new interrupt stream to already-scarce maintainer attention - [[3. Resources/Permanent Notes/Repeated Workarounds Are Unfiled Bug Reports]] — mining existing configuration focuses scarce attention on pain users already had to solve themselves - [[3. Resources/Permanent Notes/Casual Contributors Are Users Not Community Members]] — evidence-for: reviewing low-context drive-by contributions spends the scarce attention of maintainers without building a durable contributor relationship. - [[3. Resources/Permanent Notes/DevRel as Railroad Infrastructure]] — applies-in: maintainer attention is one of the invisible resources required to keep the connective tracks between projects and developer communities working - [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] — applies-in: public credit makes scarce review, triage, and maintenance work visible enough to recognize and allocate - [[3. Resources/Permanent Notes/WordPress Stores AI API Keys in a Layer Its Own Security Team Says It Cannot Encrypt]] — applies-in: shipping a core encryption API depends on scarce maintainer attention even when the security gap is already known. - [[3. Resources/Readwise/Articles/WordPress Announces Core Security Initiative as AI-Driven Vulnerability Reports Hit Record Levels]] — added 2026-09-05: instance of this note's mechanism at the WordPress security-team scale — HackerOne reports reportedly rose from a decade-long 20-30/month to 450 in July 2026, and the response was a backlog-to-zero pledge and a narrower disclosure-eligibility policy, not 15x more fixes. AI lowered the cost of finding bugs; triage (maintainer attention) stayed the binding constraint. - [[3. Resources/Readwise/Articles/Updates to the WordPress Vulnerability Disclosure Program]] — added 2026-09-05: the policy consequence of the same shift — narrowing bounty eligibility by required role is this note's claim made explicit as published policy, doubling as a statement of where the security team's scarce hours go. - [[3. Resources/Permanent Notes/A Code of Conduct File Being Present and Being Maintained Are Separate Facts]] — applied in: a code of conduct's edit history is checkable, but no edit pattern was found to predict community health, so an untouched file is a question and not a verdict. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists it under Leadership challenges as the same attention scarcity DevRel faces. ## Source - [[3. Resources/Permanent Notes/Gate Contributions on Demonstrated Comprehension Not on Tooling]] — applies-in (added 2026-08-01): the concrete mechanism for conserving the attention this note names as scarce — push validation cost back onto the submitter who generated it, rather than detecting the tool they used - [[3. Resources/Permanent Notes/A Defense Experts Fail Is Not a Defense for Users]] — evidence-for (added 2026-08-01): the AUR reviewers who missed malware across two campaigns were not short of knowledge, they were short of attention. Repository review is the same scarcity this note names, and its failure is what "read the build script yourself" is quietly covering for. - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] - [[3. Resources/Readwise/Books/Working in Public]] - [[3. Resources/Readwise/Books/The Art of Community|The Art of Community]] - See also: [[Open Source Governance MOC]], [[AI & the Future of Knowledge Work MOC]]