sigh. darcs? mercurial? Is it really that hard?
We've got 2 exciting announcements regarding Google Code and Ohloh.
Firstly, as announced on Google Code's Blog, you can now embed Gadgets in your Google Code Wiki - and, more specifically, Ohloh Widgets. Ohloh Widgets are a great way to enhance your project community. Here's some gadget examples for CakePHP:
Development StatsCommunity |
Code Calculator |
We even have some gadgets to enhance your own developer profile (here's an example of Linus Torvalds):
Find or Add your Ohloh project page. Then, follow the "Widgets" link in the "General" sidebar section. From there you can pick which gadget you'd like.
Secondly, we're happy to announce a long overdue change to Ohloh's project coverage. We're enhancing our community's contributions with an automated crawler to help keep Ohloh up-to-date with the world's open source projects. We've naturally kicked off this effort by indexing Google Code's extensive list of open source projects.
Our indexer works in tandem with our community - and only serves to augment the community's input - not replace it. Feel free to contact us if you'd like more info.
I agree with splitbrain. You wanted to do software metrics after all, and given that there are so many converters between the repo formats, I don't understand anymore why new VCS'es seem to be way down your list.
I agree with splitbrain and Torsten. If I read correctly on other forums, one of the Google SOC students was able to put together Mercurial support ... it just had to be implemented? (I may be mistaken ..)
I really wish all of my projects could be tracked because employers are starting to use Ohloh stats as a metric to judge applicants. Right now, I have only 35 commits tracked.
Hopefully, support for HG is coming soon.. its not like Mercurial is some unknown DVCS, its widely used and very popular.
I'm glad to see things picking up for Ohloh .. I just really wish my stuff could be tracked because (due to your popularity) you have become an authority.
Well, it’s possible to work around it. For instance, I set up a cvs pserver and a git dæmon just for ohlol, and symlinked the anoncvs/anonrsync-over-ssh repo into the pserver and used hg-to-git.py for mcabber et al.
While I’d quite like them to support other methods (cvs using :ext: with ssh, cvs direct comma-v file parsing obtained via rsyncd or rsync-over-ssh, hg, …) this is a workaround until they get to it.
I bet none of you will pay for the manpower and servers needed to support them right now, will you?
Thorsten, I didn't ask for additional manpower but for other priorities. This blog entry shows that they actually do new things. I just wonder why these things are so ... well ... superficial.