Forums : Feedback Forum

While I understand that the current focus of Ohloh is on providing per-project metrics, I think many of us would love to see global statistics, similar to those published in your blog post on PHP vs. Rails. This would be the killer-feature for Ohloh, something that would set it apart from existing tools to measure code statistics.

A few random ideas that should be easy to implement:

• top n projects by number of developers
• top n projects by codebase size
• top n projects by codebase longevity
• top n projects by commit frequency
• top n projects by documentation/code ratio;
• top n projects by stack size;
• distribution of projects in the Ohloh base, following the above criteria;
• top projects as above categorized by programming language;
• top projects as above categorized by tag;

The latter could be particularly useful to compare competing projects within the same segment (blog engines, forum engines, wikis, feed readers etc.). Coupled with an API to export these data, global statistics may be a tremendous selling point: many projects may reference Ohloh's stats to show they are in the top ten in their category. This would also put a lot of pressure on projects to be tracked by Ohloh.

dartar almost 18 years ago

HI dartar,

I love these suggestions! We've been thinking similar thoughts recently. In fact, we're close to releasing an interactive language browser.

As for your specific suggestions, the data you are asking for is easy for us to generate. The biggest challenge is getting the UI right. We'll probably start by enabling sorting and filtering on the project listing. However we'd love to have a better project browsing interface than just a boring list.

We're big fans of data visualization and are on a lookout for something more informative and interactive (shades of the digg visualization tools). Any ideas?

Jason Allen almost 18 years ago

Hi Jason, I was not familiar with Digg labs, amazing! As you pointed out in another thread, though, Ohloh is not about real-time activity, which seems to be the main strength behind the Digg visualization tools. It would be great to see projects grow in real time, Digg-style, but I understand this is not Ohloh's priority.

Options for filtering the big project table is a good idea: even if you think it's boring, this makes data accessible to users who don't like or can't use Flash.

I must confess I don't really see the added value of interactivity to display static data, unless it's a very large dataset, in which case some interactivity may help exploring the dataset at different scales, or unless you give users the possibility to generate custom reports on the fly, by toggling specific metrics and filtering the kind of projects to be displayed in the graph. In this case, I think the flexibility offered by Flash-based graphs could be interesting.

My 2 cents

dartar almost 18 years ago

Hello

I'd like to know if an API has been developed about this. I'm not only interested in language statistics, but also in all MIME-type that appear in the commits. I have in mind a project more or less inspired by code_swarm, hence it would be important to know what are the more frequent file extensions. In fact, an API is not mandatory, an HTML page generated automatically everyday or something would be sufficient.

Thanks.

Committo Ergo Sum almost 15 years ago

Hello, I'm doing an analysis of a FOSS project, specifically Sakai.
I've been running sloccount to review the project Sakai (core), and the number of lines of code I get is 791,792. Ohloh.net According to statistics of the number of lines exceeds 2 million.

The sloccount I applied to:
Trunk (latest development):
https: / / source.sakaiproject.org / svn / sakai / trunk.

Someone could explain to me that this difference in the number of lines of code?

Thank you.

Nana46 almost 15 years ago

Hi Nana46,

I'm not surprised that our number is much higher, because Ohloh is counting much more than just https://source.sakaiproject.org/svn/sakai/trunk.

We are computing the total lines for a large collection of specific Subversion directories, including /sakai/trunk. You can see the complete list here.

If this list of Subversion directories is incorrect, feel free to add or remove Subversion URLs as appropriate.

If you like, you can download the source code for our line counter Ohcount and compare its results to sloccount.

Let me know if you have more questions,

Robin

Robin Luckey almost 15 years ago

Hi Robin, thanks for the reply. If I have more questions and I will make you know. Again, thank you very much.

Nana46 almost 15 years ago