it's there http://www.ohloh.net/projects/3926

Any feedback on this?

Hi there, thanks for your reply. I believe we may be able to detect dependencies automatically using our source code analysis tools I had this feeling but didn't dare ask :) Automatically ... [More] detecting dependencies/bundled libraries sounds like the right way to go, I'm looking forward to this! how would you feel if I added a dropdown that let people choose between: 1. I used this as an application. 2. I coded against its API Sounds sensible and I now understand better what your intention was when you introduced this feature. [Less]

+1 for this proposal

FYI CIA lets developers specify a URL scheme to a browsable version of the repository, you may want to take a look at how they do this.

I second this suggestion.

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]

jason, to me this feature (post-commit update triggers) only makes sense if the average update rate is too slow for very active projects and too fast for lazy projects. Ideally Ohloh may not want to ... [More] download every day a huge codebase for a project that has only one or two commits a year, at the cost of slowing down updates of smaller and more active projects. If your hardware upgrade allows daily updates for any project, this feature request becomes somewhat irrelevant. [Less]

It'd be great if the most recent figures approximatively displayed in the codebase history graph (code, comments, blank) were made explicit, e.g. code.............2123 lines.....64.5% ... [More] comments.....1032 lines.....31.3% blank..............134 lines.....4.2 % this would be especially useful to understand how specific projects position themselves with respect to the reference values Ohloh uses to establish factoids. For example: projects are marked as well documented if their comment/code ratio (N%) is above the average (M%) for that language category. At the moment, though, there is no way to know the comment/code ratio for projects not highlighted through factoids. [Less]