You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2id="information-for-speakers">Information for Speakers</h2>
121
-
122
-
<ul>
123
-
<li>Please be in your presentation room at least 15 minutes before your talk to meet your session chair.</li>
124
-
<li>A Quiet Room will be available for attendees and speakers on all conference days.</li>
125
-
<li>We reserve the right to ask for a draft of your slides/notes not more than 3 weeks in advance of the presentation for review. This draft will not be shared with anyone outside the program and code of conduct teams.</li>
126
-
</ul>
127
-
128
-
<h2id="need-some-help-with-your-presentation">Need some help with your presentation?</h2>
129
-
130
-
<p>Presenters, regardless of experience, sometimes want a little help. If you’d like any help in preparing or presenting your talk, some awesome members of our community have volunteered to be speaker mentors. A mentor is an experienced presenter who has volunteered to help other presenters. For first-time presenters, non-native English speakers, under-confident or uncertain speakers, or anyone who would just appreciate another set of eyes, our mentors will be here to help. You’ll get the best results by forming a relationship with one mentor, rather than contacting several.</p>
131
-
132
-
<ul>
133
-
<li>
134
-
<ahref="mailto:[email protected]">Eng Seng Ng</a>, Senior Engineer at Energy Solutions. Eng Seng leads the documentation and training team for a climate-change-fighting software product at Energy Solutions.</li>
135
-
<li>
136
-
<ahref="mailto:[email protected]">Katie McLaughlin</a>, Developer Advocate and frequent public speaker (occasional keynoter), DjangoCon AU organiser, and Secretary for the Django Software Foundation.</li>
137
-
</ul>
138
-
139
-
<h2id="talk-guidelines">Talk Guidelines</h2>
120
+
121
+
<h2id="information-for-speakers">Information for Speakers</h2>
122
+
<ul>
123
+
<li>The Speaker Green Room will be in <strong>Meeting Room 2</strong> on Monday-Wednesday.</li>
124
+
<li>Please be in your presentation room at least 15 minutes before your talk to meet your session chair.</li>
125
+
<li>A Quiet Room will be available for attendees and speakers on all conference days.</li>
126
+
<li>We reserve the right to ask for a draft of your slides/notes not more than 3 weeks in advance of the presentation for review. This draft will not be shared with anyone outside the program and code of conduct teams.</li>
127
+
</ul>
140
128
141
-
<h3id="accessibility">Accessibility</h3>
129
+
<h2id="need-some-help-with-your-presentation-">Need some help with your presentation?</h2>
130
+
<p>Presenters, regardless of experience, sometimes want a little help. If you’d like any help in preparing or presenting your talk, some awesome members of our community have volunteered to be speaker mentors. A mentor is an experienced presenter who has volunteered to help other presenters. For first-time presenters, non-native English speakers, under-confident or uncertain speakers, or anyone who would just appreciate another set of eyes, our mentors will be here to help. You’ll get the best results by forming a relationship with one mentor, rather than contacting several.</p>
131
+
<ul>
132
+
<li><ahref="mailto:[email protected]">Anna Ossowski</a>, Anna works as a Senior Community Program Manager at Github and actively volunteer across many different open source communities related to the Python Programming Language. This includes her former role on the Board of the Directors for the Python Software Foundation and as a current organizer for PyLadies in London. She’s a strong advocate for mental health and mentorship as well as supporting effective open source communities. Her newest hobby is writing and performing stand up comedy.</li>
133
+
<li><ahref="mailto:[email protected]">Frank Wiles</a>, Former President of the Board, Django Software Foundation, Founder, REVSYS.</li>
134
+
</ul>
142
135
143
-
<ul>
144
-
<li>You can submit a draft copy of your slides with notes indicating what you plan to say a minimum of three weeks before your talk to give the captioners time to train on your data and therefore improve caption accuracy. This is extremely helpful to our attendees who read the live captions if you’re using jargon beyond “Django” and “the ORM”.</li>
145
-
<li>These slides will not be shared outside of the organizing team and the captioners. Send the slides to hello AT djangocon DOT us when you are ready. It’s perfectly fine if your slides and notes change between the draft and final version.</li>
146
-
<li>When describing media in your talk (images, screenshots, graphs, videos, etc.), please give a verbal description of what you’re showing so that blind or vision-impaired attendees can understand what you’re describing.
147
-
<ul>
148
-
<li>Example: instead of “here’s a graph showing performance improvements with our new async code,” say “here’s a line graph showing our average response time that decreased from 450 milliseconds to 150 milliseconds after adding our new async code.”</li>
149
-
</ul>
136
+
<!-- <ul>
137
+
<li><a href="mailto:[email protected]">Eng Seng Ng</a>, Senior Engineer at Energy Solutions. Eng Seng leads the documentation and training team for a climate-change-fighting software product at Energy Solutions.</li>
138
+
<li><a href="mailto:[email protected]">Katie McLaughlin</a>, Developer Advocate and frequent public speaker (occasional keynoter), DjangoCon AU organiser, and Secretary for the Django Software Foundation.</li>
139
+
<li><a href="mailto:[email protected]">Philip James</a>, Core Contributor to the BeeWare project and Senior Software Engineer at Patreon. Philip has spoken at a number of DjangoCons and PyCons around the world.</li>
140
+
<li><a href="mailto:[email protected]">Dr. Russell Keith-Magee</a>, Founder of the BeeWare project, developing GUI tools and libraries to support the development of Python software on desktop and mobile platforms. He is also a 13 year veteran of the Django Core Team, and for 5 years, was President of the Django Software Foundation. In his day job, he wrangles data pipelines for Survata.
150
141
</li>
151
-
</ul>
152
-
153
-
<h3id="general">General</h3>
154
-
155
-
<ul>
156
-
<li>Use gender-neutral language wherever possible. Don’t default to <ahref="https://heyguys.cc">using “he”, “him”, or “guys”</a> everywhere.</li>
157
-
<li>Be respectful of other speakers, your audience, and the community at large, especially when offering critiques. It’s possible to say “this needs improvement” without saying “this is bad.”</li>
142
+
</ul> -->
143
+
144
+
<h2id="talk-guidelines">Talk Guidelines</h2>
145
+
<h3id="accessibility">Accessibility</h3>
146
+
<ul>
147
+
<li>You can submit a draft copy of your slides with notes indicating what you plan to say a minimum of three weeks before your talk to give the captioners time to train on your data and therefore improve caption accuracy. This is extremely helpful to our attendees who read the live captions if you're using jargon beyond "Django" and "the ORM".</li>
148
+
<li>These slides will not be shared outside of the organizing team and the captioners. Send the slides to hello AT djangocon DOT us when you are ready. It's perfectly fine if your slides and notes change between the draft and final version.</li>
149
+
<li>When describing media in your talk (images, screenshots, graphs, videos, etc.), please give a verbal description of what you're showing so that blind or vision-impaired attendees can understand what you're describing.<ul>
150
+
<li>Example: instead of "here's a graph showing performance improvements with our new async code," say "here's a line graph showing our average response time that decreased from 450 milliseconds to 150 milliseconds after adding our new async code."</li>
151
+
</ul>
152
+
</li>
153
+
</ul>
154
+
<h3id="general">General</h3>
155
+
<ul>
156
+
<li>Use gender-neutral language wherever possible. Don't default to <ahref="https://heyguys.cc">using "he", "him", or "guys"</a> everywhere.</li>
157
+
<li>Be respectful of other speakers, your audience, and the community at large, especially when offering critiques. It's possible to say "this needs improvement" without saying "this is bad."</li>
158
158
<li>Consider including your social media handle(s) on your opening and closing slides! If you have space, you can even include them on the footer of every slide.</li>
159
159
<li>Consider publishing your slides after your talk (on the platform of your choice) and sharing the link with the #DjangoCon hashtag on social media.</li>
160
-
<li>Include a copy of what you plan to say in each slide’s notes (if possible). This will help you while you’re in presenter view and also make it easier for people who may be looking at your slides after the conference.</li>
160
+
<li>Include a copy of what you plan to say in each slide's notes (if possible). This will help you while you're in presenter view and also make it easier for people who may be looking at your slides after the conference.</li>
161
161
<li>Before you connect your laptop to the projector, make sure you have every window except for your slides minimized or closed to avoid accidental information disclosure.</li>
162
-
<li>Make sure you turn on your computer’s do not disturb mode before starting your presentation to avoid interruptions.</li>
163
-
<li>If your computer needs a dongle to connect to an HDMI cable, please bring it. We’ll have most of the common ones, including a USB-C/Thunderbolt connector, but it always helps to have one that you know works.</li>
164
-
</ul>
165
-
166
-
<h2id="slide-guidelines">Slide Guidelines</h2>
167
-
168
-
<h3id="format">Format</h3>
169
-
170
-
<ul>
162
+
<li>Make sure you turn on your computer's do not disturb mode before starting your presentation to avoid interruptions.</li>
163
+
<li>If your computer needs a dongle to connect to an HDMI cable, please bring it. We'll have most of the common ones, including a USB-C/Thunderbolt connector, but it always helps to have one that you know works.</li>
164
+
</ul>
165
+
<h2id="slide-guidelines">Slide Guidelines</h2>
166
+
<h3id="format">Format</h3>
167
+
<ul>
171
168
<li>Minimal slides are best—-avoid walls of text and long lists of bullets.</li>
172
169
<li>Light background with dark text is easiest to read; be mindful that the projection screen is white.
173
-
Choose fonts with adequate spacing between letters, and avoid thin or cursive fonts.</li>
174
-
<li>Leave the bottom 25% of your slides free of text to ensure nothing is obscured by other attendees’ heads.</li>
170
+
Choose fonts with adequate spacing between letters, and avoid thin or cursive fonts.</li>
171
+
<li>Leave the bottom 25% of your slides free of text to ensure nothing is obscured by other attendees' heads.</li>
175
172
<li>If your talk requires live coding or using the terminal, make sure your editor or terminal settings are legible. Dark text on a light background (high contrast) with a large font is best.</li>
176
173
<li>Images, memes, and GIFs should be appropriate for a professional audience.</li>
177
-
</ul>
178
-
179
-
<h3id="accessibility-1">Accessibility</h3>
180
-
181
-
<ul>
174
+
</ul>
175
+
<h3id="accessibility">Accessibility</h3>
176
+
<ul>
182
177
<li>Aim for high contrast slides, avoiding colors that may be difficult to see for those with colorblindness. (You can <ahref="http://webaim.org/resources/contrastchecker/">check your contrast online</a>; you just need the hex codes for your colors!)</li>
183
178
<li>Avoid or limit flashing videos or animated GIFs, as these may have negative effects for people with seizure disorders, migraines, or ADD/ADHD.</li>
184
179
<li>Make text as large as possible. People need to be able to read the text from a very long distance.</li>
185
180
<li>Your talk should lose nothing if the slides aren’t visible. Generally describe graphs, images, and other information for the audience.</li>
186
-
</ul>
181
+
</ul>
182
+
<p>Thanks to <ahref="https://www.alterconf.com/speak">AlterConf</a> for their amazing speaking recommendations!</p>
187
183
188
-
<p>Thanks to <ahref="https://www.alterconf.com/speak">AlterConf</a> for their amazing speaking recommendations!</p>
0 commit comments