Hi, it would be nice if you added all-time commit timeline for a person. That way it can be seen when a person had gaps in working on opensource projects ;) Currently only per-project per-person timeline can be seen. Thanks

It would seem that in such case it's ok to use it on Wikipedia. Correct?

Cheers, three months, guys ;) This project is having GPLv2 incorrectly detected http://www.ohloh.net/projects/10570 From what I can see, GPLv3 differs by a small number in the header -- v2=>v3, and ... [More] by replacement of FSF's address by an URL :) If you're only reading first few lines, well, that's where the problem probably lies. So, what are you waiting, guys? :) [Less]

It would be nice if it would be possible to search the forums. What I do on most forums is search for "posts made by " and then I see which threads in which I participated contain unread posts. And ... [More] apart from searching for posts made by me or someone else, it's generally nice to be able to search by keyword in order to avoid repeating. [Less]

Just a small thing: when I enlisted a code.google.com repo, it showed up as Google Code repository. While I could have enlisted other projects as sourceforge.net (which would, I'm sure, result in ... [More] showing up as Sourceforge repository) I have not. So, just a tiny thing: it might be good to add a label for sf.net, namely Sourceforge. [Less]

Here's my two Sourceforge: Has a time delay before project activation, but provides much more options. Also allows importing from a SVN dump which is interesting to you Google Code: Immediate ... [More] activation. Limit of creation of up to 3 projects per account for lifetime, however. Does not seem to have importing nor exporting of SVN. Online Wiki page editing (Wiki saving actually creates a commit in the repository.) So it's a matter of taste. It seems that GC is overall a bit faster; with SF.net's activation delay in addition to the service being just a bit slower you also get impression that it's sluggish, while in fact it's providing much more features. [Less]

Regarding the branching, LOC and commit problem. Why not add a possibility to add "secondary" repositories, which would not be counted in LOC, but would show up in commits?

It might be interesting to see the number of projects in queue before certain project gets updated (for example, on KDevelop's or Firefox's project page, a small line mentioning number of projects ... [More] that need to be updated before KDevelop or Firefox gets updated). And if/when that is done, perhaps a small graph of total number of projects in queue on all servers displayed through time ;) [Less]

Robin, are you sure you want to suggest that approach to people? That might generate a lot of traffic to Ohloh, especially if the script wants to update its data every day or two :) It would really ... [More] be much smarter if you'd generate the data at every night. It would be much less resource intensive against your service than the approach you suggested. And I'm sure that we can all agree that if the database is well organized (which I'm sure it is!) that should take about 20-30 min, and that's a pessimist view :) [Less]

Personally I would have nothing against ads, in fact, I support such a move since this kind of site is perfect for something like Google Ads.