[VTK ARB] Git

[Berk Geveci]

I have been reading about Git and Mercurial and I now think that which
one we use on the server side is not relevant to what people use on
their local machines. You can clone a Git repository using Mercurial
and you can commit change to a Git repository from Mercurial. As for
the Github issues, we would not use Github. We would run our own
Gitorious server since Gitorious itself is open-source. We could also
push repos to Github if we wanted to.

I was pushing for considering Mercurial as well as Git as an option
but I am now all for Git (on the server side). The main reason is that
there is not equivalent of Gitorious for  Mercurial. The code behind
bitbucket is not open-source. There is a particular and wonderful
use-case that Git+Gitorious would enable: running a continuous
dashboard before accepting any change to the central repo. Here is how
it would work:

* Developer makes changes and pushes them to his/her VTK fork on Gitorious
* User makes a "pull request" on Gitorious. This means : "I want these
changes on a certain branch of the official repo". This request is
automatically put on a queue
* The "repo robot" pulls the next request from the queue, tests the
changes and if the dashboard passes, it merges these changes to the
official repo. If the dashboard fails, the developer gets an e-mail
and changes are not merged.

This is a very short description of the sort of thing Git+Gitorious
would allow us to do and I think it's fantastic. It would allow us to
do have green(er) dashboards and it would allow us to collaborate with
groups that do not have write access to the repo. (This is all Bill
Hoffman's idea by the way). There is no clean way of doing this with
SVN. So a very enthusiastic two-thumbs-up to Git from me. And as I
mentioned, you can still use Mercurial on your machine.

-berk

On Mon, Nov 2, 2009 at 4:32 PM, Wylie, Brian <bnwylie at sandia.gov> wrote:
> Hi All,
>
>
>
> Sorry to come in late on the Git topic (I’ve been out of the country for a
> few weeks).
>
>
>
> Sandia has a few fans of mercurial, and I haven’t seen it mentioned at all.
> Sandia has quite a few active VTK developers (about 1/3 on windows), so we
> would like to see those people supported by whatever decision gets made.
> Also we’re having “issues” with github, we are currently tracking these down
> but are having a much more positive experience with bitbucket (equiv site
> for mercurial).
>
>
>
> Here’s a link that folks may already know about done by the folks at Google
> code. One thing to note here is that  HTTP transport will be critically
> important to “lab folks” who have firewall issues (mercurial seems to be
> better in this regard, although I’m sure git is worked on this…)
>
>
>
> http://code.google.com/p/support/wiki/DVCSAnalysis
>
>
>
> http://kerneltrap.org/mailarchive/git/2008/8/3/2795094/thread (http post)
>
>
>
>
>
>   Brian Wylie - Org 1424
>
>   Sandia National Laboratories
>
>   MS 1323 - Building CSRI/242
>
>   (505)844-2238 FAX(505)284-2518
>
>        _______ __
>
>       /_  __(_) /_____ _____
>
>        / / / / __/ __ `/ __ \
>
>       / / / / /_/ /_/ / / / /
>
>      /_/ /_/\__/\__,_/_/ /_/
>
>             Informatics Toolkit
>
>
>
> From: arb-bounces at vtk.org [mailto:arb-bounces at vtk.org] On Behalf Of Will
> Schroeder
> Sent: Thursday, October 22, 2009 6:53 AM
> To: arb at vtk.org
> Subject: [VTK ARB] Next meeting
>
>
>
> I'd like to schedule the next VTK ARB meeting. I propose 10:00am on November
> 3 ET. Again this is a hardship on Andrew and some of the mountain time
> folks, but I think it's a reasonable compromise (eventually Andrew's
> mounting good karma is going to allow him to specify a more convenient time
> for himself :-)).
>
> Here are the proposed topics:
>
> + Compiler support
> + Documentation / feedback (uservoice, InsightJournal) update and next steps
> + Development process (continuing discussions) Git / SVN
>
> Berk is in the middle of setting up UserVoice and it should be done by the
> next meeting, so we will have accomplished something :-)
>
> The agenda may appear sparse, but remember we are aiming to pick one topic
> that can be decided and executed (compilers) in combination with meatier
> issues; as well as keeping the meeting less than an hour in length.
>
> If you want a head start on these topics, the ARB email list is ready to
> accommodate you :-)
>
> Will
>
> --
> William J. Schroeder, PhD
> Kitware, Inc.
> 28 Corporate Drive
> Clifton Park, NY 12065
> will.schroeder at kitware.com
> http://www.kitware.com
> (518) 881-4902
>
>
> _______________________________________________
> Arb mailing list
> Arb at vtk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/arb
>
>