Change Request Closure Ratio
Question: Is the project keeping up with change requests?
Overview
Change Request Closure Ratio evaluates if the project is handling change requests (e.g., pull requests / merge requests) in a timely fashion by measuring the ratio between the total number of change requests closed during a time period versus the total number of open change requests during that same period. A high change request closure ratio indicates that changes are addressed promptly, reducing frustration and encouraging continued participation while a low change request closure ratio indicates that the project is not keeping up with contributions and might suggest a lack of maintainers or an overburdened team, necessitating adjustments. Change Request Closure Ratio provides insight for understanding whether a project has enough maintainers to keep up with change requests, encouraging maintainers to close change requests that will not be merged, even when this might involve difficult conversations and monitoring long closure times or neglected change requests which may be a barrier to contribution for participants from underrepresented groups.
Want to Know More?
Filters (optional)
- Date ranges (e.g., past 90 days, past year)
- Automated responses, e.g., only count replies from real people by filtering bots and other automated replies
- Labels
- Type of change request (bug fixes vs. new features)
- Type of close (accepted vs. rejected)
Visualizations (optional)
Total vs. Closed Pull Requests: Data from Augur displayed using the Seaborn Python library.
REI Data from GrimoireLab (REI: Review Efficiency Index, defined as the number of closed pull requests divided by the number of open ones in a given period of time. Measures efficiency closing pull requests.)
References
Contributors
- Dawn Foster
- Matt Germonprez
- Kevin Lumbard
- Elizabeth Barron
- Yehui Wang
- Peculiar C. Umeh
Additional Information
To edit this metric please submit a Change Request here.
To reference this metric in software or publications please use this stable URL:https://chaoss.community/?p=4834
The usage and dissemination of health metrics may lead to privacy violations. Organizations may be exposed to risks. These risks may flow from compliance with the GDPR in the EU, with state law in the US, or with other laws. There may also be contractual risks flowing from terms of service for data providers such as GitHub and GitLab. The usage of metrics must be examined for risk and potential data ethics problems. Please see CHAOSS Data Ethics document for additional guidance.