emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten <quintfall@googlemail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Google Summer of Code 2012 Student Application
Date: Fri, 06 Apr 2012 11:40:37 +0200	[thread overview]
Message-ID: <871uo1nqp6.fsf@googlemail.com> (raw)
In-Reply-To: <87d37ljnr2.fsf@gnu.org> (Bastien's message of "Fri, 06 Apr 2012 09:57:53 +0200")

Bastien <bzg@gnu.org> writes:

> Thorsten <quintfall@googlemail.com> 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

  reply	other threads:[~2012-04-06  9:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  4:25 Google Summer of Code 2012 Student Application Andrew Young
2012-04-05  6:48 ` Bastien
2012-04-05  7:46   ` Torsten Wagner
2012-04-05  7:46   ` Torsten Wagner
2012-04-05 11:20     ` Andrew Young
2012-04-05 11:49   ` Andrew Young
2012-04-05 12:59     ` Bastien
2012-04-05 13:36       ` Thorsten
2012-04-05 14:07         ` Bastien
2012-04-06  7:57         ` Bastien
2012-04-06  9:40           ` Thorsten [this message]
2012-04-06 10:44         ` Andrew Young
2012-04-06  6:23     ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871uo1nqp6.fsf@googlemail.com \
    --to=quintfall@googlemail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).