As per the Code Review work group meeting discussions, we'd like to define a set of metrics (probably one or two to start with) to help us establish a baseline to improve upon. Although these metrics are focused primarily on responsiveness, we want to insure that we encourage sound code review processes and outcomes as well.
Behaviors to be mindful of:
- Quick initial response with slow follow-through.
- No response from patch submitter.
- Merging everything in order to be "responsive".
Ultimately these metrics will be available on some form of Code Stewardship dashboard to help Code Stewards manage review requests and resources.