|Re: [jdt-dev] JDT-Core: Report on Gerrit code review|
I hope you had the chance to look at our report and found it interesting.
Our goal is to create a Code Review Analytics tool to give the developers and project managers a better idea of what is really going on inside the code review process.
This could lead to further improve it, optimising the effort that the developers spent on it. For instance, reducing the number of documentation changes might allow a reviewer to allocate more time on finding functional defects.
Another possible application might be to help optimising the allocation of the developers to a particular review.
Here is a link to the report:
I would like to keep improving our tool adding more and more actionable information. This is just the first step, so I am interested in hearing your feedback so I could keep improving it.
Please, consider to help me by answering the survey attached to the report if you think is information are useful or might be useful in the future with the next steps we would like to take in improving the tool.
Thank you very much.
On 17 Aug 2019, at 18:13, Enrico Fregnan <fregnan@xxxxxxxxxx> wrote:
Back to the top