diff options
Diffstat (limited to '2022/organizers-notebook/index.org')
| -rw-r--r-- | 2022/organizers-notebook/index.org | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org index 3ed4b1f4..a778b6f4 100644 --- a/2022/organizers-notebook/index.org +++ b/2022/organizers-notebook/index.org @@ -93,7 +93,7 @@ Previous priorities; | [[#caption-workflow][caption workflow]] | YT autosubs | Whisper autosubs | *DONE: Whisper + more granular timestamps* | | [[#wiki-design][wiki]] | plain text, markdown | *DONE S: some JS and CSS enrichment* | more JS and CSS, embeds, videoplayer | | [[#ansible][ansible]] | none | *DONE S: some automation* | comprehensive, can also work against containers | -| [[#intro][intro and exit]] | *DONE: slide on screen, host on Mumble* | per-talk video, recorded voiceover | Emacs thing so we can display info, countdowns, IRC | +| [[#intro][intro and exit]] | DONE: slide on screen, host on Mumble | *per-talk video, recorded voiceover* | Emacs thing so we can display info, countdowns, IRC | * Next comms update SCHEDULED: <2022-12-18 Sun> :PROPERTIES: @@ -248,7 +248,7 @@ from the screenshare. We also want to check if people accidentally shared sensitive information on their screen, or if anyone said something that they -might not have said if they remembered that thethe Q&A videos will be +might not have said if they remembered that the the Q&A videos will be shared after the talk. Sometimes there's some time before we get around to closing the meeting at the end of the Q&A. Usually, a quick read of the transcript will show anything that needs to be trimmed. @@ -1877,8 +1877,6 @@ CLOCK: [2022-12-02 Fri 12:56]--[2022-12-02 Fri 15:59] => 3:03 ;; ;; close ;; (shell-command "xdotool mousemove 2100 996 click 1") ;; ) - - #+end_src *** DONE upload the rest of the files onto Toobnix CLOSED: [2022-12-02 Fri 12:54] SCHEDULED: <2022-12-02 Fri> @@ -2450,6 +2448,16 @@ Consider if we need extra scaling beyond being on a beefy live0? Will need to try this again when we resize nodes. Probably just the extra memory will be enough and the CPU use from node won't step on the streaming, but not sure +*** DONE Create pads for all the talks +CLOSED: [2023-10-17 Tue 09:46] SCHEDULED: <2023-11-05 Sun> +:PROPERTIES: +:CUSTOM_ID: create-pads +:CREATED: [023-10-13 Fri 10:1] +:END: + +Because the pads refer to the next and previous talks and include the talk titles, this is best redone after the schedule has settled down. + + *** DONE Use the API to create pages based on all the slugs CLOSED: [2022-10-11 Tue 20:41] *** CANCELLED Figure out monitoring; maybe get everything daily and commit to git repo? |