A developer’s frustration over a feature request languishing for over a year in Jellyfin web development illustrates a systemic problem plaguing popular open source projects. Despite getting approvals, isolated, small pull requests faced review droughts, revealing that slow feedback severely degrades contributor engagement and code velocity.

Queuing theory explains this decay: as maintainer utilization nears 100%, wait times grow exponentially, not linearly. With Jellyfin web managing around 200 open PRs against a limited reviewer pool, the average cycle time stretches to 6.7 months. This bottleneck creates a 'Batch Size Death Spiral' where stalled features encourage larger, slower submissions.

Solutions focus on protecting the lone maintainer's time, drawing from the Theory of Constraints. Suggestions include implementing hard caps on PR size, perhaps around 300 lines, and automating quality gates to prevent maintainers from wasting cycles on incomplete submissions or merge conflicts.

Prioritizing feature work based on the cost of delay, rather than simply merging the smallest bug fixes first, is also proposed. This reframing seeks to ensure essential feature development keeps pace with necessary maintenance, a common failing point in volunteer-driven software ecosystems.