Talk:ParticipationMetrics/Community Dashboard/Codereviewdbspec

From MozillaWiki
Jump to: navigation, search

Usage tips

Copy and paste the wiki source from the main page that you want to comment on. You can call out the quote by prefixing each line with a colon like this:

 :**a view that looks at a users patches and tells us how long each one has been in review.

Use four dashes to separate discussion topics:

 ...end of previous discussion
 ----
 New discussion topic

Use four tilde marks to prefix a comment with your Wiki username and timestamp like this:

 :some quoted text
 DEinspanjer 09:41, 24 June 2011 (PDT) I think this is a great idea!

Discussion

    • average time all bugzilla bugs spend in any given "state" in bugzilla (submitted, confirmed, assigned, review, etc...) It might be good to maybe compute that average by removing that outlier 1 or 2 percentile bugs, but I'm not totally sure of that).
    • average time a module's bugs spend in any given "state" in bugzilla (submitted, confirmed, assigned, review, etc...) (recognize this may not be possible
    • average time a specific users bugs spend in any given "state" in bugzilla (submitted, confirmed, assigned, review, etc...)
    • a view that looks at a users patches and tells us how long each one has been in review.

DEinspanjer 09:41, 24 June 2011 (PDT) When bugs change assignee or product/component, does that reset their time in a state? I can see it useful to measure either way. David Eaves 09:50, 24 June 2011 (PDT) My sense is that we should measure both (total time in all states vs. each iteration of code review) but that in our case, the priority should be that code review means each time it goes into that state -> because that's what matters to the contributor. In addition, it's also how we can measure the speed of code reviewers


    • average time a specific users bugs spend in any given "state" in bugzilla (submitted, confirmed, assigned, review, etc...)
    • a view that looks at a users patches and tells us how long each one has been in review.

DEinspanjer 09:41, 24 June 2011 (PDT) Does "user" here mean the reporter or an assignee? Again, I can see it being useful to measure either way. David Eaves 09:50, 24 June 2011 (PDT) I was definitely thinking assignee, as again, I think we are focused on developer contributors and figuring out how to make their lives better. For non-developers who submit bugs I think they will be more generally interested in how long a bug takes to get patched (on average), they are less concerned with the sausage making (e.g. how long in each state).