I authored a number of changes in the kt-dms project. I'm listed in the commit log, but I'm unable to claim them. https://www.ohloh.net/p/kt-dms/commits/29743856 ... [More] https://www.ohloh.net/p/kt-dms/commits/29743855 https://www.ohloh.net/p/kt-dms/commits/29754605 https://www.ohloh.net/p/kt-dms/commits/92583768 https://www.ohloh.net/p/kt-dms/commits/29754551 https://www.ohloh.net/p/kt-dms/commits/92583712 https://www.ohloh.net/p/kt-dms/commits/92583699 https://www.ohloh.net/p/kt-dms/commits/29754539 [Less]

I get an HTTP 500 error on this page: https://www.ohloh.net/p/mostfit/similar_projects

Rock!

https://www.ohloh.net/p/FrozenHell has no description, enlistments are dead, and homepage doesn't work.

Right on. Thank you very much for the update. I don't know if this matters, but in May we converted our source repositories from svn to git. Let me know if you'd like any additional information.

Awesome, thank you!

Ah, thank you! I wasn't aware that Ohloh doesn't update the project fully until all enlistments successfully pass. I don't think we've migrated that code from svn to git, but I'll do that eventually and add the new git enlistments to ohloh.

We have a couple of committers on our project (mifos) that only commit on long-standing development branches which are periodically merged to the trunk. Is there some way to give them credit for their ... [More] work? We use Subversion. I'm afraid if I add the branches as enlistments, a bunch of bogus commits (those copied from the trunk) will be analyzed. Here's an example merge I performed: https://www.ohloh.net/p/mifos/commits/47127614 Notice how all I did was merge ugupta's commit from branches/unitTestImprovements, so I guess I am technically the committer, but he's really the author of that changeset. [Less]

Looks like the trunk is working now. The cheetah enlistment (the big next version of our software) split into two (a trunk and dev spikes), so I updated that as well.