Forums : Posts

Hi Armin, Yes, our report for pygments is incorrect. I've scheduled a new report with a fix. This should be ready in an hour or two. Thanks for pointing out the problem, Robin

Hi ted, I've removed the duplicate project 3264, and I corrected the report on project 18 to be the latest information. All of the ratings and stacks and such have been moved over to project 18. ... [More] You're not the first to requests a duplicate-detection feature, and when time allows we'll probably try to implement one. For now, we're cleaning them up manually, and so far it hasn't been too much of an issue. Thanks for finding this and letting us know, Robin [Less]

Any update on widgets? I thought we would see other JSON widgets soon, e.g. the code history graphs or the contributor commit graph as in http://www.ohloh.net/projects/45/analyses/latest/contributors.

I second this proposal. What I miss in Ohloh is data about the distribution of specific metrics (LOC, average commits by year, comment/code ratio etc.) across all projects currently in the Ohloh DB. ... [More] That would make factoids such as this is one of the most actively developed project much more significant. [Less]

For reference, somone noticed there were some errors in the log about svnserve respawning too fast from inetd and so svnserve being temporarily disabled; I upped the limit in inetd (the default was 40 ... [More] spawns every 60 seconds) and ohloh seems to have grabbed the rest in one go. Perhaps this was the cause of the problems, if you're opening a new connection for each revision - just noting it because I notice there are some other forum posts discussing similar issues and perhaps ohloh might try slowing down a little or people could perhaps try making the same change server-side if running from inetd. :) [Less]

What about differentiation between 'the projects codebase is expanding' (commits that add stuff) and 'the projects codebase is maturing/getting refactored' (its not growing a lot, but its changing). I ... [More] think the only fact that would be worth warning is a project with no commit for a year. If the commit ration is linearily decreasing over time, than a weak warning might be also okay. Too bad that bugtrackers have no standart API, because having a bugtracker with bugs filed, but no activity is also a good indicator for a dead project. [Less]

Hi jjstwerff, In the near future, we are planning to add a feature that would allow you to specifiy ignored files or directories in your project. For now, I don't know if there is a good workaround ... [More] for you. Ohloh will count everything it finds, even if that code is auto-generated. [Less]

Hi MikaIH, Assuming the repositories are exactly the same, only the URLs have changed, then I can easily rename our existing downloads for the new URL. I'll make the change and schedule new updates ... [More] for these projects. Thanks for the heads-up, Robin [Less]

Hi nasheet, iTextSharp is a SourceForge project. You can get the latest source code from http://downloads.sourceforge.net/itextsharp/itextsharp-4.0.3.zip

Hi dannii, Anything is possible, but after spending some time thinking about this problem I can't see a simple way for us to do this. Our current parser works by comparing two complete files. ... [More] Attempting to parse an XML patch set, identify the languages used from small or non-existent code fragments, and to determine the resulting changes when we we don't have the original target source files could lead to some real head-scratchers. In time, we could revisit this question if there is demand from the community. [Less]