+1 for ArneBab-like user.

I'm hoping for hg support too... Xen (which I work on) also uses Mercurial, as do a number of Linux kernel projects (those that don't use git typically use hg).

All of my personal projects are stored in Mercurial too, so I'm not really able to make much use of the statistics on Ohloh :-(

Of course, keeping the business going is important and I'm sure we wish you all the best.

+1 for hg support

Hm, funny. Everytime I get a mail about a new post in this thread I am deep in my heart hoping that there's finally support for mercurial. ;)

You're not the only one, Christoph. ;)

I always come here with hoje too ;)

I always hold high hopes while I scan the subscription mail for the text :)

Anyone interested in counting the number of votes Mercurial support already has? :)

46, but I might've missed a few.

I just hope they haven't forgotten us..

It looks like it will eventually happen .. when it does will hg repositories be imported like subversion, i.e. a few years worth of commit histories?

I've been using hg ever since Xen switched over from Bit Keeper, it would be great to get all commitments tracked. If not, no worries :) I'm just happy to see it eventually happen.

Ehm sorry, but I don't get the point?

We already know that Mercurial is superior to Subversion, that's why we would like to see support in Ohloh. ;)

But it's a bit sad that you still hadn't the time to look at Mercurial after a year of discussion..

What about the several offers of people in this thread that would like to help?

Hi Robin,

thanks for your reply again. The problem is the copyright of the code? Well, guess you don't have to show the whole code, just the svn importer should be enough to (hopefully) rebuild it for mercurial. ;)

For me I would even sign a NDA to get this support. ;)

Hi Robin - You would not have to go through all of those crazy steps in order to get the full history .. you'll get it the first time you clone a repository. You can then go back to the initial revision and work your way back to the tip. Mercurial is a little "heavy handed" if the diffs between revisions are huge .. but no more than Subversion. All in all, I think you'd find it easier to track :) Looking forward to it in months to come!

Then maybe I can add one reason, why Mercurial support could provide something for ohloh it doesn't yet have:

• Shared codeswarms

With it you can do things like "The weekly code_swarm of selected free software projects".

It's a current project of mine to visually track the development of different free software projects. I use Mercurial to easily aggregate code and to create the logfiles for the codeswarm.

It might be a bit too heavy in terms of CPU usage right now, but it could become a future feature once you get the funding stuff: An Ohloh livestream for the people who always want to track how their projects progress, seeing commits in almost realtime (i.e. depending of the update-cycle). It's a different kind of news, but quite addicting :)

Arg, a typo in the link!

shared codeswarms

Or perhaps, cannot it be hacked using tailor to convert to git and then analyze?

Oh.. When I got the mail I first thought it's time for the monthly mercurial reminder in the ohloh forum. ;)

Does anyone here use tailor/git-export-stuff to keep your project on ohloh in sync?

I worked with Ohloh during the Google summer of code and after completing my main project (rewriting Ohcount to use a faster parser), I submitted code for tracking Mercurial repositories. Obviously the devs just don't have the time to integrate it. (I don't blame them with the workloads they have.) It'll come when it does.

@Christoph,

I thought about tailor/etc however it seemed to be a little too much work and headache just to have stuff tracked.

1 - I would have people sending patches against both trees, which I really don't want to deal with.

2 - When hg support arrives, I'd have to switch everything over .. or continue to maintain two repos per project (I maintain 11+).

For me, the value of Ohloh is mostly ohcount (although the networking is cool). Since I can just ohcount -s myrepo.hg ... I'm quite content to wait :)

oh good grief sorry about the text .. I forgot about the markup :)

@mitchell: Cool! I hope we'll see it soon!

@tim: People send patches only for the mercurial tree, I use the git-export-stuff only to keep it in sync from time to time. ;)

@mitchell: Oh - that sounds promising!