summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2021-11-09 18:05:12 -0500
committerSacha Chua <sacha@sachachua.com>2021-11-09 18:05:12 -0500
commit9c8309273b105d46ee4ee13f857487f49468842f (patch)
treec2f8a14aefbc2cfcd6ba116da21545d9cdeb9d62
parentc6e842c5b2e1a6ab4f85c16a494e99992ed28346 (diff)
downloademacsconf-wiki-9c8309273b105d46ee4ee13f857487f49468842f.tar.xz
emacsconf-wiki-9c8309273b105d46ee4ee13f857487f49468842f.zip
Add test Etherpad, note about questions and answers
Diffstat (limited to '')
-rw-r--r--2021/contribute.md44
1 files changed, 32 insertions, 12 deletions
diff --git a/2021/contribute.md b/2021/contribute.md
index 9a11abce..183c3a5a 100644
--- a/2021/contribute.md
+++ b/2021/contribute.md
@@ -38,20 +38,28 @@ Here are some notes on the process:
- Can you hear me? Can I hear you?
- Explain process
-- Test audio, webcam, screensharing, collaborative pad
- - Music demos and other things that use system audio will need to be
- prerecorded (or done through virtual loopback device, maybe?
- Technical risk.)
+- Test audio, webcam, screensharing
+ - Encourage webcam for Q&A, although make it clear that it's totally optional
+ - Audio: System audio will generally not be picked up by BBB unless
+ there's a virtual loopback device, so music demos and other things
+ that use system audio will need to be prerecorded
- Multi-monitor setups might not be handled well by BBB; share
window instead of desktop
- - Possible picture-in-picture approach to maximize screen real estate if
- needed
- - Linux: share desktop, run cheese, set Always on Top
-- Check if comfortable checking into IRC: #emacsconf-org
-- Get phone number for emergency contact, store in private wiki
-- Write down IRC nick, name pronunciation, and pronouns for inclusion in the
- public wiki
-- Encourage webcam for Q&A, although make it clear that it's totally optional
+ - Difficult to show webcam and shared screen at the same time
+ because BBB makes the shared screen too small. If the speaker is
+ interested, consider using a webcam app (Windows: their webcam's
+ camera app, Linux: Cheese, set to Always on Top)
+- Check if comfortable checking into IRC: #emacsconf-org channel via
+ https://chat.emacsconf.org or their favorite IRC client (libera.chat
+ network)
+- Check if the speaker is comfortable finding their section in the
+ [test Etherpad](https://etherpad.wikimedia.org/p/emacsconf-2021-test),
+ typing in text, etc.
+- Write down IRC nick, preferred public contact info, name
+ pronunciation, and pronouns for inclusion in the public wiki if not
+ already on their talk page
+- Get phone number for emergency contact, store in private wiki or
+ e-mail it to emacsconf-submit@gnu.org
# Running Alternate Streams
@@ -61,6 +69,18 @@ one or more of your favorite sessions from the [[schedule]] and get
set up for doing an extended stream, allowing more time for Q&A and
live demonstrations.
+# Capture questions and answers
+
+During the conference, people will be sending questions via Etherpad
+and IRC, and speakers might answer live or via Etherpad or IRC. As a
+volunteer, you can help make sure those questions and answers don't
+get lost. It would be great to get as many questions as possible
+written down in the Etherpad, along with their answers. This means
+copying questions and answers from IRC, typing in answers given live,
+copying questions from the pad into IRC if that's where the speaker is
+paying attention, and so on. It's a bit of a scramble, but it keeps
+the conversation going even after the event.
+
# Volunteer
Thought of another way to help? Sure, suggest away.