# Plugin Maintenance Attaches to a Person Not the Organization ## Claim An agency may own a plugin on paper, but its support capacity usually lives in one individual, so a single departure can degrade maintenance for every site depending on it with no ownership change to signal the risk. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for org-owned open-source projects where support work is not deliberately rotated across a team. - Breaks where maintenance is genuinely distributed across multiple active contributors, or where a formal succession plan exists and is exercised before a departure, not improvised after. - Says nothing about code ownership or licensing — only about the support relationship, which is the part users actually experience day to day. ## Evidence Michael Beckwith's departure from WebDevStudios after 13 years and 7 months leaves Custom Post Type UI and WP Search with Algolia — two widely-installed community plugins — without their most consistent support presence, with no public change in the plugins' formal ownership. He names community support, not code, as what he's proudest of, which is exactly the labor category that disappears from view when the person providing it leaves and nothing on the plugin's listing changes. ## Links - [[3. Resources/Permanent Notes/Update Signatures Prove Provenance Not Freshness]] — because contrasts: that note is about a different maintenance-legibility gap (signed updates say nothing about active support); together they cover two ways a plugin can look maintained while support quietly erodes - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — because applies-in: maintainer continuity is a security property of the ecosystem, not just a career-story detail ## Tests / falsifiers - Track wordpress.org support-forum response latency for CPT UI and WP Search with Algolia across the 90 days before and after 2026-07-23; a real degradation would confirm the mechanism. - Find a counterexample: an org-owned plugin whose support quality held steady through a maintainer departure because support was already rotated — would show the claim's scope condition is doing real work, not just hedging. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/And Now My Watch Has Ended (Michael Beckwith, WebDevStudios)]] — reports the separation and the unresolved continuity question for both plugins.