summaryrefslogtreecommitdiffstats
path: root/2022
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2022-11-13 08:24:59 -0500
committerSacha Chua <sacha@sachachua.com>2022-11-13 08:24:59 -0500
commit7bb861108a335184dfc9df883a2b8d61762beaeb (patch)
treedef8a8e7d19ccad5a7eb5f6affa3528bc1499657 /2022
parent1d5b69de743b32ca92ea40b9c7a1b7ca178b1532 (diff)
downloademacsconf-wiki-7bb861108a335184dfc9df883a2b8d61762beaeb.tar.xz
emacsconf-wiki-7bb861108a335184dfc9df883a2b8d61762beaeb.zip
Add an anchor for the mastering section
Diffstat (limited to '')
-rw-r--r--2022/organizers-notebook.md514
-rw-r--r--2022/organizers-notebook/index.org20
2 files changed, 297 insertions, 237 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index bab6ec3c..58793825 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -8,7 +8,6 @@ This file is automatically exported from [/2022/organizers-notebook/index.org](/
- [Cadence](#cadence)
- [Overall priorities](#overall)
-- [Time-sensitive](#time-sensitive)
- [Projects and other long-running tasks](#projects)
- [Projects to bear in mind but which are not actual](#maybe-projects)
- [Things to figure out / decisions to make](#decisions)
@@ -20,16 +19,7 @@ This file is automatically exported from [/2022/organizers-notebook/index.org](/
- [Supporting code](#code)
- [Lessons learned](#lessons)
-Time-sensitive tasks:
-
-- [Send prerec reminder](#prerec-reminder)
-- [Use Mumble for backchannel coordination and also on-stage](#mumble)
-- [Make a linear hyperlist for managing EmacsConf](#hyperlist):sachac:
-- [Send schedule-published email for emacsconf-discuss](#announce-program):needsowner:timesensitive:email:
-- [Flesh out prepare.md for audio-recording tips before the prerec-deadline](#prepare-audio):zaeph:
-- [Volunteer update](#volunteer-2022-11-14)
-
-Other projects:
+Projects and tasks:
- [Record intro/outro for day-1 and day-2](#rec-intro):zaeph:
- [Prepare for prerecs](#prepare-prerec-process):zaeph:
@@ -53,6 +43,9 @@ Other projects:
- [Set up BBB rooms and update conf.org](#create-bbb):sachac:
- [Coordinate and help volunteers](#coordinate-volunteers):sachac:
- [Investigate streaming options, maybe OBS in the cloud](#streaming):sachac:
+- [Use Mumble for backchannel coordination and also on-stage](#mumble)
+- [Volunteer update](#volunteer-2022-11-14)
+- [Make a linear hyperlist for managing EmacsConf](#hyperlist):sachac:
Schedule by status: (gray: waiting, light yellow: processing, yellow: to assign, light green: captioning, green: captioned and ready) - Updated by conf.org and the wiki repository
@@ -381,142 +374,6 @@ interests you!
</table>
-<a id="time-sensitive"></a>
-
-# Time-sensitive
-
-Ordered chronologically (and therefore by importance).
-
-- [Send prerec reminder](#prerec-reminder)
-- [Use Mumble for backchannel coordination and also on-stage](#mumble)
-- [Make a linear hyperlist for managing EmacsConf](#hyperlist):sachac:
-- [Send schedule-published email for emacsconf-discuss](#announce-program):needsowner:timesensitive:email:
-- [Flesh out prepare.md for audio-recording tips before the prerec-deadline](#prepare-audio):zaeph:
-- [Volunteer update](#volunteer-2022-11-14)
-
-
-<a id="prerec-reminder"></a>
-
-## TODO Send prerec reminder
-
-
-### TODO Update logbook with notes from e-mails :zaeph:
-
-
-### TODO Follow up with speakers based on their availability
-
-
-<a id="mumble"></a>
-
-## TODO Use Mumble for backchannel coordination and also on-stage
-
-
-### TODO Make sure volunteers can access Mumble :sachac:
-
-- [ ] FlowyCoder
-- [ ] jman
-- [ ] vetrivln
-
-
-### DONE Generate certificates, add them to conf.org, and register the users :sachac:
-
-
-### TODO Let sachac know how to manage the Mumble server, or update the config :bandali:
-
-- [ ] Add emacsconf-gen and emacsconf-dev channels
-- [ ] Give the emacsconf-gen and emacsconf-dev users access to them
-- [ ] Give the other organizers access to emacsconf-gen, emacsconf-dev, and org-private
-
-
-<a id="hyperlist"></a>
-
-## DONE Make a linear hyperlist for managing EmacsConf :sachac:
-
-Goal:
-
-- Volunteers should be able to coordinate everything by stepping through a linear list of things to do
-- The hyperlist will primarily live on orga@res.emacsconf.org and be accessed through emacsclient. (Maybe sat.org and sun.org)
-- Volunteers should be able to take breaks as needed
-
-- 9:05 Journalism
- - [ ] Check ${name} into <span class="underline">BBB room</span>
- - [X] [Start talk]((emacsconf-update-talk-status "journalism" "." "PLAYING"))
- - [X] [Start closed Q&A]((emacsconf-update-talk-status "journalism" "." "CLOSED_Q"))
- - [ ] [Open Q&A]((emacsconf-update-talk-status "journalism" "." "OPEN_Q"))
- - [ ] [Mark Q&A as unstreamed]((emacsconf-update-talk-status "journalism" "." "UNSTREAMED_Q"))
- - [ ] [Finish talk]((emacsconf-update-talk-status "journalism" "." "TO_ARCHIVE"))
-- 9:40 Handwritten
- - [ ] [Start talk]((emacsconf-update-talk-status "handwritten" "." "PLAYING"))
- - [ ] [Start closed Q&A]((emacsconf-update-talk-status "handwritten" "." "CLOSED_Q"))
- - [ ] [Open Q&A]((emacsconf-update-talk-status "handwritten" "." "OPEN_Q"))
- - [ ] [Mark Q&A as unstreamed]((emacsconf-update-talk-status "handwritten" "." "UNSTREAMED_Q"))
- - [ ] [Finish talk]((emacsconf-update-talk-status "handwritten" "." "TO_ARCHIVE"))
-
-See sat.org and sun.org in the conf private repo
-
-
-<a id="announce-program"></a>
-
-## DONE Send schedule-published email for emacsconf-discuss :needsowner:timesensitive:email:
-
-Schedule is now available; post to emacsconf-discuss, emacs-tangents
-<https://lists.gnu.org/archive/html/emacsconf-discuss/2022-10/msg00000.html>
-
-
-### DONE Post it to r/emacs as well :reddit:zaeph:
-
-Please let zaeph know when it’s live so that the post can be distinguished.
-
-
-### Template
-
-Greetings, fellow Emacsians!
-
-On behalf of the EmacsConf 2022 organizers team, I&rsquo;m very excited to
-announce the schedule for EmacsConf 2022 (Dec 3 and 4), available at:
-
-<https://emacsconf.org/2022/talks>
-
-All of the times listed on the schedule are in EST (UTC-5). You can
-click on each talk&rsquo;s title to open its page for more information,
-including its scheduled time in your local time. (Displaying local time
-requires running a tiny bit of AGPLv3+-licensed free/libre JavaScript
-code, included on the talk pages.)
-
-For prerecorded talks, this time is also when the talk&rsquo;s video will be
-made available on the same page. Please note that the times are
-approximations, and that the schedule may change leading up to the
-conference.
-
-As the conference approaches, we&rsquo;ll post more details on how to watch
-and participate.
-
-You can subscribe to the emacsconf-discuss mailing list at
-<https://lists.gnu.org/mailman/listinfo/emacsconf-discuss> to
-be sure you&rsquo;ll get updates.
-
-Want to help make EmacsConf even awesomer? Volunteer!
-<https://emacsconf.org/2022/volunteer/>
-
-We hope to see you all around on Dec 3-4 for EmacsConf 2022!
-
-P.S. please direct all replies to this post either to myself or to the
-emacsconf-discuss list, so as to help avoid generating extra off-topic
-chatter in the other lists cc&rsquo;d in this message; thank you.
-
-
-<a id="prepare-audio"></a>
-
-## DONE Flesh out prepare.md for audio-recording tips before the prerec-deadline :zaeph:
-
-
-<a id="volunteer-2022-11-14"></a>
-
-## Volunteer update
-
-- talk banners, akshay
-
-
<a id="projects"></a>
# Projects and other long-running tasks
@@ -543,6 +400,9 @@ chatter in the other lists cc&rsquo;d in this message; thank you.
- [Set up BBB rooms and update conf.org](#create-bbb):sachac:
- [Coordinate and help volunteers](#coordinate-volunteers):sachac:
- [Investigate streaming options, maybe OBS in the cloud](#streaming):sachac:
+- [Use Mumble for backchannel coordination and also on-stage](#mumble)
+- [Volunteer update](#volunteer-2022-11-14)
+- [Make a linear hyperlist for managing EmacsConf](#hyperlist):sachac:
Ordered by importance.
@@ -1101,24 +961,33 @@ great to have you on board.${wrap}
We&rsquo;ve set up ${backstage} as the backstage area where you can view the
videos and resources uploaded so far. You can access it with the
username "${backstage-user}&ldquo; and the password &rdquo;${backstage-password}&ldquo;.
-Please keep the backstage password and other speakers&rsquo; talk resources
-secret. If you see a talk that you&rsquo;d like to caption, you can e-mail
-me at sacha@sachachua.com and I can reserve it for you. Then you can
-correct any misrecognized words, fix capitalizations, remove filler
-words as needed, and so on.${wrap}
-
-You can find captioning tips at <https://emacsconf.org/captioning/> .
-Feel free to use your favourite subtitle editor, and you can convert
-it to whatever format you like. If you prefer to work with plain text,
-we can probably even figure out the timestamps afterwards.
-
-Let me know if you want to reserve a talk for captioning or if you
-have any questions or suggestions. Thank you!
+Please keep the backstage password and resources secret. If you see a
+talk that you&rsquo;d like to caption, you can e-mail me at
+sacha@sachachua.com and I can reserve it for you. Then you can correct
+any misrecognized words, fix capitalizations, remove filler words as
+needed, and so on.${wrap}
+
+You&rsquo;ll probably want to work with either the VTT or the TXT versions
+(VTT is WebVTT format and has timestamps), but you can check the other
+talk resources in case the speaker has posted scripts or other useful
+things. Both VTT and TXT are plain text, so feel free to use your
+favourite text or subtitle editor. I&rsquo;ve posted a brief demo of how I
+edit captions at
+<https://media.emacsconf.org/2022/backstage/editing-captions.html> , and
+you can find more captioning tips at <https://emacsconf.org/captioning/>
+. You can convert it to whatever format you like. If you prefer to
+work with plain text, we can figure out the timestamps afterwards.
+
+Let me know if you want to reserve a talk for captioning or if you have
+any questions or suggestions. We&rsquo;re also in the #emacsconf-org channel
+on the libera.chat IRC network, which you can connect to with your
+favourite IRC client or through the web-based interface at
+<https://chat.emacsconf.org/> .
Sacha Chua
-### TODO Support cue IDs in subed-vtt.el
+### DONE Support cue IDs in subed-vtt.el
### TODO jiwer · PyPI - measure error rate
@@ -1402,6 +1271,8 @@ Dry run checklist:
- [ ] Adjust the volume in OBS
- [ ] SSH to the server and play a video off-screen
- [ ] SSH to the server with X forwarding and adjust the volume off-screen
+
+ add kitty-terminfo
### Broadcasting from local OBS (option A)
@@ -1461,6 +1332,8 @@ Dry run checklist:
You can play a video with `play video-id` (ex: `play meetups`), or you can specify the filename (ex: ~play ~/stream/emacsconf-2022-meetups\*.webm).
+ termit: Ctrl-Shift-t makes a new tab
+
i3 cheat sheet:
- Alt-Enter creates a terminal
@@ -1473,6 +1346,8 @@ Dry run checklist:
- Alt-Shift-Left moves the current window to the left
- Alt-Shift-Right moves the current window to the right
+TODO add kitty and kitty-terminfo to install
+
1. Test Q&A. You can either wait for the video to finish or quit it with &ldquo;q&rdquo;.
You can paste in the URLs or use
`firefox /data/emacsconf/2022/index-$TRACK.html`
@@ -1689,6 +1564,69 @@ so that the streamer can adjust volume offscreen?
### TODO recruit at least one more person to help operate the &ldquo;video bouncer&rdquo;
+<a id="mumble"></a>
+
+## TODO Use Mumble for backchannel coordination and also on-stage
+
+
+### TODO E-mail volunteers and help them get on Mumble :bandali:
+
+- [ ] FlowyCoder
+- [ ] jman
+- [ ] vetrivln
+
+
+### TODO Update the Mumble setup :bandali:
+
+- [ ] Add emacsconf-gen and emacsconf-dev channels
+- [ ] Give the emacsconf-gen and emacsconf-dev users access to them
+- [ ] Give the other organizers access to emacsconf-gen, emacsconf-dev, and org-private
+
+
+### DONE Generate certificates, add them to conf.org, and register the users :sachac:
+
+
+<a id="volunteer-2022-11-14"></a>
+
+## Volunteer update
+
+- talk banners, akshay
+
+
+<a id="hyperlist"></a>
+
+## TODO Make a linear hyperlist for managing EmacsConf :sachac:
+
+Goal:
+
+- Volunteers should be able to coordinate everything by stepping through a linear list of things to do
+- The hyperlist will primarily live on orga@res.emacsconf.org and be accessed through emacsclient. (Maybe sat.org and sun.org)
+- Volunteers should be able to take breaks as needed
+
+- 9:05 Journalism
+ - [ ] Check ${name} into <span class="underline">BBB room</span>
+ - [X] [Start talk]((emacsconf-update-talk-status "journalism" "." "PLAYING"))
+ - [X] [Start closed Q&A]((emacsconf-update-talk-status "journalism" "." "CLOSED_Q"))
+ - [ ] [Open Q&A]((emacsconf-update-talk-status "journalism" "." "OPEN_Q"))
+ - [ ] [Mark Q&A as unstreamed]((emacsconf-update-talk-status "journalism" "." "UNSTREAMED_Q"))
+ - [ ] [Finish talk]((emacsconf-update-talk-status "journalism" "." "TO_ARCHIVE"))
+- 9:40 Handwritten
+ - [ ] [Start talk]((emacsconf-update-talk-status "handwritten" "." "PLAYING"))
+ - [ ] [Start closed Q&A]((emacsconf-update-talk-status "handwritten" "." "CLOSED_Q"))
+ - [ ] [Open Q&A]((emacsconf-update-talk-status "handwritten" "." "OPEN_Q"))
+ - [ ] [Mark Q&A as unstreamed]((emacsconf-update-talk-status "handwritten" "." "UNSTREAMED_Q"))
+ - [ ] [Finish talk]((emacsconf-update-talk-status "handwritten" "." "TO_ARCHIVE"))
+
+See sat.org and sun.org in the conf private repo
+
+Try them in an Etherpad
+
+[How do we want to coordinate during the conference itself?](#coordination)
+
+
+### TODO Try writing it to an Etherpad
+
+
<a id="maybe-projects"></a>
# Projects to bear in mind but which are not actual
@@ -1707,7 +1645,7 @@ Note on how DebConf handled incidents:
# Things to figure out / decisions to make
-- [How do we want to handle organizer audio?](#org40d1de4)
+- [How do we want to coordinate during the conference itself?](#coordination)
- [How do we want to make the full schedule more manageable?](#sched-decision)
- [How much do we want to enrich the wiki with JS?](#wiki-design)
- [What ideas do we want to borrow from other conferences?](#other-confs)
@@ -1721,15 +1659,27 @@ Note on how DebConf handled incidents:
- [Decision archive](#decision-archive)
-<a id="org40d1de4"></a>
+<a id="coordination"></a>
+
+## How do we want to coordinate during the conference itself?
-## How do we want to handle organizer audio?
+- Considerations:
+ - Good to have something that the hosts and streamers can walk through step by step
+ - Do we want the check-in volunteer to also keep something
+ - Announcing and publishing are easier if the task states are updated
- Mumble for walkie-talkie communications?
- Can we keep it off the stream more reliably, but still be able to choose to put it on the stream?
- We can keep it in the combined sink and then manually go to that
channel in our clients when we want to talk on stream
- Should we have a Gen channel and a Dev channel so that we can choose to speak into ?
+- Checklist
+ - Etherpad
+ - All the volunteers can access it easily
+ - Tasks can be updated through SSH commands
+ - conf.org
+ - Run Emacs commands directly from it
+ - A little trickier in terms of access
<a id="sched-decision"></a>
@@ -2145,7 +2095,7 @@ AM: 9-12 PM EST, PM: 1-5 PM EST (plus a little extra for setup/transition)
Saturday Dec 3
-<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="orge500349" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>
@@ -2158,66 +2108,67 @@ Saturday Dec 3
<col class="org-left" />
<col class="org-left" />
+
+<col class="org-left" />
</colgroup>
-<tbody>
+<thead>
<tr>
-<td class="org-left">&#xa0;</td>
-<td class="org-left">Gen AM</td>
-<td class="org-left">Gen PM</td>
-<td class="org-left">Dev AM</td>
-<td class="org-left">Dev PM</td>
+<th scope="col" class="org-left">&#xa0;</th>
+<th scope="col" class="org-left">Host</th>
+<th scope="col" class="org-left">Streamer</th>
+<th scope="col" class="org-left">Checkin</th>
+<th scope="col" class="org-left">IRC</th>
+<th scope="col" class="org-left">Pad</th>
</tr>
+</thead>
-
+<tbody>
<tr>
-<td class="org-left">Host</td>
-<td class="org-left">zaeph</td>
+<td class="org-left">Gen AM</td>
<td class="org-left">zaeph</td>
-<td class="org-left">bandali</td>
-<td class="org-left">vetrivln</td>
-</tr>
-
-
-<tr>
-<td class="org-left">Streamer</td>
<td class="org-left">corwin</td>
-<td class="org-left">corwin</td>
-<td class="org-left">bandali</td>
-<td class="org-left">bandali</td>
+<td class="org-left">sachac</td>
+<td class="org-left">sachac</td>
+<td class="org-left">publicvoit</td>
</tr>
<tr>
-<td class="org-left">Check-in</td>
-<td class="org-left">sachac</td>
+<td class="org-left">Gen PM</td>
+<td class="org-left">zaeph</td>
+<td class="org-left">corwin</td>
<td class="org-left">FlowyCoder</td>
-<td class="org-left">&#xa0;</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">dto</td>
+<td class="org-left">publicvoit</td>
</tr>
<tr>
-<td class="org-left">IRC</td>
+<td class="org-left">Dev AM</td>
+<td class="org-left">bandali</td>
+<td class="org-left">bandali</td>
<td class="org-left">sachac</td>
<td class="org-left">dto</td>
-<td class="org-left">dto</td>
-<td class="org-left">vetrivln</td>
+<td class="org-left">&#xa0;</td>
</tr>
<tr>
-<td class="org-left">Pad</td>
-<td class="org-left">publicvoit</td>
-<td class="org-left">publicvoit (until 4pm)</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">Dev PM</td>
+<td class="org-left">vetrivln</td>
+<td class="org-left">bandali</td>
+<td class="org-left">FlowyCoder</td>
+<td class="org-left">vetrivln</td>
<td class="org-left">&#xa0;</td>
</tr>
</tbody>
</table>
+publicvoit - pad until 4pm on Sat, until 2pm on Sun
+
Sunday Dec 4
-<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="orgce0b88c" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>
@@ -2230,58 +2181,57 @@ Sunday Dec 4
<col class="org-left" />
<col class="org-left" />
+
+<col class="org-left" />
</colgroup>
-<tbody>
+<thead>
<tr>
-<td class="org-left">&#xa0;</td>
-<td class="org-left">Gen AM</td>
-<td class="org-left">Gen PM</td>
-<td class="org-left">Dev AM</td>
-<td class="org-left">Dev PM</td>
+<th scope="col" class="org-left">&#xa0;</th>
+<th scope="col" class="org-left">Host</th>
+<th scope="col" class="org-left">Streamer</th>
+<th scope="col" class="org-left">Checkin</th>
+<th scope="col" class="org-left">IRC</th>
+<th scope="col" class="org-left">Pad</th>
</tr>
+</thead>
-
+<tbody>
<tr>
-<td class="org-left">Host</td>
-<td class="org-left">zaeph</td>
+<td class="org-left">Gen AM</td>
<td class="org-left">zaeph</td>
-<td class="org-left">bandali</td>
-<td class="org-left">vetrivln</td>
-</tr>
-
-
-<tr>
-<td class="org-left">Streamer</td>
<td class="org-left">corwin</td>
-<td class="org-left">jman</td>
-<td class="org-left">bandali</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">sachac</td>
+<td class="org-left">sachac</td>
+<td class="org-left">publicvoit</td>
</tr>
<tr>
-<td class="org-left">Check-in</td>
-<td class="org-left">sachac</td>
+<td class="org-left">Gen PM</td>
+<td class="org-left">zaeph</td>
+<td class="org-left">jman</td>
<td class="org-left">FlowyCoder</td>
-<td class="org-left">&#xa0;</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">dto</td>
+<td class="org-left">publicvoit</td>
</tr>
<tr>
-<td class="org-left">IRC</td>
+<td class="org-left">Dev AM</td>
+<td class="org-left">bandali</td>
+<td class="org-left">bandali</td>
<td class="org-left">sachac</td>
<td class="org-left">dto</td>
-<td class="org-left">dto</td>
-<td class="org-left">vetrivln</td>
+<td class="org-left">&#xa0;</td>
</tr>
<tr>
-<td class="org-left">Pad</td>
-<td class="org-left">publicvoit</td>
-<td class="org-left">publicvoit (until 2pm)</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">Dev PM</td>
+<td class="org-left">vetrivln</td>
+<td class="org-left">bandali</td>
+<td class="org-left">FlowyCoder</td>
+<td class="org-left">vetrivln</td>
<td class="org-left">&#xa0;</td>
</tr>
</tbody>
@@ -2295,6 +2245,45 @@ Backups:
Interested in a shift? Please e-mail <mailto:emacsconf-org-private@gnu.org> and we&rsquo;ll help you figure out what you need to learn.
+ `(setq emacsconf-shifts
+ (list
+ ,@(apply #'append
+ (mapcar
+ (lambda (day)
+ (let ((headers (mapcar (lambda (field) (intern (concat ":" (downcase field))))
+ (cdr (car (cadr day))))))
+ (mapcar
+ (lambda (row)
+ (apply #'append
+ (list 'list :id
+ (when (string-match "^\\([^ ]+\\) \\(AM\\|PM\\)" (car row))
+ (format "%s-%s-%s"
+ (car day)
+ (downcase (match-string 2 (car row)))
+ (downcase (match-string 1 (car row)))))
+ :track
+ (if (string-match "^Gen" (car row)) "General" "Development")
+ :start
+ (format "%sT%s:00:00%s"
+ (elt day 2)
+ (if (string-match "AM" (car row)) "08" "13")
+ emacsconf-timezone-offset)
+ :end
+ (format "%sT%s:00:00%s"
+ (elt day 2)
+ (if (string-match "AM" (car row)) "12" "18")
+ emacsconf-timezone-offset))
+ (seq-map-indexed
+ (lambda (value index)
+ (unless (string= value "")
+ (list (elt headers index) value)))
+ (cdr row))))
+ (cdr (cadr day)))
+ ))
+ (list
+ (list "sat" sat "2022-12-03")
+ (list "sun" sun "2022-12-04"))))))
+
## After the conference
@@ -2615,10 +2604,11 @@ model-based filters after.
#### Audacity workflow
When we process a prerec, we extract the audio of the original upload
-and add it to the backstage. You should be able to find it under the
-name &#x2013;original.$audio\_format. If it’s not there, it’s easy to extract
-the audio from the original video, but we’d prefer if you warned
-core-organizers about it because it’s not normal.
+and add it to the backstage. You should be able to find it under the
+name &#x2013;original.$audio\_format or &#x2013;main.$audio\_format. If it’s not
+there, it’s easy to extract the audio from the original video, but
+we’d prefer if you warned core-organizers about it because it’s not
+normal.
We’ve simplified the process down to these steps:
@@ -3222,7 +3212,7 @@ Probably focus on grabbing the audio first and seeing what&rsquo;s worth keeping
Make a table of the form
-<table id="org02d187a" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="org1e85b1f" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>
@@ -4549,6 +4539,68 @@ EmacsConf is a little less than four weeks away. Stuff is happening!
Sacha
+## DONE Send prerec reminder :sachac:
+
+
+### DONE Update logbook with notes from e-mails :sachac:
+
+
+### DONE Follow up with speakers based on their availability
+
+
+<a id="announce-program"></a>
+
+## DONE Send schedule-published email for emacsconf-discuss :needsowner:timesensitive:email:
+
+Schedule is now available; post to emacsconf-discuss, emacs-tangents
+<https://lists.gnu.org/archive/html/emacsconf-discuss/2022-10/msg00000.html>
+
+
+### DONE Post it to r/emacs as well :reddit:zaeph:
+
+Please let zaeph know when it’s live so that the post can be distinguished.
+
+
+### Template
+
+Greetings, fellow Emacsians!
+
+On behalf of the EmacsConf 2022 organizers team, I&rsquo;m very excited to
+announce the schedule for EmacsConf 2022 (Dec 3 and 4), available at:
+
+<https://emacsconf.org/2022/talks>
+
+All of the times listed on the schedule are in EST (UTC-5). You can
+click on each talk&rsquo;s title to open its page for more information,
+including its scheduled time in your local time. (Displaying local time
+requires running a tiny bit of AGPLv3+-licensed free/libre JavaScript
+code, included on the talk pages.)
+
+For prerecorded talks, this time is also when the talk&rsquo;s video will be
+made available on the same page. Please note that the times are
+approximations, and that the schedule may change leading up to the
+conference.
+
+As the conference approaches, we&rsquo;ll post more details on how to watch
+and participate.
+
+You can subscribe to the emacsconf-discuss mailing list at
+<https://lists.gnu.org/mailman/listinfo/emacsconf-discuss> to
+be sure you&rsquo;ll get updates.
+
+Want to help make EmacsConf even awesomer? Volunteer!
+<https://emacsconf.org/2022/volunteer/>
+
+We hope to see you all around on Dec 3-4 for EmacsConf 2022!
+
+P.S. please direct all replies to this post either to myself or to the
+emacsconf-discuss list, so as to help avoid generating extra off-topic
+chatter in the other lists cc&rsquo;d in this message; thank you.
+
+
+## DONE Flesh out prepare.md for audio-recording tips before the prerec-deadline :zaeph:
+
+
<a id="comms"></a>
# Communications
diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org
index bf68afc2..3bc1be96 100644
--- a/2022/organizers-notebook/index.org
+++ b/2022/organizers-notebook/index.org
@@ -623,8 +623,11 @@ you can find more captioning tips at https://emacsconf.org/captioning/
. You can convert it to whatever format you like. If you prefer to
work with plain text, we can figure out the timestamps afterwards.
-Let me know if you want to reserve a talk for captioning or if you
-have any questions or suggestions. Thank you!
+Let me know if you want to reserve a talk for captioning or if you have
+any questions or suggestions. We're also in the #emacsconf-org channel
+on the libera.chat IRC network, which you can connect to with your
+favourite IRC client or through the web-based interface at
+https://chat.emacsconf.org/ .
Sacha Chua
*** DONE [#C] Support cue IDs in subed-vtt.el
@@ -1944,6 +1947,10 @@ before the conference!
Sacha Chua
*** Mastering the prerec’s audio-track
+:PROPERTIES:
+:CUSTOM_ID: mastering
+:END:
+
Mastering is the process of preparing an audio-track for a purpose. For
us, the purpose is quite simple: maximize the intelligibility of the
speaker and minimize the noise.
@@ -1958,10 +1965,11 @@ model-based filters after.
**** Audacity workflow
When we process a prerec, we extract the audio of the original upload
-and add it to the backstage. You should be able to find it under the
-name --original.$audio_format. If it’s not there, it’s easy to extract
-the audio from the original video, but we’d prefer if you warned
-core-organizers about it because it’s not normal.
+and add it to the backstage. You should be able to find it under the
+name --original.$audio_format or --main.$audio_format. If it’s not
+there, it’s easy to extract the audio from the original video, but
+we’d prefer if you warned core-organizers about it because it’s not
+normal.
We’ve simplified the process down to these steps: