linaro-project-management team mailing list archive

[Joey STANFORD <joey@xxxxxxxxxx>]

Hi,

> What if we have just 4 big spaces that get statically scheduled for
> the week and then do everything else in free floating breakout
> sessions?

I think we're saying the same thing. Please correct me if I'm wrong.
4+ dedicated rooms for 4 to 6 tracks and then a handful of smaller
rooms that people can have pre-planned sessions or breakouts.  Is that
where you were mostly going?

I can envision a transition period happening where we do the big
sessions during the morning and then people feeling like they need
breakouts in the afternoon over hacking. My fear with this is that
we'll essentially nullify the hacking sessions because of the need for
the smaller meetings (some of which are going to be very valid to have
too).   I wonder if we can position this somehow so that we do this:

 * Morning: 4 to 6 large-attendance sessions around a
project/topic/epic (e.g. big.LITTLE Switcher, KVM, UMM, Let's rewrite
the entire Linux scheduler from scratch, etc)
 * Lunch: Yum
 * Afternoon: 4 to 6 large-attendance "Let's just go
spike/prototype/implement what we talked about this morning"

The on-topic breakouts can be done in the afternoon coding sessions.
Off-topic breakouts would hopefully be kept to a minimum or we
dedicate part of a day for them. (still worried about off-topic but
necessary breakouts being distracting)

Thoughts?

Joey