A place to cache linked articles (think custom and personal wayback machine)
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.

index.html 41KB

il y a 4 ans
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang=fr>
  4. <!-- Has to be within the first 1024 bytes, hence before the <title>
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset=utf-8>
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name=viewport content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>What Can Conferences Do To Attract More Women Speakers? (archive) — David Larlet</title>
  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">
  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">
  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">
  17. <link rel="manifest" href="/manifest.json">
  18. <link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">
  19. <link rel="shortcut icon" href="/static/david/icons/favicon.ico">
  20. <meta name="apple-mobile-web-app-title" content="David Larlet">
  21. <meta name="application-name" content="David Larlet">
  22. <meta name="msapplication-TileColor" content="#da532c">
  23. <meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">
  24. <meta name="theme-color" content="#f0f0ea">
  25. <!-- That good ol' feed, subscribe :p. -->
  26. <link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">
  27. <meta name="robots" content="noindex, nofollow">
  28. <meta content="origin-when-cross-origin" name="referrer">
  29. <!-- Canonical URL for SEO purposes -->
  30. <link rel="canonical" href="https://trishagee.github.io/post/more_women_speakers/">
  31. <style>
  32. /* http://meyerweb.com/eric/tools/css/reset/ */
  33. html, body, div, span,
  34. h1, h2, h3, h4, h5, h6, p, blockquote, pre,
  35. a, abbr, address, big, cite, code,
  36. del, dfn, em, img, ins,
  37. small, strike, strong, tt, var,
  38. dl, dt, dd, ol, ul, li,
  39. fieldset, form, label, legend,
  40. table, caption, tbody, tfoot, thead, tr, th, td,
  41. article, aside, canvas, details, embed,
  42. figure, figcaption, footer, header, hgroup,
  43. menu, nav, output, ruby, section, summary,
  44. time, mark, audio, video {
  45. margin: 0;
  46. padding: 0;
  47. border: 0;
  48. font-size: 100%;
  49. font: inherit;
  50. vertical-align: baseline;
  51. }
  52. /* HTML5 display-role reset for older browsers */
  53. article, aside, details, figcaption, figure,
  54. footer, header, hgroup, menu, nav, section { display: block; }
  55. body { line-height: 1; }
  56. blockquote, q { quotes: none; }
  57. blockquote:before, blockquote:after,
  58. q:before, q:after {
  59. content: '';
  60. content: none;
  61. }
  62. table {
  63. border-collapse: collapse;
  64. border-spacing: 0;
  65. }
  66. /* http://practicaltypography.com/equity.html */
  67. /* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */
  68. /* https://www.filamentgroup.com/lab/js-web-fonts.html */
  69. @font-face {
  70. font-family: 'EquityTextB';
  71. src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),
  72. url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');
  73. font-weight: 300;
  74. font-style: normal;
  75. font-display: swap;
  76. }
  77. @font-face {
  78. font-family: 'EquityTextB';
  79. src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),
  80. url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');
  81. font-weight: 300;
  82. font-style: italic;
  83. font-display: swap;
  84. }
  85. @font-face {
  86. font-family: 'EquityTextB';
  87. src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),
  88. url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');
  89. font-weight: 700;
  90. font-style: normal;
  91. font-display: swap;
  92. }
  93. @font-face {
  94. font-family: 'ConcourseT3';
  95. src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),
  96. url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');
  97. font-weight: 300;
  98. font-style: normal;
  99. font-display: swap;
  100. }
  101. /* http://practice.typekit.com/lesson/caring-about-opentype-features/ */
  102. body {
  103. /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */
  104. font-family: "EquityTextB", Palatino, serif;
  105. background-color: #f0f0ea;
  106. color: #07486c;
  107. font-kerning: normal;
  108. -moz-osx-font-smoothing: grayscale;
  109. -webkit-font-smoothing: subpixel-antialiased;
  110. text-rendering: optimizeLegibility;
  111. font-variant-ligatures: common-ligatures contextual;
  112. font-feature-settings: "kern", "liga", "clig", "calt";
  113. }
  114. pre, code, kbd, samp, var, tt {
  115. font-family: 'TriplicateT4c', monospace;
  116. }
  117. em {
  118. font-style: italic;
  119. color: #323a45;
  120. }
  121. strong {
  122. font-weight: bold;
  123. color: black;
  124. }
  125. nav {
  126. background-color: #323a45;
  127. color: #f0f0ea;
  128. display: flex;
  129. justify-content: space-around;
  130. padding: 1rem .5rem;
  131. }
  132. nav:last-child {
  133. border-bottom: 1vh solid #2d7474;
  134. }
  135. nav a {
  136. color: #f0f0ea;
  137. }
  138. nav abbr {
  139. border-bottom: 1px dotted white;
  140. }
  141. h1 {
  142. border-top: 1vh solid #2d7474;
  143. border-bottom: .2vh dotted #2d7474;
  144. background-color: #e3e1e1;
  145. color: #323a45;
  146. text-align: center;
  147. padding: 5rem 0 4rem 0;
  148. width: 100%;
  149. font-family: 'ConcourseT3';
  150. display: flex;
  151. flex-direction: column;
  152. }
  153. h1.single {
  154. padding-bottom: 10rem;
  155. }
  156. h1 span {
  157. position: absolute;
  158. top: 1vh;
  159. left: 20%;
  160. line-height: 0;
  161. }
  162. h1 span a {
  163. line-height: 1.7;
  164. padding: 1rem 1.2rem .6rem 1.2rem;
  165. border-radius: 0 0 6% 6%;
  166. background: #2d7474;
  167. font-size: 1.3rem;
  168. color: white;
  169. text-decoration: none;
  170. }
  171. h2 {
  172. margin: 4rem 0 1rem;
  173. border-top: .2vh solid #2d7474;
  174. padding-top: 1vh;
  175. }
  176. h3 {
  177. text-align: center;
  178. margin: 3rem 0 .75em;
  179. }
  180. hr {
  181. height: .4rem;
  182. width: .4rem;
  183. border-radius: .4rem;
  184. background: #07486c;
  185. margin: 2.5rem auto;
  186. }
  187. time {
  188. display: bloc;
  189. margin-left: 0 !important;
  190. }
  191. ul, ol {
  192. margin: 2rem;
  193. }
  194. ul {
  195. list-style-type: square;
  196. }
  197. a {
  198. text-decoration-skip-ink: auto;
  199. text-decoration-thickness: 0.05em;
  200. text-underline-offset: 0.09em;
  201. }
  202. article {
  203. max-width: 50rem;
  204. display: flex;
  205. flex-direction: column;
  206. margin: 2rem auto;
  207. }
  208. article.single {
  209. border-top: .2vh dotted #2d7474;
  210. margin: -6rem auto 1rem auto;
  211. background: #f0f0ea;
  212. padding: 2rem;
  213. }
  214. article p:last-child {
  215. margin-bottom: 1rem;
  216. }
  217. p {
  218. padding: 0 .5rem;
  219. margin-left: 3rem;
  220. }
  221. p + p,
  222. figure + p {
  223. margin-top: 2rem;
  224. }
  225. blockquote {
  226. background-color: #e3e1e1;
  227. border-left: .5vw solid #2d7474;
  228. display: flex;
  229. flex-direction: column;
  230. align-items: center;
  231. padding: 1rem;
  232. margin: 1.5rem;
  233. }
  234. blockquote cite {
  235. font-style: italic;
  236. }
  237. blockquote p {
  238. margin-left: 0;
  239. }
  240. figure {
  241. border-top: .2vh solid #2d7474;
  242. background-color: #e3e1e1;
  243. text-align: center;
  244. padding: 1.5rem 0;
  245. margin: 1rem 0 0;
  246. font-size: 1.5rem;
  247. width: 100%;
  248. }
  249. figure img {
  250. max-width: 250px;
  251. max-height: 250px;
  252. border: .5vw solid #323a45;
  253. padding: 1px;
  254. }
  255. figcaption {
  256. padding: 1rem;
  257. line-height: 1.4;
  258. }
  259. aside {
  260. display: flex;
  261. flex-direction: column;
  262. background-color: #e3e1e1;
  263. padding: 1rem 0;
  264. border-bottom: .2vh solid #07486c;
  265. }
  266. aside p {
  267. max-width: 50rem;
  268. margin: 0 auto;
  269. }
  270. /* https://fvsch.com/code/css-locks/ */
  271. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  272. font-size: 1rem;
  273. line-height: calc( 1.5em + 0.2 * 1rem );
  274. }
  275. h1 {
  276. font-size: 1.9rem;
  277. line-height: calc( 1.2em + 0.2 * 1rem );
  278. }
  279. h2 {
  280. font-size: 1.6rem;
  281. line-height: calc( 1.3em + 0.2 * 1rem );
  282. }
  283. h3 {
  284. font-size: 1.35rem;
  285. line-height: calc( 1.4em + 0.2 * 1rem );
  286. }
  287. @media (min-width: 20em) {
  288. /* The (100vw - 20rem) / (50 - 20) part
  289. resolves to 0-1rem, depending on the
  290. viewport width (between 20em and 50em). */
  291. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  292. font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );
  293. line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );
  294. margin-left: 0;
  295. }
  296. h1 {
  297. font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  298. line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );
  299. }
  300. h2 {
  301. font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  302. line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );
  303. }
  304. h3 {
  305. font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );
  306. line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );
  307. }
  308. }
  309. @media (min-width: 50em) {
  310. /* The right part of the addition *must* be a
  311. rem value. In this example we *could* change
  312. the whole declaration to font-size:2.5rem,
  313. but if our baseline value was not expressed
  314. in rem we would have to use calc. */
  315. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  316. font-size: calc( 1rem + .6 * 1rem );
  317. line-height: 1.5em;
  318. }
  319. p, li, pre, details {
  320. margin-left: 3rem;
  321. }
  322. h1 {
  323. font-size: calc( 1.9rem + 1.5 * 1rem );
  324. line-height: 1.2em;
  325. }
  326. h2 {
  327. font-size: calc( 1.5rem + 1.5 * 1rem );
  328. line-height: 1.3em;
  329. }
  330. h3 {
  331. font-size: calc( 1.35rem + 1.5 * 1rem );
  332. line-height: 1.4em;
  333. }
  334. figure img {
  335. max-width: 500px;
  336. max-height: 500px;
  337. }
  338. }
  339. figure.unsquared {
  340. margin-bottom: 1.5rem;
  341. }
  342. figure.unsquared img {
  343. height: inherit;
  344. }
  345. @media print {
  346. body { font-size: 100%; }
  347. a:after { content: " (" attr(href) ")"; }
  348. a, a:link, a:visited, a:after {
  349. text-decoration: underline;
  350. text-shadow: none !important;
  351. background-image: none !important;
  352. background: white;
  353. color: black;
  354. }
  355. abbr[title] { border-bottom: 0; }
  356. abbr[title]:after { content: " (" attr(title) ")"; }
  357. img { page-break-inside: avoid; }
  358. @page { margin: 2cm .5cm; }
  359. h1, h2, h3 { page-break-after: avoid; }
  360. p3 { orphans: 3; widows: 3; }
  361. img {
  362. max-width: 250px !important;
  363. max-height: 250px !important;
  364. }
  365. nav, aside { display: none; }
  366. }
  367. ul.with_columns {
  368. column-count: 1;
  369. }
  370. @media (min-width: 20em) {
  371. ul.with_columns {
  372. column-count: 2;
  373. }
  374. }
  375. @media (min-width: 50em) {
  376. ul.with_columns {
  377. column-count: 3;
  378. }
  379. }
  380. ul.with_two_columns {
  381. column-count: 1;
  382. }
  383. @media (min-width: 20em) {
  384. ul.with_two_columns {
  385. column-count: 1;
  386. }
  387. }
  388. @media (min-width: 50em) {
  389. ul.with_two_columns {
  390. column-count: 2;
  391. }
  392. }
  393. .gallery {
  394. display: flex;
  395. flex-wrap: wrap;
  396. justify-content: space-around;
  397. }
  398. .gallery figure img {
  399. margin-left: 1rem;
  400. margin-right: 1rem;
  401. }
  402. .gallery figure figcaption {
  403. font-family: 'ConcourseT3'
  404. }
  405. footer {
  406. font-family: 'ConcourseT3';
  407. display: flex;
  408. flex-direction: column;
  409. border-top: 3px solid white;
  410. padding: 4rem 0;
  411. background-color: #07486c;
  412. color: white;
  413. }
  414. footer > * {
  415. max-width: 50rem;
  416. margin: 0 auto;
  417. }
  418. footer a {
  419. color: #f1c40f;
  420. }
  421. footer .avatar {
  422. width: 200px;
  423. height: 200px;
  424. border-radius: 50%;
  425. float: left;
  426. -webkit-shape-outside: circle();
  427. shape-outside: circle();
  428. margin-right: 2rem;
  429. padding: 2px 5px 5px 2px;
  430. background: white;
  431. border-left: 1px solid #f1c40f;
  432. border-top: 1px solid #f1c40f;
  433. border-right: 5px solid #f1c40f;
  434. border-bottom: 5px solid #f1c40f;
  435. }
  436. </style>
  437. <h1>
  438. <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>
  439. What Can Conferences Do To Attract More Women Speakers? (archive)
  440. <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>
  441. </h1>
  442. <section>
  443. <article>
  444. <h3><a href="https://trishagee.github.io/post/more_women_speakers/">Source originale du contenu</a></h3>
  445. <p>Now I’ve been speaking at (mostly Java) conferences for a while (six years now), I get asked to
  446. present at a lot of conferences. <em>Obviously</em> all these conferences are mostly interested in my
  447. terribly educational talks, but it’s also because I’m a technical woman and there aren’t very
  448. many technical women speaking at conferences.</p>
  449. <p>In my experience, conferences want to do the right thing - they want a diverse line up of
  450. speakers, they want to attract diverse attendees. Often this is not as easy as it may seem, and
  451. frequently conferences are Twitter-shamed for not having enough women speakers. When it gets to
  452. this point (and often before), conferences frequently ask me for advice on
  453. speakers they could invite, and how to attract more women.</p>
  454. <p>I do at this point have to roll my eyes somewhat though. It’s an additional bit of workload that
  455. my male peers do not have to do: they are not asked to recommend suitable women speakers; they
  456. are not asked what a conference should be doing to improve diversity. And let’s not forget that
  457. one of the reasons why I have made it to this point in our male industry is by having some
  458. combination of luck, selective blindness and an unusual attitude which means that I’m probably not
  459. qualified to speak on behalf of all the other women developers/speakers out there.</p>
  460. <p>Anyway. To save myself some time in the future, here’s my blog post version of
  461. stuff-that-I-can-think-of-that-might-help. This is not scientific. There’s a bunch more stuff out
  462. there on the internet (including
  463. <a href="https://continuousdelivery.com/2013/09/how-we-got-40-female-speakers-at-flowcon/">one from Jez Humble</a>
  464. and
  465. <a href="https://medium.com/samsung-internet-dev/help-someone-has-pointed-out-my-conference-has-diversity-issues-c1162a1e8d4c">help, my conference has diversity issues</a>),
  466. please do Google for more. The following suggestions come from my experience as a) a speaker b)
  467. a programme committee member of QCon London, DevoxxUK and DevoxxUS and c) just a normal person
  468. who thinks about these things.</p>
  469. <h2 id="toc_0">Have a Code of Conduct</h2>
  470. <p>Many many things have been written about this, I don’t intend to rehash them. You need one, if
  471. you don’t have one go and research this and put one in place.</p>
  472. <h2 id="toc_1">Consider Diversity as a Key, Cross-Cutting Concern of Your Conference</h2>
  473. <p>You couldn’t have a
  474. conference without researching venues; without figuring out the catering; without doing analysis
  475. of costs. If you’re serious about diversity, about improving the industry, or even just about not
  476. being attacked on Twitter, you have to consider diversity right from the start, and you have to
  477. consider it in the context of almost every other decision: Does the venue have step-free access?
  478. Can the caterers provide a range of non-alcoholic drinks rather than just the standard beers? Do
  479. the dates clash with some major religious festival? Or football event? (for example).
  480. Considering people with different needs, cultures, interests is something that you need to take
  481. seriously at every step. Diversity is not something you can just tack on at the last minute.
  482. This Is Hard. It helps if your organisers/program committee members are diverse, as others will
  483. think of things you have not.</p>
  484. <h2 id="toc_2">Your Website and Marketing Material Should Represent the People You Want to Attract</h2>
  485. <p>Make
  486. sure that on your website and in your emails/tweets, photos of attendees and speakers
  487. represent the range of people you want to come. Don’t just put up a handful of photos
  488. from last year’s conference without looking very closely at who is, and who is not, shown in
  489. these photos. From a gender diversity point of view, my rule of thumb is that every photo should
  490. have at least one female-looking person visible in it, ideally closer to 50%. Other measures of
  491. diversity that may be visible in photos include race and age, but
  492. it can also be things like dress code - the first DevoxxUK attracted people with pink mohawks,
  493. goths, men/women in suits, as well as the usual tshirt-and-jeans brigade. It was wonderful!</p>
  494. <p>To showcase diversity in photos/images, you can:</p>
  495. <ul>
  496. <li>Show your organisers/programme committee. In my experience there are usually women in amongst
  497. the organisers, having photos of them on the site in a visible place is a good way to suggest to
  498. women that if they submit a talk they will be evaluated by people like them. As usual, I’m
  499. focusing on gender, but this can apply to other dimensions too.</li>
  500. <li>Select photos from previous conferences that include women (I’ve heard that the new
  501. <a href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation">GDPR</a> may prevent you from
  502. posting photos of people publicly without their consent, so be careful here). Make sure they’re
  503. not booth babes (Note: Do Not Allow Booth Babes. By all means, women should work on
  504. sponsor booths, but they should be employees of the company, not women hired in to look a
  505. particular way to sell the product). Ideally in these photos the women should look like they are
  506. being included, e.g. in groups talking to people, not standing alone to one side.</li>
  507. <li>Showcase your diverse speakers. This is a catch 22 of course, because you want to showcase
  508. diversity in order to attract speakers to submit, so you can’t show diverse speakers before
  509. you’ve had speakers submit… You can show speakers from previous years; you can show your
  510. keynote speakers (hint: it’s a good idea to have at least one woman giving a keynote and you
  511. should secure them well before the CFP closes so you can show them off); you can invite selected
  512. speakers early who won’t go through the CFP and show them on the site (see next
  513. section)</li>
  514. </ul>
  515. <p>It’s not just about photos, it’s also logos/imagery and language. If you have characters, make
  516. sure they’re not all men/masculine. If you have a theme, make sure it’s open to all. I really
  517. loved
  518. <a href="https://www.linkedin.com/pulse/devoxx-uk-2015-stephan-janssen/">DevoxxUK’s League of Extraordinary Developers</a>,
  519. it showed a range of diverse characters, not
  520. just gender and race but implied we’re not all the same and we have different strengths and
  521. skills.</p>
  522. <p>Also check the language you use. There have been a number of studies
  523. that show that <a href="https://www.forbes.com/sites/hbsworkingknowledge/2016/12/14/how-to-take-gender-bias-out-of-your-job-ads/#490276c71024">language in job adverts can subtly imply male vs female
  524. roles</a>. But even easier
  525. than that, make sure you don’t assume attendees will be a “he” and don’t use words like “guys” -
  526. you may have seen this used in a gender neutral way but many people feel it is <em>not</em> gender
  527. neutral and implies “men”.</p>
  528. <h2 id="toc_3">Invite Women Speakers Early, and Personally</h2>
  529. <p>Women speakers are very much in demand. There
  530. are more conferences than women speakers, and we get booked up well in advance (my next 9-12
  531. months are usually already booked up). If you want to
  532. ensure you have a decent proportion of women speakers, you need to reach out to us personally,
  533. early, and ideally offer us a guaranteed speaking slot. I’m not a fan of being asked to submit
  534. to a CFP, I get invited to enough conferences that I don’t need to go to more, and going through a
  535. CFP adds a lot of variability. For experienced speakers who you know you’re likely
  536. to accept anyway, consider offering them a guaranteed slot. For less experienced / new speakers,
  537. invite them to submit. But whoever you’re reaching out to, at least (please) put their name on the
  538. email. One of the conferences suffering from a lack of women speakers at the moment invited me
  539. with a standard email addressed to “Dear madam”. I’m usually strict about replying to requests
  540. but I didn’t take the time to reply to this one as they didn’t take the time to customise their
  541. request to me. On this topic, what I want to see in an invitation email (and maybe other people
  542. are different) are:</p>
  543. <ul>
  544. <li>In the first paragraph: which conference (with link); date; city; very very short description
  545. of the conference (“community run Java conference”, “Europe’s biggest devops conference”,
  546. something that gives me a rough idea of technology and community); what do you want me to
  547. speak about (either a specific talk, or a more general topic).</li>
  548. <li>If you cover travel/accommodation, put that somewhere near the beginning of your email, this
  549. can make it much easier for a speaker to say “yes” to your conference.</li>
  550. <li>Other useful information can go in the later paragraphs: approx number of attendees; who else
  551. is presenting / has presented in the past; interesting activities during the conference / in
  552. the city. None of this stuff is mandatory.</li>
  553. <li>A bit of flattery / how you know about me is always welcome. Oh but don’t be creepy <em>shudder</em>.</li>
  554. </ul>
  555. <h2 id="toc_4">Find Women</h2>
  556. <p>Easy, right? Not so much. But please, don’t just email the first woman speaker
  557. who comes to your mind and say “please come and speak, and also if you could find us all the other
  558. women speakers we need that would be great too”. By all means ask for recommendations (from all
  559. speakers actually, it’s freaking exhausting being a woman speaker because we do a lot of work in
  560. this area, connecting people up and pointing them in the right direction and plenty of
  561. experienced male speakers are better at this than me). But this is a numbers game - there aren’t
  562. many women speakers and those that do this regularly are very in demand, you’re going to need to
  563. invite a <em>lot</em> of women to stand a chance of having a diverse line up. Here are some suggestions
  564. based on what I’ve done in the past to find women speakers:</p>
  565. <ul>
  566. <li>Google “Women in…” Java, Data, Blockchain, whatever.</li>
  567. <li>Look at big conferences in this space from the last two years, spot the female-ish faces and
  568. make a list of them. When asked for Java/JVM recommendations, I check JavaOne,
  569. DevoxxUK/Belgium, JavaZone, JFokus and maybe Google “Java conferences” to find the others I’ve
  570. forgotten. For broader topics I look at QCon London because I know they always
  571. work hard on diversity and have had a bunch of really fantastic women speakers in the past. I
  572. sometimes check out the GOTO conferences for the same reason.</li>
  573. <li>Look for local user groups who could help. You can search Meetup.com
  574. for “Women code”, “Lady developers” and variations on that theme. Find the groups in the area
  575. local to the conference, and reach out really nicely to them to ask if they wouldn’t mind
  576. circulating the details of your CFP amongst their members. Remember to provide them with
  577. information about why their members want to speak
  578. (all travel covered/opportunities to meet various people/mentoring provided, whatever). If you
  579. can see previous speakers at these groups, you could add them to your list of women to reach
  580. out to personally.</li>
  581. <li>Ask <a href="https://twitter.com/callbackwomen">Callback women</a> to retweet the CFP details</li>
  582. <li>Check out the networks of women speakers, like
  583. <a href="http://articulate-network.lanyrd.com/">Articulate Network</a>,
  584. <a href="https://github.com/fempire/women-tech-speakers-organizers">this list of women speakers</a>, and
  585. <a href="https://womenwhokeynote.com/">Women who keynote</a>. Google
  586. for these lists too, there’s loads of them. Sadly these resources are not very centralised.</li>
  587. </ul>
  588. <h2 id="toc_5">Provide Travel and Accommodation</h2>
  589. <p>Particularly if you’re trying to attract/grow new
  590. speakers. You may not have budget to apply this to everyone, but if you really want to have diverse
  591. speakers you may need to set aside some budget to pay for them. In my first year of presenting I
  592. was doing it more or less on my own (vacation) time because I had a real job as a real
  593. developer, and I could only speak at conferences who would cover my costs. This is even more
  594. tricky for self employed people as they’re also losing money by attending your conference. Be
  595. aware that not everyone a) is a professional advocate (and even when we are it’s easier to say
  596. yes to a conference if our employer doesn’t have to pay) b) is employed by a forward-thinking
  597. employer who is happy to let employees go to conferences or c) has paid vacation time they are
  598. willing/able to use. Be aware that for some people this cost might be more than just
  599. the cheapest flight and cheapest hotel for one person - one conference paid for me,
  600. my partner and my (at the time) one-year-old to travel halfway around the world so I could speak at
  601. the conference. I couldn’t take that time away from my family so they brought the whole family,
  602. I would not have been able to speak there otherwise. Another conference this year is paying
  603. for all four of us to travel, plus a family hotel room - I’m currently breastfeeding and I can’t
  604. leave the baby for very long, and if I’m going to bring the baby I need to bring the husband to
  605. take the baby while I’m talking, which means we also need to bring the toddler, because she’s
  606. a bit young to leave at home alone for a weekend. I don’t always need all these costs covering,
  607. I’m not always breastfeeding, and even after the first was born there were plenty of times I could
  608. travel alone. But if you want to improve your diversity you’re going to need to consider these
  609. sorts of cases.</p>
  610. <h2 id="toc_6">Provide rehearsal space</h2>
  611. <p>This is quite time consuming and relies on having people willing
  612. to watch the rehearsal and give feedback. I actually mean <em>virtual</em> space here, I’ve given my talk
  613. via hangouts to the track lead for QCon New York to get feedback on a new talk.</p>
  614. <p>If you’re trying
  615. to attract new talent, consider involving one or more local user groups and running a speaker
  616. training session. The London Java Community has done this a couple of times. You need to select
  617. the people who will provide mentoring / feedback <em>very</em> carefully. They need to be aware of the
  618. type of gendered words that are frequently used for women and avoid them (would
  619. you ever use the word “feisty” for a man? No, you would not); they
  620. need to be aware that women get
  621. <a href="https://hbr.org/2017/04/how-gender-bias-corrupts-performance-reviews-and-what-to-do-about-it">critical personality feedback</a>
  622. instead of actionable feedback.
  623. The feedback to help mentor new speakers, particularly women speakers, needs to be well thought
  624. out (not “you seem nervous”, maybe “is there some section of the content
  625. that makes you uncomfortable”, for example). These mentors need to be experienced speakers.
  626. Ideally they should also be diverse, but if this is not possible then men who are experienced at
  627. championing women will be OK (my mentors were all men).</p>
  628. <p>You can also run community nights, these
  629. aren’t sessions aimed at training the speakers, but user group events where you can have
  630. prospective speakers present their talk. Obviously this works if a) the speaker is local and b)
  631. you have links with appropriate local user groups. But this is a good way to grow the community,
  632. and to try out speakers without having to judge them through a CFP.</p>
  633. <h2 id="toc_7">Have lightning talks on the agenda</h2>
  634. <p>Lightning talks can be a very mixed bag of quality and can introduce complexity to your scheduling.
  635. But they’re also a good way to get inexperienced speakers
  636. into the conference, and to give them an opportunity to be videoed (and have conference speaking
  637. on their CV) so they can break into speaking properly. As an attendee I like lightning talks -
  638. the topics are often varied, and ones I often wouldn’t bother watching a whole hour of, and I’ll
  639. tolerate poor content/poor delivery for 10 minutes without complaint. You will need to consider
  640. your cost/benefit here though, I doubt you’ll want to pay expenses to ship a whole family of four
  641. over to your conference for the sake of a 10 minute talk, these seem to work best in encouraging
  642. local developers to speak at your conference. Again, ties with local user groups will be key here.</p>
  643. <h2 id="toc_8">Be Open to Flexible Scheduling</h2>
  644. <p>I know, I really do, that your conference is really hard to
  645. schedule. Not just the
  646. actual dates, but who presents in which room at what time. This is super difficult, and most
  647. speakers understand this and will accept the vague “your talk will be one of these three days”
  648. notice. Many speakers who are just starting will probably love to be there for the whole
  649. conference, I certainly did! But this is really hard for people who can’t get the time off work
  650. or away from their family. It’s also less exciting when you’ve already seen many of the talks
  651. you care about.</p>
  652. <p>When I started doing this, my work was peeved if I took three days off to travel to a
  653. conference. Now, I’m peeved if I take three days away from my family. There’s a really hard
  654. balance for us speakers to strike, especially when
  655. we book our own travel: we either need to book early to get cheap travel, in which case we
  656. don’t know when our talk is so we have to be there for the whole conference; or we book as soon
  657. as we know the date and time of the talk, in which case someone is going to be stung with higher
  658. travel costs.</p>
  659. <p>Considering diversity also means understanding that not everyone lives in or near a city
  660. with a major airport. It’s easy to get spoilt in London, Paris, Madrid, Amsterdam, because
  661. there are so many flights to so many places from there. But because I’m
  662. travelling from somewhere that isn’t a major airport,
  663. direct flights to many conference locations are rare, and if they exist are almost always only
  664. on a couple
  665. of days the week and at horrible times, so my ability to get to and from the conference is
  666. limited. This either adds one or two days either side of the conference waiting for the
  667. right flight (so days and days away from the family for a one hour talk), or means I have a very
  668. small window during your conference that I can be there. What would make my life easier is one of:</p>
  669. <ul>
  670. <li>Tell me my time slot as soon as possible. Oh, and do tell me. Most conferences don’t
  671. bother, I have to check the schedule when it’s posted on the website which is often only a
  672. couple of weeks before the conference.</li>
  673. <li>Allow me to suggest the best dates/times for me. I know it’s not possible to accommodate
  674. everyone, but for those of us with difficult schedules and/or who want to limit time away from
  675. home/work, I would really like to be able to say “I can only do this conference if I can talk
  676. Monday afternoon” and not sound like a diva.</li>
  677. </ul>
  678. <h2 id="toc_9">Consider Diversity Scholarships</h2>
  679. <p>Some conferences offer discounts/free tickets for underrepresented groups.
  680. I feel a bit torn on this topic personally because I’m not a big fan of positive discrimination and
  681. this looks a bit like that. But if you have offered something like this, it may attract
  682. speakers from underrepresented groups as well, because you are doing something proactive. If you
  683. consider this idea please do your research in this area.</p>
  684. <h2 id="toc_10">Swag isn’t Just for Boys</h2>
  685. <p>When I first started going to conferences I got really annoyed
  686. that all the free t-shirts were “unisex”, i.e. male. I don’t really care about this any more
  687. because I’d like to wear clothes that I’ve actually chosen and paid for that actually fit me.
  688. But it does annoy a lot of women
  689. speakers and attendees, and it’s always noticeable when a conference goes out of
  690. its way to have women’s shapes and sizes. But don’t make them a different colour/logo, this just
  691. says “hey women, you’re like a totally different species and we’re going to make you stand out”.
  692. Doesn’t matter that in 100% of the cases where I’ve had a different colour the men have been
  693. totally jealous of my much more attractive women’s cut top, what matters is you don’t want to
  694. make the minorities stand out even more than they already do.</p>
  695. <p>It’s not just t-shirts either. For each bit of swag, think “would I give this to my sister / gay
  696. friend / muslim co-worker?“. Not everyone at the conference is a beer-drinking, youngish,
  697. straight, white, single male. And even those who are can be offended by swag that stereotypes
  698. what they should be interested in.</p>
  699. <h2 id="toc_11">Consider having a blind CFP</h2>
  700. <p>I’ve written in the past that I’m really not sure about this
  701. as a solution, but other sectors and other conferences have had success with this. Perhaps if
  702. you combine this with actively reaching out to women and giving them guaranteed speaking slots,
  703. maybe this will address the weaknesses of both the invitation and the CFP processes. Do your
  704. research, see how you feel.</p>
  705. <h2 id="toc_12">Note for women speakers</h2>
  706. <p>After all that advice for conference organisers, I’d really like to say something to the women
  707. speakers out there. As usual, my advice applies to men too, but I want to talk specifically to the
  708. ladies.</p>
  709. <p>If a conference invites you to speak and you have no intention of going, please respond with a
  710. “no” as promptly as possible. I’ve been on both sides of the
  711. invitation (inviting speakers to speak and being invited) and as an inviter it is very very
  712. frustrating not to hear anything back from a valued speaker, especially if there’s a slot held
  713. for this speaker that needs to be filled. As a speaker, every time I’ve said “no”
  714. within a few hours of getting the email, I almost always get a very nice response
  715. saying “thanks for the quick reply”. Saying “no” quickly is not ever going to be considered
  716. rude, it’s actually very helpful to the organisers. Waiting a while because you want to phrase
  717. it in a nice way, or
  718. simply never getting around to responding because you mean to think the offer through and/or
  719. spend some time on the reply (and I am <em>the worst</em> at this in most of my email) puts the
  720. conference into limbo - yes, they will have invited plenty
  721. of other speakers so they’re not just dependent upon you, but if half of them don’t take the
  722. time to respond the organisers don’t know if they need to reach out to more people or not. And
  723. as a speaker it’s a bit embarrassing to respond a week or more later with a “yes” only to have the
  724. conference say “er, sorry, we didn’t hear from you so we’re all full now”. This has happened to
  725. me. I felt bad.</p>
  726. <p>So:</p>
  727. <ul>
  728. <li>If you know you’re not going, say “no” straight away (“thanks for the invite, really pleased
  729. you’re interested in having me, but I’m afraid I can’t make it”, or something, doesn’t have to be
  730. long winded and you don’t have to justify why you’re not going).<br/></li>
  731. <li>If you’re thinking about it
  732. but you have to work out details/check with work/run it past your partner/research costs,
  733. respond telling them you’re thinking about it, and give a rough date of when you’ll get back to
  734. them (“thanks for the invite, it looks really interesting, I can’t commit right now because
  735. I’ve got some stuff to work out, if I don’t get back to you by the end of next week please give
  736. me a nudge”). If you’re having some trouble working out the details (maybe the flights are too
  737. expensive, maybe work won’t give you the time off) update the conference with this information
  738. because they might be able to do something (give you money towards travel; send you some useful
  739. blurb to wave at your boss about why this is a good business investment for them, etc)</li>
  740. <li>Obviously if it’s a yes just respond straight away with yes.</li>
  741. </ul>
  742. <p>Don’t, please, just fail to respond. I know you’re super busy, I know you have an inbox stacked
  743. full of more important things you haven’t got around to. Set up a
  744. <a href="https://support.google.com/inbox/answer/7107959?hl=en">Google template</a> (or equivalent) and it
  745. will take seconds to reply, and it’s one more mail you can get out of your inbox. I’ve heard a lot
  746. of frustration from conference organisers that the women they contact never reply, and because human
  747. nature is the way it is, it leaves organisers feeling demotivated and makes them less likely to
  748. reach out to other women. I know this isn’t your fault, but it is something we can all help to
  749. improve.</p>
  750. <h2 id="toc_13">In Summary</h2>
  751. <p>There are probably loads and loads of things I haven’t mentioned. And it’s possible that
  752. conference organisers could do all of these things and still not reach the numbers they want. But I
  753. can practically guarantee that if, as an organiser, you don’t do any of these, you aren’t going
  754. to get many women speakers at all. Please, read all of these items again, and for your next
  755. conference create a tick-list of all the
  756. things you’re going to do, and all the things you need to check at each stage (like the imagery
  757. and language of your marketing material).</p>
  758. </article>
  759. </section>
  760. <nav id="jumpto">
  761. <p>
  762. <a href="/david/blog/">Accueil du blog</a> |
  763. <a href="https://trishagee.github.io/post/more_women_speakers/">Source originale</a> |
  764. <a href="/david/stream/2019/">Accueil du flux</a>
  765. </p>
  766. </nav>
  767. <footer>
  768. <div>
  769. <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
  770. <p>
  771. Bonjour/Hi!
  772. Je suis <a href="/david/" title="Profil public">David&nbsp;Larlet</a>, je vis actuellement à Montréal et j’alimente cet espace depuis 15 ans. <br>
  773. Si tu as apprécié cette lecture, n’hésite pas à poursuivre ton exploration. Par exemple via les <a href="/david/blog/" title="Expériences bienveillantes">réflexions bimestrielles</a>, la <a href="/david/stream/2019/" title="Pensées (dés)articulées">veille hebdomadaire</a> ou en t’abonnant au <a href="/david/log/" title="S’abonner aux publications via RSS">flux RSS</a> (<a href="/david/blog/2019/flux-rss/" title="Tiens c’est quoi un flux RSS ?">so 2005</a>).
  774. </p>
  775. <p>
  776. Je m’intéresse à la place que je peux avoir dans ce monde. En tant qu’humain, en tant que membre d’une famille et en tant qu’associé d’une coopérative. De temps en temps, je fais aussi des <a href="https://github.com/davidbgk" title="Principalement sur Github mais aussi ailleurs">trucs techniques</a>. Et encore plus rarement, <a href="/david/talks/" title="En ce moment je laisse plutôt la place aux autres">j’en parle</a>.
  777. </p>
  778. <p>
  779. Voici quelques articles choisis :
  780. <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
  781. <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
  782. <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
  783. <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
  784. <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
  785. <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
  786. <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
  787. <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
  788. <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
  789. <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
  790. <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
  791. <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
  792. <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
  793. <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
  794. <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
  795. et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
  796. </p>
  797. <p>
  798. On peut <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">échanger par courriel</a>. Si éventuellement tu souhaites que l’on travaille ensemble, tu devrais commencer par consulter le <a href="http://larlet.com">profil dédié à mon activité professionnelle</a> et/ou contacter directement <a href="http://scopyleft.fr/">scopyleft</a>, la <abbr title="Société coopérative et participative">SCOP</abbr> dont je fais partie depuis six ans. Je recommande au préalable de lire <a href="/david/blog/2018/cout-site/" title="Attention ce qui va suivre peut vous choquer">combien coûte un site</a> et pourquoi je suis plutôt favorable à une <a href="/david/pro/devis/" title="Discutons-en !">non-demande de devis</a>.
  799. </p>
  800. <p>
  801. Je ne traque pas ta navigation mais mon
  802. <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
  803. conserve des logs d’accès.
  804. </p>
  805. </div>
  806. </footer>
  807. <script type="text/javascript">
  808. ;(_ => {
  809. const jumper = document.getElementById('jumper')
  810. jumper.addEventListener('click', e => {
  811. e.preventDefault()
  812. const anchor = e.target.getAttribute('href')
  813. const targetEl = document.getElementById(anchor.substring(1))
  814. targetEl.scrollIntoView({behavior: 'smooth'})
  815. })
  816. })()
  817. </script>