<div dir="ltr"><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 16 Jun 2019 at 8:05 PM, Vijay Kumar <<a href="mailto:vijaykumar@bravegnu.org" target="_blank">vijaykumar@bravegnu.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sunday 16 June 2019 07:05 PM, Pradyun Gedam wrote:<br>
<br>
> On Sun, 16 Jun 2019 at 2:27 PM, Vijay Kumar <<a href="mailto:vijaykumar@bravegnu.org" target="_blank">vijaykumar@bravegnu.org</a> <br>
> <mailto:<a href="mailto:vijaykumar@bravegnu.org" target="_blank">vijaykumar@bravegnu.org</a>>> wrote:<br>
><br>
> Please let me know your thoughts on this.<br>
><br>
> It is important to note why PyCascades removed Q&A -- to "/make it a <br>
> more friendly environment for first time and new speakers/.", which is <br>
> especially relevant to PyCascades, since it is a single track <br>
> conference. PyCascades also goes out of it's way to be welcoming, and <br>
> has a substantial effort put into Diversity and Inclusion (they have a <br>
> Diversity Chair), so removing a potential area of stress for such <br>
> speakers is especially relevant to them. I don't think these points <br>
> apply to PyCon India, since the structure of the conference is <br>
> different and there are a lot of cultural differences in the audience.<br>
<br>
This actually applies to PyCon India, as well. Diversity and inclusion <br>
is a key part of our efforts too. We also have a Diversity workgroup <br>
that is putting in efforts to bring in speakers and participation from <br>
under-represented groups.</blockquote><div dir="auto"><br></div><div dir="auto">Indeed, I wasn't implying that there are no diversity and inclusion efforts at PyCon India or that they aren't a positive influence on the conference. I do think scopes of the D&I efforts are different since there are substantial cultural differences in the audiences of the conference. </div><div dir="auto"><br></div><div dir="auto">I also mentioned that PyCascades is a single track conference<span class="gmail_default" style="font-family:arial,helvetica,sans-serif">, which is likely more relevant anyway.<br></span></div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> Eric Holscher's has a blog post [1] about a few approaches that are <br>
> better than "let anyone in the audience ask a question publicly". I <br>
> think we should support the ones that are relevant to us (I think it's <br>
> all of them are but I defer to the organizers to decide, since they'll <br>
> have to do the prep for them).<br>
<br>
Thanks for this link. The experience of other conference organizers is <br>
surely helpful. I think the moderated questions is a good idea. And I <br>
would personally prefer the low tech cards approach, over the Slack / IRC.<br>
<br>
> As another data point, PyCon US 2019 provided options for speakers to <br>
> choose from, 5 minutes prior to their talk (No Q&A, 5 minutes Q&A, <br>
> book a room after talk for Q&A). They received feedback that this is <br>
> good information to have, and that it should be communicated earlier <br>
> to the speakers (i.e. when accepted / when applying).<br>
<br>
This was another option, I was thinking about, as well. On a lighter <br>
note, PyCon India speakers have always had this option, by overrunning <br>
their time-slot, and ending up with no time for QA. :-)</blockquote><div dir="auto"><br></div><div dir="auto">The important part here is actively telling the speakers that they have this option. ;)</div><div dir="auto"> </div><div dir="auto">Best,</div><div dir="auto">Pradyun (on mobile)</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Regards,<br>
Vijay<br>
_______________________________________________<br>
<a href="https://mail.python.org/mailman/listinfo/inpycon" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/inpycon</a><br>
Mailing list guidelines :<a href="http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf" rel="noreferrer" target="_blank">http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf</a><br>
</blockquote></div></div>
</div>