[Teammetrics-discuss] Gitstat problems.

[Sukhbir Singh]

Hi,

I tested gitstat.py with two repositories, a simple one such as ours
and a complex one such as the ball.git repository of debian-med.

For a simple repository such as ours with no merges, branches or tags,
it works fine and the output matches to the expected output.

However, for repositories with lots of activity and with the problem
of upstream contributors, there are some problems:

    - I am not sure whether 'git log' is enough for such repositories
OR whether more needs to be taken care of.
    - David's script seems to (I am not sure but it should) separate
the upstream contributors but I have not been able to integrate it.

The stats in this case are the main thing and we should be _sure_ that
we are calling `git log` with the right parameters. This is absolutely
important. I suggest that we get in touch with someone who is familiar
with Git development in Debian and then integrate David's script,
which I am sure there will be an easier way of integrating from the
command line itself.

The problem right now is, I am not sure that what we are doing is
enough. For simple repositories, it works wonderfully. But for
repositories with lots of activity (and which will be the case 90%),
is what we are doing enough? I have my doubts.

So how do we take this ahead then?

-- 
Sukhbir