summaryrefslogtreecommitdiffstats
path: root/2021/meetings.org
diff options
context:
space:
mode:
authorLeo Vivier <zaeph@zaeph.net>2021-10-30 18:12:05 +0200
committerLeo Vivier <zaeph@zaeph.net>2021-10-30 18:12:14 +0200
commit03ef8e8fe17c70fb070e4b217271d4ea20a60947 (patch)
tree08763a59858453b3c755852db4c50755d15ea756 /2021/meetings.org
parent5b630b7eff64654f1dcb7808c7cef8a30f013fb3 (diff)
downloademacsconf-wiki-03ef8e8fe17c70fb070e4b217271d4ea20a60947.tar.xz
emacsconf-wiki-03ef8e8fe17c70fb070e4b217271d4ea20a60947.zip
Add notes from last session
Diffstat (limited to '2021/meetings.org')
-rw-r--r--2021/meetings.org153
1 files changed, 152 insertions, 1 deletions
diff --git a/2021/meetings.org b/2021/meetings.org
index 2762be5a..68c0ee91 100644
--- a/2021/meetings.org
+++ b/2021/meetings.org
@@ -18,7 +18,8 @@
- Tech
- Figuring out a better streaming workflow (speakers & OBS)
- CDN with Nate Sales: mplsCorwin, bandali
- - Stand-by until late-April
+ - Stand-by for now
+ - Separate from Fosshost
- Documenting our infrastructure
- bandali and gopar's podcast: bandali, gopar
@@ -96,6 +97,8 @@
- EmacsVerse
- Vet Mailman and exim instance for usergroups: bandali
+ - Figure out the interactions between (potential) emacsverse.org and emacs.org
+ - It’s about control domains and sources of truth
- Misc
- Writing about Emacs: zaeph
@@ -107,6 +110,154 @@
*** Email speaker
- Push speakers to add talk links, homepage/social & sponsoring links on their page (ideally could have been done with our first "please edit your talk page" email)
+* November 6, 2021
+- TODOs:
+ - Everyone:
+ - Get working on contribute.md by Tue-Wed
+ - Non-exhaustive list of tasks to mention (relevant for this year):
+ 1. Editing captions or writing new ones
+ 2. Helping with tech-checks
+ 3. Looking at the schedule, and if there’s something they particularly like, they could run get ready for a prolonged Q&A session
+ - bandali:
+ - ASAP: Give SSH access to sachac on ftp-upload@emacsconf.org
+ - Ping corwin to get another distro installed on vm02 (possibly Trisquel or Alpine)
+ - Look into making TLS/SSL optional
+ - sachac: Right now, the configuration for the ftp server forces it.
+ - Fosshost: Drop an application for another storage-server for the prerecs
+ - zaeph:
+ - ASAP: Email designated volunteers
+ - Create BBB accounts for new tech-checkers
+ - Publicise contribe.md on r/emacs when it’s published
+ - Make a pinned comment on the program announcement asking for volunteers, linking to contribute.md, and maybe keeping it up to date by editing it to reflect current needs
+ - corwin:
+ - Record a 6-second video ad
+ - Go through the script together
+
+* October 30, 2021 meeting
+
+- Check-ins
+ - sachac:
+ - Using Emacs itself to record her talk, and has even managed to get a spectrum analyser right into it!
+ - [[https://github.com/sachac/subed-waveform][sachac/subed-waveform: Minor mode for displaying the waveform for the current subtitle in an Emacs subed-mode buffer]]
+ - bandali:
+ - Busy with the emails and around GNU in general
+ - Almost finished with a paper building on parts of his MA dissertation
+ - Last week’s presentation went well despite some minor hiccups
+ - It was a *long* session, so a 5-min break can be glossed over
+ - zaeph:
+ - All is well! A lot of swimming and fun experimentations!
+ - corwin:
+ - Pretty rested!
+ - Lots of stuff brewing with Fosshost
+
+- FTP:
+ - sachac: Where can I find the recordings?
+ - If we get talks early, we might get started on the subtitling
+ - bandali: Tried to setup the 2nd upload server
+ - Couldn’t get it to work; the same configuration on front0 for testing was working, but not onl
+ - The FSF sysadmins gave us access to a session/server which we might use as replacement
+ - sachac: Where can we keep the talks on front0?
+ - Reasoning:
+ - Last year, one of the issue that th epeople who had missed a talk wished they could have watched it
+ - Whilst the prerec is playing on the stream, we could put in a public directory to be able to watch it
+ - It’d be amazing if we could get the recordings ASAP this year, since most of them will be prerecs
+ - People need to be uploading files to the very server that we will be storing them on.
+ - Discussion:
+ - bandali: The main VMs that we have (live0 and front0) are fairly small, 20-25GB each. What we’ve been doing for the past couple EmacsConf has been to upload to a server provided Computer Science of the University of Waterloo
+ - Options:
+ - Fosshost
+ - corwin: Disk-space comes super-cheap to Fosshost, which means that it might be a good option.
+ - Could become our primary source (vs. CS Club which we use currently)
+ - CS Club (University of Waterloo); we might not have it eternally
+ - At the moment, it is our primary source
+ - We can still use it as a mirror
+ - audio-video.gnu.org (FSF)
+ - yang’s 2 mirrors in Europe
+ - Other options that we might consider for other editions:
+ - Justification:
+ - corwin: The footprint of EmacsConf will always grow as long as we maintain older publications for posterity, even if the grow is fairly linear.
+ - Linode block storage
+ - 1$/month for 10 GB
+ - corwin’s favourite provider
+ - Meta:
+ - Having 3 ISP is better than having 2
+ - From a growth perspective, it’s good to have some cash outlay to help people understand that we have a need for money
+ - This also appeared with the android-app
+ - Other considerations
+ - Using emacsconf.org for redirections
+ - bandali: Someone set up two mirrors for us in Europe; it’d be nice to have mirror-resolve/-rotator that we could put in front to do the redirecting
+ - sachac: That would put more sysad work on bandali, though
+ - How do we handle the private→public publishing of the recording?
+ 1. Upload all the files to the public server
+ 2. chmod o-r on all the talks
+ 3. When a talk goes live: chmod o+r
+ - Handling redirections à la CDN
+ - bandali:
+ - We might want to add A records pointing to all the servers that we’re using as mirrors (in a round-robin fashion)
+ - GNU might have solutions
+
+- Asking new domains to the FSF sysadmins, especially on .emacs.org
+ - Have we considered having a .gnu.org domain linking to emacs.org?
+ - conf.emacs.org could be very nice for visibility.
+ - corwin: Could we do the same with orgmode.org?
+ - Imagine if the org-mode website had a featured talk from the EmacsConf!
+ - corwin: Once the relationship exists between emacs.org and orgmode.org, a lot of bridges can be built between the communities with mutual benefits
+
+- Alternate streams & Rebroadcasts
+ - APAC:
+ - sachac: As the prerecs come in, we can touch base with dragestil re: APAC event
+ - Other streamers:
+ - sachac: These next few weeks are also the best time to onboard alternate streamers
+ - corwin: Our must important work right now is bringing more talents/newcommers, and get them to the level where they feel technically-competent and empowered to help us further.
+
+- How to get new organisers involved as well they could be with the project?
+ - Doing tech-checks is a pretty good and easy to get started with volunteers.
+ - sachac: When we activate the other volunteers, what should we be asking them to consider? *Ordered by priority*, and which we should mention on the ~contribute.md~:
+ 1. Editing captions or writing new ones
+ 2. Helping with tech-checks
+ 3. Looking at the schedule, and if there’s something they particularly like, they could run get ready for a prolonged Q&A session
+ - sachac: We might have a ~contribute.md~ page similar to the prepare.md page
+ - We should link from /2021 to /2021/contribute.md.
+ - Also, other people who could come across it rather than just our current volunteers.
+ - corwin: ~contribute.md~ is the invitation, and the ~prepare.md~ is the directions to the party.
+ - How do we publicise this contribue.md?
+ - zaeph: Could we publicise contribute.md on r/emacs
+ - corwin: Yes! It’s a great piece of promotion to do.
+ - bandali: It might make sense to mention contribute.md to speakers
+ - Our next email to speakers should link to contribute.md
+
+- Tech-checks
+ - Getting organisers on board with tech-checks
+ - Which new volunteers could be bring along on this project?
+ - acdw (AM)
+ - dragestil (APAC)
+ - bhavin192 (APAC)
+ - seabass (EU)
+ - zleap (EU)
+ - zaeph (EU)
+ - corwin (AM)
+ - ???
+ - bandali (AM)
+ - Putting the finishing touches on the checklist
+ #+begin_quote
+ - Would you please share your pronouns?
+ - Can you tell us how to pronounce your name?
+ - Can you speak and be heard? Is there echo?
+ - Can you hear the organizer (me)?
+ - Can you share your screen? Is the screen readable?
+ - If you plan to show your keystrokes, is that display visible?
+ - If you want to share your webcam (optional), can you enable it? Is it visible? Will there likely be distractions in the background?
+ - Can you view the collaborative pad? Will you be comfortable reviewing questions on your own (perhaps by keeping it open beside your shared window), or will you need a volunteer to relay questions to you?
+ - Can you share contact information (ex: phone number) so that we can get in touch with you in case of technical issues or scheduling changes?
+ - Do you need help finding your way around IRC so that you can check into `#emacsconf-org`? What is your IRC nickname?
+ #+end_quote
+
+- What to mention in our closing remarks
+ - Acknowledging volunteers
+ - Inviting other volunteers
+ - Alternate streams / Multiple tracks
+
+
* October 23, 2021 meeting
- TODO