The casco project (https://www.ohloh.net/p/casco) hasn't been updated since april. Could someone check to see what's wrong? I also just added an enlistment for tdp4r (https://www.ohloh.net/p/tdp4r) ... [More] , but it failed during the history download. I assume it's because rubyforge's CVS servers are a bit flaky. Could someone restart it and keep an eye on that until it is imported? [Less]

Hm, I now noticed that the link actually got updated correctly. I did get the message, however (maybe I didn't notice the link got updated because the message was so prominent). I was doing two ... [More] things at the same time when I got this message. Possibly the "edit link" page was displaying the error flash from the "download logs" bit :) [Less]

Nobody registered himself as "manager' for the Chicken project yet, as can be seen at https://www.ohloh.net/p/chicken/managers For some reason it is now impossible to edit the links or access the ... [More] download logs. When I try to do so, I get redirected to a login prompt telling me that in order to do those things, I have to be a manager for project Chicken. However, before the managers feature got integrated, it was possible to edit the links. Now we're stuck with an outdated link and nobody can edit it! (unless they sign up for "manager" but I'm not willing to do that as I'm not even an active contributor to the project itself, and none of the core hackers have Ohloh accounts) [Less]

A better workaround for Subversion is to make the 3rd party code an svn external. Last time I checked, Ohloh doesn't traverse externals. You can do this by adding the 3rd party code outside the ... [More] regular code tree, for example at /3rdparty instead of /trunk/3rdparty and make /trunk/3rdparty an external pointing to /3rdparty. [Less]

My colleagues and I think it would be really cool if it was possible to have "company" profiles in addition to "developer" profiles we have now. Currently it's already possible for a developer to ... [More] indicate that he or she held a particular position in a project at a company. This is currently just a text string with the name of the company, but for this feature that would be an actual link to a company. This would be a great way for developers to assess potential new employers by their contributions to free software, just like Ohloh can already be used by employers to assess potential new employees by their contributions. [Less]

Congrats, guys! I hope SF will help Ohloh grow and become even more awesome!

The OP's problem doesn't seem to be fixed either; clicking on Limesurvey's "established codebase" factoid reveals that ohloh thinks its first commit is from 2006, not 2003 as would be correct ... [More] (according to the post, the project was 4 years old at the time, and the post is 2 years old). [Less]

Oh, by the way: the wmiirc-chicken, uri-generic and chicken-9p eggs exist only since release/3 and have been copied once to release/4. The intarweb and uri-common eggs only exist in release/4. I ... [More] believe all the others I listed have been around since either release 2 or have seen the copy from /projectname to release/2/projectname. For other people's eggs (yet to be added to ohloh), I'm not 100% sure they've all been nicely copied using svn copy, so it would be nice if there was a way to access the old directories using an explicit revision enlistment. [Less]

Well, I'm a pretty active contributor of extensions ("eggs") for the Chicken project. So far, I've created ohloh projects for the following (not all are affected by this problem, see below): ... [More] chicken-postgresql intarweb uri-common uri-generic imlib2-chicken epeg-chicken spiffy phoghorn wmiirc-chicken web-unity chicken-9p Now, Chicken's subversion repository has a pretty unusual layout where directories are copied for every major release, so that eggs for the previous release can still be maintained (each release's egg directory has a trunk, tags and branches). But there was also a large reorganisation a few years back when every egg (chicken extension library) was kept in the root of the repository. For illustration, we can look at one particularly bad example; the chicken-postgresql project. It was first moved from /postgresql to /release/2/postgresql, which was then copied to /release/3/postgresql and then all files in there were moved again into /release/3/postgresql/trunk and then this was copied to /release/4/postgresql/trunk I'm sure you'll agree this is a pretty horrible thing to enlist. I cannot manually get at two parts of this tree: The original /postgresql, and the /release/3/postgresql files before they were moved to /release/3/postgresql/trunk I had to enlist all three release entries to get Ohloh to properly "see" all 5 contributors, but now ohloh thinks the egg has three times the LOC count it should have (you can see huge jumps in the code graph). I'm not sure if it now sees the entire revision history, as there's no easy way to check this with Ohloh. You can also view its history from Trac here (using the 'postgresql.scm' file which is a constant throughout its entire history) [Less]

There was some talk about a new native subversion adapter that ought to be capable of doing this. What's the status on that? Losing years of commit history info isn't fun :(