Skip to content
This repository has been archived by the owner. It is now read-only.

Toil metrics; time to triage issues #19

Open
jlewi opened this issue Jul 25, 2019 · 1 comment
Open

Toil metrics; time to triage issues #19

jlewi opened this issue Jul 25, 2019 · 1 comment

Comments

@jlewi
Copy link
Contributor

@jlewi jlewi commented Jul 25, 2019

The story we want to tell is we increased productivity using ML and various productivity tools.

For that we need a good metric for toil/productivity.

The ideal metric would be something like time to resolve/close issues but this will have high variability and it will be difficult to iterate since we have to wait a long time.

I think a good proxy metric would be time to triage issues.

kubeflow/community#280 proposes a well defined definition for when to consider an issue has been triaged.

Using that criterion we can easily measure how long it took for an issue to get triaged.

We can also look at how many interactions by a human (e.g. comments) were required for an issue to be triaged.

We can easily backfill that metric for all previous issues.

So we could then compute stats like average and mean across issues in some rolling window.

@issue-label-bot
Copy link

@issue-label-bot issue-label-bot bot commented Jul 25, 2019

Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.

@jlewi jlewi added this to Needs triage in Needs Triage Jul 26, 2019
@jlewi jlewi removed this from To Do in Needs Triage Jul 26, 2019
@hamelsmu hamelsmu added this to Ideas in Code Intelligence via automation Jul 31, 2019
@hamelsmu hamelsmu moved this from Ideas to Accepted-On Roadmap in Code Intelligence Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Code Intelligence
  
Accepted-On Roadmap
Development

No branches or pull requests

1 participant