Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [etrice-dev] eTrice Gerrit code review report

Hi Henrik,

Thank you very much for your reply.

This is just a first step, but I would like to keep improving the tool and code review analytics in general to reach a level in which this information are to the point and actionable.

If it’s not too much to ask, it would be great if you could fill in our survey (https://www.surveygizmo.com/s3/5177387/Code-review-changes-report-Etrice). I would like to use this feedback to understand what already works, what can be improved and which new information I can add in future “releases”.

Thank you again.

Best, 
   Enrico

On 22 Aug 2019, at 12:26, <hrr@xxxxxxxxx> <hrr@xxxxxxxxx> wrote:

Enrico,
 
thanks for your efforts and suggestions.
 
I like what you propose even though I doubt that it would be of great help in our project.
 
Thanks,
Henrik
 
 
Von: etrice-dev-bounces@xxxxxxxxxxx <etrice-dev-bounces@xxxxxxxxxxx> Im Auftrag von Enrico Fregnan
Gesendet: Donnerstag, 22. August 2019 11:39
An: etrice-dev@xxxxxxxxxxx
Betreff: [etrice-dev] eTrice Gerrit code review report
 
Dear eTrice compass 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 the majority of the changes happened during a code review in the last year in your project involve documentation issues? 
 
My goal is to give developers insight on what really happens during the code review process to check if this matches their expectations or if the process can be improved (e.g. improving the way in which reviewers are chosen, revising the code review policies and so on.)

You will more data about your project at the following link:


https://www.surveygizmo.com/s3/5177387/Code-review-changes-report-Etrice


I would like to understand better what works already and what still needs to be improved. I am planning to keep improving the tool adding more and more feature, but I would need your help to understand which information should be added/removed etc. 
 
For this reason, the link contains the report and some questions we would like to ask you about it. However, 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. 

Cheers,
Enrico

Diese Nachricht wurde mit einer kostenlosen Version von Proxy-Manager gesendet.
Wollen Sie von Ihrem Exchange-Konto mit einer Ihrer Proxy SMTP-Adressen senden?
Testen Sie Proxy-Manager kostenlos! 
Diese Fußzeile wird nicht in der registrierten Version von Proxy-Manager angezeigt.
Klicken Sie hier, um Proxy-Manager zu registrieren.
_______________________________________________
etrice-dev mailing list
etrice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/etrice-dev


Back to the top