From 7471712babf9d1d9eb86c1a578779b26774facd8 Mon Sep 17 00:00:00 2001
From: Sacha Chua <sacha@sachachua.com>
Date: Tue, 8 Nov 2022 11:56:17 -0500
Subject: Add mumble
---
2022/organizers-notebook/index.org | 62 ++++++++++++++++++++++++++++++++------
1 file changed, 52 insertions(+), 10 deletions(-)
(limited to '2022/organizers-notebook')
diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org
index 5b2ec130..e6a783bf 100644
--- a/2022/organizers-notebook/index.org
+++ b/2022/organizers-notebook/index.org
@@ -124,6 +124,22 @@ SCHEDULED: <2022-11-11 Fri>
:END:
*** TODO Update logbook with notes from e-mails :zaeph:
*** TODO Follow up with speakers based on their availability
+** TODO Use Mumble for backchannel coordination and also on-stage
+:PROPERTIES:
+:CUSTOM_ID: mumble
+:END:
+
+*** TODO Make sure volunteers can access Mumble :sachac:
+- [ ] FlowyCoder
+- [ ] jman
+- [ ] vetrivln
+*** DONE Generate certificates, add them to conf.org, and register the users :sachac:
+CLOSED: [2022-11-08 Tue 11:33]
+*** TODO Let sachac know how to manage the Mumble server, or update the config :bandali:
+- [ ] Add emacsconf-gen and emacsconf-dev channels
+- [ ] Give the emacsconf-gen and emacsconf-dev users access to them
+- [ ] Give the other organizers access to emacsconf-gen, emacsconf-dev, and org-private
+
** TODO Make a linear hyperlist for managing EmacsConf :sachac:
:PROPERTIES:
:CUSTOM_ID: hyperlist
@@ -935,8 +951,13 @@ CLOSED: [2022-10-13 Thu 13:46]
console.log(JSON.stringify([...document.querySelectorAll('.delete-room')].map((o) => { return { name: o.getAttribute('data-name'), path: o.getAttribute('data-path') }}).filter((o) => o.name.match(/^ec22/))))
see conf.org for the rest of the process
-*** TODO Add volunteers to the BBB rooms
-DEADLINE: <2022-11-18 Fri>
+*** DONE Add volunteers to the BBB rooms
+CLOSED: [2022-11-08 Tue 09:48] DEADLINE: <2022-11-18 Fri>
+
+- vetrivln: sat-am-dev, sun-am-dev
+- FlowyCoder: sat-pm-gen, sun-pm-gen
+- jman: sun-pm-gen
+
** INPROGRESS Coordinate and help volunteers :sachac:
:PROPERTIES:
:CUSTOM_ID: coordinate-volunteers
@@ -993,6 +1014,20 @@ During the conference, you will:
- adjust the volume if needed
- arrange windows and focus the BBB room on the speaker's webcam if needed
- if you like, you can be responsible for managing the track from conf.org on orga@res.emacsconf.org
+
+Dry run checklist:
+
+- [ ] Connect to the server
+ ssh orga@res.emacsconf.org -p 46668
+- [ ] Forward ports and connect via VNC
+- [ ] Find the OBS or start it if it is not running
+- [ ] Start recording
+- [ ] Play a video
+- [ ] Open two Firefox windows and arrange them
+- [ ] Manage windows on the workspace
+- [ ] Adjust the volume in OBS
+- [ ] SSH to the server and play a video off-screen
+- [ ] SSH to the server with X forwarding and adjust the volume off-screen
*** Broadcasting from local OBS (option A)
- You can copy the profile from your track or look inside it for the icecast mount point details:
@@ -1025,6 +1060,7 @@ During the conference, you will:
- gen: export TRACK=gen; export TRACK_PORT=5905; export SSH_PORT=46668
- dev: export TRACK=dev; export TRACK_PORT=5906; export SSH_PORT=46668
+
4. Copy the password:
scp emacsconf-$TRACK@res.emacsconf.org:~/.vnc/passwd vnc-passwd-$TRACK -p $SSH_PORT
@@ -1034,10 +1070,11 @@ During the conference, you will:
#+begin_example
ssh emacsconf-$TRACK@res.emacsconf.org -N -L $TRACK_PORT:127.0.0.1:$TRACK_PORT -p $SSH_PORT &
+ sleep 4 # Give it time to establish the tunnels
xvncviewer 127.0.0.1:$TRACK_PORT -shared -geometry 1280x720 -passwd vnc-passwd-$TRACK &
#+end_example
- (If this doesn't find a VNC server to connect to, you can start it with ~ssh emacsconf-$TRACK@res.emacsconf.org -p $SSH_PORT ~/bin/track-vnc~)
+ (If this doesn't find a VNC server to connect to, you can start it with ~ssh emacsconf-$TRACK@res.emacsconf.org -p $SSH_PORT /home/emacsconf-$TRACK/bin/track-vnc~)
6. Start *recording* (not streaming). If you don't see OBS when you connect, it's probably on workspace 2, so you can switch with Alt-2. If you still don't see it there, you can open a terminal with Alt-Enter and then run ~track-obs~. After you start recording, confirm that it is now broadcasting to the stream.
@@ -1053,11 +1090,8 @@ During the conference, you will:
9. Play a video. It should display the video and update the overlays. If you need to update the overlays manually, you can copy files from ~/data/emacsconf/overlays~ onto ~$HOME/other.png~ and ~$HOME/video.png~.
- #+begin_example
- cd /data/emacsconf/stream/2022
- track-mpv filename.webm
- #+end_example
-
+ You can play a video with ~play video-id~ (ex: ~play meetups~), or you can specify the filename (ex: ~play ~/stream/emacsconf-2022-meetups*.webm).
+
i3 cheat sheet:
- Alt-Enter creates a terminal
- Alt-d runs a command
@@ -1076,8 +1110,8 @@ During the conference, you will:
Other notes and tips:
- - Use OBS or ~pavucontrol~ to adjust the volume of BBB as needed.
- - You can use Emacs for emergency announcements.
+ - You can use Emacs for emergency or ad-hoc announcements.
+ - Use OBS or ~pavucontrol~ to adjust the volume of BBB as needed. You might be able to manage ~pavucontrol~ off-screen with ~ssh emacsconf-$TRACK@res.emacsconf.org -X -p $SSH_PORT pavucontrol~.
- You can also ~ssh emacsconf-$TRACK@res.emasconf.org -p 46668~ and start new processes from the command-line, such as using ~track-mpv~. If you specify commands when you call SSH instead of using an interactive shell, you may need to also specify DISPLAY=:5 (for the gen track) or DISPLAY=:6 (for the dev track), since ssh won't pick up the variables from ~.bashrc~.
*** Managing the stream from the agenda (option B2)
@@ -1256,6 +1290,14 @@ https://www.mail-archive.com/search?l=debconf-team@lists.debian.org&q=subject:%2
:END:
#+TOC: headlines 1 local
+** How do we want to handle organizer audio?
+
+- Mumble for walkie-talkie communications?
+ - Can we keep it off the stream more reliably, but still be able to choose to put it on the stream?
+ - We can keep it in the combined sink and then manually go to that
+ channel in our clients when we want to talk on stream
+ - Should we have a Gen channel and a Dev channel so that we can choose to speak into ?
+
** How do we want to make the full schedule more manageable?
:PROPERTIES:
--
cgit v1.2.3