From a.janke at gmail.com  Thu Mar  8 15:48:33 2012
From: a.janke at gmail.com (Andrew Janke)
Date: Fri, 9 Mar 2012 06:48:33 +1000
Subject: [MINC-development] BIC-MNI organization on github
In-Reply-To: <4F58FAA6.2000300@ilmarin.info>
References: <4F58FAA6.2000300@ilmarin.info>
Message-ID: <CAG0CB238X-Cqpn+4FQ0md8y9b0V6FbeDTq3nBpQskCJEk3Fzbg@mail.gmail.com>

There is a way in github that you can transfer a repository (in the
admin page) so I have done this.

I have CC'd this to minc-dev so that others know. putting MINC in my
account was always a test, but the test seems to have worked well so
onwards and upwards from here.

I'll write a nice email to minc-users shortly.


a

On 9 March 2012 04:29, Vladimir S. FONOV <v.s.fonov at ilmarin.info> wrote:
> Hello Andrew,
>
> have you seen the all new https://github.com/BIC-MNI ?
>
> could you fork your repository of minc there ?
> --
> Best regards,
> ?Vladimir S. Fonov ~ v.s.fonov <at> ilmarin.info

From a.janke at gmail.com  Thu Mar  8 18:46:05 2012
From: a.janke at gmail.com (Andrew Janke)
Date: Fri, 9 Mar 2012 09:46:05 +1000
Subject: [MINC-development] BIC-MNI organization on github
In-Reply-To: <4F591D89.7020700@ilmarin.info>
References: <4F58FAA6.2000300@ilmarin.info>
	<CAG0CB238X-Cqpn+4FQ0md8y9b0V6FbeDTq3nBpQskCJEk3Fzbg@mail.gmail.com>
	<4F591D89.7020700@ilmarin.info>
Message-ID: <CAG0CB225hJSYXOTiFgW4er46jfDGedbBfn7fdySCC3CZ+z6+CQ@mail.gmail.com>

It would possibly make things cleaner.

Or at least it will make for a clean fork queue!


a

On 9 March 2012 06:58, Vladimir S. FONOV <v.s.fonov at ilmarin.info> wrote:
> So, should I delete forked repositories and transfer ownership instead?

From a.janke at gmail.com  Wed Mar 21 07:24:02 2012
From: a.janke at gmail.com (Andrew Janke)
Date: Wed, 21 Mar 2012 21:24:02 +1000
Subject: [MINC-development] New MINC world order.
Message-ID: <CAG0CB20B0iQymSatp2nZEEL4zDwVckJBdBPsyNEhMGknwHnYyA@mail.gmail.com>

Hi all,

Some of you will have noticed a bit of a flurry of activity on github
MINC as of late. Short version is on the prompting of Louis there have
been a few changes to MINC.

First is that given that the MINC github repository seemed to work
well we've made a BIC-MNI account and put MINC and in time all the
existing tools there:

   https://github.com/BIC-MNI

The plan is that over the next few weeks we'll also start to include
more and more in the base MINC package, this means that with many
developers it's now time to shift to a branching model with a master
and a develop branch. Meaning anyone who know commits to the master
branch better have a good reason! :) This link will give a good
introduction to what we are about:

  http://nvie.com/posts/a-successful-git-branching-model/

The develop branch is here:

  https://github.com/BIC-MNI/minc/tree/develop

The process by which a new release will be staged into master is still
not nailed down (as to who will do it), I am guessing myself.

So, by all means fork and clone away, ask either Vladimir or Myself if
you are interested in having commit privileges on the main tree or any
of the other packages.

Thanks


a