Merge branch 'master' of git.emacsconf.org:emacsconf-wiki

4 files changed, 326 insertions, 135 deletions

diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index 078b1642..20d88c26 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -41,6 +41,12 @@ Planned dates and phases:
 
 
 <tr>
+<td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-10-02 Sun]</span></span></td>
+<td class="org-left">Confirm time allocations for early submissions</td>
+</tr>
+
+
+<tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-10-07 Fri]</span></span></td>
 <td class="org-left">Yes/no comments for late submissions</td>
 </tr>
@@ -71,7 +77,7 @@ Planned dates and phases:
 
 
 <tr>
-<td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-11-05 Sat]</span></span></td>
+<td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-11-04 Fri]</span></span></td>
 <td class="org-left">Target date to receive prerecs; earlier is better</td>
 </tr>
 
@@ -104,15 +110,38 @@ Planned dates and phases:
 Current phase: No prerecs to process yet, so it's a good time to focus on infrastructure
 
 
-## TODO Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgf454f74), Oct 7 for everything     :organizers:
+## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgbb35d27), Oct 7 for everything     :organizers:
 
 -   zaeph: will start reviewing on Sep 21
 
 
-## INPROGRESS Write preparation instructions and decide on deadline for prerecs     :zaeph:
+## DONE Write preparation instructions     :zaeph:
 
 2021/prepare.md can be reused.
 
+Extra stuff to consider adding:
+
+-   DONE Suggestions for themes (especially wrt colourscape)
+-   DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it's easier to write, record, and edit your voiceover, and then record the video to go along with it."
+-   DONE Allowing speakers to plant questions, esp. to cover tangential stuff that couldn’t fit in the prerec
+
+
+## STANDBY Add nice-to-have stuff to prepare.md     :zaeph:
+
+-   org-reveal config
+-   SIL fonts choice
+
+
+## TODO Prepare for prerecs     :zaeph:
+
+
+### TODO Optimize ffmpeg incantation
+
+Remember to update <prepare.md> with the new incantation.
+
+
+### TODO Figure out workflow for handling submitted prerecs
+
 We need time after the prerecs get submitted to:
 
 -   convert the videos and check that they've been reencoded properly by watching the re-encoded ones all the way to the end
@@ -120,16 +149,35 @@ We need time after the prerecs get submitted to:
 -   capture any extra info
 -   follow up with missing prerecs
 
-zaeph will also figure out the ffmpeg incantation for converting videos and the process for handling submitted prerecs
 
-Extra stuff to consider adding:
+## INPROGRESS Find volunteers for tech-checks     :zaeph:
 
--   STRT Suggestions for org-reveal, fonts and themes (especially wrt colourscape)
--   DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it's easier to write, record, and edit your voiceover, and then record the video to go along with it."
--   DONE Allowing speakers to plant questions, esp. to cover tangential stuff that couldn’t fit in the prerec
 
+### DONE Add entry in 2022/volunteer.md
 
