Here is a list of packages I needed to install on hardy heron to run compile ohcount from version control: libpcre3-dev libpcrecpp0 ruby1.8 ruby1.8-dev libruby1.8-extras rubygems ruby-pkg-tools ... [More] svn-buildpackage Some other packages may have already been install from other stuff i was doing and some packages were pulled in by these, so it's not a complete list. The "-dev" endings are important, and you'll get obscure error messages if you don't install them... cheers stuart [Less]

It seems to me that there are a range of interesting possibilities for ranking projects that are being overlooked. The criteria for "interesting" here is (a) useful (b) showing off data that ohloh has ... [More] that isn't widely known. My suggestions for how to order projects include: number of committers in the last month; number of new committers in the last month combined kudos of committers average kudos of committers increase in kudos of committers in the last month oldest projects newest projects number of lifetime committers completeness of ohloh entry and newness (i.e. list only projects with complete ohloh entries, by newness, encouraging developers to fully complete their projects ohloh entry) While many of these look expensive to calculate (and are), they could easily be cached for hours or days, since these aren't (or shouldn't be) changing very fast. [Less]

Better presentation of languages data. Idea for better presentation of the graphics at: http://www.ohloh.net/languages (1) Don't normalise across the entire site, to prevent the current occurrence ... [More] of many graphs which are apparently flat lines at zero. (2) Provide the Code / Commets / Blanks as a pie graph. (3) Add a little white space on the graph so that volatile graphs (i.e. c++ commits) don't get truncated by the graph boundary (4) Rather than (or as well as?) the drop-down to sort at the top of the page, decorate the labels with little icons to sort by that metric. [Less]