The "languages" graph for pkgsrc (the NetBSD packages collection) clearly shows that the most dominant language is Make. After Make there's shell scripts and only after that comes C (and that mostly ... [More] because of a few in-tree source packages files, and mostly because of patch files for C programs) So why does it say that it was mostly written in C? [Less]

Thanks for the quick responses and fixing the enlistment!

I'm confused: what does "svnsync" represent?

You're right, it was a temporary issue. Sorry for being so quick on the draw ;)

Hm, I now noticed that the link actually got updated correctly. I did get the message, however (maybe I didn't notice the link got updated because the message was so prominent). I was doing two ... [More] things at the same time when I got this message. Possibly the "edit link" page was displaying the error flash from the "download logs" bit :) [Less]

My colleagues and I think it would be really cool if it was possible to have "company" profiles in addition to "developer" profiles we have now. Currently it's already possible for a developer to ... [More] indicate that he or she held a particular position in a project at a company. This is currently just a text string with the name of the company, but for this feature that would be an actual link to a company. This would be a great way for developers to assess potential new employers by their contributions to free software, just like Ohloh can already be used by employers to assess potential new employees by their contributions. [Less]

Currently you have to edit a stack, remove the project and add it back to another stack. It would be nice if there were an quicker/easier way to rearrange your stacks. For example, next to 'remove ... [More] from stack', you could add a 'move to stack' dropdown. [Less]

For subversion projects, a simple way to accomplish this is making the path that should be excluded into an svn external. Ohloh does not check out svn externals. This external does not have to live ... [More] on some other server, you could just store it in a "3rdparty" directory just below root, ie at the same level where "trunk" is so that it does not get pulled in when trunk is pulled in. When developers make a checkout, they'll just get the sources like before. An added advantage is that you could make the path readonly for developers, and only writable for the automated user that builds the JavaDoc, to prevent people from accidentally checking in modified docs. [Less]