<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>Anand C has the sheets</span></div><div><br></div> <div style="font-size: 10pt; font-family: arial, helvetica, sans-serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Noufal Ibrahim <noufal@nibrahim.net.in><br> <b><span style="font-weight: bold;">To:</span></b> Mailing list for the PyCon India conference <inpycon@python.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, 2 October 2012 1:11 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Inpycon] Collated feedback<br> </font> </div> <br><br>Good idea. Who has the feedback sheets?<br><br>kracekumar <<a ymailto="mailto:me@kracekumar.com"
href="mailto:me@kracekumar.com">me@kracekumar.com</a>> writes:<br><br>> It would be good if we send the feedback of the respective sessions to<br>> the speaker, saying "Topic: total +1, -1, -0 represented as charts"<br>><br>>> Hi,<br>>><br>>> First, congrats to the organisers of Pycon India, for pulling it<br>>> off, given that we had a late start this year, with the venue shifting<br>>> to Bangalore and all that. And we had really nice key note speakers.<br>>> Both the presentations were good.<br>>><br>>> Thanks to Noufal for this mail. It is a nice summary of the over<br>>> all mood. I would like to add a few of my suggestions.<br>>><br>>> On Mon, Oct 1, 2012 at 1:37 PM, Noufal Ibrahim <<a ymailto="mailto:noufal@nibrahim.net.in" href="mailto:noufal@nibrahim.net.in">noufal@nibrahim.net.in</a>>
wrote:<br>>>><br>>>> - OTOH, maybe it is sensible to avoid tutorials all together. 3 days is<br>>>> harrowing for everybody and the separate registrations and stuff makes<br>>>> it quite hard.<br>>>><br>>> I would like to have tutorials(though I couldn't attend them<br>>> this year due to unavoidable reasons). This where people new to python<br>>> pick things up. But, here is what I would suggest. We should do the<br>>> CfP by around April, and announce the selected proposals by around<br>>> mid-July. We can use the intervening time to do rigorous rounds of<br>>> selection - including asking the presenter to show a non-trivial<br>>> working example of his talk(and it should not be picked from the<br>>> tool's tutorial page). This is just a
suggestion<br>>><br>>><br>>><br>>>> 5. Poor talk quality - This was by far the biggest complaint. Following<br>>>> are some suggestions.<br>>>><br>>> This was felt by a lot of people. We felt that some of the<br>>> presenters were actually disinterested. May be their organisation<br>>> asked them to give a talk ? Again, talks should not be blind<br>>> theoretical data, picked from various web sites. These are a few<br>>> things that we should take into account.<br>>><br>>> Probably, we need to ask people to upload their complete<br>>> material, including slides and code, and with more volunteers review<br>>> the content, at least a month before the event. I agree that we need a<br>>> lot more man power for this. But we will do our best.<br>>><br>>>> - One hour is too
long for a talk and gives people time to ramble. 30<br>>>> minutes of talk plus 10 or 15 minutes of questions. If it takes more<br>>>> than that, it's covering too much.<br>>>><br>>> May be like the US pycon, we can have longer sessions, in<br>>> which lengthy discussions can be organised. For eg., someone<br>>> explaining the ZTK may not be able to cover up a lot of things in a<br>>> diligent way within 1 hour.<br>>><br>>>> - CFP and selection done *much* earlier with a larger review<br>>>> committee. Perhaps with multiple meetings of members (over IRC). We'll<br>>>> have to take into consideration the bio of the presenter and get a<br>>>> little brutal with selection.<br>>>><br>>> Yes :) About April beginning, and close it by
first week of May.<br>>> After selecting the proposals, allow uploads of presentation material<br>>> till middle of June. And do further checks on that ? Will that be<br>>> possible if we have an expert panel of volunteers ?<br>>><br>>>> 6. Too tight a schedule - No sufficient gap between talk slots.<br>>>><br>>>> - We should keep 5 (or even 10) minutes of "free time" between slots and<br>>>> mercilessly enforce this.<br>>>><br>>> Yes, by the time we move out of a hall and get into the next, the<br>>> speaker has already finished the intent and purpose of the talk.<br>>><br>>> Thanks again to the organisers for making it a good event. We will do<br>>> our best to improve the event further :)<br>>><br><br>-- <br>Cordially,<br>Noufal<br><a href="http://nibrahim.net.in/"
target="_blank">http://nibrahim.net.in</a><br>_______________________________________________<br>Inpycon mailing list<br><a ymailto="mailto:Inpycon@python.org" href="mailto:Inpycon@python.org">Inpycon@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/inpycon" target="_blank">http://mail.python.org/mailman/listinfo/inpycon</a><br><br><br> </div> </div> </div></body></html>