Call me ignorant since I've never really used Gerrit. Someone just brought it to my attention once. Initially I just liked it because it seemed like a nice tool for collaborating (commenting) on code rather than using it for review policy enforcement. I understand as a matter of policy, code review requirements is not a direction you want to go in. However it seems like a nice tool to use once and a while when working on a tough piece of code to socially hack at it.
I think we have something like this unofficially for commenting on the code called Review Board [0]. One of my reasons for this post is to make that known. I think Gerrit works much better and offers some workflow features for actually conducting code reviews. I don't know if Review Board does the same. Gerrit seems more oriented towards git though. Anyhoo what I am saying is, it might be nice to have the tool without having the hard policy. And people can do reviews when they like to do reviews without it being mandatory. To suggest this was my second reason. Just my 2 cents. -- Best Regards, -- Alex --------- [0] -- https://reviews.apache.org/dashboard/
