Questions about code reviews and static analysis tools for TU Delft research

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Questions about code reviews and static analysis tools for TU Delft research

Radjino Bholanath
Hi everyone,

I'm doing research on code reviews and static analysis tools at the SERG group ( of the Delft University of Technology. Currently, we want to give an overview of the usage of code review and static analysis tools in open source projects. Therefore, I would be very happy to know a little bit more about how code reviews are used in MinGW and if (and maybe how) static analysis tools are used. I have a couple of questions for anyone willing to answer:

1. Do all developers (contributors and core developers) have to submit a code review for every change? I’m asking because many projects only review changes made by contributors.

2. Which code review tools are used?

3. Are static analyzers used? If they are used:
  a. Is passing the checks of the static analyzers necessary for a change to be accepted?
  b. Which static analyzers are used?



Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now.
MinGW-users mailing list
[hidden email]

This list observes the Etiquette found at
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

You may change your MinGW Account Options or unsubscribe at:
Also: mailto:[hidden email]?subject=unsubscribe