Skip to content

Commit

Permalink
Merge pull request #3068 from github/zkoppert-patch-1
Browse files Browse the repository at this point in the history
Add link to github action for measuring maintainer response time
  • Loading branch information
ahpook authored Aug 10, 2023
2 parents 5dc1e66 + ebc5efb commit 22b16c0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _articles/metrics.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ Unresponsive maintainers become a bottleneck for open source projects. If someon

[Research from Mozilla](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177) suggests that maintainer responsiveness is a critical factor in encouraging repeat contributions.

Consider tracking how long it takes for you (or another maintainer) to respond to contributions, whether an issue or a pull request. Responding doesn't require taking action. It can be as simple as saying: _"Thanks for your submission! I'll review this within the next week."_
Consider [tracking how long it takes for you (or another maintainer) to respond to contributions](https://github.blog/2023-07-19-metrics-for-issues-pull-requests-and-discussions/), whether an issue or a pull request. Responding doesn't require taking action. It can be as simple as saying: _"Thanks for your submission! I'll review this within the next week."_

This comment has been minimized.

Copy link
@Artemi24

Artemi24 Aug 22, 2023

❤️❤️❤️❤️


You could also measure the time it takes to move between stages in the contribution process, such as:

Expand Down

1 comment on commit 22b16c0

@Artemi24
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

Please sign in to comment.