diff options
Diffstat (limited to '2024/organizers-notebook/index.org')
-rw-r--r-- | 2024/organizers-notebook/index.org | 98 |
1 files changed, 84 insertions, 14 deletions
diff --git a/2024/organizers-notebook/index.org b/2024/organizers-notebook/index.org index a5fd8d3f..bbb1032a 100644 --- a/2024/organizers-notebook/index.org +++ b/2024/organizers-notebook/index.org @@ -1,4 +1,4 @@ -# [[elisp:(progn (memoize 'emacsconf-get-talk-info "5 seconds") (org-md-export-to-markdown) (memoize-restore 'emacsconf-get-talk-info))][Export this file to Markdown]] +# [[elisp:(progn (memoize 'emacsconf-get-talk-info "5 seconds") (org-md-export-to-markdown) (memoize-restore 'emacsconf-get-talk-info))][EPpxport this file to Markdown]] #+TAGS: emacsconf # [[elisp:(memoize 'emacsconf-get-talk-info "5 seconds")][Memoize emacsconf-get-talk-info]] - [[elisp:(memoize-restore 'emacsconf-get-talk-info)][Unmemoize]] #+todo: TODO(t) SOMEDAY STARTED INPROGRESS(i) WAITING(w) STANDBY(s) BLOCKED(b) | DONE(x) CANCELLED(c) @@ -179,6 +179,7 @@ CLOSED: [2024-11-02 Sat 11:38] (emacsconf-schedule-validation-functions '(emacsconf-schedule-validate-time-constraints ;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered + emacsconf-schedule-validate-no-cancelled-talks emacsconf-schedule-validate-all-talks-present emacsconf-schedule-validate-no-duplicates))) (setq emacsconf-schedule-plan @@ -187,7 +188,6 @@ CLOSED: [2024-11-02 Sat 11:38] papers ; <= 10:00 project ; any org-update ; <= 13:00 EST Sat or >= 15:00 Sat or <= 14:00 Sun, Sat preferred - flp ; any, Sat pref color ; <= 12:00 sat pref (lunch :start "12:00") theme ; >= 12:30 @@ -412,15 +412,30 @@ SCHEDULED: <2024-11-15 Fri> :CREATED: [2024-11-02 Sat 11:50] :END: ** IRC web client -*** TODO Ask libera.chat to increase connections allowed from chat.emacsconf.org on Dec 7 and 8 +*** WAITING Ask libera.chat to increase connections allowed from chat.emacsconf.org on Dec 7 and 8 ** IRC announcements *** DONE Confirm manual IRC announcements CLOSED: [2024-11-02 Sat 12:05] *** TODO Confirm automated IRC announcements from res -** TODO Publishing videos to the media server +** Media + +*** TODO Switch public media to unprotected root before the conference +SCHEDULED: <2024-11-29 Fri> +:PROPERTIES: +:CREATED: [2024-11-12 Tue 14:18] +:END: + +1. Clear public media directory. +2. Set =media_protect_root= to false in Ansible =group_vars/all.yml=. +3. =ansible-playbook -i inventory.yml prod-playbook.yml --tags media= + +You can generate the index with =emacsconf-publish-update-media=. ** TODO Publishing resources to the wiki -*** +ansible-playbook -i inventory.yml prod-playbook.yml --tags publish + + +** TODO Publishing videos to the media server ** Playing videos, switching to windows *** TODO Generate test videos for everything @@ -472,24 +487,79 @@ The server running bbb.emacsverse.org has been decommissioned, since the nonprof - also includes some notes on hosting - Nice thing about running our own server: we can make one room per speaker, pre-assign their URLs, and let people stay as long as they want in recorded Q&A sessions +Recommendation: + +We spin up a shared CPU 4GB under bandali's Linode +account (for bandwidth pooling and easier +reimbursement), do the setup/testing over the next +few weeks, scale up to dedicated CPU 16GB a day or +two before the conference, and keep it at that +level until the recordings are all done. I have +access to that Linode account, so I can set it up. +If bandali can configure emacsverse.org to be +handled by Linode, I can manage the DNS changes, +or he can change bbb.emacsverse.org to the IP +address of the new node. + Some options: -- Go back to using meet.jit.si +- Linode with 16GB RAM and 8 cores + - Advantages: can experiment with both Galene and BBB, manage things ourselves, have filesystem access + - Disadvantages: needs someone to do it + - Base pricing + - Shared CPU 4GB 80GB storage: hourly USD 0.04, monthly USD 24 + - Dedicated CPU 16GB: hourly USD 0.22, monthly USD 144 - meets minimum requirements and can probably support 200 simultaneous ([[https://docs.bigbluebutton.org/support/faq/][FAQ]]) + - Shared CPU 8GB 160GB storage: hourly USD 0.07 + - Shared CPU 16GB 320GB storage: hourly USD 0.14 + - Last year + - Block storage: $1/10GB/month + - 125M/hour - [[https://docs.bigbluebutton.org/support/faq/#what-is-the-disk-space-usage-for-storing-one-hour-of-recordings][FAQ]] + - In 2023, we had 31 hours of trimmed recordings (main + answers), + - (* 31 0.125) 3.875, oh, maybe we can get away with 10GB storage and add another chunk of 10GB midway if we need it, or extend the dedicated + - Actually, block storage probably not needed if we're going to keep the big instance up until the recordings are done + - Ideas + - *Option A: Run a small instance continuously, scale up for the conference, pull the recordings off, spin the instance down* - est total USD 60+tax + - There are three weeks between now and the conference (* 0.04 24 7 3) USD 20 + - Last year, recordings were available within three days after the conference + - Let's plan for a week at high capacity. (* 0.22 24 7) USD 36.96 + - and a month of 10GB, possibly up to 30GB. USD 3 + - That's probably small enough that it doesn't make as much sense to try to fully spin down for a week in between now and the conference (* 0.04 24 7) - which would save USD 6.72 but require figuring out backing up, etc. + - *Option B: Run a slightly larger shared CPU instance from now until shortly before the conference, then scale up* in case BBB does not work for installation/testing with less memory; block storage probably not needed + - (* 0.07 24 7 3) USD 35.28 for 8GB, total (+ 35.28 36.96) USD 72.24 + - (* 0.14 24 7 3) USD 70.56 for 16GB, total (+ 70.56 36.96) USD 107.52 + +- Ask FSF if we can borrow their BBB or Galene, maybe limit it to cycling among 6 or 7 rooms + - Waiting for feedback; Corwin has asked them +- Pay for BigBlueButton hosting; can we find one that's compatible with our commitment to freedom? + - https://bigbluebutton.host/plans/#economyplans - Economy 120 (USD 130/month) or Economy 80 (USD 85/month), custom URL + - https://www.bigbluemeeting.com/#pricing - 100 concurrent users: USD 125/month, custom URL + - https://www.mynaparrot.com/affordable-bigbluebutton-hosting + - 100 concurrent users: USD 79/month + - 200 concurrent users and custom URL: USD 15 setup fee + USD 149/month + - https://www.webhostingzone.org/solutions/bigbluebutton-hosting.html - 150 concurrent, USD 75/month + - https://bbbplugin.com/en/pricing/bigbluebutton-for-api/ - 250 concurrent, USD 49 setup + USD 108.80/month + - https://biggerbluebutton.com/plans + - 150 concurrent users, 10 concurrent meetings, USD 40/month + - custom domain, 600 concurrent users, USD 149/month + - Compare with Linode pricing +- Try to squeeze it onto res.emacsconf.org + - Tricky to run on a shared server; it likes to use a lot of ports and strongly recommends running it on its own server +- Go back to using meet.jit.si? - Free: - Need to check speed, reliability - Can send RTMP from the meeting itself + - [2024-11-13 Wed] I attended Ihor's + OrgMeetup, which he hosted on meet.jit.si. I + think he had bandwidth issues at some point + and we lost his audio. I remember we ran + into that problem before, too, when we used + Jitsi for one of the Emacsconfs. Free Jitsi + hosting might not be the right fit for us. - Paid: USD 99/month + $0.01/min for recordings + $0.01 min (optional) for RTMP streaming -- Try to squeeze it onto res.emacsconf.org - - Tricky to run on a shared server; it likes to use a lot of ports and strongly recommends running it on its own server -- Linode with 16GB RAM and 8 cores - - Dedicated CPU 16GB is $.216/hour at Linode - - Premium CPU is $.26/hour - - Plus block storage, $1/10GB/month charged hourly (recommended 500, so $+18/month) -- Ask FSF if we can borrow theirs, maybe limit it to cycling among 6 or 7 rooms -- Pay for BigBlueButton hosting; can we find one that's compatible with our commitment to freedom? - Galene? - [2024-10-31 Thu] I checked out Galene in the last Emacs Berlin meeting. It's promising, but I think the user interface might still need a bit of work. Simple deployment (run one Go binary, I think), but muting/unmuting doesn't trigger enabling the microphone, and the chat was buggy to get to on my mobile device. Supposed to have support for raising hands. + * Support code :PROPERTIES: :CUSTOM_ID: support-code |