Re: [O] Google Summer of Code 2012 Student Application

[Thorsten]

Bastien <address@hidden> writes:

> Thorsten <address@hidden> writes:
>
>> What I really would need to decide upon at the very beginning is the git
>> workflow - not too complicated, but somehow scalable for the future is
>> the project succeeds. Any suggestion besides having a master and a
>> private branch? 
>
> Start with a git repo somewhere.
>
> Maybe prefer gitorious to github, GNU admins tend to be sensible
> to such nice little attentions.

Its all done on github now, I wasn't aware that gitorious is a GNU
project, it seemed everybody is on github. But github is terribly slow.
I have (free private 2GB) repos at assembla too, and pushing to
assembla is really fast, while pushes to github take quite some time
even if only a typo was changed. 

> We can also consider hosting a new git project on orgmode.org, 
> if your needs are pretty basics.

I think github and worg will suffice for code and docs, maybe with some
more private stuff on assembla.

>> Should I already consider a workflow similar to the one used by you
>> for Org-mode?
>
> I'd say no: start with only one public master branch (and small local
> branches when needed, of course), and change this workflow when needed.

Ok, I keep it simple then.

> If there are changes that need to be part of Org at some point, we will
> create a branch for you, just as we have feature branch right now.

at this simple level git seems to be really fun, while following your
discussions with regards to org/git & emacs/bzr clearly shows that it all
can end up in a nightmare of complexity ;)

Thanks for the tips

-- 
cheers,
Thorsten