[caudium-devel] Re: how about redmine?

[bertrand.lupart AT linkeo.com (Bertrand LUPART)]

> > > - CVS over SSH is pain in the ass in term of security... if you have
> > > hww AT cvs,
> > >  the you have to run a different ssh server to handle CVS and
> > > local accounts...
> > Seems that svn is much powerfull on this aspect. 
> not really. should be the same mess unless you want to use apache and
> http or maybe webdav (not sure about that) for access.

If you use apache, you can have a different user database (but i'm only
using svn+ssh).

I using svn+ssh, you have the same problem than cvs.

> > We'll have a look at git in Copenhagen too.
> 
> git provides a git-shell kind of thing that can be used for restricted
> ssh access. (ie users that have a git-shell configured can only access
> git)

I guess you can configure sshd to do the same with cvs and svn.

> another nice thing about git is that it can send commits by mail, and
> has tools to automaticly create commit-emails and apply such commits.
> that would make it easy for anyone to supply proper patches. (because
> git generates the mail on the contributors end, and applies the mail on
> the maintainers end, so there is no messing around with manual work.)
> 
> git also provides a (i think read only) cvs server and can be made
> available via http for read-only access.
> 
> and, just in case anyone wonders, it is possible to use git in a
> centralized fashion like you'd do with cvs or svn, without needing to
> know more commands. 
> 
> cvs checkout -> git clone (initial checkout)
>                 git checkout (to get a different branch)
> cvs update -> git pull
> cvs add -> git add
> cvs commit -> git commit -a; git push
> cvs diff -> git diff
> (of these only clone, pull and push go over the network)
> 
> but git has a wealth of commands that go beyond that and allow you to do
> things that cvs or svn users can only dream of.

Is there an official move to git planned for some of our project?

-- 
Bertrand