diff options
| -rw-r--r-- | 2022/organizers-notebook.md | 130 | ||||
| -rw-r--r-- | 2022/organizers-notebook/index.org | 40 |
2 files changed, 118 insertions, 52 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md index 073d70b5..6315f4b2 100644 --- a/2022/organizers-notebook.md +++ b/2022/organizers-notebook.md @@ -104,9 +104,8 @@ on infrastructure - [Time-sensitive](#time-sensitive) - [Projects and other long-running tasks](#projects) - [Projects to bear in mind but which are not actual](#maybe-projects) -- [Find volunteers for tech-checks](#tech-checks):zaeph: -- [Update viewing instructions and watch pages](#write-viewing):zaeph: -- [Add category tags and possibly links between talks across 2022 and all previous years](#link-pages):needsowner:wiki: + +[Overall prioritization of effort](#overall) <a id="time-sensitive"></a> @@ -204,10 +203,17 @@ Blocked by [Figure out web-based file upload](#upload) - [Coordinate and help volunteers](#coordinate-volunteers):sachac: - [Prepare for prerecs](#prepare-prerec-process):zaeph: - [Delete all the EmacsConf BBB rooms from last year](#bbb-cleanup):chore:bbb: +- [Plan Etherpad use and hosting](#etherpad):sachac: +- [Update IRC instructions because of multiple tracks](#irc) - [Investigate streaming options, maybe OBS in the cloud](#streaming):corwin:zaeph: - [Work on the OBS scenes](#obs-scenes):zaeph:corwin: -- [Move scheduling and publishing code to Emacs on a VPS so that other people can help out](#publishing-vps):sachac: +- [Move scheduling and publishing code to Emacs on a VPS so that other people can help out](#publishing-sched):sachac: - [Add nice-to-have stuff to prepare.md](#extra-prepare):zaeph: +- [Find volunteers for tech-checks](#tech-checks):zaeph: +- [Update viewing instructions and watch pages](#write-viewing):zaeph: +- [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: Ordered by importance. @@ -300,6 +306,21 @@ For the admins on BBB. The list is accessible here: [Organization Settings](htt Should take no more than ~20′. +<a id="etherpad"></a> + +### TODO Plan Etherpad use and hosting :sachac: + +- 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> + - [Etherpad integration in Jitsi ](https://community.jitsi.org/t/tutorial-etherpad-integration-in-jitsi-meetings/99697) + + +<a id="irc"></a> + +### TODO Update IRC instructions because of multiple tracks + + <a id="streaming"></a> ### TODO Investigate streaming options, maybe OBS in the cloud :corwin:zaeph: @@ -332,7 +353,7 @@ Resources: - [ ] corwin is out from Nov 11-20, and we should start working on them before then. -<a id="publishing-vps"></a> +<a id="publishing-sched"></a> ### Move scheduling and publishing code to Emacs on a VPS so that other people can help out :sachac: @@ -359,36 +380,22 @@ Where: - SIL fonts choice -<a id="maybe-projects"></a> - -## Projects to bear in mind but which are not actual - - -### 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> - - <a id="tech-checks"></a> -## INPROGRESS Find volunteers for tech-checks :zaeph: +### INPROGRESS Find volunteers for tech-checks :zaeph: -### DONE Add entry in 2022/volunteer.md +#### DONE Add entry in 2022/volunteer.md -### INPROGRESS Write protocol for adding tech-checker volunteer +#### INPROGRESS Write protocol for adding tech-checker volunteer - Invite volunteer to BBB (ask core organizers) - Update <prepare.md> 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: @@ -404,7 +411,7 @@ From previous years: <a id="write-viewing"></a> -## STANDBY Update viewing instructions and watch pages :zaeph: +### STANDBY Update viewing instructions and watch pages :zaeph: Extra stuff to consider adding: @@ -413,9 +420,19 @@ Extra stuff to consider adding: Also add to watch page +<a id="publish-live"></a> + +### TODO Make talk pages easy to update when the talk is live :sachac: + + +<a id="video-platforms"></a> + +### TODO Set up talks on Toobnix and YouTube :sachac: + + <a id="link-pages"></a> -## TODO Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki: +### TODO Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki: - Prerequisite: Can edit wiki pages (<https://emacsconf.org/edit/>) - Goal: Make it easier for people to discover interesting related talks @@ -429,6 +446,20 @@ Also add to watch page You can make a new heading called `# Related talks` +<a id="maybe-projects"></a> + +## Projects to bear in mind but which are not actual + + +### 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> + + <a id="decisions"></a> # Things to figure out / decisions to make @@ -477,7 +508,7 @@ so we know what we need to scramble to do. <tbody> <tr> -<td class="org-left">schedule</td> +<td class="org-left"><a href="#sched-decision">schedule</a></td> <td class="org-left">one track</td> <td class="org-left"><b>DONE S: two tracks</b></td> <td class="org-left">aligned times, full roster</td> @@ -493,7 +524,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">upload</td> +<td class="org-left"><a href="#upload">upload</a></td> <td class="org-left">FTP</td> <td class="org-left"><b>S?: web-based</b></td> <td class="org-left">auto-encoded, preview (SReview?)</td> @@ -501,7 +532,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">stream</td> +<td class="org-left"><a href="#streaming">streaming</a></td> <td class="org-left">ffmpeg from computer</td> <td class="org-left">DONE OBS</td> <td class="org-left"><b>Z: OBS in cloud, switchable hosts</b></td> @@ -509,7 +540,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">prerec</td> +<td class="org-left"><a href="#prepare-prerec-process">prerec</a></td> <td class="org-left">play original</td> <td class="org-left">Z: normalize audio</td> <td class="org-left"><b>S: post as soon as talk is live</b></td> @@ -525,7 +556,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">watch page</td> +<td class="org-left"><a href="#write-viewing">watch page</a></td> <td class="org-left">stream</td> <td class="org-left"><b>S: + IRC</b></td> <td class="org-left">+ talk info, maybe even pad</td> @@ -533,7 +564,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">pad</td> +<td class="org-left"><a href="#etherpad">pad</a></td> <td class="org-left">one pad for conf</td> <td class="org-left">one pad per talk, wikimedia</td> <td class="org-left"><b>one pad per talk, self-hosted</b> so we can access API</td> @@ -541,7 +572,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">IRC</td> +<td class="org-left"><a href="#irc">IRC</a></td> <td class="org-left">#emacsconf, -org</td> <td class="org-left"><b>tracks, hallway, org</b></td> <td class="org-left">IRC volunteer copying to pads; maybe even IRC bots</td> @@ -549,7 +580,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">sched update</td> +<td class="org-left"><a href="#publishing-sched">sched update</a></td> <td class="org-left"><b>S: publish at start</b></td> <td class="org-left">update main sched</td> <td class="org-left">update talk pages</td> @@ -557,7 +588,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">talk pages</td> +<td class="org-left"><a href="#publish-live">talk pages</a></td> <td class="org-left"><b>S: link to stream, pad, IRC</b></td> <td class="org-left"><b>link to prerec when live</b></td> <td class="org-left">embed stream, pad, IRC, prerec</td> @@ -565,7 +596,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">other streams</td> +<td class="org-left"><a href="#other-streams">other streams</a></td> <td class="org-left">480p</td> <td class="org-left">+ Toobnix</td> <td class="org-left"><b>S: + YouTube</b></td> @@ -573,7 +604,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">other platforms</td> +<td class="org-left"> </td> <td class="org-left"><b>S: Toobnix & YT after event</b></td> <td class="org-left"> </td> <td class="org-left">S: Toobnix + YT when live</td> @@ -581,7 +612,7 @@ so we know what we need to scramble to do. <tr> -<td class="org-left">wiki</td> +<td class="org-left"><a href="#wiki-design">wiki</a></td> <td class="org-left">plain text, markdown</td> <td class="org-left"><b>S: some JS enrichment</b></td> <td class="org-left">more JS and CSS, embeds, videoplayer</td> @@ -624,6 +655,25 @@ Shifts will be Sat AM, Sat PM, Sun AM, or Sun PM per track. People can take mult - Figure out how publishing can be done in shifts - Console Emacs in a VM with everything set up for publishing to the wiki +<span class="timestamp-wrapper"><span class="timestamp">[2022-10-04 Tue]</span></span> + +- 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 + +<span class="timestamp-wrapper"><span class="timestamp">[2022-10-04 Tue]</span></span> + +- 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. + +<span class="timestamp-wrapper"><span class="timestamp">[2022-10-03 Mon]</span></span> + +- 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 + <a id="wiki-design"></a> @@ -1143,7 +1193,7 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau ### Test stream setup -[Stream](#stream) +[Stream](#other-streams) ### Set up MPV for captions @@ -1258,6 +1308,8 @@ Links: EmacsConf 2021 starting now: <https://emacsconf.org/2021/> +<a id="other-streams"></a> + ##### Stream @@ -1615,7 +1667,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping Make a table of the form -<table id="org4574d98" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> +<table id="org37a1830" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> <colgroup> diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org index e198898a..bf517b5c 100644 --- a/2022/organizers-notebook/index.org +++ b/2022/organizers-notebook/index.org @@ -66,6 +66,8 @@ on infrastructure #+TOC: headlines 1 local +[[#overall][Overall prioritization of effort]] + ** Time-sensitive :PROPERTIES: :CUSTOM_ID: time-sensitive @@ -235,7 +237,10 @@ Should take no more than ~20′. - 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 Update IRC instructions because of multiple tracks +:PROPERTIES: +:CUSTOM_ID: irc +:END: *** TODO Investigate streaming options, maybe OBS in the cloud :corwin:zaeph: DEADLINE: <2022-11-20 Sun> :PROPERTIES: @@ -264,7 +269,7 @@ DEADLINE: <2022-11-11 Fri> *** Move scheduling and publishing code to Emacs on a VPS so that other people can help out :sachac: :PROPERTIES: -:CUSTOM_ID: publishing-vps +:CUSTOM_ID: publishing-sched :END: Ideal: - Update pages with watching information, additional resources, etc. as talks go live @@ -313,6 +318,15 @@ From previous years: Extra stuff to consider adding: - Suggestions for mpv-filter to invert colourscape. Also add to watch page +*** TODO Make talk pages easy to update when the talk is live :sachac: +:PROPERTIES: +:CUSTOM_ID: publish-live +:END: +*** TODO Set up talks on Toobnix and YouTube :sachac: +:PROPERTIES: +:CUSTOM_ID: video-platforms +:END: + *** TODO [#C] Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki: :PROPERTIES: :CUSTOM_ID: link-pages @@ -362,18 +376,18 @@ so we know what we need to scramble to do. |-----------------+-------------------------------+-----------------------------+------------------------------------------------------| | [[#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* | +| [[#upload][upload]] | FTP | *S?: web-based* | auto-encoded, preview (SReview?) | +| [[#streaming][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 | +| [[#write-viewing][watch page]] | stream | *S: + IRC* | + talk info, maybe even pad | +| [[#etherpad][pad]] | one pad for conf | one pad per talk, wikimedia | *one pad per talk, self-hosted* so we can access API | +| [[#irc][IRC]] | #emacsconf, -org | *tracks, hallway, org* | IRC volunteer copying to pads; maybe even IRC bots | +| [[#publishing-sched][sched update]] | *S: publish at start* | update main sched | update talk pages | +| [[#publish-live][talk pages]] | *S: link to stream, pad, IRC* | *link to prerec when live* | embed stream, pad, IRC, prerec | +| [[#other-streams][other streams]] | 480p | + Toobnix | *S: + YouTube* | +| [[#other-platforms][other platforms]] | *S: Toobnix & YT after event* | | S: Toobnix + YT when live | +| [[#wiki-design][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: @@ -896,7 +910,7 @@ Links: ***** Stream :PROPERTIES: -:CUSTOM_ID: stream +:CUSTOM_ID: other-streams :END: ****** Low-res stream |