summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--2020/submissions.org67
1 files changed, 67 insertions, 0 deletions
diff --git a/2020/submissions.org b/2020/submissions.org
index 73fd90b7..fbf343ca 100644
--- a/2020/submissions.org
+++ b/2020/submissions.org
@@ -2921,6 +2921,73 @@ The total is written to the MIN_TIME_SUM property of this heading"
(lambda () (org-entry-get (point) "MIN_TIME")) nil 'tree))))))))
#+end_src
+* COMMENT Notes
+
+O1 - main organizer, O2 - secondary organizer or volunteer
+
+
+** Overview
+- 1 green room for speaker checkin, 4 rooms
+- 4 rooms streamed as room sources. O1 picks up the appropriate source and uses it for main conference mount point and individual talk mount points
+- main conference can be streamed through OBS if that doesn't work out
+** Things to check or decide
+- Mail merge?
+- Amin to investigate if Icecast can take one stream source and send it to the main conference stream and the individual talk stream
+- Assign rooms shortly before presentation
+ - *Shortly before presentation:* accommodates reshuffling
+- Generating static images
+ - Before the presentation: Talk title, speaker
+ - Speaker checked in
+ - After the presentation: pointer to main conference stream
+ - After the conference: conference has ended, we'll take some time to prepare the recording
+
+** Before the conference
+- Do tech checks and get alternative ways to contact speakers (phone number? IRC nick? Something that goes ding?)
+- Turn on audio alert
+- Install Mute Tab extension
+** Tech check
+- Explain process
+- Test audio, webcam, screensharing, collaborative pad
+** Shortly before the presentation
+- Speaker joins green room (O2 home room). O2 gets alert
+- O2 directs speaker to available room
+- Speaker joins talk room
+- O2 makes speaker presenter and moderator (so they can kick out recorder when done), does tech check
+- Speaker tries screen sharing and webcam, then returns to uploaded presentation
+- O2 starts secondary stream and recording, checks individual page
+- O2 notifies O1 with link to the talk room
+- O1 joins meeting
+- O1 sets conference stream to individual talk endpoint
+- O2 starts recording in BBB
+** During the presentation
+- Speaker presents, keeping an eye on the collaborative pad for questions
+- O1 stays with speaker to help with questions and timing
+- O2 wanders off to do the tech check with the next person and pings O1 when ready
+** After the presentation
+- O1 announces next steps: If you want to continue the conversation, go to the individual talk page
+- O1 goes to next talk when ready
+- Speaker continues with extended presentation if they want
+** After the extended presentation (if any)
+- Speaker removes the recorder/streamer user to end the stream and recording
+- Speaker stops the BBB recording
+** Scenarios
+*** Prerecorded presentations
+- O1 streams presentation to both endpoints (is there a neat command-line way to do this?)
+https://stackoverflow.com/questions/7869190/is-it-possible-to-pull-a-rtmp-stream-from-one-server-and-broadcast-it-to-another
+or maybe IceCast can handle the splitting
+*** Tech issues
+- If can't be easily resolved, play pre-recorded talk early and try again later (or follow up)
+- Stream a technical issues slide to the end point
+*** Speaker can stream directly from computer over RTMP
+- Can skip BigBlueButton entirely if they want
+- Speaker starts streaming to talk endpoint
+- O2 verifies that it's playing and communicates with speaker through collaborative pad
+- O1 switches conference stream to talk endpoint
+*** Speaker is giving another talk soon
+- Stay in same room
+- O2 checks in near the time of the next talk
+- O2 stops and restarts recorder, giving it the next talk's stream endpoint
+
* COMMENT Possible rough flow suggested by Sacha
#+begin_src emacs-lisp :exports both