Remove tech notes

1 files changed, 0 insertions, 59 deletions

diff --git a/2020/submissions.org b/2020/submissions.org
index 1053073f..73fd90b7 100644
--- a/2020/submissions.org
+++ b/2020/submissions.org
@@ -2921,65 +2921,6 @@ 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 Tech notes
-O1 - main organizer, O2 - secondary organizer or volunteer
-
-** Things to check
-- Mail merge?
-- Decisions
-  - One room per talk? One room per speaker? Five or six rooms, rotating among them?
-    - One room per talk: Fewer rooms to set up
-    - RECOMMENDED: One room per speaker: Speaker doesn't have to move after talks that are close together
-- Generating static images and PDFs
-  - 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 recordings
-- Easy way to generate lots of rooms? I can probably automate this with Puppeteer =)
-** Before the conference
-- Can set up room to allow anyone to start the meeting; people joining can talk and use webcam, but can't present
-- Upload a presentation - PDF, with the speaker information and URLs for collaborative pad, main conference stream, individual stream page
-- 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 starts meeting and pings O2
-- O2 joins meeting
-- 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
-- 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 switches conference stream to next talk when ready
-** 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
-*** 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
-** Tech notes
-- Switching the conference stream source: could be O1 streaming directly through OBS, or https://stackoverflow.com/questions/7869190/is-it-possible-to-pull-a-rtmp-stream-from-one-server-and-broadcast-it-to-another
 * COMMENT Possible rough flow suggested by Sacha
 
 #+begin_src emacs-lisp :exports both