Skip to content

Limit on number of concurrent FCPs #2142

Open

Description

Most people have lives outside of Rust and only have a limited amount of time each week to dedicate to reading RFCs and commenting. Even when someone does have plenty of time, they can still get burnt out focusing on just a few really lively RFCs. When a whole truckload of RFCs are shoved through FCP at the same time, people end up only being able to pay attention to some of them, while other RFCs slip by unnoticed. The current situation is borderline ridiculous:

Rust is not currently lacking in things to implement or stabilize (we have 277 open tracking issues!), so perhaps it might be wise to limit the number of RFCs that can be in FCP at a given time. We should instead strive to have a slow continuous stream of RFCs so there is always something to comment on, but not so much that people are inundated.

And no, having an "impl period" where you don't merge RFCs and instead focus on implementation is not a valid excuse for cramming as many RFCs into FCP in preparation for that "impl period".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    T-communityRelevant to the community team, which will review and decide on the RFC.T-coreRelevant to the core team, which will review and decide on the RFC.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions