[Metrics] Common Metrics - Time to First Response

[xiaoya-yaya]

Description

• How much time passes between when an activity requiring attention is created and the first response?
• 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

Filters

• 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), change requests

Instances of Implementation Time to first response of an activity = time first response was posted to the activity - time the activity was created

Resource CHAOSS: Common Metrics -> When https://chaoss.community/metric-time-to-first-response/

[open-digger-bot[bot]]

This issue has not been replied for 24 hours, please pay attention to this issue: @sunshinemingo @wengzhenjie

[frank-zsy]

As we already have issue response time metric, how can we implement this one?

IMO, this metric is a quite abstract metric and we need some implementations like issue response time and change request response time, but no more other response time needed for GitHub data, but if we have more data, we can have like email response time in the future.

So maybe we just should add a change request response time like issue's. @xgdyp @xiaoya-yaya @longyanz

[xiaoya-yaya]

Agree!

[frank-zsy]

/self-assign