diff options
Diffstat (limited to '2021/meetings.org')
| -rw-r--r-- | 2021/meetings.org | 322 |
1 files changed, 320 insertions, 2 deletions
diff --git a/2021/meetings.org b/2021/meetings.org index e6588a0a..e33e8e38 100644 --- a/2021/meetings.org +++ b/2021/meetings.org @@ -18,7 +18,9 @@ - Tech - Figuring out a better streaming workflow (speakers & OBS) - CDN with Nate Sales: mplsCorwin, bandali - - Stand-by until late-April + - maybe also FTP upload for speakers + - Stand-by for now + - Separate from Fosshost - Documenting our infrastructure - bandali and gopar's podcast: bandali, gopar @@ -91,15 +93,330 @@ - It might be hard to jump from 2-day to full-week. - It’s hard to have people available across the entire period. - We should make it easier for other people to edit the conf.org for publishing the schedule; for 2021, sachac and zaeph were able to do it, but we should make it more our functions more robust. + - Add edit-in-place functionality to ikiwiki + - An alternative would be to enable push-via-https, but bandali isn’t enthused by it. - 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 - mplsCorwin's livestreaming project, working on trimming - Diversity outreach: gopar, sachac, zaeph, mplsCorwin +* EmacsConf 2021: Long-running TODOs + +* November 6, 2021 +- Check-ins + - zaeph is dealing with TZ change + +- TODOs: + - Everyone: + - [X] 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: + - [X] ASAP: Give SSH access to sachac on ftp-upload@emacsconf.org + - Ping corwin to get another distro installed on vm02 (possibly Trisquel or Alpine) + - [X] Look into making TLS/SSL optional + - sachac: Right now, the configuration for the ftp server forces it. + - bandali is looking into FTP for resume, no worries about being able to see filenames (not allowed to download files) + - probably no risk from other people maliciously "resuming" other people's files + - ideas for the future: + - can have speaker accounts for FTP (... maybe if Amin gets the hang of automating e-mails =) ) + - region servers to upload to, maybe as part of CDN project + - TODO enable continuation for FTP + - Fosshost: Drop an application for another storage-server for the prerecs + - zaeph: + - [X] ASAP: Email designated volunteers + - Create BBB accounts for new tech-checkers + - Publicise contribute.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 +- sachac: Status update: 9 prerecs received + - 7 talks captioned + - Emacs News Highlights + - NonGNU ELPA Update + - telega.el and the Emacs community on Telegram + - Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide (thanks bhavin!) + - The use of Org mode syntax outside of GNU/Emacs - checked with speaker + - How Emacs made me appreciate software freedom + - Moldable Emacs, a step towards sustainable software - checked with speaker + - 2 more talks waiting for captions from bhavin: + - Using Org-Mode For Recording Continuous Professional Development + - Emacs with Nyxt: extend your editor with the power of a Lisp browser + - Compressed with q=56 script from last year, uploaded to front:/var/www/media.emacsconf.org/2021/protected , see private wiki for password + - Things to consider: + - Broadcast with open captions or direct people who need closed + captions to the wiki page? Spam #emacsconf-accessible with + caption text? + - Sample: https://emacsconf.org/2021/talks/news/ + - Compression okay? Do we need to dial it back? + - Plan for handling compression for the talks coming in this weekend; can we run it on the VM? + - Audio normalization? + - Low-res version? + - More proof-reading welcome + - Start thinking about workflow for publishing talks, maybe even concurrently with the stream + - No reason not to make them public right away, so if we want them to be available on something else in addition to emacsconf.org and Youtube (Toobnix?), we can plan ahead +- TODO bandali also, icecast fallback override possibility so that bandali might be + able to use ffmpeg to broadcast directly to icecast while handling + continuity? Does anyone want to experiment with that? +- does anyone want to write an ICS to Org thing that can handle + schedule updates, maybe taking advantage of icalendar? +- pronouns/website/sponsor info can probably be an e-mail to speakers +- e-mail to send on the deadline (tomorrow) + - reminder to send it + - let's use a carrot approach, not stick (10 talks have already been submitted, yay, and most of them have been captioned!); we're actually okay with dealing with prerecs or live on the day of the event + - nudge script submission esp. close to the deadline to help with captions +- publishing the schedule with the times, ICS; maybe Nov 14? + - probably can do even with the uncertainty +- 10 minutes hard to do live (or record); 15 min next time? +- maybe postpone letting people plan for live presentation until a little bit later +- future: shorter CFP, longer prep period + +#+begin_example +Hello, ____! + +,* TODO [#A] Send pre-recording to EmacsConf + +Lots of speakers have already submitted their talks for EmacsConf +2021, and we've even be able to caption them. Yay! Here are some of +the presentations that have already come in: + + - Emacs News Highlights + - NonGNU ELPA Update + - telega.el and the Emacs community on Telegram + - Creating technical API documentation and presentations using org-babel, restclient, and org-treeslide + - The use of Org mode syntax outside of GNU/Emacs + - How Emacs made me appreciate software freedom + - Moldable Emacs, a step towards sustainable software + +We're looking forward to getting your presentation. If you send it in +as soon as you can, we can add it to the queue for captioning. We'd +like to stream as many talks with captions to make things more +accessible, and the text makes it easier to search too. Also, sending +the prerecorded video will make the conference day less stressful for +everyone. =) If you need extra time to get your prerecorded video, no +worries, we'll figure it out somehow. Please try to do it as soon as +you can! + +,* TODO Send page information (name pronunciation, pronouns, homepage, contact, sponsor links) + +We'd also like to add some standard information to the talk +information page to make it easier for people to talk about your talk, +find more information, contact you, or support you. + +Name pronunciation: +Pronouns: +Homepage: +Preferred contact info: +Links for sponsoring/supporting (if any): + +For example, Sacha's is: + +Name pronunciation: SA-sha CHEW-ah +Pronouns: she/her +Homepage: https://sachachua.com +Preferred contact info: sacha@sachachua.com +Links for sponsoring/supporting (if any): + +,* TODO Plan tech check if you're doing live Q&A + +Also, if you are planning to do live Q&A and you've already done the +tech check at test.bigbluebutton.org, we can set up a tech check call +with an organizer or volunteer. Sometimes there are technical issues +with sharing desktops or hearing audio, so it's good to get it sorted +out as soon as possible. Please check _____ for some options for a +live tech check and reach out to someone who's available when you are. +We hope to get more volunteers for tech checks, so if you can't find +someone whose availability matches yours, please e-mail us at _____ +and we'll try to find something that works. + +,* Also, sneak preview of talks =) + +As a thank-you for working on a talk for EmacsConf, here's a sneak +preview of the talks that have been submitted so far. Please don't +share it widely. If you want to refer to other people's talks in +yours, it's a good time to check out related talks! + +(TODO - info not in here) + +Thank you so much! + +Amin +#+end_example + +--- +TODO Sneak preview e-mail for people who have already submitted + + +--- +- Also do we want to give speakers early access to each other's talks? + - OK, ask them not to share yet +- ffmpeg installed on FTP upload +- TODO bandali to check compressed video and see if we want to change the settings +- TODO: Sacha - Make Etherpad template for speakers? Actually, e-mail might be easier to copy and paste from + - Name pronunciation + - Pronouns + - Links + - Homepage, socials + - Sponsor +- TODO: Sacha - send bandali Bcc list for nudge e-mails +- How many people did we do live tech checks last year? +- zaeph will not be very available. +- TODO maybe seabass? zaeph will e-mail. +- publicize contribute page to the mailing list? and stress the need for tech checkers +- TODO sachac: add current captioning results +- Future: bake it into the submission process (when will be a good time over the next 1-2 months) +- If we don't have enough people to do the tech checks, Leo will step up and maybe do some kind of office hours thing +- Process: + 1. E-mail the volunteers + 2. Update the table on the page + 3. If anyone wants to get started now, you can e-mail us +- BBB slide presentation feature broken, may be related to LetsEncrypt, can't leave messages on the screen; probably won't need it for EmacsConf +- DECISION Yes, broadcast open captions; published videos can be CC +- TODO zaeph will come up with the MPV settings for displaying open captions +- EmacsConf: friendly and relaxed =) + +- Summary + - #A zaeph: Set up tech check information, e-mail volunteers + - #A zaeph: Finish draft of e-mail for tomorrow or the day after + - zaeph: Figure out mpv settings + - bandali: Check video settings, see if we need to tweak compression/audio + - sachac: Keep captioning + +* 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) + - ullbeking (?) + - 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 @@ -1708,7 +2025,8 @@ Which again could be somewhere to promote emacs / emacs conf - mplsCorwin: Talk with Nate Sales - We want to talk with Nate Sales about CDN stuff - mplsCorwin will be asking Nate Sales to come again on [2021-05-01 Sat] - + - Also to be used for FTP uploads + - mplsCorwin update on FH - mplsCorwin is mentioning that we might get another server to handle - Depending on the location |