summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--2022/speakers.md79
1 files changed, 79 insertions, 0 deletions
diff --git a/2022/speakers.md b/2022/speakers.md
new file mode 100644
index 00000000..4fc7c713
--- /dev/null
+++ b/2022/speakers.md
@@ -0,0 +1,79 @@
+[[!meta title="Conference-day instructions for speakers"]]
+[[!meta copyright="Copyright © 2021 Sacha Chua"]]
+
+# How to check in
+
+Please check in at least 30 minutes before the start of your Q&A
+session. You can check in on IRC by joining the #emacsconf-org channel
+on libera.chat using your favorite IRC client or using
+[https://chat.emacsconf.org](https://chat.emacsconf.org/?join=emacsconf-org).
+If you want, you can also join the channel for your track as well
+(either #emacsconf-gen or #emacsconf-dev).
+
+Say something like "Hi, this is <your name> checking in" in the
+\#emacsconf-org channel and one of the organizers will check you in.
+If you are having a hard time with IRC, e-mail
+<emacsconf-submit@gnu.org> and we can give you the URL of a
+BigBlueButton room to join.
+
+# The process
+
+- If you want to do Q&A over IRC or Etherpad:
+ - You can hang out in the IRC channel for your track and/or on the
+ pad for your talk.
+- If you want to do Q&A over Mumble:
+ - You can connect to mumble.emacsconf.org.
+- If you want to do Q&A in a BigBlueButton room (ex: quick demoes):
+ - We'll set you up in a BigBlueButton room (check your e-mail for
+ the URL, or ask in #emacsconf-org). You can keep watching the
+ conference or doing other things while waiting there. We'll let
+ you know shortly before your prerec ends. If you want, you can get
+ things ready for whatever you might want to demonstrate.
+ - Please use headphones or earphones to minimize the risk of audio
+ feedback. Webcams are optional.
+- While your prerec plays: people will add notes and questions on the
+ pad, or they'll ask them on IRC. Volunteers will try to copy all the
+ questions to the pad. If you're looking at the Etherpad or IRC, you
+ can start answering whenever you like.
+- General notes about answering questions:
+ - You can answer questions in any order, and you can skip any questions you like.
+ - You don't have to answer questions right away. If you want to take
+ some time to think about things, that's okay.
+ - If you're answering questions by voice and the host is not reading
+ the questions out for you, please read the question out before you
+ answer it. This makes it easier to follow the conversation and to
+ copy the answers to the talk page afterwards.
+- After your prerec finishes:
+ - If you're doing IRC/Etherpad: we'll let people know where to ask
+ questions and we can read out some of the questions and answers
+ that are there.
+ - If you're on Mumble: we'll pull you into the channel room and the
+ streamer will connect to it. When we confirm that you can be
+ heard, you and the host can go ahead with the Q&A.
+ - If you're doing Q&A in a BBB room:
+ - We'll switch the stream to broadcast from the BBB room you're
+ in, and we'll start recording the session so that Q&A can be
+ available after the conference.
+ - Depending on your preferences, the host can read questions to
+ you, or you can read questions off the pad/IRC yourself.
+ - We'll open up the Q&A for other people to join if there's time
+ for a longer discussion. If so, this conversation can continue
+ for as long as you like. If it's time for the next talk to
+ start, we'll give you a heads-up and your Q&A can continue off
+ the stream in the same BBB room. When you are ready to stop
+ answering questions, you can wrap up however you'd like and
+ leave the meeting.
+- After the conference, we'll collect questions and answers from IRC
+ and the pad. We'll put them on the talk page and e-mail them to you
+ in case you want to follow up or keep the conversation going. We'll
+ also work on extracting the videos from the Q&A sessions and we'll
+ post them on the talk page.
+
+# Tips and backup plans
+
+- Doing a tech check can help if you want to do live Q&A.
+ https://test.bigbluebutton.org has a self-serve tech check.
+- Please let us know if you're running late or if it turns out you
+ can't make it. Drop by #emacsconf-org, e-mail us at
+ <emacsconf-submit@gnu.org> , or use the emergency contact
+ information from the check-in instructions email.