[Biopython-dev] Moving from CVS to git

Peter biopython at maubp.freeserve.co.uk
Mon Aug 17 12:43:01 UTC 2009


Hi all,

Now that Biopython 1.51 is out (thanks Brad), we should
discuss finally moving from CVS to git. This was something
we talked about at BOSC/ISMB 2009, but not everyone was
there. We have two main options:

(a) Move from CVS (on the OBF servers) to github. All our
developers will need to get github accounts, and be added
as "collaborators" to the existing github repository. I would
want a mechanism in place to backup the repository to the
OBF servers (Bartek already has something that should
work).

(b) Move from CVS to git (on the OBF servers). All our
developers can continue to use their existing OBF accounts.
Bartek's existing scripts could be modified to push the
updates from this OBF git repository onto github.

In either case, there will be some "plumbing" work required,
for example I'd like to continue to offer a recent source code
dump at http://biopython.open-bio.org/SRC/biopython/ etc.

Given we don't really seem to have the expertise "in house"
to run an OBF git server ourselves right now, option (a) is
simplest, and as I recall those of us at BOSC where OK
with this plan.

Assuming we go down this route (CVS to github), everyone
with an existing CVS account should setup a github account
if they want to continue to have commit access (e.g. Frank,
Iddo). I would suggest that initially you get used to working
with git and github BEFORE trying anything directly on what
would be the "official" repository. It took me a while and I'm
still learning ;)

Is this agreeable? Are there any other suggestions?

[Once this is settled, we can talk about things like merge
requests and if they should be accompanied by a Bugzilla
ticket or not.]

Peter



More information about the Biopython-dev mailing list