Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a WP-CLI command reports GitHub pull request stats #13492

Closed
danielbachhuber opened this issue Jan 24, 2019 · 3 comments
Closed

Create a WP-CLI command reports GitHub pull request stats #13492

danielbachhuber opened this issue Jan 24, 2019 · 3 comments
Labels
[Type] Project Management Meta-issues related to project management of Gutenberg

Comments

@danielbachhuber
Copy link
Member

danielbachhuber commented Jan 24, 2019

Following up on #13441 (comment), I'd like to create a WP-CLI command that generates some top-level GitHub pull request stats we want to track.

Currently, here are the metrics I'm thinking of:

  • Unreviewed PRs:
    • Total number of unreviewed PRs
    • Unreviewed PRs older than 2 business days
    • Number of unreviewed PRs older than 2 business days broken down by label
  • Overall metrics:
    • For open PRs, average time it takes to first review.
    • Total PRs created in the last 7 days.
    • Number of PRs created in the last 7 days broken down by label.
    • Total PRs merged in the last 7 days.
    • Number of PRs merged in the last 7 days broken down by label.
    • Median time between when a PR is opened and its first review.
    • Median time between when a PR is opened and it's merged or closed.
    • Total number of reviewers in the last 14 days.
    • Number of reviews in the last 14 days broken down by reviewer.

As a v1, this WP-CLI command would fetch data from the GitHub API, process it, and spit out a JSON report. We could put the JSON into some other system for tracking this data over time, or build a simple web page that presents this data in a human-readable format.

Feel free to weigh in with any additional metrics you think are worth tracking, or whether you'd change the ones I've identified. The challenge with metrics is that people tend to optimize for them over time. We'll want to make sure what we track is actually worth optimizing for.

@danielbachhuber danielbachhuber added the [Type] Project Management Meta-issues related to project management of Gutenberg label Jan 24, 2019
@danielbachhuber danielbachhuber self-assigned this Jan 24, 2019
@danielbachhuber
Copy link
Member Author

danielbachhuber commented Jan 24, 2019

Going to pick this up over the next couple or few weeks (unless someone wants to hack on it before me).

One important qualifying question: if we only picked five (5) of these metrics, which would be the most important?

@danielbachhuber danielbachhuber changed the title Create a WP-CLI command reports GitHub repo stats Create a WP-CLI command reports GitHub pull request stats Jan 26, 2019
@bph
Copy link
Contributor

bph commented Jan 30, 2019

As to your question regarding what are the top 5 metrics, for the weekly meeting 7 days is your reporting period

  • Total Open PRS at the beginning of the week
  • Total New PRs in last 7 days
  • Reviewed PRs in the last 7 days
  • Merged in the last 7 days
  • Total Open PRs at the end of the week.

To measure sucess of activities to increase number reviewers

  • Median time between when a PR is opened and its first review.
  • Median time between when a PR is opened and it's merged or closed
    And their diffs to last week.

oops not five per se... but it gives a fast overview:-)

@mtias
Copy link
Member

mtias commented Jul 13, 2021

Closing for now.

@mtias mtias closed this as completed Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Project Management Meta-issues related to project management of Gutenberg
Projects
None yet
Development

No branches or pull requests

3 participants