diff options
Diffstat (limited to '2021')
| -rw-r--r-- | 2021/contribute.md | 59 | ||||
| -rw-r--r-- | 2021/meetings.org | 157 | ||||
| -rw-r--r-- | 2021/prepare.md | 17 |
3 files changed, 226 insertions, 7 deletions
diff --git a/2021/contribute.md b/2021/contribute.md new file mode 100644 index 00000000..7c8bd03c --- /dev/null +++ b/2021/contribute.md @@ -0,0 +1,59 @@ +[[!meta title="Contribute to EmacsConf 2021"]] +[[!meta copyright="Copyright © 2021 Sacha Chua"]] + +Want to help with EmacsConf 2021? Here's how you can make it even better! + +# Tech checks + +Many sessions will have live question and answer sessions via Big Blue +Button. Everything works more smoothly when the speakers are all +set up and ready to go: their audio works, their screen can be shared +properly, and so on. You can help by testing their setup beforehand. + +You can test your own connection at <https://test.bigbluebutton.org> +. If that works for you, you can be a tech check volunteer. Let us +know what your availability is and we can match you up with speakers +who want to doublecheck their setup before the conference. + +Here are some notes on the tech check process: + +- Can you hear me? Can I hear you? +- Explain process +- Test audio, webcam, screensharing, collaborative pad + - Music demos and other things that use system audio will need to be + prerecorded (or done through virtual loopback device, maybe? + Technical risk.) + - Multi-monitor setups might not be handled well by BBB; share + window instead of desktop + - Possible picture-in-picture approach to maximize screen real estate if needed + - Linux: share desktop, run cheese, set Always on Top +- Check if comfortable checking into IRC: #emacsconf-org +- Get phone number for emergency contact, store in private wiki +- Write down IRC nick, name pronunciation, and pronouns for inclusion in the public wiki +- Encourage webcam for Q&A, although make it clear that it's totally optional + +# Alternate streams + +Do you have a pretty good network connection and a computer capable of +livestreaming? Consider becoming an alternate streamer! You can pick +one or more of your favorite sessions from the [[schedule]] and get +set up for doing an extended stream, allowing more time for Q&A and +live demonstrations. + +# Captions + +Want to help make videos easier for people to enjoy during the +conference, or find and learn from afterwards? Please volunteer to +help caption recorded talks! You'll get a sneak preview of a talk, +and possibly auto-generated captions that you can use as a starting +point. [subed.el](https://github.com/rndusr/subed/) mode makes it +easier to adjust the timings or edit the text. + +# Volunteer + +Thought of another way to help? Sure, suggest away. + +To volunteer, please e-mail <emacsconf-submit@gnu.org>. We'd love to +hear from you! + +Thanks for contributing to EmacsConf 2021! diff --git a/2021/meetings.org b/2021/meetings.org index 2762be5a..f5532f4f 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 @@ -103,9 +106,155 @@ - Diversity outreach: gopar, sachac, zaeph, mplsCorwin * EmacsConf 2021: Long-running TODOs -** Closer to the conference week -*** 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) + - 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 diff --git a/2021/prepare.md b/2021/prepare.md index 669088de..ea8efd2c 100644 --- a/2021/prepare.md +++ b/2021/prepare.md @@ -101,9 +101,9 @@ WebM format if possible.* > format. The closer to this format submitted video files arrive in, > the easier it will be to process and upload them. -After you send in your video, if you've indicated that you'd like to -do live Q&A, we'll set up a tech-check call with you. We'll post -details here closer to that time. +If you're planning to do live Q&A, you can check your system setup at +https://test.bigbluebutton.org/ . We'll set up a tech-check call with +you, too. We'll post details here closer to that time. Thank you so much for helping with EmacsConf 2021! @@ -157,6 +157,17 @@ up the talk wiki pages. That way, you can see what else is going on in the conference and maybe coordinate with other speakers in order to minimize overlap and maximize awesomeness. +## What if there are lots of great questions during Q&A and we run out of time? + +You can continue answering questions on the collaborative pad or IRC, +and we'll copy questions and answers onto the wiki page +afterwards. You can also answer questions on the wiki page even after the event. + +An extended live demo or Q&A session might be possible if someone +volunteers to broadcast it on an alternative stream. If you or a +volunteer is interested in helping with this, please feel free to +contact us at <emacsconf-submit@gnu.org>. + ## More questions? Please email <emacsconf-submit@gnu.org>. We'd love to hear from you. |