Reorganize, add tocs

2 files changed, 295 insertions, 207 deletions

diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index 3bfe56bc..9361a991 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -101,30 +101,28 @@ Planned dates and phases:
 Current phase: No prerecs to process yet, so it's a good time to focus
 on infrastructure
 
--   [Time-sensitive](#org2db84f2)
--   [Projects and other long-running tasks](#org1e6b753)
--   [Projects to bear in mind but which are not actual](#orgd21e52c)
--   [Find volunteers for tech-checks](#org53ebeba):zaeph:
--   [Add nice-to-have stuff to prepare.md](#orgce43a0a):zaeph:
--   [Write viewing instructions](#org6e7cc99):zaeph:
--   [Add category tags and possibly links between talks across 2022 and all previous years](#org48fafc0):needsowner:wiki:
--   [Archive](#orga41dec5):ARCHIVE:
+-   [Time-sensitive](#org3a2dd47)
+-   [Projects and other long-running tasks](#org485507e)
+-   [Projects to bear in mind but which are not actual](#maybe-projects)
+-   [Find volunteers for tech-checks](#tech-checks):zaeph:
+-   [Update viewing instructions and watch pages](#write-viewing):zaeph:
+-   [Add category tags and possibly links between talks across 2022 and all previous years](#link-pages):needsowner:wiki:
 
 
-<a id="org2db84f2"></a>
+<a id="org3a2dd47"></a>
 
 ## Time-sensitive
 
 Ordered chronologically (and therefore by importance).
 
--   [Volunteer communications: E-mail update for Oct 9, 2022](#org23e51b3):email:volunteers:
--   [Remind people about confirming e-mail communications](#org32b3b9e):sachac:email:speakers:
--   [Send people schedule information and doublecheck their availability/Q&A preference](#org2ab6c80):sachac:email:speakers:
--   [Send program-published email for emacsconf-discuss](#org70e448d):needsowner:timesensitive:email:
--   [Prepare email for nudging speakers to send prerec, and inform on upload workflow](#org231f141):timesensitive:needsowner:
+-   [Volunteer communications: E-mail update for Oct 9, 2022](#volunteer-2022-10-09):email:volunteers:
+-   [Remind people about confirming e-mail communications](#confirm-email):sachac:email:speakers:
+-   [Send people schedule information and doublecheck their availability/Q&A preference](#check-sched):sachac:email:speakers:
+-   [Send program-published email for emacsconf-discuss](#announce-program):needsowner:timesensitive:email:
+-   [Prepare email for nudging speakers to send prerec, and inform on upload workflow](#mail-upload):timesensitive:needsowner:
 
 
-<a id="org23e51b3"></a>
+<a id="volunteer-2022-10-09"></a>
 
 ### Volunteer communications: E-mail update for Oct 9, 2022     :email:volunteers:
 
@@ -152,19 +150,19 @@ Help wanted / upcoming tasks:
 You're receiving this e-mail because you're on the emacsconf-org mailing list.
 
 
-<a id="org32b3b9e"></a>
+<a id="confirm-email"></a>
 
 ### TODO Remind people about confirming e-mail communications     :sachac:email:speakers:
 
-Look for the TO\_CONFIRM status
+Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
 
 
-<a id="org2ab6c80"></a>
+<a id="check-sched"></a>
 
 ### TODO Send people schedule information and doublecheck their availability/Q&A preference     :sachac:email:speakers:
 
 
-<a id="org70e448d"></a>
+<a id="announce-program"></a>
 
 ### TODO Send program-published email for emacsconf-discuss     :needsowner:timesensitive:email:
 
@@ -191,25 +189,24 @@ to their availability, and will add the allocated time slots for the
 talks in the coming weeks.
 
 
-<a id="org231f141"></a>
+<a id="mail-upload"></a>
 
 ### BLOCKED Prepare email for nudging speakers to send prerec, and inform on upload workflow     :timesensitive:needsowner:
 
 Blocked by [Figure out web-based file upload](#upload)
 
 
-<a id="org1e6b753"></a>
+<a id="org485507e"></a>
 
 ## Projects and other long-running tasks
 
 -   [Figure out web-based file upload](#upload):needsowner:zaeph:bandali:
--   [Prepare for prerecs](#org2bbef8d):zaeph:
--   [Delete all the EmacsConf BBB rooms from last year](#orgc2e46a9):chore:bbb:
--   [Investigate streaming options, maybe OBS in the cloud](#obscloud):corwin:zaeph:
--   [Work on the OBS scenes](#org73749aa):zaeph:corwin:
--   [Create Org heading for scheduling caption team's live IRC duty shifts](#org8582971):dto:
--   [Move scheduling and publishing code to Emacs on a VPS so that other people can help out](#org8a922d4):sachac:
--   [Add nice-to-have stuff to prepare.md](#org8d8ea6c):zaeph:
+-   [Prepare for prerecs](#prepare-prerec-process):zaeph:
+-   [Delete all the EmacsConf BBB rooms from last year](#bbb-cleanup):chore:bbb:
+-   [Investigate streaming options, maybe OBS in the cloud](#streaming):corwin:zaeph:
+-   [Work on the OBS scenes](#obs-scenes):zaeph:corwin:
+-   [Move scheduling and publishing code to Emacs on a VPS so that other people can help out](#publishing-vps):sachac:
+-   [Add nice-to-have stuff to prepare.md](#extra-prepare):zaeph:
 
 Ordered by importance.
 
@@ -263,7 +260,7 @@ Considerations:
 #### TODO Notify speakers when the final solution is available
 
 
-<a id="org2bbef8d"></a>
+<a id="prepare-prerec-process"></a>
 
 ### TODO Prepare for prerecs     :zaeph:
 
@@ -283,7 +280,7 @@ We need time after the prerecs get submitted to:
 -   follow up with missing prerecs
 
 
-<a id="orgc2e46a9"></a>
+<a id="bbb-cleanup"></a>
 
 ### TODO Delete all the EmacsConf BBB rooms from last year     :chore:bbb:
 
@@ -291,7 +288,7 @@ For the admins on BBB.  The list is accessible here: [Organization Settings](htt
 Should take no more than ~20′.
 
 
-<a id="obscloud"></a>
+<a id="streaming"></a>
 
 ### TODO Investigate streaming options, maybe OBS in the cloud     :corwin:zaeph:
 
@@ -316,21 +313,14 @@ Resources:
 #### TODO corwin: recruit at least one more person to help operate the "video bouncer"     :corwin:
 
 
-<a id="org73749aa"></a>
+<a id="obs-scenes"></a>
 
 ### TODO Work on the OBS scenes     :zaeph:corwin:
 
 -   [ ] corwin is out from Nov 11-20, and we should start working on them before then.
 
 
-<a id="org8582971"></a>
-
-### CANCELLED Create Org heading for scheduling caption team's live IRC duty shifts     :dto:
-
-See [Shifts](#shifts)
-
-
-<a id="org8a922d4"></a>
+<a id="publishing-vps"></a>
 
 ### Move scheduling and publishing code to Emacs on a VPS so that other people can help out     :sachac:
 
@@ -343,11 +333,13 @@ Where:
 
 -   front? my own VPS?
     
+    Nice if there's an Ansible playbook
+    
     sachac's notes:
     <file:///home/sacha/code/docker/emacsconf-publish/>
 
 
-<a id="org8d8ea6c"></a>
+<a id="extra-prepare"></a>
 
 ### STANDBY Add nice-to-have stuff to prepare.md     :zaeph:
 
@@ -355,7 +347,7 @@ Where:
 -   SIL fonts choice
 
 
-<a id="orgd21e52c"></a>
+<a id="maybe-projects"></a>
 
 ## Projects to bear in mind but which are not actual
 
@@ -365,8 +357,11 @@ Where:
 We’re not sure if we’re going to get a presentation or a prerec for them
 this year, but we need to keep this at the back of our minds.
 
+Note on how DebConf handled incidents:
+<https://www.mail-archive.com/search?l=debconf-team@lists.debian.org&q=subject:%22Re%5C%3A+DebConf+21+Incident+Response%22&o=newest&f=1>
+
 
-<a id="org53ebeba"></a>
+<a id="tech-checks"></a>
 
 ## INPROGRESS Find volunteers for tech-checks     :zaeph:
 
@@ -395,33 +390,31 @@ From previous years:
 > -   Do you need help finding your way around IRC so that you can check into \`#emacsconf-org\`? What is your IRC nickname?
 
 
-<a id="orgce43a0a"></a>
-
-## STANDBY Add nice-to-have stuff to prepare.md     :zaeph:
-
--   org-reveal config
--   SIL fonts choice
-
+<a id="write-viewing"></a>
 
-<a id="org6e7cc99"></a>
-
-## STANDBY Write viewing instructions     :zaeph:
+## STANDBY Update viewing instructions and watch pages     :zaeph:
 
 Extra stuff to consider adding:
 
 -   Suggestions for mpv-filter to invert colourscape.
 
+Also add to watch page
 
-<a id="org48fafc0"></a>
-
-## TODO Add category tags and possibly links between talks across 2022 and all previous years     :needsowner:wiki:
 
-List of talks: <https://emacsconf.org/talks/>
+<a id="link-pages"></a>
 
+## TODO Add category tags and possibly links between talks across 2022 and all previous years     :needsowner:wiki:
 
-<a id="orga41dec5"></a>
+-   Prerequisite: Can edit wiki pages (<https://emacsconf.org/edit/>)
+-   Goal: Make it easier for people to discover interesting related talks
 
-## Archive     :ARCHIVE:
+-   List of talks for EmacsConf 2022:  <https://emacsconf.org/talks/>
+-   List of talks: <https://emacsconf.org/talks/>
+-   List of categories: <https://emacsconf.org/CategoryCategory/>
+-   To add something to a category, add `\[[!taglink CategoryName]]` to the bottom of its talk page (ex: 2022/talks/maint.md is in CategoryCommunity)
+-   You can create new categories by making up new CategoryNames.
+-   You can also link to a talk with a link like this: `\[[/2022/talks/maint|Maintaining the Maintainers: Attribution as an Economic Model for Open Source]]`
+    You can make a new heading called `# Related talks`
 
 
 <a id="decisions"></a>
@@ -429,17 +422,15 @@ List of talks: <https://emacsconf.org/talks/>
 # Things to figure out / decisions to make
 
 -   [How fancy do we want to get this year? (overall prioritization)](#overall)
--   [How do we want to make the full schedule more manageable?](#org6d9894a)
--   [How much do we want to enrich the wiki with JS?](#org671bd0e)
--   [What ideas do we want to borrow from other conferences?](#orgbe5bf61)
--   [Do we want to make the ikiwiki web-editable?](#orgf9f0808)
--   [How do we want to make better use of Etherpad?](#org2e44f4b)
--   [Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?](#org538d010)
--   [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#org277efeb)
--   [How many BBB rooms do we want to set up?](#orgdf41952)
--   [Do we want to do alt-stream the same way again this year?](#org8b62354)
--   [Do we want people to advertise any openings with their companies or any work that they're looking for?](#org6305952)
--   [Archive](#org07028ad)
+-   [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)
+-   [Do we want to make the ikiwiki web-editable?](#cgi)
+-   [How do we want to make better use of Etherpad?](#pad-decision)
+-   [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#irc-markers)
+-   [How many BBB rooms do we want to set up?](#bbb-rooms)
+-   [Do we want people to advertise any openings with their companies or any work that they're looking for?](#advertising)
+-   [Decision archive](#decision-archive)
 
 
 <a id="overall"></a>
@@ -587,7 +578,7 @@ so we know what we need to scramble to do.
 </table>
 
 
-<a id="org6d9894a"></a>
+<a id="sched-decision"></a>
 
 ## How do we want to make the full schedule more manageable?
 
@@ -617,12 +608,12 @@ Shifts will be Sat AM, Sat PM, Sun AM, or Sun PM per track. People can take mult
 -   Figure out how hosting can be done in shifts
     -   Add notes in one place
 -   Figure out how streaming can be done in shifts: OBS in the cloud?
-    -   [Investigate streaming options, maybe OBS in the cloud](#obscloud)
+    -   [Investigate streaming options, maybe OBS in the cloud](#streaming)
 -   Figure out how publishing can be done in shifts
     -   Console Emacs in a VM with everything set up for publishing to the wiki
 
 
-<a id="org671bd0e"></a>
+<a id="wiki-design"></a>
 
 ## How much do we want to enrich the wiki with JS?
 
@@ -649,7 +640,7 @@ gitolite should have some options to do this
 Might not be necessary.
 
 
-<a id="orgbe5bf61"></a>
+<a id="other-confs"></a>
 
 ## What ideas do we want to borrow from other conferences?
 
@@ -667,7 +658,7 @@ Might not be necessary.
     -   libreadventure, minetest?
 
 
-<a id="orgf9f0808"></a>
+<a id="cgi"></a>
 
 ## Do we want to make the ikiwiki web-editable?
 
@@ -684,7 +675,7 @@ Options:
     -   Reduces merge conflict potential
 
 
-<a id="org2e44f4b"></a>
+<a id="pad-decision"></a>
 
 ## How do we want to make better use of Etherpad?
 
@@ -729,30 +720,12 @@ Options:
 -   Embed the IRC channel instead
 
 
-<a id="org538d010"></a>
-
-## Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
-
-Pain points:
-
--   Many talk pages don't have public e-mail addresses, so it takes a
-    little extra work (or is sometimes impossible) for people to follow
-    up if they have questions
-
-Options:
-
--   Do nothing (current)
--   Add a mailto link to emacsconf-discuss that prepopulates the subject
--   Add a mailto link to emacsconf-org
-    -   Wider discussion
--   Add a mailto to emacsconf-org-private
-    -   Private feedback that can be forwarded to the speaker
-
-
-<a id="org277efeb"></a>
+<a id="irc-markers"></a>
 
 ## Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?
 
+Two tracks mean two IRC channels with lots of space for Q&A, so this may become less of an issue
+
 Pain points:
 
 -   Q&A/discussions often overlap with the next talks
@@ -775,7 +748,7 @@ Ideas:
 -   Maybe a volunteer can have an ERC command that copies a question into a buffer, or even into the Etherpad
 
 
-<a id="orgdf41952"></a>
+<a id="bbb-rooms"></a>
 
 ## How many BBB rooms do we want to set up?
 
@@ -789,19 +762,7 @@ Ideas:
     -   Worked fine last time
 
 
-<a id="org8b62354"></a>
-
-## Do we want to do alt-stream the same way again this year?
-
--   Alt stream joins the current session and then continues with it until the Q&A finishes; people join the BBB room if they want to ask questions
-    -   Nice and convivial, Q&A still gets captured
-    -   Inertia means most people get the main message
--   Multiple streams with more space between talks, people choose which stream they want to watch
-    -   How other conferences do it
-    -   Speakers can attend related talks more easily
-
-
-<a id="org6305952"></a>
+<a id="advertising"></a>
 
 ## Do we want people to advertise any openings with their companies or any work that they're looking for?
 
@@ -809,9 +770,9 @@ Ideas:
 -   General audience on a wiki page somewhere?
 
 
-<a id="org07028ad"></a>
+<a id="decision-archive"></a>
 
-## Archive
+## Decision archive
 
 
 ### Where should volunteers e-mail?
@@ -831,6 +792,36 @@ Ideas:
         specific reasons, rather than the other way around
 
 
+### CANCELLED Do we want to do alt-stream the same way again this year?
+
+Superseded by decision to have multiple tracks
+
+-   Alt stream joins the current session and then continues with it until the Q&A finishes; people join the BBB room if they want to ask questions
+    -   Nice and convivial, Q&A still gets captured
+    -   Inertia means most people get the main message
+-   Multiple streams with more space between talks, people choose which stream they want to watch
+    -   How other conferences do it
+    -   Speakers can attend related talks more easily
+
+
+### DONE Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
+
+Pain points:
+
+-   Many talk pages don't have public e-mail addresses, so it takes a
+    little extra work (or is sometimes impossible) for people to follow
+    up if they have questions
+
+Options:
+
+-   Do nothing (current)
+-   Add a mailto link to emacsconf-discuss that prepopulates the subject
+-   Add a mailto link to emacsconf-org
+    -   Wider discussion
+-   **Add a mailto to emacsconf-org-private**
+    -   Private feedback that can be forwarded to the speaker
+
+
 <a id="roles"></a>
 
 # Roles needed
@@ -1092,38 +1083,18 @@ Interested in a shift? Please e-mail <mailto:emacsconf-org-private@gnu.org> and
 
 # Other tasks and processes
 
-
-## DONE Sacha: Organize volunteer information     :sachac:
+-   [As prerecorded talks come in](#prerec-process)
+-   [When a talk is captioned](#org01e0d53)
+-   [Other tasks before the conference](#before)
+-   [During the conference](#during-conference)
+-   [After the conference](#after-conference)
+-   [In case of](#exceptions)
 
 
-## Once talks are approved
-
--   sacha: Publish initial talk information pages
--   Double-check talk pages, format them nicely
--   Publish draft schedule
--   Confirm e-mail communication with all of the speakers
-
-Process for accepting a talk:
-
--   Create subtree for talk and populate it with properties.
-    -   Required: CUSTOM\_ID SLUG NAME NAME\_SHORT EMAIL AVAILABILITY Q\_AND\_A TRACK MAX\_TIME
-    -   Optional: PRONOUNS PRONUNCIATION IRC PUBLIC\_EMAIL MIN\_TIME EMERGENCY
-    -   Can be validated with `emacsconf-validate-talk-subtree`
-    -   Add a talk abstract subtree
--   Add it to emacsconf-schedule-plan and fiddle with it until the flow looks good
--   Execute the draft-schedule block to update the schedule in the Org file
--   Add the talk page to the wiki with `emacsconf-add-talk-page`.
--   Stage, commit, and push the wiki files. Make sure to add the talk page and the info pages.
--   Doublecheck the wiki page on the web, since the e-mail refers to it.
--   E-mail the speaker the acceptance by using `emacsconf-draft-acceptance-for-email-group` from `organizers-notebook/`.
--   Log the acceptance using `C-c C-z` in the talk subtree in `conf.org`, noting the number of minutes.
--   Change the status to TO\_CONFIRM.
-
+<a id="prerec-process"></a>
 
 ## As prerecorded talks come in
 
--   
-
 -   Sacha: Parcel out captioning work to volunteers, help them get set up
 -   Volunteers: Caption pre-recorded videos (usually starting from autogenerated ones for easier work)
 -   Make sure all the links/resources mentioned are written down somewhere (web page and enriched captions for pasting into #emacsconf-accessible)
@@ -1142,10 +1113,16 @@ Usage: `compress-video.sh original-file output-file`:
 We tried using q56 before, but it was a little too aggressive. Q=32 is the default and is probably a reasonable space vs. quality compromise.
 
 
+<a id="org01e0d53"></a>
+
 ## When a talk is captioned
 
--   Upload talk
+-   Combine captions with talk
+-   Upload captions to YT and Toobnix
+-   Prepare captions for wiki inclusion
+
 
+<a id="before"></a>
 
 ## Other tasks before the conference
 
@@ -1208,6 +1185,8 @@ Links:
         rsync -avzue ssh front:/var/www/media.emacsconf.org/2021/protected/*--main.webm .
 
 
+<a id="during-conference"></a>
+
 ## During the conference
 
 
@@ -1466,6 +1445,8 @@ Exceptions:
 -   bandali figures out the downstream
 
 
+<a id="after-conference"></a>
+
 ## After the conference
 
 
@@ -1622,7 +1603,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping
 
 Make a table of the form
 
-<table id="org66ae3dc" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="orge4a8e24" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
 
 
 <colgroup>
@@ -1712,6 +1693,8 @@ Make a table of the form
 ### BLOCKED Downsize the server     :bandali:
 
 
+<a id="exceptions"></a>
+
 ## In case of
 
 
diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org
index 837337ed..f8367288 100644
--- a/2022/organizers-notebook/index.org
+++ b/2022/organizers-notebook/index.org
@@ -74,6 +74,9 @@ Ordered chronologically (and therefore by importance).
 
 *** Volunteer communications: E-mail update for Oct 9, 2022 :email:volunteers:
 SCHEDULED: <2022-10-09 Sun>
+:PROPERTIES:
+:CUSTOM_ID: volunteer-2022-10-09
+:END:
 
 Add your news and requests to this.
 
@@ -98,14 +101,24 @@ You're receiving this e-mail because you're on the emacsconf-org mailing list.
 
 *** TODO Remind people about confirming e-mail communications :sachac:email:speakers:
 SCHEDULED: <2022-10-08 Sat>
+:PROPERTIES:
+:CUSTOM_ID: confirm-email
+:END:
+
+Look for the TO_CONFIRM status in conf.org, probably include in schedule e-mail
 
-Look for the TO_CONFIRM status
 
 *** TODO Send people schedule information and doublecheck their availability/Q&A preference :sachac:email:speakers:
 SCHEDULED: <2022-10-08 Sat>
+:PROPERTIES:
+:CUSTOM_ID: check-sched
+:END:
 
 *** TODO Send program-published email for emacsconf-discuss :needsowner:timesensitive:email:
 DEADLINE: <2022-10-14 Fri> SCHEDULED: <2022-10-11 Tue>
+:PROPERTIES:
+:CUSTOM_ID: announce-program
+:END:
 
 Probably post schedule instead if available by that date
 **** TODO Post it to r/emacs as well                        :reddit:zaeph:
@@ -126,6 +139,9 @@ to their availability, and will add the allocated time slots for the
 talks in the coming weeks.
 
 *** BLOCKED Prepare email for nudging speakers to send prerec, and inform on upload workflow :timesensitive:needsowner:
+:PROPERTIES:
+:CUSTOM_ID: mail-upload
+:END:
 Blocked by [[*Figure out web-based file upload][Figure out web-based file upload]]
 
 ** Projects and other long-running tasks
@@ -176,6 +192,9 @@ Considerations:
 
 *** TODO Prepare for prerecs                                         :zaeph:
 DEADLINE: <2022-10-28 Fri>
+:PROPERTIES:
+:CUSTOM_ID: prepare-prerec-process
+:END:
 **** TODO Optimize ffmpeg incantation
 Remember to update [[file:prepare.md::Compression]] with the new incantation.
 **** TODO Figure out workflow for handling submitted prerecs
@@ -186,13 +205,16 @@ We need time after the prerecs get submitted to:
 - follow up with missing prerecs
 
 *** TODO Delete all the EmacsConf BBB rooms from last year      :chore:bbb:
+:PROPERTIES:
+:CUSTOM_ID: bbb-cleanup
+:END:
 For the admins on BBB.  The list is accessible here: [[https://bbb.emacsverse.org/b/admins/rooms][Organization Settings]].
 Should take no more than ~20′.
 
 *** TODO Investigate streaming options, maybe OBS in the cloud :corwin:zaeph:
 DEADLINE: <2022-11-20 Sun>
 :PROPERTIES:
-:CUSTOM_ID: obscloud
+:CUSTOM_ID: streaming
 :END:
 - Issue: zaeph was dropping frames and couldn’t pay attention to as many things as he wanted
 - Issue: corwin needs assistance to not be locked in his chair for the whole conf.  Premptively, zaeph can do it by broadcasting OBS scenes via the rtmp (instead of just his webcam).
@@ -210,13 +232,15 @@ Resources:
 
 *** TODO Work on the OBS scenes                               :zaeph:corwin:
 DEADLINE: <2022-11-11 Fri>
+:PROPERTIES:
+:CUSTOM_ID: obs-scenes
+:END:
 - [ ] corwin is out from Nov 11-20, and we should start working on them before then.
 
-*** CANCELLED Create Org heading for scheduling caption team's live IRC duty shifts :dto:
-CLOSED: [2022-10-07 Fri 14:24] DEADLINE: <2022-09-30 Fri>
-See [[#shifts]]
-
 *** Move scheduling and publishing code to Emacs on a VPS so that other people can help out  :sachac:
+:PROPERTIES:
+:CUSTOM_ID: publishing-vps
+:END:
 Ideal:
 - Update pages with watching information, additional resources, etc. as talks go live
 - Update the schedule as needed (cancelled or reordered talks, etc.)
@@ -224,20 +248,34 @@ Ideal:
 Where:
 - front? my own VPS?
 
+  Nice if there's an Ansible playbook
+  
   sachac's notes:
   [[file:~/code/docker/emacsconf-publish/]]
   
 *** STANDBY Add nice-to-have stuff to prepare.md                    :zaeph:
+:PROPERTIES:
+:CUSTOM_ID: extra-prepare
+:END:
 - org-reveal config
 - SIL fonts choice
 
 ** Projects to bear in mind but which are not actual
+:PROPERTIES:
+:CUSTOM_ID: maybe-projects
+:END:
 
 *** STANDBY Find a way to accommodate a specific return-speaker
 We’re not sure if we’re going to get a presentation or a prerec for them
 this year, but we need to keep this at the back of our minds.
 
+Note on how DebConf handled incidents:
+https://www.mail-archive.com/search?l=debconf-team@lists.debian.org&q=subject:%22Re%5C%3A+DebConf+21+Incident+Response%22&o=newest&f=1
+
 ** INPROGRESS Find volunteers for tech-checks                        :zaeph:
+:PROPERTIES:
+:CUSTOM_ID: tech-checks
+:END:
 *** DONE Add entry in 2022/volunteer.md
 *** INPROGRESS Write protocol for adding tech-checker volunteer
 - Invite volunteer to BBB (ask core organizers)
@@ -255,21 +293,29 @@ From previous years:
 - 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 Add nice-to-have stuff to prepare.md                      :zaeph:
-- org-reveal config
-- SIL fonts choice
-** STANDBY Write viewing instructions                                :zaeph:
+** STANDBY Update viewing instructions and watch pages               :zaeph:
+:PROPERTIES:
+:CUSTOM_ID: write-viewing
+:END:
 Extra stuff to consider adding:
 - Suggestions for mpv-filter to invert colourscape.
+Also add to watch page
 ** TODO Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki:
-List of talks: https://emacsconf.org/talks/
-** Archive                                                         :ARCHIVE:
-
-CLOSED: [2022-09-29 Thu 20:29] DEADLINE: <2022-09-26 Mon>
 :PROPERTIES:
-:ARCHIVE_TIME: 2022-10-01 Sat 00:33
+:CUSTOM_ID: link-pages
 :END:
-- zaeph: will start reviewing on Sep 21
+
+- Prerequisite: Can edit wiki pages (https://emacsconf.org/edit/)
+- Goal: Make it easier for people to discover interesting related talks
+
+- List of talks for EmacsConf 2022:  https://emacsconf.org/talks/
+- List of talks: https://emacsconf.org/talks/
+- List of categories: https://emacsconf.org/CategoryCategory/
+- To add something to a category, add =\[[!taglink CategoryName]]= to the bottom of its talk page (ex: 2022/talks/maint.md is in CategoryCommunity)
+- You can create new categories by making up new CategoryNames.
+- You can also link to a talk with a link like this: =\[[/2022/talks/maint|Maintaining the Maintainers: Attribution as an Economic Model for Open Source]]=
+  You can make a new heading called =# Related talks=
+  
 * Things to figure out / decisions to make
 :PROPERTIES:
 :CUSTOM_ID: decisions
@@ -305,6 +351,9 @@ so we know what we need to scramble to do.
 | wiki                                 | plain text, markdown          | *S: some JS enrichment*     | more JS and CSS, embeds, videoplayer                 |
 
 ** How do we want to make the full schedule more manageable?
+:PROPERTIES:
+:CUSTOM_ID: sched-decision
+:END:
 
 updated by conf.org
 [[file:schedule.svg]]
@@ -335,6 +384,9 @@ https://emacsconf.org/2022/decisions/#schedule
   - Console Emacs in a VM with everything set up for publishing to the wiki
     
 ** How much do we want to enrich the wiki with JS?
+:PROPERTIES:
+:CUSTOM_ID: wiki-design
+:END:
 Ideas to consider:
 - Toggling local time display on the schedule
 - Making organizers-notebook nicer to browse through (or maybe use organice?)
@@ -351,6 +403,9 @@ gitolite should have some options to do this
 Might not be necessary.
   
 ** What ideas do we want to borrow from other conferences?
+:PROPERTIES:
+:CUSTOM_ID: other-confs
+:END:
 
 - FOSDEM had a conference track
   - https://archive.fosdem.org/2022/schedule/track/conference_organisation/
@@ -365,6 +420,9 @@ Might not be necessary.
 - LibrePlanet https://libreplanet.org/2022/
   - libreadventure, minetest?
 ** [#C] Do we want to make the ikiwiki web-editable?
+:PROPERTIES:
+:CUSTOM_ID: cgi
+:END:
 Pain points:
 - Speakers usually ended up going through us
 
@@ -376,6 +434,9 @@ Options:
   - Reduces merge conflict potential
 
 ** How do we want to make better use of Etherpad?
+:PROPERTIES:
+:CUSTOM_ID: pad-decision
+:END:
 Pain points:
 - Lots of scrolling for speakers
 - Takes some effort to move questions from IRC to the pad
@@ -406,21 +467,12 @@ Options:
   - Individual talk page can embed the iframe
 - Embed the IRC channel instead
   
-** Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
-Pain points:
-- Many talk pages don't have public e-mail addresses, so it takes a
-  little extra work (or is sometimes impossible) for people to follow
-  up if they have questions
-
-Options:
-- Do nothing (current)
-- Add a mailto link to emacsconf-discuss that prepopulates the subject
-- Add a mailto link to emacsconf-org
-  - Wider discussion
-- Add a mailto to emacsconf-org-private
-  - Private feedback that can be forwarded to the speaker  
-
 ** Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?
+:PROPERTIES:
+:CUSTOM_ID: irc-markers
+:END:
+
+Two tracks mean two IRC channels with lots of space for Q&A, so this may become less of an issue
 
 Pain points:
 
@@ -443,6 +495,9 @@ Ideas:
   - Needs logging and more organizer attention
 - Maybe a volunteer can have an ERC command that copies a question into a buffer, or even into the Etherpad
 ** How many BBB rooms do we want to set up?
+:PROPERTIES:
+:CUSTOM_ID: bbb-rooms
+:END:
 
 - One per talk
   - We can send speakers a direct link to their room and they can check into it themselves
@@ -452,20 +507,18 @@ Ideas:
 - Five or so, rotating among them
   - Check-in person directs the speaker to the next available room
   - Worked fine last time
-** Do we want to do alt-stream the same way again this year?
-
-- Alt stream joins the current session and then continues with it until the Q&A finishes; people join the BBB room if they want to ask questions
-  - Nice and convivial, Q&A still gets captured
-  - Inertia means most people get the main message
-- Multiple streams with more space between talks, people choose which stream they want to watch
-  - How other conferences do it
-  - Speakers can attend related talks more easily
 ** Do we want people to advertise any openings with their companies or any work that they're looking for?
+:PROPERTIES:
+:CUSTOM_ID: advertising
+:END:
 
 - Speakers on their page?
 - General audience on a wiki page somewhere?
   
-** Archive
+** Decision archive
+:PROPERTIES:
+:CUSTOM_ID: decision-archive
+:END:
 *** Where should volunteers e-mail?
 :LOGBOOK:
 - Note taken on [2022-09-23 Fri 11:26] \\
@@ -486,6 +539,31 @@ Ideas:
   - i just think most folks would want to do this publicly unless for
     specific reasons, rather than the other way around
   
+*** CANCELLED Do we want to do alt-stream the same way again this year?
+
+Superseded by decision to have multiple tracks
+
+- Alt stream joins the current session and then continues with it until the Q&A finishes; people join the BBB room if they want to ask questions
+  - Nice and convivial, Q&A still gets captured
+  - Inertia means most people get the main message
+- Multiple streams with more space between talks, people choose which stream they want to watch
+  - How other conferences do it
+  - Speakers can attend related talks more easily
+*** DONE Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
+CLOSED: [2022-10-07 Fri 14:45]
+Pain points:
+- Many talk pages don't have public e-mail addresses, so it takes a
+  little extra work (or is sometimes impossible) for people to follow
+  up if they have questions
+
+Options:
+- Do nothing (current)
+- Add a mailto link to emacsconf-discuss that prepopulates the subject
+- Add a mailto link to emacsconf-org
+  - Wider discussion
+- *Add a mailto to emacsconf-org-private*
+  - Private feedback that can be forwarded to the speaker  
+
 * Roles needed
 :PROPERTIES:
 :CUSTOM_ID: roles
@@ -610,31 +688,13 @@ Interested in a shift? Please e-mail [[mailto:emacsconf-org-private@gnu.org]] an
 :PROPERTIES:
 :CUSTOM_ID: other
 :END:
-** DONE Sacha: Organize volunteer information                       :sachac:
-** Once talks are approved
-- sacha: Publish initial talk information pages
-- Double-check talk pages, format them nicely
-- Publish draft schedule
-- Confirm e-mail communication with all of the speakers
 
-Process for accepting a talk:
-
-- Create subtree for talk and populate it with properties.
-  - Required: CUSTOM_ID SLUG NAME NAME_SHORT EMAIL AVAILABILITY Q_AND_A TRACK MAX_TIME
-  - Optional: PRONOUNS PRONUNCIATION IRC PUBLIC_EMAIL MIN_TIME EMERGENCY
-  - Can be validated with ~emacsconf-validate-talk-subtree~
-  - Add a talk abstract subtree
-- Add it to emacsconf-schedule-plan and fiddle with it until the flow looks good
-- Execute the draft-schedule block to update the schedule in the Org file
-- Add the talk page to the wiki with ~emacsconf-add-talk-page~.
-- Stage, commit, and push the wiki files. Make sure to add the talk page and the info pages.
-- Doublecheck the wiki page on the web, since the e-mail refers to it.
-- E-mail the speaker the acceptance by using ~emacsconf-draft-acceptance-for-email-group~ from ~organizers-notebook/~.
-- Log the acceptance using ~C-c C-z~ in the talk subtree in ~conf.org~, noting the number of minutes.
-- Change the status to TO_CONFIRM.
-  
+#+TOC: headlines 1 local
 ** As prerecorded talks come in
-- 
+:PROPERTIES:
+:CUSTOM_ID: prerec-process
+:END:
+
 - Sacha: Parcel out captioning work to volunteers, help them get set up
 - Volunteers: Caption pre-recorded videos (usually starting from autogenerated ones for easier work)
 - Make sure all the links/resources mentioned are written down somewhere (web page and enriched captions for pasting into #emacsconf-accessible)
@@ -653,12 +713,24 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau
 
 
 ** When a talk is captioned
-- Upload talk
+- Combine captions with talk
+- Upload captions to YT and Toobnix
+- Prepare captions for wiki inclusion
+  
 ** Other tasks before the conference
+:PROPERTIES:
+:CUSTOM_ID: before
+:END:
 - Coordinate volunteer schedules so all the roles are covered
 *** Test stream setup
+:PROPERTIES:
+:CUSTOM_ID: test-stream
+:END:
 [[*Stream][Stream]]
 *** Set up MPV for captions
+:PROPERTIES:
+:CUSTOM_ID: mpv-captions
+:END:
 
 **** mpv profile
 Add the following profile to ~~/.config/mpv/mpv.conf~:
@@ -698,7 +770,7 @@ Links:
 - WOFF from GitHub repo: [[https://github.com/intel/clear-sans/tree/main/WOFF][clear-sans/WOFF at main · intel/clear-sans]]
 *** Download prerecorded videos from ${protected}
 :PROPERTIES:
-:CUSTOM_ID: days-before
+:CUSTOM_ID: download-videos
 :END:
 
 - STREAM: Download prerecorded videos from ${protected}
@@ -709,6 +781,9 @@ Links:
 
 
 ** During the conference  
+:PROPERTIES:
+:CUSTOM_ID: during-conference
+:END:
 
 *** Set up
 :PROPERTIES:
@@ -971,7 +1046,7 @@ Exceptions:
 - CHECK uses =conf-upcoming-add-subtree= to add the afternoon talks to upcoming.org
 - HOST doublechecks network transfer limit and server health
 
-
+  
 *** End of stream
 :PROPERTIES:
 :CUSTOM_ID: end
@@ -986,6 +1061,9 @@ Exceptions:
 - bandali figures out the downstream
   
 ** After the conference
+:PROPERTIES:
+:CUSTOM_ID: after-conference
+:END:
 *** Send thanks
 [[*Thank you, next steps][Thank you, next steps]]
 *** Extract the opening and closing remarks
@@ -1556,6 +1634,33 @@ CLOSED: [2022-10-07 Fri 14:18]
 | survey  | Results of the 2022 Emacs Survey                                              |
 :end:
 
+** CANCELLED Create Org heading for scheduling caption team's live IRC duty shifts :dto:
+CLOSED: [2022-10-07 Fri 14:24] DEADLINE: <2022-09-30 Fri>
+See [[#shifts]]
+
+** DONE Sacha: Organize volunteer information                       :sachac:
+** DONE Once talks are approved
+- sacha: Publish initial talk information pages
+- Double-check talk pages, format them nicely
+- Publish draft schedule
+- Confirm e-mail communication with all of the speakers
+
+Process for accepting a talk:
+
+- Create subtree for talk and populate it with properties.
+  - Required: CUSTOM_ID SLUG NAME NAME_SHORT EMAIL AVAILABILITY Q_AND_A TRACK MAX_TIME
+  - Optional: PRONOUNS PRONUNCIATION IRC PUBLIC_EMAIL MIN_TIME EMERGENCY
+  - Can be validated with ~emacsconf-validate-talk-subtree~
+  - Add a talk abstract subtree
+- Add it to emacsconf-schedule-plan and fiddle with it until the flow looks good
+- Execute the draft-schedule block to update the schedule in the Org file
+- Add the talk page to the wiki with ~emacsconf-add-talk-page~.
+- Stage, commit, and push the wiki files. Make sure to add the talk page and the info pages.
+- Doublecheck the wiki page on the web, since the e-mail refers to it.
+- E-mail the speaker the acceptance by using ~emacsconf-draft-acceptance-for-email-group~ from ~organizers-notebook/~.
+- Log the acceptance using ~C-c C-z~ in the talk subtree in ~conf.org~, noting the number of minutes.
+- Change the status to TO_CONFIRM.
+  
 * Communications
 :PROPERTIES:
 :CUSTOM_ID: comms