A nice side-effect of using reviews is that it will ensure that other programmers have some knowledge of the code that is being merged to the project. The more that reviews changes to the project the more spread the knowledge is - which ought to increase the bus factor.Now the problem is that people quit (and hopefully isn't hit by the bus) so after a while both the author of the code and those who reviewed the changes are no longer present. The solution to this problem is to do post-merge reviews to the code to restore the common knowledge of the code.Probably such a process would benefit from a tool that can produce statistics over the common knowledge of the code. That is files that contains commits where neither the author nor those who reviewed it are present any longer, files that only one involved person is present and so on.First question is of course if someone has done something similar and if it works well in practice?The question is if this is possible to do in Gerrit? That is can I do a review, add comments and so on even after the changeset is closed?
Using gerrit(-like) tool to ensure high bus-factor
development process;code reviews;gerrit