[Inpycon] Points to ponder

[Dhruv Baldawa]

Someone had created it last year. I think Anand C.
https://github.com/pythonindia/pyconindia-handbook

--
Dhruv Baldawa
(http://www.dhruvb.com)


On Tue, Sep 3, 2013 at 10:11 AM, Bibhas <me at bibhas.in> wrote:

>
>
> konark modi <modi.konark at gmail.com> wrote:
> >Was an amazing conference, I have had one of the best experiences of
> >being
> >part as a volunteer and work with a great and super awesome team which
> >I
> >would cherish for long.
> >
> >Was looking forward for some insights from the organizing team on :
> >
> >1. Which are the areas of bottle neck during the initial planning
> >because
> >of which kind of get delayed in starting , if we could help reduce
> >those
> >bottle necks, involve more people probably we can start with lot of
> >things
> >early.
> >
> >2. Kiran had given a useful suggestion on maintain a hand-book via
> >PyCon
> >git repo, to push all check-lists. (I'll be doing that for all the
> >templates used for volunteering purposes.)
> >
>
> We thought of doing it last year, called it PyCon handbook but it got lost
> in discussions. I think we should start as soon as possible with this,
> before our memories betray us.
>
> >3. If we start early we can break the tasks into chunks and let focused
> >groups work on them, otherwise we end up having same people work on lot
> >of
> >different things, which makes it tough on them.
> >
> >Will update as and when have more ideas.
> >
> >Regards
> >Konark
> >
> >
> >On Mon, Sep 2, 2013 at 12:12 PM, Noufal Ibrahim
> ><noufal at nibrahim.net.in>wrote:
> >
> >>
> >> First of all, Congratulations to everyone involved in running this.
> >The
> >> conference was a definite improvement over the past few years.
> >>
> >> Here are some points I have that we should consider.
> >>
> >> 1. We need more "heads" that decide all details of each activity.
> >Just
> >>    like Vishal headed the a/v thing. I'm saying this because for
> >things
> >>    like open spaces, there were issues like opening up the one on
> >top, A/C
> >>    in audi 3 etc. These are decisions that Anand and Vijay shouldn't
> >>    have to bother about. There should be one guy in charge of this
> >and
> >>    that's that. It will make management much more smooth.
> >>
> >> 2. We have to keep a note of FAQs people ask. I'm emphasising the "F"
> >in
> >>    FAQ. One example. Lots of people got confused about the workshop
> >>    tickets and having to pay separately for them. We should really
> >call
> >>    them "Python workshops before PyCon India" or something similar
> >and have
> >>    maybe even have a separate doattend page for them. Anything to
> >make them
> >>    distinct from the main conference registrations.
> >>
> >> 3. We need to make the conference more woman friendly. It was better
> >>    than last time but female participants especially from outside
> >>    Bangalore asked about things like accomodation, travel etc. These
> >are
> >>    important and we need to have something in place for them. I'd
> >very
> >>    much like organisations like pyladies to take a more active role
> >in
> >>    matters like this.
> >>
> >> 4. We need to have way more time for the CFP and for talk
> >>    selection. This time was much better and I think we hit a decent
> >>    method. Now, we just need to scale it up.
> >>
> >> 5. Let's open up a small lightning talk registration online before
> >the
> >>    event starts? Might get more interesting people.
> >>
> >> 6. More work on panels.
> >>
> >> Thanks.
> >>
> >> --
> >> Cordially,
> >> Noufal
> >> http://nibrahim.net.in
> >> _______________________________________________
> >> Inpycon mailing list
> >> Inpycon at python.org
> >> http://mail.python.org/mailman/listinfo/inpycon
> >>
> >
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >Inpycon mailing list
> >Inpycon at python.org
> >http://mail.python.org/mailman/listinfo/inpycon
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> Inpycon mailing list
> Inpycon at python.org
> http://mail.python.org/mailman/listinfo/inpycon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20130903/ca181c51/attachment.html>