From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Google Summer of Code 2012 Student Application Date: Fri, 06 Apr 2012 09:57:53 +0200 Message-ID: <87d37ljnr2.fsf@gnu.org> References: <87398i65e7.fsf@gnu.org> <87ehs2e3mf.fsf@gnu.org> <87limanvw5.fsf@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:56558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG42F-0000fF-6Y for emacs-orgmode@gnu.org; Fri, 06 Apr 2012 03:56:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SG42D-0002mw-Lk for emacs-orgmode@gnu.org; Fri, 06 Apr 2012 03:56:42 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:33260) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG42D-0002mo-CL for emacs-orgmode@gnu.org; Fri, 06 Apr 2012 03:56:41 -0400 Received: by werj55 with SMTP id j55so1658820wer.0 for ; Fri, 06 Apr 2012 00:56:39 -0700 (PDT) In-Reply-To: <87limanvw5.fsf@googlemail.com> (Thorsten's message of "Thu, 05 Apr 2012 15:36:10 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Thorsten Cc: emacs-orgmode@gnu.org Thorsten 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. We can also consider hosting a new git project on orgmode.org, if your needs are pretty basics. > 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. 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. HTH, -- Bastien