[Biopython-dev] Moving from CVS to git

[Peter]

On Wed, Aug 19, 2009 at 10:45 AM, Bartek
Wilczynski<bartek at rezolwenta.eu.org> wrote:
>> Sure. Right now I don't think anyone at Biopython knows exactly
>> what would be involved in running a gitserver, and it would take
>> some investment of time to get to that point.
>
> I think there is some grave misunderstanding here.

You have certainly clarified a few things for me ;)

> There is nothing magical or difficult in installing git on OBF
> servers. It's  just a package. There is no effort to be spearheaded
> by anyone. The command "yum install git" needs to be run by
> someone with root privileges. That's it. It's absolutely enough
> to allow people with obf developer accounts to use git for
> development.

Oh. That is less complicated than I realised - assuming all the
existing dev accounts have SSH access.

> As for running a git-protocol-server, this is a bit more complicated
> and can be done in many more ways than with CVS. I don't think
> that anyone is expecting OBF to provide git repository hosting in
> a standardized way (currently only BioRuby uses git and they
> seem to be fine with github, similar for biopython)
>
> The importance of having git installed on OBF machines comes
> from the fact that it can be useful for many things even if we don't
> host the repository on OBF servers.

I had been assuming we would also need the git-protocol-server,
and to mess about with the firewall and perhaps webserver, but
if I understand you correctly even *just* the core git tool running
on the OBF would be useful (even if just for backups). So let's try
and do that...

> ...
> To summarize, I think that the only thing we really need from OBF is
> to have git installed

Any of the OBF server admins should be able to install the git
*package* for us (this should be trivial as long as the Linux OS
is fairly up to date). We should probably ask via a support
request on on the root-l mailing list... let's just give Hilmar a
chance to reply first.

Peter