path: root/2022/decisions.md

# Table of Contents

-   [How do we want to schedule talks?](#schedule)
    -   [Legend](#legend)
    -   [Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10](#gen-and-dev)
    -   [Option B: Two afternoon tracks (dev starts at 13:30), 10/20 buffer, 60 min lunch](#two-afternoons)
    -   [Option C: One afternoon track, 5/10 minute buffers, 60 minute lunch](#one-afternoon)
    -   [Option D: Remove buffer from non-live talks](#no-irc)
    -   [Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch](#non-round)
    -   [Option F: Pack everything in one long day](#long)


<a id="schedule"></a>

# How do we want to schedule talks?


<a id="legend"></a>

## Legend

-   Green: no availability constraints
-   Red: invalid because of availability constraint
-   Dashed: IRC/pad Q&A, not live


<a id="gen-and-dev"></a>

## Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10

-   Lots of space for Q&A and hallway conversations
-   People can probably find lots of sessions that interest them throughout the day
-   Need host/streamer(s) for dev track

-   ![img](schedule-option-gen-and-dev.svg)


<a id="two-afternoons"></a>

## Option B: Two afternoon tracks (dev starts at 13:30), 10/20 buffer, 60 min lunch

-   Some room to breathe, some dev talks still on the main track

-   LUNCH: Ends at 13:45 after 13:30
-   ![img](schedule-option-two-afternoon-tracks.svg)


<a id="one-afternoon"></a>

## Option C: One afternoon track, 5/10 minute buffers, 60 minute lunch

-   Lightens up the schedule a little bit, allows us to test out tracks without committing too much
-   Needs a host/streamer for the other track

-   ![img](schedule-option-one-afternoon-track.svg)


<a id="no-irc"></a>

## Option D: Remove buffer from non-live talks

-   Considerations:
    -   Frees up about 20 minutes on each day, so we might be able to squeeze in two more talks sideways.
    -   Pretty frenetic

-   ![img](schedule-option-only-live-qa.svg)


<a id="non-round"></a>

## Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch

-   Schedule looks too precise, sets expectations; timekeeping is more challenging
-   Pretty frenetic
-   Could probably use shifts for hosts or streamers

-   ![img](schedule-option-non-round-buffer.svg)


<a id="long"></a>

## Option F: Pack everything in one long day

-   Considerations:
    -   Difficult to accommodate extra talks
    -   Host/streamer have a very long intense day
-   Ideas:
    -   Split up hosting duties into shifts (volunteers can read the questions)
    -   Use prerecorded intros and outros
    -   Split up streaming duties into shifts (volunteers can adjust audio volume, switch to the right BBB room)
    -   Set up cloud streaming so that streamers can work in shifts

-   ![img](schedule-option-one-full-day.svg)