On Jul 25, 2012, at 12:39 AM, Ryan Lane wrote:
Many claims that "Gerrit sucks" tend to be due with misunderstandings of how Gerrit works. Many other claims are due to our workflow or our restrictions with access currently. Of course, many claims are legitimate and we are reporting the issues, tracking them upstream, and in some cases pushing in fixes.
In their defense, I think a lot of it has to do with terrible UI/UX in Gerrit. The basics is can be modified by CSS and templates (I believe we've done some), but it only goes so far. How do I modify Javascript in Gerrit? I think it starts (and ends) somewhere in the hell that is GWT… and when GWT begins with, something about how awesome it is to be able to write Ajax stuff using Java, I stop reading http://www.flickr.com/photos/tychay/1388234558/
I've not added this complaint because David already put 90% of this in the #1 reason on his list already. ;-)
Related is the fact that we seem to have a lot of PHP web dev expertise (for some reason) and Gerrit went from Python (serviceable) to Java (totally opaque). Apologies to those of you at the WMF who lurv themselves some Java… all two of you… and one of you is probably the guy who wrote the "case against"
…
But it is true a lot of the griping was related to people from a SVN/CVS model not understanding the Git model at all (in my more cynical moments, I feel that neither do Gerrit's developers :-D ).
Take care,
terry