You are here:

Change Request Review Duration

This metric is a release candidate. To comment on this metric please see Issue #88. Following a comment period, this metric will be included in the next regular release.

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

Context Tags: Contribution, Lifecycle

Keywords: Change Request Review, Change Request, Code Review, Time, Pull Request

Description

The Change Request Review Duration metric measures the time from when a submitter has submitted a change within a review cycle until it is reviewed. This metric measures one review, however, there may be multiple reviews within a Review Cycle Duration within a Change Request and this measures time of each review. The time waiting for a review is zero if the change request is merged without any requested revisions or clarification.

Objectives

Long waiting periods for a change request review may indicate potential lack of experience by a maintainer, lack of time, hesitation on the part of the maintainer, or any other blocker. Delayed reviews in a community may cause a decline of interest by potential contributors or cause original changes to be out-of-sync with the rest of the code base. The Change Request Review Duration metric helps identify:

Maintainer workload adequacy and potential for burnout Whether delays are the responsibility of a reviewer Discrepancies in review times for different contributors to indicate whether the review process is inclusive.

Implementation

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 law. 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.

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

Figure - Source: Augur Image API & Documentation

Tools Providing the Metric

  • Augur
  • GrimoireLab

References

Contributors

  • Vinod Ahuja
  • Dawn Foster
  • Elizabeth Barron
  • Kevin Lumbard
  • Matt Germonprez
  • Sean Goggins

To edit this metric please submit a Change Request here: https://github.com/chaoss/wg-common/blob/main/focus-areas/time/change-request-review-duration.md

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