Actually, mpg123 is a much nicer example for difficulties with code history. You have movements plus a frankenstein-like history resulting from generating some initial svn history via diffs from ... [More] release versions, plus integrating some CVS history (older commit dates, but newer code) and then actually committing stuff in svn. What mpg123 also nicely shows is the problem of correct attribution: I created the initial commits from code written many years before by Michael Hipp... well, I could manipulate revision history to change commiter name and commit date (setting to release/tarball modification time of version x), but that would still leave open the problem of commits that actually have two contributors behind them (no fantasy, they are there;-). Well, what I want to say is: Once ohloh gets the meaning of mpg123 svn history right, it is a good way near perfection;-) [Less]

Well, I'm also curious about my initial kudos calculation... but it is undetermined for several days now.

Well, also doing my me-too. My prototype project with this issue is DerMixD. At some time stuff has been moved from dermixd/trunk/ to trunk/ (that's what's left from migration out of some bigger CVS ... [More] repo, even). I must admit that I wonder what the ohloh code does to get the history... a simple svn log -v --xml svn://orgis.org/dermixd/trunk gives you the proper history with movements as far as subversion can tell. Well, I am standing in line, waiting for the fix to get my commit count up;-) [Less]