diff options
Diffstat (limited to '')
| -rw-r--r-- | 2022/organizers-notebook.md | 77 | ||||
| -rw-r--r-- | 2022/organizers-notebook/index.org | 11 | ||||
| -rw-r--r-- | 2022/talks/orgsuperlinks.md | 50 |
3 files changed, 87 insertions, 51 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md index 6539eb39..4af5a3a1 100644 --- a/2022/organizers-notebook.md +++ b/2022/organizers-notebook.md @@ -27,8 +27,9 @@ Time-sensitive tasks: Other projects: +- [Record intro/outro for day-1 and day-2](#org4067ddb):zaeph: - [Prepare for prerecs](#prepare-prerec-process):zaeph: -- [Work on the OBS scenes](#obs-scenes):zaeph:corwin: +- [Work on the OBS scenes](#obs-scenes):zaeph:corwin:sachac: - [Make something to display between talks](#intro):akshay196: - [Create protocol for live Q&A](#live-protocol):zaeph: - [Find volunteers for tech-checks](#tech-checks):zaeph: @@ -446,8 +447,9 @@ chatter in the other lists cc’d in this message; thank you. # Projects and other long-running tasks +- [Record intro/outro for day-1 and day-2](#org4067ddb):zaeph: - [Prepare for prerecs](#prepare-prerec-process):zaeph: -- [Work on the OBS scenes](#obs-scenes):zaeph:corwin: +- [Work on the OBS scenes](#obs-scenes):zaeph:corwin:sachac: - [Make something to display between talks](#intro):akshay196: - [Create protocol for live Q&A](#live-protocol):zaeph: - [Find volunteers for tech-checks](#tech-checks):zaeph: @@ -472,6 +474,11 @@ chatter in the other lists cc’d in this message; thank you. Ordered by importance. +<a id="org4067ddb"></a> + +## TODO Record intro/outro for day-1 and day-2 :zaeph: + + <a id="prepare-prerec-process"></a> ## DONE Prepare for prerecs :zaeph: @@ -525,7 +532,7 @@ Make changes in [As prerecorded talks come in](#prerec-process) <a id="obs-scenes"></a> -## TODO Work on the OBS scenes :zaeph:corwin: +## INPROGRESS Work on the OBS scenes :zaeph:corwin:sachac: - [ ] corwin is out from Nov 11-20, and we should start working on them before then. @@ -788,7 +795,7 @@ Agenda: - Dev: rsync -avze ssh emacsconf-dev@res.emacsconf.org:~/.config/obs-studio/basic/profiles/ ~/.config/obs-studio/basic/profiles/ - Sacha will turn off the OBS recordings on res so that you can test streaming from your computer - - If you’re doing this independently, you can jump ahead to “Test connecting to the VNC” in order to stop the recording yourself + - If you’re doing this independently, you can jump ahead to &lsquo ;Test connecting to the VNC’ in order to stop the recording yourself - Verify with MPV: @@ -839,7 +846,7 @@ Agenda: cd /data/emacsconf/stream/2022 track-mpv filename.webm -11. Test Q&A. You can either wait for the video to finish or quit it with “q”. +11. Test Q&A. You can either wait for the video to finish or quit it with &lsquo ;q’. You can paste in the URLs or use `firefox /data/emacsconf/2022/index-$TRACK.html` @@ -953,7 +960,7 @@ Can I use aeneas for alignment instead? Reflow the .txt file and reupload to res if needed call ../run-aeneas.sh from the directory with the opus or ogg and the txt file -sachac@res-https://emacsconf.org/2022/talks/~/current/meetups$ python3 -m aeneas.tools.execute\_task emacsconf-2022-meetups–attending-and-organizing-emacs-meetups–bhavin-gandhi–main.opus reflowed.srt “task\_language=eng|os\_task\_file\_format=json|is\_text\_type=subtitles” output.json +sachac@res-https://emacsconf.org/2022/talks/~/current/meetups$ python3 -m aeneas.tools.execute\_task emacsconf-2022-meetups–attending-and-organizing-emacs-meetups–bhavin-gandhi–main.opus reflowed.srt &lsquo ;task\_language=eng|os\_task\_file\_format=json|is\_text\_type=subtitles’ output.json I might try out lhotse and torchaudio someday, but it’s low priority. aeneas seems to do a reasonable job of @@ -1057,8 +1064,8 @@ Thank you for volunteering for ${conf-name} ${year}! We’ve set up ${backstage} as the backstage area where you can view the videos and resources uploaded so far. You can access it with the -username "${backstage-user}“ and the password ”${backstage-password}“. -Please keep the backstage password and other speakers’ talk resources +username "${backstage-user}&lsquo ; and the password ’${backstage-password}&lsquo ;. +Please keep the backstage password and other speakers” talk resources secret. For some ideas on ways to help, you can check out @@ -1103,8 +1110,8 @@ great to have you on board.${wrap} We’ve set up ${backstage} as the backstage area where you can view the videos and resources uploaded so far. You can access it with the -username "${backstage-user}“ and the password ”${backstage-password}“. -Please keep the backstage password and other speakers’ talk resources +username "${backstage-user}&lsquo ; and the password ’${backstage-password}&lsquo ;. +Please keep the backstage password and other speakers” talk resources secret. If you see a talk that you’d like to caption, you can e-mail me at sacha@sachachua.com and I can reserve it for you. Then you can correct any misrecognized words, fix capitalizations, remove filler @@ -1177,7 +1184,7 @@ in prod or docker container ### DONE icecast on live0 -(find-file “/ssh:live|sudo::/etc/icecast2/icecast.xml”) +(find-file &lsquo ;/ssh:live|sudo::/etc/icecast2/icecast.xml’) #### DONE Set up watch/gen-480p @@ -1330,7 +1337,7 @@ see conf.org for the rest of the process <a id="coordinate-volunteers"></a> -## TODO Coordinate and help volunteers :sachac: +## INPROGRESS Coordinate and help volunteers :sachac: - <../volunteer> - Figure out what information volunteers need in order to feel @@ -1347,7 +1354,7 @@ see conf.org for the rest of the process <a id="streaming"></a> -## TODO Investigate streaming options, maybe OBS in the cloud :sachac: +## DONE Investigate streaming options, maybe OBS in the cloud :sachac: Current status @@ -1359,7 +1366,7 @@ Goals: - [X] Have another session with the sound isolated - [X] Split the audio so that we can join the Q&A room before the MPV ends - handled by automatic scene switcher detecting mpv - [X] Control MPV from the commandline: track-mpv appears in the correct display, and it can also be controlled via the socket like this: - echo ’{ “command”: [“loadfile”, “test2.webm”] }’ | socat - ~/mpv-socket-emacsconf-dev + echo ’{ &lsquo ;command’: [&lsquo ;loadfile’, &lsquo ;test2.webm’] }’ | socat - ~/mpv-socket-emacsconf-dev - [ ] Share the window instead of the desktop? @@ -1376,7 +1383,7 @@ Goals: 3. Start up the VNC server if it’s not already running - ssh emacsconf-$TRACK@res.emacsconf.org “~/bin/track-vnc” + ssh emacsconf-$TRACK@res.emacsconf.org &lsquo ;~/bin/track-vnc’ 4. Forward your local ports @@ -1493,8 +1500,8 @@ and type your message in. #### Kill the VNC server: -ssh emacsconf-gen@res.emacsconf.org “vncserver -kill” -ssh emacsconf-dev@res.emacsconf.org “vncserver -kill” +ssh emacsconf-gen@res.emacsconf.org &lsquo ;vncserver -kill’ +ssh emacsconf-dev@res.emacsconf.org &lsquo ;vncserver -kill’ <table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> @@ -1522,7 +1529,7 @@ ssh emacsconf-dev@res.emacsconf.org “vncserver -kill” ### Other notes There are sockets in the home directory for MPV control if you want to keep that process. -echo ’{ “command”: [“loadfile”, “test2.webm”] }’ | socat - ~/mpv-socket-emacsconf-dev +echo ’{ &lsquo ;command’: [&lsquo ;loadfile’, &lsquo ;test2.webm’] }’ | socat - ~/mpv-socket-emacsconf-dev ### DONE Move my conf.org setup to res so that we can control everything from there @@ -1617,7 +1624,7 @@ so that the streamer can adjust volume offscreen? - <https://obsproject.com/forum/threads/run-obs-on-vm-in-the-cloud.122543/> -### TODO recruit at least one more person to help operate the “video bouncer” +### TODO recruit at least one more person to help operate the &lsquo ;video bouncer’ <a id="maybe-projects"></a> @@ -2494,7 +2501,7 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau Hi, ${speakers-short}! Just a quick note to let you know that I’ve downloaded your -submission for “${title}”. We’ve added your submission to the backstage +submission for &lsquo ;${title}’. We’ve added your submission to the backstage area at ${backstage} (username: ${backstage-user}, password: ${backstage-password}), and we’ll post the files on your talk page when the talk is public. A quick check shows that your video is about @@ -2825,9 +2832,9 @@ Exception: [CHECK is unavailable](#check-gone) with instructions, so please check there. Let me know if you don’t get them. - Private messages: - - (erc-message “PRIVMSG” (format “%s You can use this BBB room: %s . I’ll join you there shortly to set up the room and do the last-minute tech check.” nick room-url)) - - (erc-message “PRIVMSG” (format “%s The collaborative pad we’ll be using for questions is at %s . We’ll collect questions from #emacsconf and put them there. If you’d like to jump to your part of the document, you might be able to keep an eye on questions. Alternatively, we can read questions to you.” nick conf-collaborative-pad)) - - (erc-message “PRIVMSG” (format “%s Leo Vivier will join when it’s time, and he will give you the go-ahead when it’s time to present. See you in the BBB room!” nick)) + - (erc-message &lsquo ;PRIVMSG’ (format &lsquo ;%s You can use this BBB room: %s . I’ll join you there shortly to set up the room and do the last-minute tech check.’ nick room-url)) + - (erc-message &lsquo ;PRIVMSG’ (format &lsquo ;%s The collaborative pad we’ll be using for questions is at %s . We’ll collect questions from #emacsconf and put them there. If you’d like to jump to your part of the document, you might be able to keep an eye on questions. Alternatively, we can read questions to you.’ nick conf-collaborative-pad)) + - (erc-message &lsquo ;PRIVMSG’ (format &lsquo ;%s Leo Vivier will join when it’s time, and he will give you the go-ahead when it’s time to present. See you in the BBB room!’ nick)) - CHECK directs speaker to available room with `/checkin <room> <nick>` - Speaker joins talk room - CHECK makes speaker presenter and moderator, does last-minute tech check @@ -3426,7 +3433,7 @@ mpv –vf=negate $url Extra stuff to consider adding: - DONE Suggestions for themes (especially wrt colourscape) -- DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it’s easier to write, record, and edit your voiceover, and then record the video to go along with it.“ +- DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it’s easier to write, record, and edit your voiceover, and then record the video to go along with it.&lsquo ; - DONE Allowing speakers to plant questions, esp. to cover tangential stuff that couldn’t fit in the prerec @@ -3450,7 +3457,7 @@ See the bottom of conf.org for some automated validation Extra stuff to consider adding: - DONE Suggestions for themes (especially wrt colourscape) -- DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it’s easier to write, record, and edit your voiceover, and then record the video to go along with it.“ +- DONE “Please don’t squeeze your talk by fast-forwarding your speech. Trimming silences and filler words can help, though. Sometimes it’s easier to write, record, and edit your voiceover, and then record the video to go along with it.&lsquo ; - DONE Allowing speakers to plant questions, esp. to cover tangential stuff that couldn’t fit in the prerec @@ -3558,7 +3565,7 @@ Slightly annoying to do with JS/CSS because I want it to fall back to an interle ## DONE Process confirmations as we receive them :sachac:zaeph: -- Reply to the speaker and Cc -submit to confirm the confirmation. Something like “Confirming your confirmation, no reply needed to this one. Thank you!” +- Reply to the speaker and Cc -submit to confirm the confirmation. Something like &lsquo ;Confirming your confirmation, no reply needed to this one. Thank you!’ - Update talk to WAITING\_FOR\_PREREC in conf.org - Add a note in the logbook (C-c C-z - org-add-note) for the talk entry - Add :PUBLIC\_EMAIL: t if given permission to use the e-mail on the @@ -3953,15 +3960,15 @@ It would be nice to have track-specific icals as well. zaeph: I can work on it, but I’m not experienced in this domain, so I’d prefer to be a back-up. task is currently with bandali -Lesson learned from last year: “Since people kept running into ftp +Lesson learned from last year: &lsquo ;Since people kept running into ftp problems, we might want to set up a web-frontend next year to minimise -problems.” +problems.’ Maybe we could ask some of the volunteers who wanted to help us with the infra? It shouldn’t be complicated to deploy a ready-made solution. -“file drop” is a common keyword for looking for information. +&lsquo ;file drop’ is a common keyword for looking for information. Considerations: - Probably run it on media.emacsconf.org @@ -4120,7 +4127,7 @@ Where: Nice if there’s an Ansible playbook sachac’s notes: - <file:///home/sacha/code/docker/emacsconf-publish/> + <file:///home/zaeph/code/docker/emacsconf-publish/> - probably good to set it up on front It’s now on front. @@ -4268,8 +4275,8 @@ generated captions that we can use as a starting point. We’ve set up ${backstage} as the backstage area where you can view the videos and resources uploaded so far. You can access it with the -username "${backstage-user}“ and the password ”${backstage-password}“. -Please keep the backstage password and other speakers’ talk resources +username "${backstage-user}&lsquo ; and the password ’${backstage-password}&lsquo ;. +Please keep the backstage password and other speakers” talk resources secret. ${backstage-use}${wrap} Thank you! @@ -4649,7 +4656,7 @@ ${captions} Hi, ${name}! I think we haven’t heard from you since we accepted your EmacsConf -${year} proposal for "${title}“. EmacsConf coming up soon, so I wanted +${year} proposal for "${title}&lsquo ;. EmacsConf coming up soon, so I wanted to check in with you to see how you’re doing. Could you please e-mail us to let us know if you’re still working on @@ -5358,10 +5365,10 @@ see emacsconf-import-comments-from-etherpad-text format makes it harder not only for the organizers, but also for the speakers themselves (since they will have to rethink their presentation). Maybe we can have an e-mail template for a quick - reply that says something like “Just in case we need to squeeze + reply that says something like &lsquo ;Just in case we need to squeeze talks into shorter times, could you please also propose an outline for a possible 10-minute talk that could get people interested in - your topic and point them to where they can find out more?” + your topic and point them to where they can find out more?’ - Two people is the sweet number of reviewers to have for the proposals before sending the notifications, and there’d be diminishing returns with more. Two is enough to release the pressure diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org index e4185568..06167a87 100644 --- a/2022/organizers-notebook/index.org +++ b/2022/organizers-notebook/index.org @@ -183,6 +183,7 @@ chatter in the other lists cc'd in this message; thank you. #+TOC: headlines 1 local Ordered by importance. +** TODO Record intro/outro for day-1 and day-2 :zaeph: ** DONE Prepare for prerecs :zaeph: CLOSED: [2022-10-29 Sat 09:58] DEADLINE: <2022-11-04 Fri> :PROPERTIES: @@ -231,7 +232,7 @@ We need time after the prerecs get submitted to: Make changes in [[#prerec-process]] -** TODO Work on the OBS scenes :zaeph:corwin: +** INPROGRESS Work on the OBS scenes :zaeph:corwin:sachac: DEADLINE: <2022-11-11 Fri> :PROPERTIES: :CUSTOM_ID: obs-scenes @@ -988,7 +989,7 @@ console.log(JSON.stringify([...document.querySelectorAll('.delete-room')].map((o see conf.org for the rest of the process *** TODO Add volunteers to the BBB rooms DEADLINE: <2022-11-05 Sat> -** TODO Coordinate and help volunteers :sachac: +** INPROGRESS Coordinate and help volunteers :sachac: :PROPERTIES: :CUSTOM_ID: coordinate-volunteers :END: @@ -1004,8 +1005,8 @@ DEADLINE: <2022-11-05 Sat> :PROPERTIES: :CUSTOM_ID: schedule-volunteer-qna :END: -** TODO Investigate streaming options, maybe OBS in the cloud :sachac: -DEADLINE: <2022-11-20 Sun> +** DONE Investigate streaming options, maybe OBS in the cloud :sachac: +CLOSED: [2022-11-06 Sun 18:16] DEADLINE: <2022-11-20 Sun> :PROPERTIES: :CUSTOM_ID: streaming :END: @@ -1206,8 +1207,6 @@ so that the streamer can adjust volume offscreen? - https://github.com/soonum/hubangl - https://obsproject.com/forum/threads/run-obs-on-vm-in-the-cloud.122543/ *** TODO recruit at least one more person to help operate the "video bouncer" - - * Projects to bear in mind but which are not actual :PROPERTIES: :CUSTOM_ID: maybe-projects diff --git a/2022/talks/orgsuperlinks.md b/2022/talks/orgsuperlinks.md index b86d9624..1fcf4c15 100644 --- a/2022/talks/orgsuperlinks.md +++ b/2022/talks/orgsuperlinks.md @@ -7,25 +7,55 @@ <!-- You can manually edit this file to update the abstract, add links, etc. ---> -# Linking headings with org-super-links (poor-man's Zettelkasten) +# Linking headings (poor-man's Zettelkasten) and defining advanced task dependencies Karl Voit (he/him, IRC: publicvoit, <mailto:EmacsConf22@Karl-Voit.at>) [[!inline pages="internal(2022/info/orgsuperlinks-before)" raw="yes"]] -As written on -<https://karl-voit.at/2020/06/14/Zettelkasten-concerns> Karl thinks -that a full-blown Zettelkasten workflow is not always a perfect match -for a given set of requirements. +As written in [this blog +article](https://karl-voit.at/2020/06/14/Zettelkasten-concerns), Karl +thinks that a full-blown Zettelkasten workflow is not always a perfect +match for a given set of requirements. -To him, the most important aspects of the Zettelkasten method are the -bi-directional links between arbitrary headings. If you want to use +To him, the most important aspect of the Zettelkasten method are the +**bi-directional links between arbitrary headings**. If you want to use such links without the additional burden and benefit of a Zettelkasten implementation, you might want to learn how -org-super-links is able to help you here. +bi-directional links are able to help you here. -In this talk, you will see how org-super-links are being used in -the author's setup for linking headings. +In this talk, you will see a demo how links are used in the author's +setup for linking headings and **defining advanced dependencies between +todo headings**. +You can find [the **self-contained demo file** on +Gitlab.com](https://gitlab.com/publicvoit/orgmode-link-demo). It +consists of various packages and some Elisp glue to create these methods: + +- Bi-directional links between headings: + - [org-super-links](https://github.com/toshism/org-super-links) with `org-super-links-org-ql` and `org-super-links-org-rifle` + - `org-super-links-quick-insert-inline-link` + - `org-super-links-quick-insert-drawer-link` + - [org-linker](https://github.com/toshism/org-linker) + +- Advanced dependencies: + - [org-edna](https://www.nongnu.org/org-edna-el/) + - [org-linker-edna](https://github.com/toshism/org-linker-edna) + +- Search, completion and narrowing: + - [helm](https://emacs-helm.github.io/helm/) + - [helm-org](https://github.com/emacs-helm/helm-org) + - [org-ql](https://github.com/alphapapa/org-ql) with `helm-org-ql` + +- Adding CREATED properties for new headings: [org-expiry](https://git.sr.ht/~bzg/org-contrib/blob/master/lisp/org-expiry.el) (not necessary for any demo functionality) + +More on bi-directional links and Karl's Org mode projects: + +- [UOMF: Linking Headings With org-super-links (Poor-Man's Zettelkasten)](https://karl-voit.at/2020/07/22/org-super-links/) +- [UOMF: On How to Define Projects in Org Mode](https://karl-voit.at/2019/11/03/org-projects/) +- [A Draft Workflow for Advanced Project Management Using Org Mode and Org Edna](https://karl-voit.at/2020/08/14/project-mgt-draft/) +- [Zettelkasten/Org-roam/Org-brain Is Crap](https://karl-voit.at/2020/06/14/Zettelkasten-concerns/) + +[More Emacs-related articles by Karl](https://karl-voit.at/tags/emacs/) [[!inline pages="internal(2022/info/orgsuperlinks-after)" raw="yes"]] |