diff options
author | Sacha Chua <sacha@sachachua.com> | 2022-10-01 08:45:23 -0400 |
---|---|---|
committer | Sacha Chua <sacha@sachachua.com> | 2022-10-01 08:45:23 -0400 |
commit | b2b72223a254c408613071b661c38c93614dc47a (patch) | |
tree | cf0fea08441881268dbc9011d0398d0a13dbd3eb | |
parent | f06ee57b80bf3fd74e31fcd14eae108fbebbb49a (diff) | |
download | emacsconf-wiki-b2b72223a254c408613071b661c38c93614dc47a.tar.xz emacsconf-wiki-b2b72223a254c408613071b661c38c93614dc47a.zip |
Add ID for easier linking
Diffstat (limited to '')
-rw-r--r-- | 2022/organizers-notebook.md | 133 | ||||
-rw-r--r-- | 2022/organizers-notebook.org | 3 |
2 files changed, 111 insertions, 25 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md index 7f797a7b..f21e6fa2 100644 --- a/2022/organizers-notebook.md +++ b/2022/organizers-notebook.md @@ -4,14 +4,14 @@ # Table of Contents -1. [Current tasks / status](#current) -2. [Things to figure out / decisions to make](#decisions) -3. [Roles needed](#roles) -4. [Other tasks and processes](#other) -5. [Task archive](#org512295e) -6. [Communications](#comms) -7. [Supporting code](#code) -8. [Lessons learned](#lessons) +- [Current tasks / status](#current) +- [Things to figure out / decisions to make](#decisions) +- [Roles needed](#roles) +- [Other tasks and processes](#other) +- [Task archive](#org81f9c00) +- [Communications](#comms) +- [Supporting code](#code) +- [Lessons learned](#lessons) <a id="current"></a> @@ -116,21 +116,27 @@ to their availability, and will add the allocated time slots for the talks in the coming weeks. -### INPROGRESS Come up with workflow when confirmation is received :zaeph: +### DONE Come up with workflow when confirmation is received :sachac: +- Reply to the speaker and Cc -submit to confirm the confirmation (no reply needed) - Update talk to WAITING\_FOR\_PREREC in conf.org -- Add :PUBLIC\_EMAIL: if different from :EMAIL: (might not be necessary if we ask for public-emails in the CFP form) -- Add either :PUBLIC\_EMAIL: or :EMAIL: (whichever comes first) to talk-pages (might be aided by a function) -- ? +- 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 + talk page, or set it to an alternative e-mail if provided. +- Update the public wiki's ${year}/talks/{$slug}.md page to add the + e-mail address as <mailto:person@example.com> on the speaker + information line. ### BLOCKED Prepare email for nudging speakers to send prerec, and inform on upload workflow :timesensitive:needsowner: -Blocked by [Figure out web-based file upload](#orge79c119) +Blocked by [Figure out web-based file upload](#org5fba480) ### TODO Remind people about confirming e-mail communications :sachac:email: +Look for the TO\_CONFIRM status + ### TODO Send people schedule information and doublecheck their availability/Q&A preference :sachac:email: @@ -138,15 +144,45 @@ Blocked by [Figure out web-based file upload](#orge79c119) ### Archive :ARCHIVE: -## Long-running tasks +## Projects and other long-running tasks Ordered by importance. ### TODO Figure out web-based file upload :needsowner:zaeph:bandali: -Lesson learned from last year: "Since people kept running into ftp problems, we might want to set up a web-frontend next year to minimise 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. +Lesson learned from last year: "Since people kept running into ftp +problems, we might want to set up a web-frontend next year to minimise +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. +Considerations: + +- Probably run it on media.emacsconf.org +- Bonus features: + - password-protected or hidden behind some kind of authentication or hidden behind some kind of URL, so we don't have to worry too much about spam + - extra points for sending speakers links to upload to specific folders so that we can separate resources by talk + - Resumable uploads would be good, since some speakers had a hard time with unreliable connections +- What other conferences do: + - LibrePlanet uses plain FTP and recommends FileZilla <https://libreplanet.org/wiki/Video_upload_instructions> + - FOSSDEM uses Pentabarf to receive uploads <https://archive.fosdem.org/2022/manuals/program/speaker/> + - DebConf uses SReview(?) + - FOSSGIS uses Seafile <https://vmx.cx/cgi-bin/blog/index.cgi/video-uploads-for-an-online-conference%3A2021-06-12%3Aen%2Cconference%2Cgeo> +- Some options: + - <https://www.projectsend.org/> + - <https://github.com/pomf/pomf> + - <https://github.com/dutchcoders/transfer.sh/> + - <https://github.com/epoupon/fileshelter> + - <https://github.com/mickael-kerjean/filestash> + - <https://gitlab.com/mojo42/Jirafeau> + - <https://github.com/eikek/sharry> + - <https://github.com/YouTransfer/YouTransfer> + - <https://github.com/psi-4ward/psitransfer> + - NextCloud #### TODO Create 2022/upload.md with the same workflow as last year for a start @@ -179,8 +215,18 @@ We need time after the prerecs get submitted to: ### TODO Investigate streaming options, maybe OBS in the cloud :corwin: - 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 rmtp (instead of just his webcam). - **\*** TODO corwin: plan an approach to use a centralized OBS/nginix "bouncer" :corwin: +- 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). +- With a long day, we may want to be able to schedule hosts/streamers/publishers in shifts +- Ideal: Easy reproducible setup to spin up an OBS VM with scenes set up, allowing multiple users to connect to it at the same time. Maybe x2go or vnc? VMs with 8 vCPUs and a vGPU cost more, so it would be good to figure out what's needed, spin it down, and then spin it up maybe the day before or something like that. +- Plus points if we can control the OBS via password-protected websocket so we can tell it to switch scenes (and even more points if we do so from Emacs, maybe via that obs-websocket.el ;) ). MPV is also controllable via IPC, so we can use the same MPV player and then switch videos around. Maybe mpvc? <https://unix.stackexchange.com/questions/664728/how-can-i-control-mpv-in-command-line> +- Probably Linode's Dedicated 32 GB + RTX6000 GPU x1 at $1.50 an hour for 2-3 days + dev time, since live.emacsconf.org is in Linode as well + +Resources: + +- <https://blog.wirelessmoves.com/2021/07/running-obs-studio-in-the-cloud.html> + + +#### TODO corwin: plan an approach to use a centralized OBS/nginix "bouncer" :corwin: #### TODO corwin: document such that someone else could use/fix it :corwin: @@ -206,6 +252,27 @@ We need time after the prerecs get submitted to: ### Archive :ARCHIVE: +### Move scheduling and publishing code to Emacs on a VPS so that other people can help out :sachac: + +Ideal: + +- Update pages with watching information, additional resources, etc. as talks go live +- Update the schedule as needed (cancelled or reordered talks, etc.) + +Where: + +- front? my own VPS? + + +#### TODO Set up on my own VPS (or somewhere) for testing :sachac: + +- [ ] Private wiki +- [ ] Public wiki +- [ ] Emacsconf-el +- [ ] Publishing to the wiki +- [ ] Consult and Embark shortcuts for navigation + + ## TODO Write viewing instructions :zaeph: Extra stuff to consider adding: @@ -266,7 +333,23 @@ List of talks: <https://emacsconf.org/talks/> # Things to figure out / decisions to make -## TODO Do we want to use JS on the wiki? +## How do we want to make the full schedule more manageable? + +- 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) +- Figure out how publishing can be done in shifts + - 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? + +Ideas to consider: + +- Toggling local time display on the schedule +- Making organizers-notebook nicer to browse through (or maybe use organice?) +- Improve the video player (resolution switching?) ### BLOCKED ?: Figure out JS and CSS niceties that will make organizers-notebook more enjoyable to browse through :css:js: @@ -590,7 +673,7 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau ### Test stream setup -[Stream](#orgde211ba) +[Stream](#orge32ff26) ### Set up MPV for captions @@ -907,7 +990,7 @@ Exceptions: ### Send thanks -[Thank you, next steps](#orge1e207f) +[Thank you, next steps](#orgd715409) ### Extract the opening and closing remarks @@ -1058,7 +1141,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping Make a table of the form -<table id="org9a13e40" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> +<table id="org9933b4e" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> <colgroup> @@ -1311,12 +1394,12 @@ sudo -iu ikiwiki – ikiwiki –setup ~ikiwiki/emacsconf.setup mpv –vf=negate $url -<a id="org512295e"></a> +<a id="org81f9c00"></a> # Task archive -## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#org8a63ebe), Oct 7 for everything :organizers: +## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#org551adbe), Oct 7 for everything :organizers: - zaeph: will start reviewing on Sep 21 @@ -1376,7 +1459,7 @@ That will help more people subtitle things <https://emacsconf.org/2022/volunteer> -## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#org8a63ebe), Oct 7 for everything :organizers: +## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#org551adbe), Oct 7 for everything :organizers: - zaeph: will start reviewing on Sep 21 diff --git a/2022/organizers-notebook.org b/2022/organizers-notebook.org index 7dc96386..a8525687 100644 --- a/2022/organizers-notebook.org +++ b/2022/organizers-notebook.org @@ -176,6 +176,9 @@ We need time after the prerecs get submitted to: *** TODO Investigate streaming options, maybe OBS in the cloud :corwin: DEADLINE: <2022-11-20 Sun> +:PROPERTIES: +:CUSTOM_ID: obscloud +: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). - With a long day, we may want to be able to schedule hosts/streamers/publishers in shifts |