Rearrange tasks

1 files changed, 62 insertions, 36 deletions

diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org
index 4e27cdfa..e198898a 100644
--- a/2022/organizers-notebook/index.org
+++ b/2022/organizers-notebook/index.org
@@ -205,7 +205,6 @@ Considerations:
   comfortable signing up for tasks. ex:
   https://wiki.debian.org/DebConf/21/VideoVolunteering
 - Encourage people to sign up for [[#shifts]]
-  
 *** TODO Prepare for prerecs                                         :zaeph:
 DEADLINE: <2022-10-28 Fri>
 :PROPERTIES:
@@ -227,6 +226,16 @@ We need time after the prerecs get submitted to:
 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 Plan Etherpad use and hosting  :sachac:
+:PROPERTIES:
+:CUSTOM_ID: etherpad
+:END:
+
+- Relevant links:
+  - Per-pad, nicely structured info with abstract, watching information, etc. CarpentryCon 2022 Schedule • CarpentryCon 2022 https://2022.carpentrycon.org/
+  - One pad per session: https://meta.wikimedia.org/wiki/Arctic_Knot_Conference_2021/Program#Friday,_June_25th
+  - [[https://community.jitsi.org/t/tutorial-etherpad-integration-in-jitsi-meetings/99697][Etherpad integration in Jitsi ]]
+
 *** TODO Investigate streaming options, maybe OBS in the cloud :corwin:zaeph:
 DEADLINE: <2022-11-20 Sun>
 :PROPERTIES:
@@ -276,28 +285,16 @@ Where:
 - 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:
+*** 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
+**** 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”)
+**** 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?
@@ -309,14 +306,14 @@ 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 Update viewing instructions and watch pages               :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:
+*** TODO [#C] Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki:
 :PROPERTIES:
 :CUSTOM_ID: link-pages
 :END:
@@ -332,6 +329,18 @@ Also add to watch page
 - 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=
   
+** 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
+
 * Things to figure out / decisions to make
 :PROPERTIES:
 :CUSTOM_ID: decisions
@@ -349,22 +358,22 @@ slider depending on who wants to volunteer and how much we can get
 done. At some point, we'll figure out how to track our current status
 so we know what we need to scramble to do.
 
-|                                      | Good                          | Better                      | Best                                                 |
-|--------------------------------------+-------------------------------+-----------------------------+------------------------------------------------------|
-| schedule                             | one track                     | *DONE S: two tracks*        | aligned times, full roster                           |
-| [[#schedule-publish][schedule view]]                        | text table                    | S: imagemap fallback        | *DONE S: interactive SVG*             |
-| upload                               | FTP                           | *S?: web-based*             | auto-encoded, preview (SReview?)                     |
-| stream                               | ffmpeg from computer          | DONE OBS                    | *Z: OBS in cloud, switchable hosts*                  |
-| prerec                               | play original                 | Z: normalize audio          | *S: post as soon as talk is live*                    |
-| host                                 | no host, speaker reads pad    | *host reads pad*            | host monitors IRC as well                            |
-| watch page                           | stream                        | *S: + IRC*                  | + talk info, maybe even pad                          |
-| pad                                  | one pad for conf              | one pad per talk, wikimedia | *one pad per talk, self-hosted* so we can access API |
-| IRC                                  | #emacsconf, -org              | *tracks, hallway, org*      | IRC volunteer copying to pads; maybe even IRC bots   |
-| sched update                         | *S: publish at start*         | update main sched           | update talk pages                                    |
-| talk pages                           | *S: link to stream, pad, IRC* | *link to prerec when live*  | embed stream, pad, IRC, prerec                       |
-| other streams                        | 480p                          | + Toobnix                   | *S: + YouTube*                                       |
-| other platforms                      | *S: Toobnix & YT after event* |                             | S: Toobnix + YT when live                            |
-| wiki                                 | plain text, markdown          | *S: some JS enrichment*     | more JS and CSS, embeds, videoplayer                 |
+|                 | Good                          | Better                      | Best                                                 |
+|-----------------+-------------------------------+-----------------------------+------------------------------------------------------|
+| [[#sched-decision][schedule]]        | one track                     | *DONE S: two tracks*        | aligned times, full roster                           |
+| [[#schedule-publish][schedule view]]   | text table                    | S: imagemap fallback        | *DONE S: interactive SVG*                            |
+| [[#upload]]         | FTP                           | *S?: web-based*             | auto-encoded, preview (SReview?)                     |
+| [[#streaming]]      | ffmpeg from computer          | DONE OBS                    | *Z: OBS in cloud, switchable hosts*                  |
+| [[#prepare-prerec-process][prerec]]          | play original                 | Z: normalize audio          | *S: post as soon as talk is live*                    |
+| host            | no host, speaker reads pad    | *host reads pad*            | host monitors IRC as well                            |
+| watch page      | stream                        | *S: + IRC*                  | + talk info, maybe even pad                          |
+| pad             | one pad for conf              | one pad per talk, wikimedia | *one pad per talk, self-hosted* so we can access API |
+| IRC             | #emacsconf, -org              | *tracks, hallway, org*      | IRC volunteer copying to pads; maybe even IRC bots   |
+| sched update    | *S: publish at start*         | update main sched           | update talk pages                                    |
+| talk pages      | *S: link to stream, pad, IRC* | *link to prerec when live*  | embed stream, pad, IRC, prerec                       |
+| other streams   | 480p                          | + Toobnix                   | *S: + YouTube*                                       |
+| other platforms | *S: Toobnix & YT after event* |                             | S: Toobnix + YT when live                            |
+| 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:
@@ -398,7 +407,24 @@ https://emacsconf.org/2022/decisions/#schedule
   - [[*Investigate streaming options, maybe OBS in the cloud][Investigate streaming options, maybe OBS in the cloud]]
 - Figure out how publishing can be done in shifts
   - Console Emacs in a VM with everything set up for publishing to the wiki
-    
+
+[2022-10-04 Tue]
+- Added option H: general starts with general Org use cases and moves on to more niche things on day 2.
+  - compared to A, general audience will be more interested in Org use
+    cases than in Hyperbole, and then we can look at specific
+    techniques on day 2
+  
+[2022-10-04 Tue]
+- Discussed option G with zaeph on #emacsconf-org. zaeph prefers
+  option A over option G because it gives people more choices -
+  they can hop from talk to talk.
+  
+[2022-10-03 Mon]
+- Discussed with bandali and zaeph on #emacsconf-org
+- Decided on Option A with B, C, or F as fallbacks depending on volunteer roster
+- Better for the viewers and the volunteers
+
+
 ** How much do we want to enrich the wiki with JS?
 :PROPERTIES:
 :CUSTOM_ID: wiki-design