Slow Maintainer Response and PR Review Bottleneck

8/10 High

The FastAPI maintainer (@tiangolo) is a bottleneck for development; most PRs go months without response, require extensive rework, or remain unmerged despite being high-quality. No delegation of merge permissions limits community contribution.

Category
ecosystem
Workaround
none
Freshness
worsening
Scope
single_lib
Upstream
stale
Recurring
Yes
Buyer Type
team
Maintainer
slow

Sources

Collection History

Query: “What are the most common pain points with MCP for developers in 2025?4/7/2026

Right now, every SEP requires full Core Maintainer review, regardless of domain. That's a bottleneck. It slows down Working Groups that already have the expertise to evaluate proposals in their own area.

Query: “What are the most common pain points with FastAPI for developers in 2025?4/4/2026

There are plenty of good PR asked by a lot of people. No response from @tiangolo... There are painful bugs like #3665 that we don't know if it will be fixed or not. Very few commits merged except documentation... multiple open PRs that, without input from you detailing why they're not ready to be merged, can only be considered high quality and merge-able, but have gone stale.

Created: 4/4/2026Updated: 4/7/2026