[wikke]

Recently I had to analyse the commit history of team members in a project and this tool: http://code.google.com/p/gource/ proved to be very effective.

[lifeisstillgood]

I don't mean to be disparaging but I am lost trying to understand the tool. I can see it is cool, and am fascinated by the different project styles (the tight development of git versus drupal or RoR is clearly indicative of something)

But...

How do you use that? Once you start looking at s specific function, then you need to read that function, not see a prefix

It may be me but I just don't get it

[mnutt]

Gource doesn't tell you a lot about history, but on larger projects with many people I could see how it could aid in coming up to speed with team dynamics. Maybe you could see that Module A gets updated by the newest hire once every 6 months, and that explains why it is a mix of many different coding styles. Or Module B has been maintained solely by Bob for the last 3 years, so if you have any questions about it he's probably the one to ask.

[lifeisstillgood]

But I don't see why it's a time based animation.

The stats you just mentioned seem impossible to pick from the demos. From logs and summary yes but the demo is just ... Pretty

[mnutt]

You're absolutely right; I was mistakenly thinking of codeswarm. (http://www.michaelogawa.com/code_swarm/)

[googletron]

That's pretty cool,does it provide information and code viewing tool that you can step through.

[wikke]

By default it creates a time based view to see which persons edited which files and a overview over the files at that point of time. It does not put the emphasis on the code changes but on the dynamics of the participants. To generate an overview over the paticipants commits the generated logs were parsed. Sourcecode in this file: https://github.com/educs/Documentation/blob/master/gource/ma...

TL,DR: No code viewing tool.