During the harvesting phase of the conference, we work on collecting the ideas that people shared in the Q&A sessions as well as any talks that were not available as pre-recorded videos. It's a great way to help speakers get stuff out of their heads and into a form we can all learn from. Here's a process for doing so.

Add chapter markers

Chapter markers make it easier for people to jump to the part of the Q&A that they're interested in. You can see an example of chapter headings in the Q&A for asmblox. You can make a text file with the hh:mm:ss or mm:ss timestamps and the chapter headings.

00:00 Introduction
01:12 Why did you choose an internal state versus many 'state buffers'?
02:10 Do you have plans to port shenzhen.io to Emacs?
02:29 Did this use WASM?
02:59 Why wasm rather than a more traditional Assembly dialect? It wouldn't be harder to implement, right?
05:08 Any next projects on your mind?
05:52 Does this work with any other paren-based editing packages?
06:46 What kind of tool could use this idea?
07:56 How did you go about designing the puzzles?
08:39 What are your favorite changes in the upcoming Emacs 29?
09:07 Are there tools to add more puzzles?

If you're not sure how something is spelled, you can look at the list of questions asked during the Q&A sessions by going to the wiki page for the talk (see the links from talks), or indicating it with ??.

Alternatively, you can edit the VTT file (--bbb-webcams.vtt) and add NOTE comments with the chapter headings before the subtitles that are part of that chapter. If you're using subed to edit subtitles within Emacs, you can split the subtitle as needed with M-. (subed-split-subtitle) so that the subtitle starts with the question. You don't have to worry about getting the timestamps exact, as we can re-align them with M-x subed-align. Here's what that NOTE comment can look like:

NOTE Why did you choose an internal state versus many 'state buffers'?

00:01:12.600 --> 00:01:16.039
Okay. So, the first question is why did you choose an internal state

These can then be extracted with emacsconf-subed-make-chapter-file-based-on-comments from emacsconf-subed.el and included in our publishing workflow.

Edit the transcript

If you want to make it even easier for people to learn from the Q&A, you can edit the transcript so that it can also be published on the wiki page. See Captioning tips.

EmacsConf 2022 status update: asmblox, async, buttons, dbus, detached, eshell all have large-model Whisper transcripts. The rest have small-model Whisper transcripts that might need lots of extra editing, so you can either use them just for chapter markers, wait for the better transcripts (ETA Dec 15 or so), or work with the ones made with a small model.