Talk:Git/Gerrit evaluation

The thing I most hate about gerrit is I can't get a diff like this easily from it: i.e.: A unified diff with about 3 lines of context for all files modified by the commit on a single page. I know I can open diffs in separate tabs for all files involved, but that tends to slooooow down my browser and I personally just don't like it. (perhaps there's a way to do what I want, I'm not sure. gerrit does not have a ui that leads to discoverability of features) Bawolff (talk) 16:50, 11 July 2012 (UTC)


 * Yeah, that's one of those things we'd like to add I think... --brion (talk) 17:36, 11 July 2012 (UTC)
 * There's actually work already being done on this by the folks at Qt (example). It's in the process of being upstreamed, don't know what the status is though. ^demon (talk) 18:55, 11 July 2012 (UTC)

Extensions
Are we concerned about extension development too or are we just focusing on core code? I ask because setting up an extension for Git + Gerrit was a hideous drawn out process compared to setting up a project on GitHub or Gitorious. --Cneubauer (talk) 19:21, 11 July 2012 (UTC)


 * Extensions are also very much a consideration here. -- RobLa-WMF (talk) 17:50, 12 July 2012 (UTC)


 * The fact that it was a "hideous drawn out process" is more an issue of how we at WMF use Gerrit then an inherit flaw within Gerrit. -- Drdee (talk) 17:56, 12 July 2012 (UTC)


 * True. Another point is that extensions that prefer post-commit review instead of pre-commit review lost access to Code Review with the switch to Git/Gerrit. It would be nice to have a review tool that also innately supported post-commit review. --Cneubauer (talk) 19:13, 12 July 2012 (UTC)