Hi Kevin,
Thanks for the kind words. I wish I had better news for you in response.
With Subversion repositories, Ohloh examines only current development line. If files are moved to or from other branches, Ohloh will not see what happens to those files on the branches.
If you create and edit files on a branch, then copy them to the trunk, we do not see that early editing. It looks to Ohloh as if the file was created fully formed on the day it was moved into the trunk.
On 24 Mar 2006, it looks like all of the files in this project were moved from trunk/ERP5 to erp5/trunk. From Ohloh's perspective, this is equivalent to creating a new branch called erp5/trunk.
On this repository, Ohloh measures only the erp5/trunk line, so all of the prior activity on the trunk/ERP5 line was ignored.
This isn't exactly a bug -- we do this on purpose. We fetch the Subversion log using the --stop-on-copy option. We do this because in Subversion it's delightfully easy to create a new branch of the code, so some projects have literally thousands of branches. The problem this creates for us is that each branch is potentially as large as the trunk itself, which makes our processing and storage requirements orders of magnitude larger. On our end, it's very hard to know which branches we are supposed to be following at each point in history. We had to make a hard decision to follow only the current trunk.
We may revisit this problem in the future, but for now storage and compute limitations require us to do this.
One option that might improve the report for this project would be to import the trunk/ERP5 development line in addition to the erp5/trunk line -- effectively treating these as two separate Subversion repositories. You'd then be able to see all of the older history. Be aware, however, that on Mar 24 2006, it's going to look as if everyone on the project deleted all of their code, and then someone else on the team (yo?) re-added all of that code.
