summaryrefslogtreecommitdiffstats
path: root/2022
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2022-11-20 10:50:43 -0500
committerSacha Chua <sacha@sachachua.com>2022-11-20 10:50:43 -0500
commit9c11e92b50101be61b8e45afa96d63207669bf38 (patch)
tree6e93cf38eb1445130da3cfaa8a8813f09d9ed16c /2022
parent59de540c0365c7bb7a1c3e3acfdb5b678743e846 (diff)
downloademacsconf-wiki-9c11e92b50101be61b8e45afa96d63207669bf38.tar.xz
emacsconf-wiki-9c11e92b50101be61b8e45afa96d63207669bf38.zip
Add headings to prepare
Diffstat (limited to '2022')
-rw-r--r--2022/speakers.md72
1 files changed, 37 insertions, 35 deletions
diff --git a/2022/speakers.md b/2022/speakers.md
index cab8bccc..bc95d985 100644
--- a/2022/speakers.md
+++ b/2022/speakers.md
@@ -1,7 +1,7 @@
[[!meta title="Conference-day instructions for speakers"]]
[[!meta copyright="Copyright &copy; 2021 Sacha Chua"]]
-# How to check in
+# Before your talk
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
@@ -14,8 +14,6 @@ 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.
@@ -29,10 +27,33 @@ the URL of a BigBlueButton room to join.
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.
+
+The schedule on your talk page is still tentative. Please check your
+talk page for updates, especially on the day of the talk. We've done
+some dry-runs, but just in case it turns out that running two tracks
+at the same time leaves us too frazzled, we may drop back to one track
+with Q&A on an alternate stream. We'll try our best to keep your talk
+in the same general timeslot (ex: Saturday morning, Saturday
+afternoon, Sunday morning, Sunday afternoon). If we need to do that,
+or if there are other big changes to your schedule on the day of your
+talk, you'll get an e-mail from us with a subject like "URGENT:
+EmacsConf 2022: ...".
+
+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. If we start worrying, we'll
+reach out to you via your emergency contact information.
+
+# While your talk 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 on Etherpad or IRC, you
+can start answering whenever you like.
+
+# Answering questions
+
- 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
@@ -62,33 +83,14 @@ the URL of a BigBlueButton room to join.
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.
-
-# Other notes
-
-- The schedule on your talk page is still tentative. Please check your
- talk page for updates, especially on the day of the talk. We've done
- some dry-runs, but just in case it turns out that running two tracks
- at the same time leaves us too frazzled, we may drop back to one
- track with Q&A on an alternate stream. We'll try our best to keep
- your talk in the same general timeslot (ex: Saturday morning,
- Saturday afternoon, Sunday morning, Sunday afternoon). If we need to
- do that, or if there are other big changes to your schedule on the
- day of your talk, you'll get an e-mail from us with a subject like
- "URGENT: EmacsConf 2022: ...".
+
+# After the conference
-- 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. If we start
- worrying, we'll reach out to you via your emergency contact
- information.
+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.
-Thank you so much for putting so much time and energy into sharing what you know at EmacsConf!
+Thank you so much for putting so much time and energy into sharing
+what you know at EmacsConf!