See https://www.ohloh.net/p/httplib2/enlistments. It worked wonderfully for couchdb-python, which is also hg-on-gcode, so I'm not sure why this fails.

So, it was pointed out to me that this wasn't entirely coherent. An attempt to clarify: when Ohloh makes the value judgement of e.g. "Very large, active development team" or not, it should take into ... [More] account when classifying whether a DVCS is used or not (because that has a probably somewhat significant effect on the active developer estimate). [Less]

So I was wondering if the development team size metric should be adapted a bit for projects using a DVCS. Since DVCS usually keep the original author on the changeset (at least that's the case for ... [More] Mercurial, not sure what it looks like for git, where I understand they have different tag lines in the commit message), and centralized systems have to make do with the names of the ones pushing the changesets, it seems unfair that DVCS-using projects tend to get a larger amount of names for pretty much the same amount of developers. Wouldn't it be good if Ohloh fixed this up a little bit? [Less]

See https://www.ohloh.net/p/hgsubversion/enlistments.

Robin, that sounds great! Thanks for working on it. I'll be sure to donate something too, when that stuff appears. :)

Now that Mozilla has adopted Mercurial, it would certainly be nice if Ohloh supported it. What can I do to help? I'm a Mercurial developer and wouldn't mind spending some time working on a way to let ... [More] Ohloh pull Mercurial repos into whatever sort of format they want -- just contact me and we can discuss it. [Less]

So are you getting into reading Mercurial repositories now? Would be about time...

Well, I'd like to help accelerate Mercurial support. If you need any help, just contact me.