<br><br><div class="gmail_quote">On Tue, Sep 20, 2011 at 11:57 AM, Noufal Ibrahim <span dir="ltr"><<a href="mailto:noufal@gmail.com">noufal@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Let me try to consolidate all of this (and personal feedback I've<br>
received) into a single document and put it up on the wiki. I'll censor<br>
sensitive information before doing this.<br>
<br>
This should give us a list of gotchas to avoid. I'll get it up by the<br>
coming Monday. This week is going to be really busy.<br>
<div><div></div><div class="h5"><br>
Anand Balachandran Pillai <<a href="mailto:abpillai@gmail.com">abpillai@gmail.com</a>> writes:<br>
<br>
> On Tue, Sep 20, 2011 at 11:17 AM, gaurav luthra <<a href="mailto:gauravluthra06@gmail.com">gauravluthra06@gmail.com</a>>wrote:<br>
><br>
>><br>
>> I am amused nobody pointed out the lack of sufficient power outlets.<br>
><br>
><br>
> A quick reply - We were aware of this ourselves. Frankly we didn't plan<br>
> properly for this and only bought the power strips (16 of them) the last<br>
> thing<br>
> on the previous day of the conference.<br>
><br>
> Ideally we should have stocked up a number of them (at least 30) and<br>
> serially connect them to provide power all around. I think it might have<br>
> been<br>
> felt more acutely in the auditorium. I tried my best to link a couple of<br>
> them<br>
> serially at every outlet, but we didn't have enough to cover all seats.<br>
><br>
> Point taken. We need to stock up on power strips well before<br>
> the conference.<br>
><br>
><br>
>> Although the talks were quite interesting, we could try and include a flow<br>
>> of tracks that start with some introductory overview of the language and<br>
>> progresses through some coding sprints so that newcomers understand better<br>
>> the content that they are being taught. For example, a hands-on session on<br>
>> redis in the evening would have helped. Such workshops spread over three<br>
>> days would be more helpful for some segments of the audience than sitting in<br>
>> talks they can't comprehend and worse they can't try it out then and there.<br>
>> I also suggest the speakers upload the details of the packages being used in<br>
>> the talks in advance so that attendees have them installed. Due to this I<br>
>> missed on some interesting things during the image processing talk by nitin<br>
>> in Track 3 on Day 1. And the absence of wi-fi didn't help either.<br>
>><br>
><br>
> It was perhaps I who first suggested a 1 hr duration of each talk.<br>
> This was from my (bad) experience from last year where I tried to<br>
> pack a large number of talks with barely breathing room between<br>
> each. So this year the thinking was to provide 45 min for the speaker<br>
> to complete his talk and a luxury of 15 mins to do everything else -<br>
> Q&A, audience interaction, corridor discussions, breaks etc. So not<br>
> surprising that for a few talks where the author either paced himself<br>
> too fast or didn't have enough content, people could have felt that<br>
> the entire session was on the ligher side in terms of content. However<br>
> content is only part of the experience, and we wanted to give room<br>
> to everyone to engage each other and have an all around experience.<br>
> I think it worked.<br>
><br>
><br>
>><br>
>> My 0.02$.<br>
>> --<br>
>> ~GAURAV LUTHRA~<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Inpycon mailing list<br>
>> <a 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>
<br>
--<br>
</div></div><div class="im">~noufal<br>
<a href="http://nibrahim.net.in" target="_blank">http://nibrahim.net.in</a><br>
<br>
</div>I'm proud of my humility.<br>
<div><div></div><div class="h5">_______________________________________________<br>
Inpycon mailing list<br>
<a 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>
</div></div></blockquote></div><br>From the experience point of view, I agree that the conference had something for everyone, was thoroughly enjoyable and was one of the best I've attended. Kudos to the organising team. When you create the wiki consider preparing a draft for organising any conference. A sort of "HowTo organise a successful conference in 7 days." ;)<br clear="all">
<br>-- <br>~GAURAV LUTHRA~<br><br>