Login Required. Sign up now -- its free!

Stats incorrect for project "Mime Type Detection Utility"

Avatar

nlmarco

11 months ago

Hello *,

today, I added an enlistment for the project Mime Type Detection Utility. Since the project was directly in the root of the SVN repository and we're now needing branches, I created a "trunk" folder and moved the project there. Thus, the source code history is now 1 day long (instead of 2 years) and all the code is listed as being mine (even though it's not much code, it should be assigned to the right contributors).

In order to solve this problem, I deleted the enlistment https://mime-util.svn.sourceforge.net/svnroot/mime-util/trunk and wanted to add the base URL https://mime-util.svn.sourceforge.net/svnroot/mime-util.

This, however, didn't work. Whenever I tried to re-add the enlistment, ohloh.net added the URL with "trunk"-suffix (even though I specified another URL).

After my last try, it even automatically added "MimeUtil" (i.e. a sub-project under "trunk") instead of the "trunk" base URL.

Is there a way to get the old repository information, which was https://mime-util.svn.sourceforge.net/svnroot/mime-util/MimeUtil into ohloh.net together with the current and future information from https://mime-util.svn.sourceforge.net/svnroot/mime-util/trunk (all subdirectories - not only "MimeUtil")?

Best regards, Marco :-)

Avatar

Robin Luckey

11 months ago

Hi Marco,

You're being caught between two different Ohloh design limitations. It takes a bit of explaining.

Ohloh's importer is not "branch aware". To us, the entire Subversion tree just looks like one giant mass of code, with no branch relationships. Worse, if you enlist Ohloh in a particular subdirectory, then Ohloh is unable to track any activity outside of that directory, or any activity that occured before that directory was created.

When you create the new /trunk directory and move all the code there, as you found out, Ohloh can't follow that.

So you did the "correct" thing: you tried to change the enlistment to the Subversion root, so that our report would include not just the new trunk but everything else as well.

However, here's the problem with that. Because Ohloh doesn't know about branching, each new branch just looks like a lot of new code. If you have 3 branches, your total line counts will come out 3x too high. Some developers use tags to label their daily builds -- and this can lead to literally billions of lines of code for us to count.

To prevent this very common situation, Ohloh has some internal logic that tries to locate the trunk and import only the trunk. That is what makes it impossible for you to import the root of the Subversion repository.

I can manually work around this, and add an enlistment to the Subversion root. However, be aware that each branch will multiply the line counts of our report, and additionally, if your project uses many branches or tags, it might become a real performance issue for our servers.

If this is acceptable, let me know and I'll make the change.

Thanks, Robin

Avatar

nlmarco

11 months ago

Hi Robin,

thanks a lot for the elaborate response. It would be really cool, if you could replace the current enlistment by the SVN root. I doubt that it will cause significant load to your servers, because the whole library currently has less than 2000 lines of code ;-)

We're at the moment doing some major refactorings and therefore might need a branch (we didn't create it yet - still working on trunk). If we temporarily need a branch, we'll very likely delete this work-in-progress branch when the refactorings are done.

If we find out later, that branches are regularly used, we can still delete the current root-enlistment and register trunk instead. Till then trunk is aged and the project doesn't look as if it was created yesterday ;-) Additionally, till then ohloh.net will probably have become more mature and likely the current issues have been fixed...

Best regards, Marco :-)

Avatar

Robin Luckey

11 months ago

OK Marco, I've added an enlistment the root and removed the existing enlistment.

I'll keep an eye on it to make sure it goes through. When it's done, let me know if something seems out of place.

Thanks, Robin

Post a Response