All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>, Jeff King <peff@peff.net>,
	Junio C Hamano <gitster@pobox.com>,
	Shawn Pearce <spearce@spearce.org>
Subject: Re: The GitTogether
Date: Fri, 27 Jul 2012 13:45:20 +0200	[thread overview]
Message-ID: <87k3xpe8bz.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CAP2yMaJzJyw=9DqJzUXkkQjz_jcqB4pH=FfHFRiftC9=yC7dvg@mail.gmail.com> (Scott Chacon's message of "Thu, 26 Jul 2012 15:28:00 -0700")

Scott Chacon <schacon@gmail.com> writes:

> GitHub would like to volunteer to organize and pay for these events
> this year.  I would like to hold the developer-centric one in Berlin
> in early October

Yay, Berlin!  I would be glad to join there; I would probably not have
the time and resources to travel to SF this year.

> For those of you who *have* been to a GitTogether, what did you find
> useful and/or useless about it?  What did you get out of it and would
> like to see again?  For those of you who have never been, what do you
> think would be useful?  I was thinking for both of them to have a
> combination of short prepared talks, lightning/unconference style
> talks and general discussion / breakout sessions.

I was at the 2010 GitTogether in Mountain View.  I really liked the
unconference format, and the way Shawn and Junio used it: just using the
topic stickers as a sort of todo-list, not actually fixing any schedule
in advance.  Oddly enough we also managed to avoid the usual consequence
of open-ended discussions: getting stuck endlessly on an absolutely
insignificant point.

I think the discussions were very productive.  I would love to do more
hacking than we managed in 2010, but I realize that this is not possible
if we just meet for 2-3 days.  Perhaps one option would be to plan for
1-2 days of hacking after the discussion rounds, so that the interested
people can stay a bit longer?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  parent reply	other threads:[~2012-07-27 11:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 22:28 The GitTogether Scott Chacon
2012-07-27  6:12 ` Heiko Voigt
2012-07-27 11:45 ` Thomas Rast [this message]
2012-07-29 15:55   ` Jens Lehmann
2012-07-30 13:17     ` Michael J Gruber
2012-08-09 16:38       ` Michael J Gruber
2012-08-10 14:42         ` Patrick Renaud
2012-08-10 16:30           ` Junio C Hamano
2012-09-19 13:43 ` Michael Haggerty
2012-09-20 18:53   ` Sebastian Schuberth
2012-09-21  9:20     ` Christian Couder
2012-09-21 14:05       ` Shawn Pearce
2012-09-21 14:18         ` Jeff King
2012-09-21 15:23         ` Christian Couder
2012-09-21 16:43           ` Patrick Renaud
2012-09-21 16:45             ` Scott Chacon
2012-09-21 16:55               ` Patrick Renaud
2012-09-21 16:57                 ` Luca Milanesio
2012-09-21 14:19       ` Scott Chacon
2012-09-21 14:33         ` Sebastian Schuberth
2012-09-22 10:12           ` Michael J Gruber
2012-09-22 10:45             ` Sebastian Schuberth
2012-09-22 18:09             ` Enrico Weigelt

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

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

  git send-email \
    --in-reply-to=87k3xpe8bz.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=schacon@gmail.com \
    --cc=spearce@spearce.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.