Proposals/feedback for a distributed version control system for cutecash?

[John Ralls]

On Apr 6, 2010, at 7:52 AM, Derek Atkins wrote:

> Christian Stimming <stimming at tuhh.de> writes:
> 
>>> I think it's reasonable to think about migrating from SVN to git, but I
>>> would want us going in with eyes wide open:
>>> 
>>> 1) WHY are we changing from SVN to a distributed VCS?
>> 
>> My main reason: To make it easier for new contributors to contribute their 
>> changes to a public place. With SVN they could send patches or attach them to 
>> bugzilla, both which tend to be outdated quickly and get forgotten. With git, 
>> they can either fork the whole repo (like on github.com) and push their 
>> proposals there, or push to a personal branch in the main repo. In both cases 
>> git takes care of most of the merging action, so it will be way easier to 
>> merge their changes back in.
> 
> Are you proposing we use github as our main repo?  So we no longer use
> code.gnucash.org to hold our code?  If not, then maybe you could help me
> understand how we can securely allow random people to create git
> branches on our server.

No, we can have it both ways. The master repo can remain at gnucash.org, but because of the distributed nature of git, others can publicly share their work on Github or Gitorious. A developer with write privileges on gnucash.org can easily make a local branch on his local repo, pull in the changesets from the unprivileged contributor, test, cherry-pick back into his master branch, and push to the master repo. It's much easier than passing patch files around, especially for large changesets.

Regards,
John Ralls