[Biopython-dev] biopython on github

[Peter]

On Sat, Mar 21, 2009 at 5:33 AM, Michiel de Hoon <mjldehoon at yahoo.com> wrote:
> I haven't been following this topic closely, and as an
> "outsider" using git seems more complicated than using
> cvs or svn. And to be honest, I don't know if Biopython
> actually needs the branching and forking stuff. I think
> that this is more useful for bigger projects, where
> multiple developers may be working on interrelated
> parts of code at the same time. That hardly ever
> happens in Biopython, though.

Certainly git and github is much more powerful, and
therefore more complicated.  There is no denying that.

However, if we move to git on github, I would expect
those of us with CVS access to all be given write
access to the official Biopython branch (probably
using the collaborators feature).  If that is done, I
think you won't find things so different from now.
i.e. Initially at least, it would be business as usual -
our core official developers would be trusted to work
directly on the main branch as now (with discussions
before commits as appropriate), and do not have to
worry about forking/branching etc (unless they want
to).

In terms of the actual command(s) you'd have to type
in at the terminal to commit a change to the online
repository, this goes from one step:

cvs commit -m "Comment here" file1.py file2.py

... to two steps.  First you you have to commit changes
locally (to git on your personal machine) and then
push them to the main Biopython branch on public
server (on github).  Once I'm back at work where I
have git installed, I'll write this up on the wiki -
assuming Brad doesn't beat me too it ;)

The big change is for non-core developers, i.e.
potential contributors (like Eric who is currently trying
some Bio.PDB changes).  For them, using git allows
them to work on their changes and keep in sync with
the master repository with much more ease.

Peter