Git Migration: where to host the master repository
warlord at MIT.EDU
Mon Aug 13 13:55:29 EDT 2012
Yawar Amin <yawar.amin at gmail.com> writes:
> On 2012-08-13, at 9:31, Derek Atkins <warlord at mit.edu> wrote:
>> We're still maintaining our server for email, wiki, build, docs, irc
>> logs, etc. So we're already doing system maintenance, and moving to
>> github doesn't really reduce the amount of configuration necessary. We
>> would just need to add the git support to our server, which should be
>> relatively straightforward.
> My suggestion is the following. Host the Git repos on code.gnucash.org
> and have them periodically pull from GitHub and build. Treat these as
> the canonical repos. Only a few people need have direct commit access
> to it.
> Let the GitHub repos be the main point of activity. Discourage pull
> requests and GitHub commit comments, and encourage BugZilla
> use. GnuCash-core members can have write access.
Just to be clear, I have no objection to making GitHub the main point of
random access and non-committer activity. If nothing else it would
reduce my bandwitdh consumption significantly ;) I consider that in the
same vein as us using sourceforge to distribute the release sources and
binaries -- it's a good way to distribute it. It also does make it
easier for users to join.
I just still feel that the master repo should be on code, and that the
committers should be able to push there. Then it can sync to github for
I suppose it could work in reverse, where the committers push to github
master and then code pulls from there, but I don't like that as much for
reasons that I'm still apparently not able to clearly explain.
But just to reiterate, I am NOT saying we should not use github. I'm
only saying that I feel the canonical repository should still live on
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord at MIT.EDU PGP key available
More information about the gnucash-devel