Re: [Exist-development] DVCS - Distributed Version Control?

[Andrzej J. T. <an...@ch...>]

Adam:

> Mercurial sounds very interesting and SourceForge even have some
> support for it -
> 
> http://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial

Cool....I didn't know that sf had support for Mercurial. That's good to know.

> However, the biggest limitation in my mind is that write access to
> repository can only be achieved over SSH.
> 
> Before we moved to Subversion, CVS used to be a major pain in the ass
> for me, because I work from far too many locations (offices, airports,
> trains, cafes etc) where the only access out is HTTP, Subversion works
> perfectly over HTTP. If SourceForge were to enable Mercurial writes
> over HTTP then I might be sold on the idea ;-)

Yeah...that might be a problem with firewalls and the like blocking the standard SSH port 22.

I wonder if git suffers from the same issue.  Or maybe there are other hosting providers like sourceforge that support
Mercurial over plain HTTP?

Worse case, we could set up a relay/proxy that would expose HTTP and relay over SSH to sourceforge.

However, first we probably need to discuss the pros/cons of DVCS for the eXist project, timelines and then which DVCS to
use, who would host the repository and so forth....so it's a long path still before we would even get there.

I just figured it would be good to at least start a discussion on the topic and see what everyone thinks. ;-)

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com