Time to First Response
Question: How much time passes between when an activity requiring attention is created and the first response?
The first response to an activity can sometimes be the most important response. The first response shows that a community is active and engages in conversations. A long time to respond to an activity can be a sign that a community is not responsive. A short time to respond to an activity can help to engage more members into further discussions and within the community.
Identify cadence of first response across a variety of activities, including PRs, Issues, emails, IRC posts, etc. Time to first response is an important consideration for new and long-time contributors to a project along with overall project health.
Time to first response of an activity = time first response was posted to the activity - time the activity was created.
- Role of responder, e.g., only count maintainer responses
- Automated responses, e.g., only count replies from real people by filtering bots and other automated replies
- Type of Activity, e.g., issues (see metric Issue Response Time, emails, chat, change requests
Tools Providing the Metric
To edit this metric please submit a Change Request here: https://github.com/chaoss/wg-common/blob/main/focus-areas/time/time-to-first-response.md
To reference this metric in software or publications please use this stable URL: https://chaoss.community/?p=3448
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.