On Wed, Jul 18, 2012 at 6:17 PM, Daniel Friesen lists@nadir-seen-fire.com wrote:
On Wed, 18 Jul 2012 11:41:06 -0700, Ryan Lane rlane32@gmail.com wrote:
On Wed, Jul 18, 2012 at 1:18 PM, Petr Bena benapetr@gmail.com wrote:
What about changing gerrit to our needs? It's open source, I suppose.
That's of course the route we're going right now. The biggest hurdle to doing so is that it's written in Java, and Prolog. Neither of those languages are amazingly difficult, though, so I don't really see that as a complete blocker.
- Ryan
The blocker for me was not the language, but the codebase. I wanted to make a small tweak to Gerrit so I started looking through the code. And I had absolutely no clue where to find what I was looking for. I couldn't make sense of what most of what I found was even supposed to do. And people have pointed out a number of issues with Gerrit like the way it handles output and css which feel much more like fundamental (ie: unfixable without practically rewriting) issues with Gerrit.
Diving into a large mature codebase that you've never touched is not usually something people can pick up in an afternoon. I imagine most people try to find something they do understand, grep around, and then slowly expand the areas of code they know their way around.
It's just very enterprise-y Java. It's not really all that hard if you're interested in actually diving into it.
-Chad