git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [ANNOUNCE] GitTogether 2011 - Oct 24th/25th

From
Shawn Pearce <spearce@spearce.org>
Date
Sep 7, 2011, 21:06 UTC
Message-ID
<CAJo=hJt85RgF_=45WOKnTTY9mQnWo8UQiAjnCjxjv3fdez4VmQ@mail.gmail.com>
In-Reply-To
<CAP2yMa+A3CW63ra8ndj6jtb6vHmP-1f78NB2zBLZcRBueMNUBQ@mail.gmail.com>
On Wed, Sep 7, 2011 at 13:44, Scott Chacon <schacon@gmail.com> wrote:
Show 18 quoted lines
> On Wed, Sep 7, 2011 at 7:30 PM, Jeff King <peff@peff.net> wrote:
>> 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 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.
>>
>> 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.
>
> Yeah, I think it would be best to have one track, but have breakout
> periods where people can work on stuff together or have smaller
> conversations, or even have smaller rooms that people can go into to
> work for a while.

Right now we are looking for new space on the Google campus that would allow us to get everyone in 1 room together, but also offer some break-out space. More details as soon as I know. :-)

I'd like to keep it still somewhat unconferencey. Maybe do the morning before lunch with everyone together and the topics that have the most interest, and the afternoons for more breakout style smaller discussions, especially if a subgroup identifies with something from the morning and they want to purse that a little bit more in person.

-- 
Shawn.
Previous: Scott ChaconNext: Junio C Hamano
Message 6 of 8 in “[ANNOUNCE] GitTogether 2011 - Oct 24th/25th”
  1. Shawn PearceSep 5, 2011
  2. Scott ChaconSep 7, 2011
  3. Shawn PearceSep 7, 2011
  4. Jeff KingSep 7, 2011
  5. Scott ChaconSep 7, 2011
  6. Shawn PearceSep 7, 2011
  7. Junio C HamanoSep 7, 2011
  8. Shawn PearceSep 9, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.