Dear Eclipse platform text developers, I would like to thank those of you who spent some of their time to give us some feedback. It was extremely appreciated, thank you very much.
I hope many more of 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 and so on. Here is a link to the report: https://www.surveygizmo.com/s3/5170893/Code-review-changes-report-eclipse-platform-text <https://www.surveygizmo.com/s3/5170893/Code-review-changes-report-eclipse-platform-text> 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 more of your feedback to keep improving it. Please, if you still haven’t done it, 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. Best, Enrico P.s. If you want, you can also have a look at the report we created for eclipse-platform-UI here: https://www.surveygizmo.com/s3/5169964/Code-review-changes-report-Eclipse-platform-UI <https://www.surveygizmo.com/s3/5169964/Code-review-changes-report-Eclipse-platform-UI> > On 19 Aug 2019, at 13:26, Enrico Fregnan <[email protected]> wrote: > > Dear Eclipse Platform Text developers, > > I am Enrico, a researcher at the University of Zurich and I am studying how > to evaluate the code review process to understand how it could be improved. > > I created a tool that analyses the changes that happen during a review on > Gerrit, to measure the effects of code review on code and understand which > kinds changes reviewers pay attention to. > > For example, are you aware that more than 50% of the changes happened during > a code review in the last year in your project involve documentation issues? > > You will find this and more data about your project at the following link: > > > https://www.surveygizmo.com/s3/5170893/Code-review-changes-report-eclipse-platform-text > > <https://www.surveygizmo.com/s3/5170893/Code-review-changes-report-eclipse-platform-text> > > > The link contains the report and some questions we would like to ask you > about it. The report is designed in a way that you don't have to answer the > questions (if you just want to look at the report), but it would be great if > we could know what you think about our tool/report. Answering will take you > 5/10 minutes. > > If you have any question about the report or our research, please don't > hesitate to contact me. > > Thank you very much for your time and sorry for bothering you. > > P.s. > If you want, you can also have a look at the report we created for > eclipse-platform-UI here: > > https://www.surveygizmo.com/s3/5169964/Code-review-changes-report-Eclipse-platform-UI > > <https://www.surveygizmo.com/s3/5169964/Code-review-changes-report-Eclipse-platform-UI> > > Cheers, > Enrico
_______________________________________________ platform-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