-## TODO Write viewing instructions     :zaeph:
+
+### INPROGRESS Write protocol for adding tech-checker volunteer
+
+-   Invite volunteer to BBB (ask core organizers)
+-   Update <prepare.md> with new tech-checker info
+-   Coach tech-checker on the protocol
+
+
+### INPROGRESS Write the tech-checking protocol (formerly referred to as “tech-checklist”)
+
+From previous years:
+
+> -   Can you speak and be heard? Is there echo?
+> -   Can you hear the organizer?
+> -   Can you share your screen? Is the screen readable?
+> -   If you plan to show your keystrokes, is that display visible?
+> -   If you want to share your webcam (optional), can you enable it? Is it visible? Will there likely be distractions in the background?
+> -   Can you view the collaborative pad? Will you be comfortable reviewing questions on your own (perhaps by keeping it open beside your shared window), or will you need a volunteer to relay questions to you?
+> -   Can you share contact information (ex: phone number) so that we can get in touch with you in case of technical issues or scheduling changes?
+> -   Do you need help finding your way around IRC so that you can check into \`#emacsconf-org\`? What is your IRC nickname?
+
+
+## STANDBY Write viewing instructions     :zaeph:
 
 Extra stuff to consider adding:
 
@@ -141,10 +189,19 @@ Extra stuff to consider adding:
 -   Sacha: Add submissions to emacsconf-2022-private, draft 2-day schedule by Oct 10
 
 
-## DONE Copy things over from previous notebooks     :sachac:
+## TODO Publish talk pages     :sachac:
+
 
+## TODO Send early acceptances     :sachac:
 
-## TODO Double-check sachac’s timezone conversions for availability     :corwin:
+Ideal sequence:
+
+1.  publish /2022/prepare (zaeph)
+2.  publish wiki pages
+3.  send acceptance e-mails
+    -   Allocate at most 20 minutes, say we'll try to add more time depending on the schedule (probably know by Sept 30 or Oct 1)
+    -   Include review comments
+4.  Send an additional e-mail introducing speakers who may want to coordinate
 
 
 ## TODO Investigate streaming options, maybe OBS in the cloud     :corwin:
@@ -201,15 +258,42 @@ That will help more people subtitle things
 ## TODO Create Org heading for scheduling caption team's live IRC duty shifts     :dto:
 
 
+## TODO Review metadata for speakers in conf.org     :zaeph:
+
+See the bottom of conf.org for some automated validation
+
+
+## TODO Write viewing instructions     :zaeph:
+
+Extra stuff to consider adding:
+
+-   Suggestions for mpv-filter to invert colourscape.
+
+
 ## DONE Write volunteer page     :sachac:
 
 <https://emacsconf.org/2022/volunteer>
 
 
-## TODO Review metadata for speakers in conf.org     :zaeph:
+## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgbb35d27), Oct 7 for everything     :organizers:
+
+-   zaeph: will start reviewing on Sep 21
+
+
+## DONE Double-check sachac’s timezone conversions for availability     :zaeph:
+
+zaeph helped with this, even catching some based on e-mail timestamps
+
+
+## DONE Copy things over from previous notebooks     :sachac:
+
 
+## TODO Allocate extra time if possible; send e-mail     :sachac:
 
-## TODO :zaeph:bandali:
+
+<a id="decisions"></a>
+
+# Things to figure out / decisions to make
 
 
 ## TODO Do we want to use JS on the wiki?
@@ -231,11 +315,6 @@ gitolite should have some options to do this
 Might not be necessary.
 
 
-<a id="decisions"></a>
-
-# Things to figure out / decisions to make
-
-
 ## What ideas do we want to borrow from other conferences?
 
 -   FOSDEM had a conference track
@@ -541,7 +620,7 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau
 
 ### Test stream setup
 
-[Stream](#org531b5e1)
+[Stream](#orgc0a238a)
 
 
 ### Set up MPV for captions
@@ -858,7 +937,7 @@ Exceptions:
 
 ### Send thanks
 
-[Thank you, next steps](#orgb3500be)
+[Thank you, next steps](#orge71d484)
 
 
 ### Extract the opening and closing remarks
@@ -1009,7 +1088,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping
 
 Make a table of the form
 
-<table id="org3553aac" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="org2970f57" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
 
 
 <colgroup>
@@ -1290,48 +1369,147 @@ Thanks!
 Sacha
 
 
-## TODO Early speaker notification
+## TODO Early speaker notification     :sachac:
 
 We can accept early or send people a note saying notification of acceptance will be on Oct 15, because of the extended CFP.
+Right before this e-mail:
+
+-   Publish the wiki pages
+
+Objectives for this e-mail:
+
+-   Notify people of acceptance
+-   Tell them the number of minutes to plan for\* (might get more)
+-   Tell them about the target date
+-   Get them to reply
+-   Ask for public contact information or any changes to the wiki page
+
+    (defun emacsconf-draft-early-acceptance-for-email-group (group &optional template)
+      "GROUP is (email . (talk talk))."
+      (interactive
+       (list
+        (save-window-excursion
+        (let* ((emacsconf-talk-info-functions (append emacsconf-talk-info-functions '(emacsconf-get-talk-comments-from-subtree)))
+               (info (emacsconf-filter-talks (emacsconf-get-talk-info)))
+               (grouped (seq-group-by (lambda (o) (plist-get o :email)) info))
+               (slug (emacsconf-get-slug-from-string (emacsconf-complete-talk)))
+               (email (plist-get (seq-find (lambda (o) (string= (plist-get o :slug) slug)) info) :email)))
+          (assoc email grouped)))))
+      (let* ((template (or template (emacsconf-mail-merge-get-template "early-acceptance")))
+             (talks (cdr group))
+             (first (car talks))
+             (reply-by-date (date-to-time "2022-10-08"))
+             (prerec-target (date-to-time "2022-11-07"))
+             (attrs `(:speakers-short
+                      ,(plist-get first :speakers-short)
+                      :email
+                      ,(plist-get first :email)
+                      :year
+                      ,(or (plist-get first :year) emacsconf-year)
+                      :reply-date
+                      ,(format-time-string "%b %e (%a)" reply-by-date)
+                      :titles
+                      ,(mapconcat (lambda (o) (format "\"%s\"" (plist-get o :title))) talks " and ")
+                      :prerec-target
+                      ,(format-time-string "%b %e (%a)" prerec-target)
+                      :page-urls
+                      ,(mapconcat (lambda (o) (format "https://emacsconf.org/%s/talks/%s" (plist-get o :year)
+                                                      (plist-get o :slug)))
+                                  talks "\n")
+                      :acceptance-tasks
+                      ,(concat
+                       "* TODO Reply to acceptance e-mail in order to confirm e-mail communication  :emacsconf:
+      DEADLINE: " (format-time-string "<%Y-%m-%d %a>" reply-by-date) "\n  Please include public e-mail and/or any extra information you want on\n"
+    (mapconcat (lambda (o) (format "  https://emacsconf.org/%s/talks/%s"
+                                   (plist-get o :year)
+                                   (plist-get o :slug)))
+               talks "\n") "\n"
+    (mapconcat (lambda (o) (format "* Record %s-minute talk for \"%s\"  :emacsconf:
+      DEADLINE: %s\n  https://emacsconf.org/%s/prepare/"
+                                   (plist-get o :time)
+                                   (plist-get o :title)
+                                   (format-time-string "<%Y-%m-%d %a>" prerec-target)
+                                   (plist-get o :year)))
+               talks "\n"))
+                      :talk-details-and-comments
+                      ,(mapconcat
+                        (lambda (o)
+                          (format "%s minutes: %s\nhttps://emacsconf.org/%s/talks/%s\n\n%s"
+                                  (plist-get o :time)
+                                  (plist-get o :title)
+                                  (plist-get o :year)
+                                  (plist-get o :slug)
+                                  (string-fill (emacsconf-replace-plist-in-string o (plist-get o :acceptance-comment)) 72)))
+                        talks "\n---------------------------------------------------------------------\n"))))
+        (compose-mail
+         (car group)
+         (emacsconf-replace-plist-in-string attrs (plist-get template :subject))
+         `(("Reply-To" . ,(plist-get template :reply-to))
+           ("Mail-Followup-To" . ,(plist-get template :mail-followup-to))
+           ("Cc" . ,(plist-get template :cc))))
+        (message-goto-body)
+        (save-excursion (insert (emacsconf-replace-plist-in-string attrs (plist-get template :body))))))
+    
+    (defun emacsconf-draft-all-early-acceptances ()
+      (interactive)
+      (let* ((emacsconf-talk-info-functions (append emacsconf-talk-info-functions '(emacsconf-get-talk-comments-from-subtree)))
+             (info (emacsconf-filter-talks (emacsconf-get-talk-info)))
+             (grouped (seq-group-by (lambda (o) (plist-get o :email)) info))
+             (template (emacsconf-mail-merge-get-template "early-acceptance")))
+        (mapc (lambda (group)
+                (emacsconf-draft-early-acceptance-for-email-group group template))
+              grouped)))
 
 
-### Option A: Early speaker notification(?)
-
-Hi, $name!
-
-I'm happy to tell you that we've accepted your EmacsConf proposal for "$talk." Thanks for volunteering to share what you're learning about! I know it takes a fair bit of work to prepare a presentation, so I appreciate that you're taking the time to show what's possible with Emacs and encourage people to learn more.
-
-We've extended the call for participation to Sept 30, so we might get a few more submissions over the next two weeks. That means we'll confirm time allocations on Oct 15. Since you submitted before the original deadline, we wanted to send you your acceptance by the original timeline so that you wouldn't be waiting in uncertainty. 
-
-Just like last year, talks will be prerecorded in order to minimize technical risks, make it easier for speakers to enjoy other people's talks, allow captions, and let attendees catch up or share cool stuff quickly. I hope we get everything together in time so that we can ask volunteers to check for any issues that might come up when we re-encode. (I missed parts of some talks last time because I was rushing. <blush>)
-
-&#x2013;&#x2014; if $time = $max\_time
+### Speaker acceptance
 
-You asked for $max\_time minutes for your talk and I think that should be all right.
+Hi, ${speakers-short}!
 
-&#x2013;&#x2014; else
+Summary:
+,${acceptance-tasks}
 
-You asked for at most $max\_time minutes for your talk. I think at this moment we can commit to $time minutes, with possibly more time being available depending on other submissions. If you want to plan a pre-recorded talk for that length and then use extra time for a live presentation or as Q&A, that would be great. Alternatively, you can wait until we confirm the schedule in case you want to plan a longer prerecorded talk.
+We've accepted your EmacsConf proposal for ${titles}! Thanks for
+volunteering to share what you're learning about. I know it takes a
+fair bit of work to prepare a presentation, so I appreciate that
+you're taking the time to show what's possible with Emacs and
+encourage people to learn more.
 
 ---
 
-&#x2014; if Q&A will be live or IRC &#x2014;
-
-You'll have some time after your talk for Q&A, so the $time minutes can be just for your talk. Of course, if you like, you can make it shorter.
+${talk-details-and-comments}
 
 ---
 
-If you want to get a head start on recording your talk, please feel free to do so. We'll be streaming talks at 1920x1280 resolution, so the closer your recording is to that, the easier it will be to process for streaming. .webm format is preferred, but we can convert other formats. $recording has some tips on recording tools and settings that you might find helpful. We'll send you instructions on how to upload files once we get that set up.
-
-We're going to try to caption as many talks as possible again this year, and extra time helps a lot. People found the captions really helpful while watching the stream, and sending your talk in early will make it more likely that we'll be able to get your captions edited and reviewed before the conference.
-
-Could you please reply to this email so that we can confirm that I've got the right email address for you and that messages can get properly delivered?
-
-We'll be putting up the public wiki pages for each talk soon using the information from the talk abstract, and we can put $public\_email as the contact information for you. Please let us know by $publish\_date if you would prefer something else.
+You'll have some time after your talk for Q&A, so the allocated time
+can be just for your pre-recorded talk. Of course, if you like, you
+can make it shorter.
+
+We've posted preparation tips at <https://emacsconf.org/${year}/prepare/> .
+We'll send you instructions on how to upload files once we get that
+set up.
+
+Could you please plan to ****put your pre-rec together by ${prerec-target}****
+(or even earlier if you want)? We're going to try to caption as many talks
+as possible again this year, and extra time helps a lot. People found
+the captions really helpful while watching the stream, and sending
+your talk in early will make it more likely that we'll be able to get
+your captions edited and reviewed before the conference.
+
+****Please reply to this e-mail by ${reply-date}**** (including
+emacsconf-submit@gnu.org in the To: or Cc:) so that we can confirm
+that we've got the right email address for you and that messages can
+get properly delivered. Would you like us to put ${email} as the
+public contact information for you, or would you like us to add
+something else to the talk pages?
+${page-urls}
+
+If you have any questions, please e-mail us at
+emacsconf-submit@gnu.org or pass by the #emacsconf-org IRC channel on
+irc.libera.chat (Web-based: <https://chat.emacsconf.org/#/connect>).
 
 Thank you so much!
 
-Sacha
+Sacha Chua
 
 
 ### Option B: Just letting them know it's been postponed
@@ -1350,29 +1528,14 @@ Sacha
 
 ### Acceptance
 
+This is a copy of the previous
+
 
 #### Code
 
-    (defun conf-summarize-times (time timezones)
-      (let (prev-day)
-        (mapconcat
-         (lambda (tz)
-           (let ((cur-day (format-time-string "%a %b %-e" time tz))
-                 (cur-time (format-time-string "%H%MH %Z" time tz)))
-             (if (equal prev-day cur-day)
-                 cur-time
-               (setq prev-day cur-day)
-               (concat cur-day " " cur-time))))
-         timezones
-         " / ")))
-    
-    ;; (assert (string= (conf-replace-plist-in-string '(:test "ABC") "hello ${test} world") "hello ABC world"))
-    
-    
-    (defun conf-draft-acceptance ()
+    (defun emacsconf-draft-acceptance ()
       (interactive)
-      (let* ((mustache-key-type 'keyword)
-             (sched (org-timestamp-from-string (org-entry-get (point) "SCHEDULED")))
+      (let* ((sched (org-timestamp-from-string (org-entry-get (point) "SCHEDULED")))
              (attrs
               (append (emacsconf-get-talk-info-for-subtree)
                       :other-notes
@@ -1903,7 +2066,6 @@ chatter in the other lists Cc'd on this message.  Thank you.
     (message "No longer asking for confirmation in this buffer")
 
     (setq-local emacsconf-danger-allow-dangerous-stuff t)
-    
     (org-babel-ref-resolve "elisp-no-confirmation()")
     
     (message "Now allowing dangerous stuff.  Buckle up, buckaroo!")
@@ -1977,25 +2139,27 @@ chatter in the other lists Cc'd on this message.  Thank you.
       (message "Hook is no longer active"))
 
 
-## Process review comments from pad
+## Review agenda
 
-1.  `curl https://etherpad.wikimedia.org/p/[REDACTED]/export/html`
-2.  Open curl’d html into browser
-3.  Copy just the text from the page (i.e. not the html)
-4.  Paste in Emacs buffer
+    (defcustom emacsconf-org-tag nil "Tag for your nick, for easier agenda filtering"
+      :group 'emacsconf
+      :type 'string)
 
-Inside emacs:
+\#+begin\_src emacs-lisp :results silent
+(defun emacsconf-show-my-agenda ()
+  (interactive)
+  (let\* ((org-agenda-files (list (buffer-file-name)))
+         (tag-filter (if emacsconf-org-tag (concat "<del>" emacsconf-org-tag) ""))
+         (org-agenda-tag-filter-preset (list (when emacsconf-org-tag (concat "</del>" emacsconf-org-tag))))
+         (org-agenda-custom-commands \`(("a" "Agenda"
+                                        ((agenda ,tag-filter)
+                                         (tags-todo ,(concat tag-filter "-SCHEDULED={.+}-DEADLINE={.+}")))))))
+    (org-agenda nil "a")))
 
-1.  C-s Comments for
-2.  C-M-s ^[a-z0-9]
-3.  M-<
-4.  C-x 3
-5.  C-x b comments.org (new buffer)
-6.  C-x o
-7.  Run following kmacro (eval then M-x pad-comments, then C-x e until completion)
 
-    (defalias 'emacsconf-pad-comments
-       (kmacro "C-s C-s <return> C-a C-SPC C-n C-M-s M-p <return> <return> C-b M-w C-x o C-y C-u -- C-x o"))
+## Process review comments from pad
+
+see emacsconf-import-comments-from-etherpad-text
 
 
 <a id="lessons"></a>
diff --git a/2022/organizers-notebook.org b/2022/organizers-notebook.org
index 8dc049ac..13421efc 100644
--- a/2022/organizers-notebook.org
+++ b/2022/organizers-notebook.org
@@ -1,4 +1,4 @@
-#+todo: TODO(t) INPROGRESS(i) WAITING(w) BLOCKED(b) | DONE(x) CANCELLED(c)
+#+todo: TODO(t) INPROGRESS(i) WAITING(w) STANDBY(s) BLOCKED(b) | DONE(x) CANCELLED(c)
 #+OPTIONS: h:6 toc:nil
 #+PROPERTY: header-args    :results silent :exports code :tangle yes
 
@@ -62,32 +62,54 @@ Planned dates and phases:
 
 Current phase: No prerecs to process yet, so it's a good time to focus on infrastructure
 
-** TODO Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [[*Early speaker notification][early speaker notification]], Oct 7 for everything :organizers:
-DEADLINE: <2022-09-26 Mon>
+** DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [[*Early speaker notification][early speaker notification]], Oct 7 for everything :organizers:
+CLOSED: [2022-09-29 Thu 20:29] DEADLINE: <2022-09-26 Mon>
 - zaeph: will start reviewing on Sep 21
-** INPROGRESS Write preparation instructions and decide on deadline for prerecs :zaeph:
-DEADLINE: <2022-09-26 Mon>
+** DONE Write preparation instructions                               :zaeph:
+CLOSED: [2022-09-29 Thu 20:45] DEADLINE: <2022-09-26 Mon>
 2021/prepare.md can be reused.
 
+Extra stuff to consider adding:
+- DONE Suggestions for themes (especially wrt colourscape)
+- DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it's easier to write, record, and edit your voiceover, and then record the video to go along with it."
+- DONE Allowing speakers to plant questions, esp. to cover tangential stuff that couldn’t fit in the prerec
+** STANDBY Add nice-to-have stuff to prepare.md                      :zaeph:
+- org-reveal config
+- SIL fonts choice
+** TODO Prepare for prerecs                                          :zaeph:
+*** TODO Optimize ffmpeg incantation
+Remember to update [[file:prepare.md::Compression]] with the new incantation.
+*** TODO Figure out workflow for handling submitted prerecs
 We need time after the prerecs get submitted to:
 - convert the videos and check that they've been reencoded properly by watching the re-encoded ones all the way to the end
 - caption videos
 - capture any extra info
 - follow up with missing prerecs
-
-zaeph will also figure out the ffmpeg incantation for converting videos and the process for handling submitted prerecs
-
-Extra stuff to consider adding:
-- STRT Suggestions for org-reveal, fonts and themes (especially wrt colourscape)
-- DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it's easier to write, record, and edit your voiceover, and then record the video to go along with it."
-- DONE Allowing speakers to plant questions, esp. to cover tangential stuff that couldn’t fit in the prerec
-** TODO Write viewing instructions                                   :zaeph:
+** INPROGRESS Find volunteers for tech-checks                        :zaeph:
+*** DONE Add entry in 2022/volunteer.md
+*** INPROGRESS Write protocol for adding tech-checker volunteer
+- Invite volunteer to BBB (ask core organizers)
+- Update [[file:prepare.md::Tech-check]] with new tech-checker info
+- Coach tech-checker on the protocol
+*** INPROGRESS Write the tech-checking protocol (formerly referred to as “tech-checklist”)
+From previous years:
+#+begin_quote
+- Can you speak and be heard? Is there echo?
+- Can you hear the organizer?
+- Can you share your screen? Is the screen readable?
+- If you plan to show your keystrokes, is that display visible?
+- If you want to share your webcam (optional), can you enable it? Is it visible? Will there likely be distractions in the background?
+- Can you view the collaborative pad? Will you be comfortable reviewing questions on your own (perhaps by keeping it open beside your shared window), or will you need a volunteer to relay questions to you?
+- Can you share contact information (ex: phone number) so that we can get in touch with you in case of technical issues or scheduling changes?
+- Do you need help finding your way around IRC so that you can check into `#emacsconf-org`? What is your IRC nickname?
+#+end_quote
+** STANDBY Write viewing instructions                                :zaeph:
 Extra stuff to consider adding:
 - Suggestions for mpv-filter to invert colourscape.
 ** WAITING Add more submissions (CFP deadline Sept 30)              :sachac:
 DEADLINE: <2022-09-30 Fri>
 - Sacha: Add submissions to emacsconf-2022-private, draft 2-day schedule by Oct 10
-** TODO Publish talk pages   :sachac:
+** TODO Publish talk pages                                          :sachac:
 ** TODO Send early acceptances                                      :sachac:
 DEADLINE: <2022-09-30 Fri>
 
@@ -149,13 +171,13 @@ https://emacsconf.org/2022/volunteer
 ** DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [[*Early speaker notification][early speaker notification]], Oct 7 for everything :organizers:
 CLOSED: [2022-09-27 Tue 16:14] DEADLINE: <2022-09-26 Mon>
 - zaeph: will start reviewing on Sep 21
-** DONE Double-check sachac’s timezone conversions for availability :zaeph:
+** DONE Double-check sachac’s timezone conversions for availability  :zaeph:
 CLOSED: [2022-09-27 Tue 16:14]
 
 zaeph helped with this, even catching some based on e-mail timestamps
 ** DONE Copy things over from previous notebooks                    :sachac:
 CLOSED: [2022-09-21 Wed 14:12]
-** TODO Allocate extra time if possible; send e-mail  :sachac:
+** TODO Allocate extra time if possible; send e-mail                :sachac:
 SCHEDULED: <2022-10-02 Sun>
 * Things to figure out / decisions to make
 :PROPERTIES:
@@ -396,7 +418,7 @@ The roles below are related to the proposals in the early stages of the preparat
 :PROPERTIES:
 :CUSTOM_ID: other
 :END:
-** DONE Sacha: Organize volunteer information                        :sachac:
+** DONE Sacha: Organize volunteer information                       :sachac:
 ** Once talks are approved
 - sacha: Publish initial talk information pages
 - Double-check talk pages, format them nicely
@@ -1176,7 +1198,7 @@ Thanks!
 
 Sacha
 
-** TODO Early speaker notification  :sachac:
+** TODO Early speaker notification                                  :sachac:
 DEADLINE: <2022-09-30 Fri>
 
 We can accept early or send people a note saying notification of acceptance will be on Oct 15, because of the extended CFP.
diff --git a/2022/prepare.md b/2022/prepare.md
index c080a793..2f271e77 100644
--- a/2022/prepare.md
+++ b/2022/prepare.md
@@ -4,9 +4,8 @@
 This page contains notes and tips for our speakers on preparing their
 talks and presentations.  Please read through the list and consider it
 while preparing your talk.  If you have any questions, concerns, or
-suggestions please feel free to write to one of the organizers
-directly (e.g. <bandali@gnu.org>), or write to one our organizational
-mailing lists: the public <emacsconf-org@gnu.org> list, or the private
+suggestions please feel free to write to one our organizational mailing
+lists: the public <emacsconf-org@gnu.org> list, or the private
 <emacsconf-org-private@gnu.org> list, depending on the nature of the
 matter you would like to discuss.
 
@@ -16,22 +15,22 @@ updates.
 
 ### Guidelines for conduct
 
-Please review our [[guidelines for conduct|conduct]] when preparing
-your talk, to make sure we’re all on the same page and strive to make
-the event a great experience for all.  If you’re not sure whether your
-talk or presentation style meets the guidelines laid out in the
-guidelines for conduct, we’d be happy to help.  You can email Sacha
-Chua at <sacha@sachachua.com> to chat more about this.
+Please review our [[guidelines for conduct|conduct]] when preparing your
+talk to make sure we’re all on the same page and strive to make the
+event a great experience for all.  If you’re not sure whether your talk
+or presentation style meets the guidelines laid out in the guidelines
+for conduct, we’d be happy to help.  You can email Sacha Chua at
+<sacha@sachachua.com> to chat more about this.
 
 ### Recording your talk
 
 To help EmacsConf 2022 run smoothly, please prerecord your talk, and
-send us your video(s) by **November 7** at the latest (three weeks
+send us your video(s) by **November 4** at the latest (three weeks
 before the conference), to allow us enough time to do any needed
 processing (e.g. format or codec conversion) in preparation for the
 event.  Please consider submitting a prerecording as early as possible
-so that we can see if volunteers can caption your video to make it
-more accessible and searchable.
+so that we can see if volunteers can caption your video to make it more
+accessible and searchable.
 
 To make it easier for organizers and attendees to correctly pronounce
 your name, please start your video with something along the lines of:
@@ -95,27 +94,21 @@ your video recordings:
 - [Blender](//www.blender.org)
 - [Pitivi](http://www.pitivi.org)
 
-Per GNU Project’s
-[Guide to Formats](//audio-video.gnu.org/docs/formatguide.html), we
-prefer to receive prerecorded videos in formats unencumbered by
-software patents, such as `video/webm` (WebM-encoded video files, with
-`.webm` file extension) and `video/ogg` (video files encoded with the
-Theora video codec, encapsulated in an Ogg transport layer, with
-`.ogg` or `.ogv` file extension).  However, if for one reason or
+Per GNU Project’s [Guide to
+Formats](//audio-video.gnu.org/docs/formatguide.html), we prefer to
+receive prerecorded videos in formats unencumbered by software patents,
+such as `video/webm` ([WebM](https://www.webmproject.org/)-encoded video
+files, with `.webm` file extension) and `video/ogg` (video files encoded
+with the Theora video codec, encapsulated in an Ogg transport layer,
+with `.ogg` or `.ogv` file extension).  However, if for one reason or
 another you are unable to send us your prerecorded video in one of the
-above formats, you may submit them in other common formats, like
-MPEG-4 (`.mp4`), and we will try to convert them to our preferred
-formats on your behalf.
+above formats, you may submit them in other common formats, like MPEG-4
+(`.mp4`), and we will convert them to our preferred formats on your
+behalf.
 
 *Prepare recorded video in 720p (1280px by 720px) or higher, in the
 WebM format if possible.*
 
-> The conference broadcast will most likely be in
-> [720p](https://en.wikipedia.org/wiki/720p) (1280px x 720px,
-> progressive) using the [WebM](https://www.webmproject.org/) video
-> format.  The closer to this format submitted video files arrive in,
-> the easier it will be to process and upload them.
-
 # Compression
 
 If you would like to compress your video before uploading, the following shell script may be useful:
@@ -144,7 +137,7 @@ familiarize yourself with it is to run it in a test-room:
 <https://test.bigbluebutton.org/>
 
 If this is your first time at EmacsConf or if you run into any problems,
-please get in touch with us and we’ll sort things out together!  In those
+please get in touch with us and we’ll sort things out together!  In these
 cases, since we’ll need to schedule a 1-on-1 tech-check with you, we ask that
 you email the closest volunteer to your timezone in the list below (or zaeph
 if none of the timezones is a good fit).  You can also visit us at
@@ -233,7 +226,7 @@ subtle about it, so mum’s the word!
 ## I can’t figure out how to record the video.  Can I just present the talk?
 
 We might be able to help you record your talk using the BigBlueButton
-web conferencing system before November 7.  Please email
+web conferencing system before November 4.  Please email
 <emacsconf-submit@gnu.org> with some times that might work for you and
 we’ll see if a volunteer can meet up with you to record it.
 
@@ -264,7 +257,7 @@ buffer.  For a system-wide solution, you can look into
 ## I’m not used to talking to myself.  Can I present the talk to someone?
 
 We might be able to help you record your talk using the BigBlueButton
-web conferencing system before November 7.  Please email
+web conferencing system before November 4.  Please email
 <emacsconf-submit@gnu.org> with some times that might work for you and
 we’ll see if a volunteer can meet up with you to record it.
 
@@ -278,8 +271,8 @@ minimize overlap and maximize awesomeness.
 ## What if there are lots of great questions during Q&A and we run out of time?
 
 You can continue answering questions on the collaborative pad or IRC,
-and we’ll copy questions and answers onto the wiki page
-afterwards.  You can also answer questions on the wiki page even after the event.
+and we’ll copy questions and answers onto the wiki page afterwards so
+that you can answer them in your own time after the event.
 
 An extended live demo or Q&A session might be possible if someone
 volunteers to broadcast it on an alternative stream.  If you or a
diff --git a/2022/volunteer.md b/2022/volunteer.md
index 6960d1e7..037cffa6 100644
--- a/2022/volunteer.md
+++ b/2022/volunteer.md
@@ -75,13 +75,25 @@ as an IRC monitor)) and we'll schedule you in.
 
 Do you like taking notes? Volunteer to summarize interesting points
 and links from the EmacsConf talks and Q&A sessions to the Etherpad so
-that people can review them afterwards. 
+that people can review them afterwards.
 
-To volunteer as a pad scribe monitor, 
+To volunteer as a pad scribe, 
 [let us know your availability at emacsconf-org@gnu.org](mailto:emacsconf-org@gnu.org?subject=Volunteering
 as a pad scribe) (or privately: [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org?subject=Volunteering
 as a pad scribe)) and we'll schedule you in.
 
+## BigBlueButton tech-checker
+
+Are you familiar with video-conferencing, and especially with BigBlueButton?
+Would you like to help speakers get set up for their live Q&A?  If so, you can
+join the [tech-checker team](https://emacsconf.org/2022/prepare/#tech-check)
+and help us reassure speakers that everything is going to be fine!
+
+To volunteer as a BigBlueButton tech-checker, 
+[let us know your availability at emacsconf-org@gnu.org](mailto:emacsconf-org@gnu.org?subject=Volunteering
+as a BBB tech-checker) (or privately: [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org?subject=Volunteering
+as a BBB tech-checker)) and we'll schedule you in.
+
 ## Infrastructure and video
 
 Do you have an arcane cookbook filed with `ffmpeg` incantations? Is