You are here:

Change Request Review Duration

Question: How long does it take a change request reviewer to review a specific change request?

Overview

Change Request Review Duration measures the average time between a change request submission review cycle and the time for a first review. This metric measures one review, however, there may be multiple reviews within a Review Cycle Duration within a Change Request and this measures the time of each review. The time waiting for a review is zero if the change request is merged without any requested revisions or clarification. Low change request review duration indicates an active community with engaged reviewers, timely feedback for improving code quality and faster project progress. High change request review duration may signal overburdened reviewers, lack of expertise, or hesitation to approve changes which can lead to contributors' frustrations or increased technical debt. Analyzing change request review duration across different contributors can reveal disparities in review times, maintainer workload adequacy and potential for burnout, whether delays are the responsibility of a reviewer, and discrepancies in review times for different contributors to indicate whether the review process is inclusive.

Want to Know More?

Click to read more about this metric.

Data Collection Strategies

  • Survey project contributors.
  • Use a survey to gather project demographics. (For example, using the Open Demographics questions)
  • Survey new community members as identified through such ways as attending newcomer hangout, recent introductions, and time to first PR mrge.
  • Survey that is activated by certain types of contributions like non-code contribution, community engagement etc.

Filters

  • Change Request Review Duration can be filtered by:
  • Reviewer (e.g., name or id)
  • Reviewer role (e.g., maintainer, reviewer, and member)
  • Bot reviews
  • Date and time the change request was submitted or modified
  • Date and time of the response
  • change request type and size may affect the response time.

Visualization

Augur Image


References

Contributors

  • Vinod Ahuja
  • Dawn Foster
  • Elizabeth Barron
  • Kevin Lumbard
  • Matt Germonprez
  • Sean Goggins
  • 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=4920

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.

Tags:
Was this article helpful?
Dislike 0