Write more coordination

1 files changed, 37 insertions, 13 deletions

diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index 565a48eb..a94fb60d 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -116,8 +116,8 @@ Ordered chronologically (and therefore by importance).
 
 -   [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:
--   [Plan communication rhythm](#org055f325)
--   [Send people schedule information and doublecheck their availability/Q&A preference](#check-sched):sachac:email:speakers:
+-   [Plan cadence](#cadence):email:
+-   [Send people schedule information and doublecheck their availability/Q&A preference](#check-sched):sachac:email:speakers:sched:
 -   [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:
 
@@ -157,9 +157,9 @@ You're receiving this e-mail because you're on the emacsconf-org mailing list.
 Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
 
 
-<a id="org055f325"></a>
+<a id="cadence"></a>
 
-### TODO Plan communication rhythm
+### TODO Plan cadence     :email:
 
 <table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
 
@@ -170,45 +170,61 @@ Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
 <col  class="org-left" />
 
 <col  class="org-left" />
+
+<col  class="org-left" />
+
+<col  class="org-left" />
 </colgroup>
 <tbody>
 <tr>
 <td class="org-left">&#xa0;</td>
+<td class="org-left">Work</td>
 <td class="org-left">Speakers</td>
 <td class="org-left">Volunteers</td>
+<td class="org-left">Public</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-09-30 Fri]</span></span></td>
+<td class="org-left">&#xa0;</td>
 <td class="org-left">acceptance, reply to confirm</td>
 <td class="org-left">overall priorities</td>
+<td class="org-left">&#xa0;</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-10-09 Sun]</span></span></td>
+<td class="org-left">&#xa0;</td>
 <td class="org-left">schedule, reply if not okay</td>
 <td class="org-left">infra update</td>
+<td class="org-left">&#xa0;</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-10-16 Sun]</span></span></td>
+<td class="org-left">file upload</td>
 <td class="org-left">&#xa0;</td>
 <td class="org-left">shifts</td>
+<td class="org-left">schedule</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-10-23 Sun]</span></span></td>
+<td class="org-left">etherpad, stream</td>
 <td class="org-left">file upload instructions</td>
 <td class="org-left">caption training?</td>
+<td class="org-left">&#xa0;</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-10-30 Sun]</span></span></td>
+<td class="org-left">intro, exit videos</td>
+<td class="org-left">&#xa0;</td>
 <td class="org-left">&#xa0;</td>
 <td class="org-left">&#xa0;</td>
 </tr>
@@ -216,29 +232,37 @@ Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-11-06 Sun]</span></span></td>
+<td class="org-left">&#xa0;</td>
 <td class="org-left">prerec confirmation/reminder, caption progress</td>
 <td class="org-left">caption kickoff</td>
+<td class="org-left">&#xa0;</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-11-13 Sun]</span></span></td>
+<td class="org-left">captions</td>
 <td class="org-left">tech check</td>
 <td class="org-left">&#xa0;</td>
+<td class="org-left">&#xa0;</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-11-20 Sun]</span></span></td>
+<td class="org-left">captions</td>
 <td class="org-left">checkin instructions</td>
 <td class="org-left">&#xa0;</td>
+<td class="org-left">&#xa0;</td>
 </tr>
 
 
 <tr>
 <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2022-11-27 Sun]</span></span></td>
+<td class="org-left">captions</td>
 <td class="org-left">last weekend before EmacsConf</td>
 <td class="org-left">&#xa0;</td>
+<td class="org-left">watching</td>
 </tr>
 </tbody>
 </table>
@@ -246,7 +270,7 @@ Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
 
 <a id="check-sched"></a>
 
-### TODO Send people schedule information and doublecheck their availability/Q&A preference     :sachac:email:speakers:
+### TODO Send people schedule information and doublecheck their availability/Q&A preference     :sachac:email:speakers:sched:
 
     (defun emacsconf-mail-schedule (group &optional template)
       "Send draft schedule.
@@ -276,7 +300,7 @@ Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
         :coordination-note
         (if (seq-find (lambda (o) (member (plist-get o :slug) '("journalism" "rolodex" "orgsuperlinks" "buttons" "hyperorg" "science")))
                       (cdr group))
-            "I've changed the order slightly from the coordination e-mail I sent you, as the science talk is now on Saturday morning."
+            "I've changed the order slightly from the coordination e-mail I sent you. The sequence is now journalism - science - rolodex - orgsuperlinks - buttons - hyperorg. science is now second instead of last, and the first two talks are on Sat while the last four are on Sun. That probably means you don't have to coordinate as much, but you can still do so if you would like to build on other people's talks."
           "")
         :schedule
         (mapconcat
@@ -398,8 +422,8 @@ Blocked by [Figure out web-based file upload](#upload)
 -   [Make talk pages easy to update when the talk is live](#publish-live):sachac:
 -   [Set up talks on Toobnix and YouTube](#video-platforms):sachac:
 -   [Add category tags and possibly links between talks across 2022 and all previous years](#link-pages):needsowner:wiki:
--   [Figure out why ikiwiki runs into complex regular expression issues?](#orgae83275):infra:wiki:
--   [Ask speakers for bios or support nudges to include on their talk pages](#org0976d7a)
+-   [Figure out why ikiwiki runs into complex regular expression issues?](#org3e5ee7c):infra:wiki:
+-   [Ask speakers for bios or support nudges to include on their talk pages](#org50c4e9c)
 
 Ordered by importance.
 
@@ -661,12 +685,12 @@ Also add to watch page
     You can make a new heading called `# Related talks`
 
 
-<a id="orgae83275"></a>
+<a id="org3e5ee7c"></a>
 
 ### TODO Figure out why ikiwiki runs into complex regular expression issues?     :infra:wiki:
 
 
-<a id="org0976d7a"></a>
+<a id="org50c4e9c"></a>
 
 ### TODO Ask speakers for bios or support nudges to include on their talk pages
 
@@ -1376,7 +1400,7 @@ Interested in a shift? Please e-mail <mailto:emacsconf-org-private@gnu.org> and
 
 # Other tasks and processes
 
--   [Giving conf.org access to a new volunteer or fake user](#org078de74)
+-   [Giving conf.org access to a new volunteer or fake user](#org277bbc9)
 -   [As prerecorded talks come in](#prerec-process)
 -   [When a talk is captioned](#when-captioned)
 -   [Other tasks before the conference](#before)
@@ -1385,7 +1409,7 @@ Interested in a shift? Please e-mail <mailto:emacsconf-org-private@gnu.org> and
 -   [In case of](#exceptions)
 
 
-<a id="org078de74"></a>
+<a id="org277bbc9"></a>
 
 ## Giving conf.org access to a new volunteer or fake user
 
@@ -1913,7 +1937,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping
 
 Make a table of the form
 
-<table id="org2f9e66c" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="org190b4f2" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
 
 
 <colgroup>