Question on integration of hg with kforge

[Thomas Arendsen Hein]

* Neal Becker <ndbecker2 at gmail.com> [20070117 17:30]:
> Neal Becker wrote:
> I have asked Rufus Pollock <rufus.pollock at okfn.org>, the author of kforge,
> about integration of hg with kforge.  It brings up the interesting question
> of, How should a system like kforge be integrated with a distributed VCS? 
> I don't know much about kforge (yet), but I believe it is something
> like 'trac'.

Or something like gforge which is based on the code which runs sourceforge.

> Rufus Pollock <rufus.pollock at okfn.org> writes:
> PS: in another email you were talking about support for hg repositories. 
> I have to say I hadn't looked at hg much until you mentioned it. As I 
> understand it is a decentralized VCS. As I understand it (and I don't 
> know a lot about these types of VCS) everyone has their own repository. 
> If that how does the access control/project membership stuff provided by 
> KForge help you out? Pardon my ignorance here but I'd be very interested 
> to know -- and it would obviously provide some motivation for 
> implementing that support.

While it is easy to setup a public hg repository, you still need a
server to host it. And projects still want a central repository,
despite developers having additional repositories available.

kforge and similar systems allow people with hosting capabilities to
delegate creating project pages, managing user accounts, ssh keys,
issue trackers and the central SCM instance to the (public or
project-internal) community. Otherwise these people will always be
busy doing things that the kforge-hosted project admins could do.

Or in short: Projects usually want (at least) one official repository.
Having this (central) repository managed by the project leaders
instead of the system admins is a huge plus.

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/