Hey, On Wed, Sep 7, 2011 at 7:30 PM, Jeff King <peff@xxxxxxxx> 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 >> 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. 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. I really want to have one track though - I'm personally interested in everything. I want to know how Gerrit is working these days and different workflows and stuff. I think we have enough time where even with 50 or 60 people we could have everyone who wanted to speak (which isn't going to be everybody) have a chance without being too crazy. Scott -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html