2022/decisions.md


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100


# Table of Contents

-   [How do we want to schedule talks?](#schedule)
    -   [Notes](#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>

## Notes

-   Green: no availability constraints
-   Red: invalid because of availability constraint
-   Dashed: IRC/pad Q&A, not live
    
    Updating the images requires `emacsconf-schedule.el` from
    `git@git.emacsconf.org:emacsconf-el` and `emacsconf-org-file` set to
    wherever the private conf org file is.


<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
-   Can give some talks extra time if we want
-   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)