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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
# Table of Contents
- [How do we want to schedule talks?](#schedule)
- [Notes](#schedule-notes)
- [Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10](#gen-and-dev)
- [Option G: Time-aligned](#gen-and-dev-aligned)
- [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 (not recommended)](#no-irc)
- [Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch (not recommended)](#non-round)
- [Option F: Pack everything in one long day (current schedule)](#long)
<a id="schedule"></a>
# DONE How do we want to schedule talks?
<span class="timestamp-wrapper"><span class="timestamp">[2022-10-04 Tue]</span></span>
- Discussed option G with zaeph on #emacsconf-org. zaeph prefers
option A over option G because it gives people more choices -
they can hop from talk to talk.
<span class="timestamp-wrapper"><span class="timestamp">[2022-10-03 Mon]</span></span>
- Discussed with bandali and zaeph on #emacsconf-org
- Decided on Option A with B, C, or F as fallbacks depending on volunteer roster
- Better for the viewers and the volunteers
<a id="schedule-notes"></a>
## Notes
- Green: no availability constraints
- Red: invalid because of availability constraint
- Dashed: IRC/pad Q&A, not live
Host role:
- Give the speaker a heads-up before their Q&A session begins
- If needed, read the questions from the pad to the speaker (Many speakers are comfortable reading the pad on their own.)
- Give the speaker time warnings before the end of their Q&A session on the stream. Interested participants can continue
Streamer role:
- Switch between playing the prerec and joining the Q&A session
- Adjust audio volume at the beginning of the Q&A session
- (optional) Switch scene layouts to focus on different things
Shifts will be Sat AM, Sat PM, Sun AM, or Sun PM per track. People can take multiple shifts.
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
- If they decide a talk isn't for them, they can switch and catch another one
- Stagger live Q&A sessions so that just in case we have only one streamer, they can bounce back and forth
- Can give some talks extra time if we want
- Could use dedicated host/streamer(s) for dev track; if not, they can probably pick up questions themselves
- 
<a id="gen-and-dev-aligned"></a>
## Option G: Time-aligned
- Line up the starts and the Q&A; easier to display in a table, but
then we will really need to have multiple hosts/streamers, and
people will have to choose.
- 
<a id="two-afternoons"></a>
## Option B: Two afternoon tracks (dev starts at 13:30), 10/20 buffer, 60 min lunch
- Good option if we don't have enough hosts/streamers to cover both days
- Some room to breathe, some dev talks still on the main track
- LUNCH: Ends at 13:45 after 13:30
- 
<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 an extra host and streamer for one afternoon
- 
<a id="no-irc"></a>
## Option D: Remove buffer from non-live talks (not recommended)
- Considerations:
- Frees up about 20 minutes on each day, so we might be able to squeeze in two more talks sideways.
- Pretty frenetic
- Not recommended
- 
<a id="non-round"></a>
## Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch (not recommended)
- Schedule looks too precise, sets expectations; timekeeping is more challenging
- Pretty frenetic
- Could probably use shifts for hosts or streamers
- Not recommended
- 
<a id="long"></a>
## Option F: Pack everything in one long day (current schedule)
- 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
- 
|
