# Maintenance Visibility Functions as Funding Infrastructure ## Claim Publishing routine maintenance work as a visible, recurring report is itself a funding intervention, not just a communication exercise, because unseen work is harder for sponsors and organizations to staff and defend. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for maintenance work that is real, ongoing, and valuable but structurally invisible — security triage, build infrastructure, engine correctness fixes — the kind of work with no single shippable feature to point to. - Breaks if visibility reporting becomes performative (activity theater without linked outcomes) — then it's communication without the funding effect, and the claim doesn't hold for that report. ## Evidence The PHP Foundation published its first quarterly contractor report specifically, by its own stated purpose, to improve communication about a 13-person core team's work across engine correctness, sockets/streams/TLS, build tooling, extension installation, ecosystem security triage, php.net infrastructure, and governance. The report itself is the intervention: work that was previously invisible outside the Foundation's own operations becomes something sponsors can see and, implicitly, decide to fund or not. ## Links - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — because extends; prestige and funding are adjacent scarcities, both starved by invisibility - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — because applies-in; visibility reporting is one lever for protecting that scarce resource - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; sustainable funding models for maintenance-heavy open-source projects - [[3. Resources/Literature Notes/AI Spam PRs Need a GitHub Solution — Brian and Helen Hou-Sandí (X, 2026-10-08)]] — because evidence-for: Helen Hou-Sandí asks for this mechanism applied to infrastructure costs, so maintainers' bills become contributable ## Tests / falsifiers - Track sponsor or funding response in the two quarters following this report's publication. No measurable change would weaken the claim that visibility itself moves funding, as opposed to merely informing. - Compare organizations that publish similar maintenance-visibility reports against those that don't, controlling for project size, on staffing/funding growth for maintenance roles specifically (not feature roles). ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/Quarterly Progress Report - Q2 2026]] — The PHP Foundation, first quarterly contractor report.