From: "Sébastien G" <email@example.com>
To: firstname.lastname@example.org, email@example.com
Subject: Re: [ANN] EmacsConf 2020 videos are out!
Date: Sun, 06 Dec 2020 02:59:42 +0100 [thread overview]
Message-ID: <396B09F1-593F-4FC3-A909-300D428FC1DB@k-7.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 3138 bytes --]
Thanks to everyone. 😁
Did you know if the videos are also on Peertube ?
Le 6 décembre 2020 00:05:27 GMT+01:00, Amin Bandali <firstname.lastname@example.org> a écrit :
>Hello fellow Emacsians!
>[ I originally sent this mail to the EmacsConf lists and emacs-tangents,
> but thought some folks on emacs-devel and emacs-orgmode might also be
> interested in knowing about this and watching the videos too. :-) ]
>The EmacsConf 2020 videos are now ready. Thanks to everyone who helped
>make it happen!
>You can check out https://emacsconf.org/2020/talks/ to find the videos,
>Q&A, links, and notes for each talk. The collaborative pad is archived
>at https://emacsconf.org/2020/pad/. We've also asked speakers to send
>us any additional material or resources they would like to add to their
>The videos are currently available in 720p (1280px x 720px, progressive)
>WebM format. We are working on transcoding and uploading low-resolution
>(480p or 852px x 480px, progressive) WebM as well.
>If you have questions or ideas related to the talks, please feel free to
>reach out to the speaker(s). If you think of ways to make EmacsConf
>even better, we'd love to hear from you too. You can also check out
>https://www.emacswiki.org/emacs/Usergroups for meetups and workshops
>happening throughout the year (and if you organize a meetup or would
>like to, please contact us - we'd love to help bring people together!).
>If you have any EmacsConf-related blog posts or discussions, please add
>them to https://emacsconf.org/2020/ or email us so that we could add the
>links. Let's keep the conversation going!
>Behind the scenes
>This year, we were again able to make EmacsConf happen entirely with
>Free Software. For the live talks and/or Q&A sessions with speakers,
>we used the BigBlueButton instance graciously shared with us by the
>Free Software Foundation (FSF). The whole conference was captured
>and streamed to the EmacsConf stream server running Icecast, using a
>GStreamer pipeline based on a script written by Ruben Rodriguez for
>streaming FSF events such as the LibrePlanet conference and FSF35.
>For the collaborative pad for gathering questions and show notes, we
>used an Etherpad on the Wikimedia Foundation instance hosted at
>https://etherpad.wikimedia.org. For the EmacsConf website, we used
>ikiwiki. During the conference, we used Emacs Lisp to plan the
>schedule, update the topics across our IRC channels, and send automated
>messages about upcoming talks to speakers and organizers, all inside
>As we write more about our streaming setup, infrastructure, processes,
>and code, we will update https://emacsconf.org/2020/ and post links to
>In the meantime, please don't hesitate to email me (email@example.com)
>if you would like to ask about how we organized the conference.
>Thanks again to everyone for an awesome EmacsConf!
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
[-- Attachment #2: Type: text/html, Size: 3803 bytes --]
next prev parent reply other threads:[~2020-12-06 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 23:05 [ANN] EmacsConf 2020 videos are out! Amin Bandali
2020-12-06 0:54 ` Stefan Monnier
2020-12-06 1:59 ` Sébastien G [this message]
2020-12-25 19:37 ` Amin Bandali
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).