summaryrefslogtreecommitdiffstats
path: root/2021/prepare.md
blob: ea8efd2c2b3ec65811fe900ae1bbd90767b044f9 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
[[!meta title="Notes and tips on preparing your talk"]]
[[!meta copyright="Copyright &copy; 2019, 2020 Amin Bandali<br />Copyright &copy; 2021 Amin Bandali, Sacha Chua, Leo Vivier"]]

This page contains notes and tips for our speakers on preparing their
talks and presentations.  Please read through the list and consider it
while preparing your talk.  If you have any questions, concerns, or
suggestions please feel free to write to one of the organizers
directly (e.g. <bandali@gnu.org>), or write to one our organizational
mailing lists: the public <emacsconf-org@gnu.org> list, or the private
<emacsconf-org-private@gnu.org> list, depending on the nature of the
matter you would like to discuss.

Note: being part of a wiki, this page is subject to change (including
by you!); so please check back every now and again for any changes and
updates.

### Guidelines for conduct

Please review our [[guidelines for conduct|conduct]] when preparing
your talk, to make sure we're all on the same page and strive to make
the event a great experience for all.  If you're not sure whether your
talk or presentation style meets the guidelines laid out in the
guidelines for conduct, we'd be happy to help.  You can email Sacha
Chua at <sacha@sachachua.com> to chat more about this.

### Recording your talk

To help EmacsConf 2021 run smoothly, please prerecord your talk, and
send us your video(s) by **November 7** at the latest (three weeks
before the conference), to allow us enough time to do any needed
processing (e.g. format or codec conversion) in preparation for the
event.  Please consider submitting a prerecording as early as possible
so that we can see if volunteers can caption your video to make it
more accessible and searchable.

To make it easier for organizers and attendees to correctly pronounce
your name, please start your video with something along the lines of:

"Hi! I'm ${NAME} and I'll be talking about ${TOPIC}."

Please **upload your prerecording(s) via FTP** to the FTP server
we have set up with the following details:

- host: ftp-upload.emacsconf.org
- username: anonymous
- port: 21
- folder: upload-here

