From: Jeff King <peff@peff.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: Scott Chacon <schacon@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] GitTogether 2011 - Oct 24th/25th
Date: Wed, 7 Sep 2011 15:30:06 -0400 [thread overview]
Message-ID: <20110907193006.GB13364@sigill.intra.peff.net> (raw)
In-Reply-To: <CAJo=hJvm62xPAg3v5Ay3ec-ira-i_BZ0Ej7wfdg+5r2Ls0UJQg@mail.gmail.com>
On Wed, Sep 07, 2011 at 11:38:18AM -0700, Shawn O. Pearce wrote:
> As we approach 50 people, does it makes sense to be able to break the
> event down into 2 "tracks", and have 2 meeting spaces available? I
> know a number of the folks on the attendee list are Gerrit Code Review
> / Android sorts of shops and will want to discuss topics related to
> that that aren't necessarily relevant to the GitHub users / Linux
> kernel hacking folks that are also on the list. Being able to break
> off some of those discussions might make the event more interesting
> for everyone involved.
I think that's reasonable, especially as we grow. However, one of the
valuable things (for me, anyway) in previous GitTogethers is throwing
all of these people together to some degree. I'm not terribly interested
in day-to-day Gerrit issues, but sometimes the discussions start from
some minor Gerrit annoyance, and we end up realizing that the right
solution involves changes at a more fundamental layer, and all of git is
better as a result. I'd hate to lose that developer/user interaction.
Maybe we can be segmented for part of the conference, and then bring
everybody together for other parts. I dunno. I guess that involves
predicting which parts will be useful for everybody to be together.
I assume we'll keep largely to the un-conference format, though, so
these are issues that can be ironed out in the first hour as we see
which topics people are interested in discussing.
-Peff
next prev parent reply other threads:[~2011-09-07 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 19:56 [ANNOUNCE] GitTogether 2011 - Oct 24th/25th Shawn Pearce
2011-09-07 17:11 ` Scott Chacon
2011-09-07 18:38 ` Shawn Pearce
2011-09-07 19:30 ` Jeff King [this message]
2011-09-07 20:44 ` Scott Chacon
2011-09-07 21:06 ` Shawn Pearce
2011-09-07 21:00 ` Junio C Hamano
2011-09-09 23:10 ` Shawn Pearce
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=20110907193006.GB13364@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox