On Fri, Jul 27, 2012 at 6:42 AM, MZMcBride z@mzmcbride.com wrote:
For what it's worth, I think Ryan makes a compelling case for sticking with Gerrit (and I'm still not convinced that another switch would do more good than harm). I'm still deeply worried about the ability to use and improve Gerrit. It would be horribly painful to see all of the work switching from SVN to Git (a large portion of which was intended to allow easy code contributions) go to waste because this particular Git front-end has scared everyone away.
For what it's worth, this is pretty much exactly where I'm at right now. In spite of my defense of Gerrit, I'm not blind to it's manifold deficiencies in its current form. In addition to the problems for new volunteer contributors, there's a steep learning curve for new employees. I'm also worried about the steep learning curve anyone from our community (myself included) would have in getting set up to improve Gerrit through writing patches and plugins, though I'll take Chad at his word that it's really not as bad as many of us fear.
But, I'm also still not convinced that another switch would do more good than harm.
I think our best mitigation strategy is to do as good a job as we possibly can integrating Gerrit with GitHub, combined with other improvements to Gerrit.
Rob