Perhaps this is a bit short-sighted of me, but it looks like we could actually make use of network shares to get to repositories on other machines. A “developers” share is already set up on our machines, and everybody knows how to get to it from project machines. If this is a viable solution, I wouldn’t need anything special to A) serve up a mercurial repo or ten or B) get IT to back it up, since they already take good care of our existing shares. This would totally eliminate the need to install copSSH or LightTPD, or train people on how to use them, or convince IT (both ours and our clients) that “yes, you really do want me to install this extra server.”

I like potential solutions that are actually easier than what we’re doing now.

That leaves the code review cases, where I have a changeset I want someone else to review, but it doesn’t belong in the “central” repo until after it’s passed.

Perhaps if everybody had a share set up as \\MyMachineName\hg that pointed to wherever their local repos were kept, that would simplify finding shares.

Progress! I love it!