To upload your recording and any accompanying material to the above
FTP server, you can use your FTP client of choice.  For instance,
FileZilla, a free/libre user-friendly application with a graphical
user interface.  On deb-based GNU/Linux distributions such as Trisquel
you can install FileZilla by running `sudo apt install filezilla` in a
terminal.  Otherwise, you can download FileZilla from their [project
website](https://filezilla-project.org/).

If connection fails on the first try, please check to make sure the
details are exactly as described above; and if the issue persists,
please email <emacsconf-submit@gnu.org> so we can look into it.

If you have a script or notes for your talk, please include it as well
so that we could use it to help us with the captioning of your talk.
You can also send us additional information to include on the wiki
page for your talk, such as links to other pages or additional videos.
If you need help, please email <emacsconf-submit@gnu.org>.

To record your video, you could use any of the following pieces of
free software, depending on your needs:

- [OBS](//obsproject.com)
- [SimpleScreenRecorder](//www.maartenbaert.be/simplescreenrecorder/)
- [vokoscreenNG](//linuxecke.volkoh.de/vokoscreen/vokoscreen.html)
- [peek](//github.com/phw/peek)
- [ffmpeg](//trac.ffmpeg.org/wiki/Capture/Desktop)

You might find the following free software programs useful for editing
your video recordings:

- [Kdenlive](//kdenlive.org/en/)
- [Blender](//www.blender.org)
- [Pitivi](http://www.pitivi.org)

Per GNU Project's
[Guide to Formats](//audio-video.gnu.org/docs/formatguide.html), we
prefer to receive prerecorded videos in formats unencumbered by
software patents, such as `video/webm` (WebM-encoded video files, with
`.webm` file extension) and `video/ogg` (video files encoded with the
Theora video codec, encapsulated in an Ogg transport layer, with
`.ogg` or `.ogv` file extension).  However, if for one reason or
another you are unable to send us your prerecorded video in one of the
above formats, you may submit them in other common formats, like
MPEG-4 (`.mp4`), and we will try to convert them to our preferred
formats on your behalf.

*Prepare recorded video in 720p (1280px by 720px) or higher, in the
WebM format if possible.*

> The conference broadcast will most likely be in
> [720p](https://en.wikipedia.org/wiki/720p) (1280px x 720px,
> progressive) using the [WebM](https://www.webmproject.org/) video
> format.  The closer to this format submitted video files arrive in,
> the easier it will be to process and upload them.

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!

# Frequently-asked questions

## Can I present live?

Tech issues kept happening during EmacsConf 2020, so we'd really
prefer that all talks have prerecorded videos.  There might be time
for live questions and answers over a web conference, though, so if
you can record a short video covering your main points, you might be
able to go into more detail in live Q&A.

## I have so much I want to share.  Can I record a longer video?

The conference program has so many interesting talks.  We wish we
could fit everything in at full length!  (Maybe EmacsConf month?)
Please think of your video as a short teaser that can get people
interested and point them to where they can find out more.  You can
email <emacsconf-submit@gnu.org> links and other notes to add to the
wiki page for your talk.  If you'd like to record a longer video *in
addition* to the short one for the main conference, please feel free
to send us that too.

## I can't figure out how to record the video.  Can I just present the talk?

We might be able to help you record your talk using the BigBlueButton
web conferencing system before November 7.  Please email
<emacsconf-submit@gnu.org> with some times that might work for you and
we'll see if a volunteer can meet up with you to record it.

## How do I show my keystrokes on screen?

In Emacs, you can use
[interaction-log.el](https://github.com/michael-heerdegen/interaction-log.el)
(in MELPA) to display the keystrokes and the commands they run in a separate
buffer.  For a system-wide solution, you can look into
[screenkey](https://gitlab.com/screenkey/screenkey).

## I'm not used to talking to myself.  Can I present the talk to someone?

We might be able to help you record your talk using the BigBlueButton
web conferencing system before November 7.  Please email
<emacsconf-submit@gnu.org> with some times that might work for you and
we'll see if a volunteer can meet up with you to record it.

## Can I see the other proposed talks?

Once we've emailed all the speakers about their acceptance, we'll put
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.

Thanks for contributing to EmacsConf 2021!


<!-- #### Office hours for video call tech-checks -->

<!-- After you submit your prerecorded video, we will schedule a tech-check with  -->
<!-- We ask that speakers who plan to participate in Q&A sessions and/or -->
<!-- plan to present live schedule a short tech-check with us in the weeks -->
<!-- leading to the conference, in order to quickly check their ability for -->
<!-- joining video calls and performing common tasks such as sharing their -->
<!-- screen.  The office hours will likely be on Saturdays or Sundays, but -->
<!-- we would be happy to try and work out another time if that doesn’t -->
<!-- work for a speaker. -->

<!-- To schedule a short tech-check, email one of the people listed below -->
<!-- or visit with us on [#emacsconf-org on Freenode -->
<!-- IRC](irc://chat.freenode.net/#emacsconf-org). -->

<!-- <table> -->
<!-- <thead> -->
<!-- <tr> -->
<!-- <td>Volunteer</td> -->
<!-- <td>Email</td> -->
<!-- <td>IRC Nick</td> -->
<!-- <td>Timezone</td> -->
<!-- </tr> -->
<!-- </thead> -->
<!-- <tbody> -->
<!-- <tr> -->
<!-- <td>Corwin Brust</td> -->
<!-- <td>&lt;<a href="mailto:corwin@bru.st">corwin@bru.st</a>&gt;</td> -->
<!-- <td>mplsCorwin</td> -->
<!-- <td>US/Central (UTC-6)</td> -->
<!-- </tr> -->
<!-- <tr> -->
<!-- <td>Leo Vivier</td> -->
<!-- <td>&lt;<a href="mailto:zaeph@zaeph.net">zaeph@zaeph.net</a>&gt;</td> -->
<!-- <td>zaeph</td> -->
<!-- <td>CET (UTC+1)</td> -->
<!-- </tr> -->
<!-- <tr> -->
<!-- <td>Bhavin Gandhi</td> -->
<!-- <td>&lt;<a href="mailto:bhavin192@geeksocket.in">bhavin192@geeksocket.in</a>&gt;</td> -->
<!-- <td>bhavin192</td> -->
<!-- <td>Asia/Kolkata (UTC+05:30)</td> -->
<!-- </tr> -->
<!-- <tr> -->
<!-- <td>Karl Voit</td> -->
<!-- <td>&lt;<a href="mailto:EmacsConf@Karl-Voit.at">EmacsConf@Karl-Voit.at</a>&gt;</td> -->
<!-- <td>publicvoit</td> -->
<!-- <td>CET (UTC+1)</td> -->
<!-- </tr> -->
<!-- <tr> -->
<!-- <tr> -->
<!-- <td><strong>Your Name</strong></td> -->
<!-- <td>&lt;your@email&gt;</td> -->
<!-- <td>&nbsp;</td> -->
<!-- <td>&nbsp;</td> -->
<!-- </tr> -->
<!-- <tr> -->
<!-- <td><strong>David O'Toole</strong></td> -->
<!-- <td>&lt;deeteeoh1138@gmail.com&gt;</td> -->
<!-- <td>dto</td> -->
<!-- <td>US/Eastern (UTC-5)</td> -->
<!-- </tr> -->
<!-- <tr> -->
<!-- <td>Amin Bandali</td> -->
<!-- <td>&lt;<a href="mailto:bandali@gnu.org">bandali@gnu.org</a>&gt;</td> -->
<!-- <td>bandali</td> -->
<!-- <td>US/Eastern (UTC-5)</td> -->
<!-- </tr> -->
<!-- </tbody> -->
<!-- </table> -->

<!-- If you'd like to help out with the tech-checks, feel free to add your -->
<!-- name and email to the above list and email <bandali@gnu.org> to plan -->
<!-- the logistics. -->


<!-- <a name="tech-checklist"></a> -->
<!-- #### Tech checklist -->

<!-- - Can you speak and be heard? Is there echo? -->
<!-- - Can you hear the organizer? -->
<!-- - 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? -->