Git Migration: where to host the master repository

John Ralls jralls at
Sun Aug 12 17:13:45 EDT 2012

On Aug 12, 2012, at 1:48 PM, Christian Stimming <christian at> wrote:

> Am Samstag, 11. August 2012, 14:36:18 schrieb Derek Atkins:
>> Geert Janssens <janssens-geert at> writes:
>>> On 11-08-12 12:48, Frank H. Ellenberger wrote:
>>>> Hoi,
>>>> Am 11.08.2012 12:17, schrieb Geert Janssens:
>>>>> I have created a wiki page to track the progress of our git
>>>>> migration.
>>>>> It currently lists the things I know that still have to be done.
>>>>> Please
>>>>> add to it if you know more or have fixed some items:
>>>>> Geert
>>>> Linked by ;-)
>>>> Frank
>>> Thanks :)
>> Any chance we could rename this "Git Migration" instead of "Github
>> Migration"?  I don't think we will ever full migrate fully to github.  I
>> just think it's a bad idea to let go of master.
> Actually this point is one where IMHO there is not a consensus about it. In my 
> opinion, we can very well migrate the master repository to github (or any 
> other git repo provider). I don't consider the risk of code corruption any 
> larger on a git repository other than one on, as git's checksum 
> prevents unnoticed code changes by design anyway. (That's different in SVN, 
> though, where the integrity of the server repository is much more vital than 
> for git.) 
> I remember you have always voiced very clearly you prefer to host the master 
> repository on a server that's controlled by one of the gnucash team. But 
> actually I think differently about this point and would prefer to host the 
> master repository somewhere that requires the least effort for us. IMHO that 
> does not have to be a server under our control.

I actually agree with Christian here, simply because while I appreciate Derek's efforts to maintain access, large hosting operations in large data centers like Github, Sourceforge, or even Gnome have better uptime than Derek's house.

John Ralls

More information about the gnucash-devel mailing list