Hi folks, Here is the proposal as requested, https://docs.google.com/document/d/1KsDeIx13Vm6rKfI1AYsxhZ0POK5_XlENO-43erSC... Just for convenience I am also pasting the content of the document below for convenience. Hi folks, on behalf of the PyDelhi team we hereby propose the next yearly PyCon India 2016 should be held in delhi. What are the advantages of holding an event in Delhi/NCR? - Lazy pythonistas from Northern India get a venue closer to home. - Delhi is Capital city with world class infrastructure, a city and such should theoretically attract more people from universities like DU, IP, JP, MITS, JMU, IIT, Companies like MakeMyTrip, Snapdeal,Paytm, HT Media. - Strong and active team in NCR, this allows Pythonistas from NCR to be a host. - It gives the Bangalore community some rest and a reason to travel. What We have done so far:: We have divided ourselves into a set of teams with different responsibilities for different tasks. Following tasks have been assigned so far:: Administration: Handle finance, legal issues, outline a code of conduct, Dispute resolution, Website management. Marketing: Social Media, Physical Media, Social profiles , Posting , printing posters , design , reply to comments and mails. Sponsor affairs Speaker affairs: Setting up Call for proposals, Taking votes, Managing web pages for displaying list of proposals and taking votes, Contacting and checking with speakers of their availability, Keeping in contact with the speakers, trying to help solve any issues. Venue research/management: Manage Equipment: Video, Internet, Projector, Mics, Recording Equipment, Location, food, posters, Helpdesk , Welcome kit , Name tags , tissue paper, Soaps, Stationery... We propose the following timeline to be followed:: 1. Nov End -- Finalize the Announce location Currently we are focusing on SiriFort and finalizing it as a venue. We will be needing final dates for the event before booking the Venue. - Hire firm for website, logo Design for Pycon India 2016. Question: Can we use existing firm used for 2015? - 2. Dec End -- Announce date of event, publish landing page. Finalize sponsorship prospectus, start contacting sponsors. 3. Jan end -- CFP (talks and workshop) setup, Poster Design, Tshirt design 4. Feb Start -- Send out list of possible keynote speakers and ask for input from community. 5. Feb end -- Finalize Food Vendor, Online Ticket Portal. 6. March end -- Finalize wifi, sound management, video management 7. May end -- Close CFP for talks, workshops. Start Voting procedure. Finalize Keynote speakers. 8. June end -- Open ticket sales, early bird tickets for Talks, keynote. 9. July end -- finalize talks and workshops, open tickets for Workshops. invite proposals for hackathon/open sessions/code sprints… 10. August -- Start getting in touch with vendors for accessories (Posters, goodies, pens, Lan wires, extra projectors, wifi routers, extension cables, recording audio, video equipment... ), for venues. 11.September -- Finalize everything that is left, volunteer meets, official permissions, catering… Here is the proposed format for the conference: - 3 tracks(Separate halls) - 1 keynote for each conference day - proposed schedule: - 08:00AM Breakfast - 09:00AM - 9:15AM Introductions/Welcome - 09:20AM - 10:10AM Keynote - 10:10AM - 10:50AM Break (Expo Hall 210) Hall 1 Hall 2 Hall 3 10:50AM - 11:30AM Talk Ditto Ditto 11:30AM - 12:10PM Talk Ditto Ditto 12:10PM - 12:50PM Talk Ditto Ditto 12:50PM - 01:40PM Lunch Ditto Ditto 01:40PM - 02:20PM Talk Ditto Ditto 02:20PM - 03:00PM Talk Ditto Ditto 03:00PM - 03:40PM Talk Ditto Ditto 03:40PM - 04:30PM Break Ditto Ditto 04:30PM - 05:10PM Panel Discussion 05:10PM - 05:50PM Lightning talks 05:50PM Conclusion/break networking Tea would be served in breaks Please don’t hesitate to suggest alternatives/better options or add to the timline Apart from the timeline we have started a list of documents like drafts of - sponsorship prospectus https://docs.google.com/document/d/1fY52l1V92IM7fhC_Q2yiBEVvMpWuvRWKSRoeB0vM..., - List of possible sponsors https://docs.google.com/spreadsheets/d/1bE5yG_Z1t0zpnMt-095nweK3fnM4aq1jSveI... On behalf of PyDelhi, Kind Regards
Wow! Excellent work. I'm very much looking forward to visiting Delhi for this. Just one small comment (and I've put this on the google doc too). If a talk ends at 11:30, please start the next one no earlier than 11:40. The crowd will need time to shift between halls and to stretch. Also, it gives the organisers a bit of slack to ready the stage for the next talk. This will, of course, reduce the total time but I think it's better to do it this way rather than to pack it tight and then worry when the schedule slips. -- Cordially, Noufal http://nibrahim.net.in
Hi, --- On Wed, Nov 18, 2015 at 3:36 PM, qua non <akshayaurora@gmail.com> wrote: | 05:10PM - 05:50PM Lightning talks \-- Lightning talks can be scheduled immediately after lunch. It is a welcome change after the morning talks. Late in the evening, people want to wind up quickly and go home after a long day. SK -- Shakthi Kannan http://www.shakthimaan.com
@noufal the doc has been updated to include a 10 minute gap as you suggested, Hall 1 Hall 2 Hall 3 10:50AM - 11:30AM Talk Ditto Ditto 11:40AM - 12:20PM Talk Ditto Ditto 12:30PM - 1:10PM Talk Ditto Ditto 1:10PM - 01:40PM Lunch Ditto Ditto 01:40PM - 02:20PM Talk Ditto Ditto 02:30PM - 03:10PM Talk Ditto Ditto 03:20PM - 04:00PM Talk Ditto Ditto 04:10PM - 04:40PM Break Ditto Ditto 04:40PM - 05:30PM Panel Discussion 05:10PM - 05:50PM Lightning talks 05:50PM Conclusion/break networking For putting Lightning talks before panel discussions, there are pros and cons of both. We should look at the feedback gotten from last year PyconIndia and base a decision on that. @vijay, krace, was there any feedback related to this? On Wed, Nov 18, 2015 at 7:20 PM, Shakthi Kannan <shakthimaan@gmail.com> wrote:
Hi,
--- On Wed, Nov 18, 2015 at 3:36 PM, qua non <akshayaurora@gmail.com> wrote: | 05:10PM - 05:50PM Lightning talks \--
Lightning talks can be scheduled immediately after lunch. It is a welcome change after the morning talks.
Late in the evening, people want to wind up quickly and go home after a long day.
SK
-- Shakthi Kannan http://www.shakthimaan.com _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
[...]
For putting Lightning talks before panel discussions, there are pros and cons of both. We should look at the feedback gotten from last year PyconIndia and base a decision on that. @vijay, krace, was there any feedback related to this?
We haven't received any feedback about timing this year and based on 2014 feedback we moved to afternoon. -- Regards Kracekumar Ramaraj http://kracekumar.com
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody. On 18 November 2015 at 23:30, Kracekumar Ramaraj <me@kracekumar.com> wrote:
[...]
For putting Lightning talks before panel discussions, there are pros and cons of both. We should look at the feedback gotten from last year PyconIndia and base a decision on that. @vijay, krace, was there any feedback related to this?
We haven't received any feedback about timing this year and based on 2014 feedback we moved to afternoon.
-- Regards Kracekumar Ramaraj http://kracekumar.com
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Harsh Sent from a GNU/Linux
On 19 Nov 2015 00:14, "Harsh Gupta" <gupta.harsh96@gmail.com> wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
+1
On 18 November 2015 at 23:30, Kracekumar Ramaraj <me@kracekumar.com>
wrote:
[...]
For putting Lightning talks before panel discussions, there are pros
and
cons of both. We should look at the feedback gotten from last year PyconIndia and base a decision on that. @vijay, krace, was there any feedback related to this?
We haven't received any feedback about timing this year and based on 2014 feedback we moved to afternoon.
-- Regards Kracekumar Ramaraj http://kracekumar.com
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Harsh Sent from a GNU/Linux _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
On Thu, Nov 19 2015, Harsh Gupta wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
[...] The suggestion is sensible. +1 from me. Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better. -- Cordially, Noufal http://nibrahim.net.in
hi, 20 min talks is a good suggestion +1 from me regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
On Thu, Nov 19 2015, Harsh Gupta wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
[...]
The suggestion is sensible. +1 from me.
Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better.
-- Cordially, Noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
+1 from me too to shorter talks. Shorter talks means better talks, to the point material, better concentration of the listener. *Best Regards* *Pulkit Pahwa* *8130425877* On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
hi,
20 min talks is a good suggestion +1 from me
regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
On Thu, Nov 19 2015, Harsh Gupta wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
[...]
The suggestion is sensible. +1 from me.
Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better.
-- Cordially, Noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
Here is updated schedule based on 20 minute talks. Doc updated as well. - 08:00AM Breakfast - 09:00AM - 9:15AM Introductions/Welcome - 09:20AM - 10:10AM Keynote - 10:10AM - 10:50AM Break (Expo Hall 210) Hall 1 Hall 2 Hall 3 10:50AM - 11:10AM Talk Ditto Ditto 11:20AM - 11:40PM Talk Ditto Ditto 11:50PM - 12:10PM Talk Ditto Ditto 12:20PM - 012:50PM Talk Ditto Ditto 01:00PM - 02:00PM Lunch Ditto Ditto 02:00PM - 02:20PM Talk Ditto Ditto 02:30PM - 02:50PM Talk Ditto Ditto 03:00PM - 03:20PM Talk Ditto Ditto 03:20PM - 03:50PM High Tea break 03:50PM - 04:30PM Panel Discussion 04:30PM - 05:30PM Lightning talks 05:30PM Conclusion/break networking On Thu, Nov 19, 2015 at 10:15 AM, PULKIT PAHWA <pulkitpahwa11@gmail.com> wrote:
+1 from me too to shorter talks.
Shorter talks means better talks, to the point material, better concentration of the listener.
*Best Regards* *Pulkit Pahwa* *8130425877*
On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
hi,
20 min talks is a good suggestion +1 from me
regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
On Thu, Nov 19 2015, Harsh Gupta wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
[...]
The suggestion is sensible. +1 from me.
Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better.
-- Cordially, Noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
+1 for Dehli. Thanks PyDehli team for well planned proposal so whole community can review. I think it too early to decide on schedule , we should let selection committee take those call as they are one who will work closely with each proposer/submitter. One more point: We tried to have 3 keynote speaker this year but due to budget constraint we were not able to take decision on time. I would request you guys to see if we can fit 3 keynote speaker for 2016. On Fri, Nov 20, 2015 at 12:14 AM, qua non <akshayaurora@gmail.com> wrote:
Here is updated schedule based on 20 minute talks. Doc updated as well.
-
08:00AM Breakfast -
09:00AM - 9:15AM Introductions/Welcome -
09:20AM - 10:10AM Keynote -
10:10AM - 10:50AM Break (Expo Hall 210)
Hall 1
Hall 2
Hall 3
10:50AM - 11:10AM Talk
Ditto
Ditto
11:20AM - 11:40PM Talk
Ditto
Ditto
11:50PM - 12:10PM Talk
Ditto
Ditto
12:20PM - 012:50PM Talk
Ditto
Ditto
01:00PM - 02:00PM Lunch
Ditto
Ditto
02:00PM - 02:20PM Talk
Ditto
Ditto
02:30PM - 02:50PM Talk
Ditto
Ditto
03:00PM - 03:20PM Talk
Ditto
Ditto
03:20PM - 03:50PM High Tea break
03:50PM - 04:30PM Panel Discussion
04:30PM - 05:30PM Lightning talks
05:30PM Conclusion/break networking
On Thu, Nov 19, 2015 at 10:15 AM, PULKIT PAHWA <pulkitpahwa11@gmail.com> wrote:
+1 from me too to shorter talks.
Shorter talks means better talks, to the point material, better concentration of the listener.
*Best Regards* *Pulkit Pahwa* *8130425877*
On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
hi,
20 min talks is a good suggestion +1 from me
regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
On Thu, Nov 19 2015, Harsh Gupta wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
[...]
The suggestion is sensible. +1 from me.
Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better.
-- Cordially, Noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Thanks, Vijay
When we say shorter talks of 20 mins. Are we including the time for questions and setting up as well. I think 20 minutes of speaking time is fine but we should include some 10 minutes for questions, configuration etc ... Thanks Amit On Fri, Nov 20, 2015 at 8:21 AM, vijay kumar <vnbang2003@gmail.com> wrote:
+1 for Dehli. Thanks PyDehli team for well planned proposal so whole community can review. I think it too early to decide on schedule , we should let selection committee take those call as they are one who will work closely with each proposer/submitter. One more point: We tried to have 3 keynote speaker this year but due to budget constraint we were not able to take decision on time. I would request you guys to see if we can fit 3 keynote speaker for 2016.
On Fri, Nov 20, 2015 at 12:14 AM, qua non <akshayaurora@gmail.com> wrote:
Here is updated schedule based on 20 minute talks. Doc updated as well.
-
08:00AM Breakfast -
09:00AM - 9:15AM Introductions/Welcome -
09:20AM - 10:10AM Keynote -
10:10AM - 10:50AM Break (Expo Hall 210)
Hall 1
Hall 2
Hall 3
10:50AM - 11:10AM Talk
Ditto
Ditto
11:20AM - 11:40PM Talk
Ditto
Ditto
11:50PM - 12:10PM Talk
Ditto
Ditto
12:20PM - 012:50PM Talk
Ditto
Ditto
01:00PM - 02:00PM Lunch
Ditto
Ditto
02:00PM - 02:20PM Talk
Ditto
Ditto
02:30PM - 02:50PM Talk
Ditto
Ditto
03:00PM - 03:20PM Talk
Ditto
Ditto
03:20PM - 03:50PM High Tea break
03:50PM - 04:30PM Panel Discussion
04:30PM - 05:30PM Lightning talks
05:30PM Conclusion/break networking
On Thu, Nov 19, 2015 at 10:15 AM, PULKIT PAHWA <pulkitpahwa11@gmail.com> wrote:
+1 from me too to shorter talks.
Shorter talks means better talks, to the point material, better concentration of the listener.
*Best Regards* *Pulkit Pahwa* *8130425877*
On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
hi,
20 min talks is a good suggestion +1 from me
regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
On Thu, Nov 19 2015, Harsh Gupta wrote:
I suggest reducing the duration of the talks. Most of the talks at PyCon were there to introduces a new tool or technique and 40 minutes is too long for that. More interested people can always look up details on the internet or talk to the speaker personally. I was at SciPy, Austin this summer. Except for the keynote speeches all the talks at SciPy are of 20 minutes and it works pretty well for them. Shorter talks will also allow more people to talk and I think this will be good for everybody.
[...]
The suggestion is sensible. +1 from me.
Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better.
-- Cordially, Noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Thanks, Vijay
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- A-M-I-T S|S
@amit the schedule outlined above is talks 20 minutes Plus 10 minutes of time between talks. On Fri, Nov 20, 2015 at 1:51 PM, Amit Sethi <amit.pureenergy@gmail.com> wrote:
When we say shorter talks of 20 mins. Are we including the time for questions and setting up as well. I think 20 minutes of speaking time is fine but we should include some 10 minutes for questions, configuration etc ...
Thanks Amit
On Fri, Nov 20, 2015 at 8:21 AM, vijay kumar <vnbang2003@gmail.com> wrote:
+1 for Dehli. Thanks PyDehli team for well planned proposal so whole community can review. I think it too early to decide on schedule , we should let selection committee take those call as they are one who will work closely with each proposer/submitter. One more point: We tried to have 3 keynote speaker this year but due to budget constraint we were not able to take decision on time. I would request you guys to see if we can fit 3 keynote speaker for 2016.
On Fri, Nov 20, 2015 at 12:14 AM, qua non <akshayaurora@gmail.com> wrote:
Here is updated schedule based on 20 minute talks. Doc updated as well.
-
08:00AM Breakfast -
09:00AM - 9:15AM Introductions/Welcome -
09:20AM - 10:10AM Keynote -
10:10AM - 10:50AM Break (Expo Hall 210)
Hall 1
Hall 2
Hall 3
10:50AM - 11:10AM Talk
Ditto
Ditto
11:20AM - 11:40PM Talk
Ditto
Ditto
11:50PM - 12:10PM Talk
Ditto
Ditto
12:20PM - 012:50PM Talk
Ditto
Ditto
01:00PM - 02:00PM Lunch
Ditto
Ditto
02:00PM - 02:20PM Talk
Ditto
Ditto
02:30PM - 02:50PM Talk
Ditto
Ditto
03:00PM - 03:20PM Talk
Ditto
Ditto
03:20PM - 03:50PM High Tea break
03:50PM - 04:30PM Panel Discussion
04:30PM - 05:30PM Lightning talks
05:30PM Conclusion/break networking
On Thu, Nov 19, 2015 at 10:15 AM, PULKIT PAHWA <pulkitpahwa11@gmail.com> wrote:
+1 from me too to shorter talks.
Shorter talks means better talks, to the point material, better concentration of the listener.
*Best Regards* *Pulkit Pahwa* *8130425877*
On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
hi,
20 min talks is a good suggestion +1 from me
regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
On Thu, Nov 19 2015, Harsh Gupta wrote:
> I suggest reducing the duration of the talks. Most of the talks at > PyCon were there to introduces a new tool or technique and 40 minutes > is too long for that. More interested people can always look up > details on the internet or talk to the speaker personally. I was at > SciPy, Austin this summer. Except for the keynote speeches all the > talks at SciPy are of 20 minutes and it works pretty well for them. > Shorter talks will also allow more people to talk and I think this > will be good for everybody.
[...]
The suggestion is sensible. +1 from me.
Also, in general, I'm in support of experimenting with things like schedules, talks, tracks etc. Things might go south but if we stick to "the way things always were", we'll never get better.
-- Cordially, Noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Thanks, Vijay
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- A-M-I-T S|S
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
It looks like we forgot to share the doc for venue research till now, here is the link to the doc. https://docs.google.com/spreadsheets/d/1atc1XXbl-l-qE4rWO6fzxt_jElJNVcIOJzB79c416D4/edit#gid=0&vpid=A1 Shows the list of possible even use and their details https://docs.google.com/spreadsheets/d/1atc1XXbl-l-qE4rWO6fzxt_jElJNVcIOJzB79c416D4/edit#gid=0&vpid=A1 On Tue, Nov 24, 2015 at 5:41 PM, qua non <akshayaurora@gmail.com> wrote:
@amit the schedule outlined above is talks 20 minutes Plus 10 minutes of time between talks.
On Fri, Nov 20, 2015 at 1:51 PM, Amit Sethi <amit.pureenergy@gmail.com> wrote:
When we say shorter talks of 20 mins. Are we including the time for questions and setting up as well. I think 20 minutes of speaking time is fine but we should include some 10 minutes for questions, configuration etc ...
Thanks Amit
On Fri, Nov 20, 2015 at 8:21 AM, vijay kumar <vnbang2003@gmail.com> wrote:
+1 for Dehli. Thanks PyDehli team for well planned proposal so whole community can review. I think it too early to decide on schedule , we should let selection committee take those call as they are one who will work closely with each proposer/submitter. One more point: We tried to have 3 keynote speaker this year but due to budget constraint we were not able to take decision on time. I would request you guys to see if we can fit 3 keynote speaker for 2016.
On Fri, Nov 20, 2015 at 12:14 AM, qua non <akshayaurora@gmail.com> wrote:
Here is updated schedule based on 20 minute talks. Doc updated as well.
-
08:00AM Breakfast -
09:00AM - 9:15AM Introductions/Welcome -
09:20AM - 10:10AM Keynote -
10:10AM - 10:50AM Break (Expo Hall 210)
Hall 1
Hall 2
Hall 3
10:50AM - 11:10AM Talk
Ditto
Ditto
11:20AM - 11:40PM Talk
Ditto
Ditto
11:50PM - 12:10PM Talk
Ditto
Ditto
12:20PM - 012:50PM Talk
Ditto
Ditto
01:00PM - 02:00PM Lunch
Ditto
Ditto
02:00PM - 02:20PM Talk
Ditto
Ditto
02:30PM - 02:50PM Talk
Ditto
Ditto
03:00PM - 03:20PM Talk
Ditto
Ditto
03:20PM - 03:50PM High Tea break
03:50PM - 04:30PM Panel Discussion
04:30PM - 05:30PM Lightning talks
05:30PM Conclusion/break networking
On Thu, Nov 19, 2015 at 10:15 AM, PULKIT PAHWA <pulkitpahwa11@gmail.com
wrote:
+1 from me too to shorter talks.
Shorter talks means better talks, to the point material, better concentration of the listener.
*Best Regards* *Pulkit Pahwa* *8130425877*
On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
hi,
20 min talks is a good suggestion +1 from me
regards mahanthesh hv On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> wrote:
> On Thu, Nov 19 2015, Harsh Gupta wrote: > > > I suggest reducing the duration of the talks. Most of the talks at > > PyCon were there to introduces a new tool or technique and 40 > minutes > > is too long for that. More interested people can always look up > > details on the internet or talk to the speaker personally. I was at > > SciPy, Austin this summer. Except for the keynote speeches all the > > talks at SciPy are of 20 minutes and it works pretty well for them. > > Shorter talks will also allow more people to talk and I think this > > will be good for everybody. > > [...] > > The suggestion is sensible. +1 from me. > > Also, in general, I'm in support of experimenting with things like > schedules, talks, tracks etc. Things might go south but if we stick > to > "the way things always were", we'll never get better. > > > -- > Cordially, > Noufal > http://nibrahim.net.in > _______________________________________________ > Inpycon mailing list > Inpycon@python.org > https://mail.python.org/mailman/listinfo/inpycon >
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Thanks, Vijay
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- A-M-I-T S|S
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
On Tue, Nov 24, 2015 at 6:16 PM, qua non <akshayaurora@gmail.com> wrote:
It looks like we forgot to share the doc for venue research till now, here is the link to the doc.
Shows the list of possible even use and their details https://docs.google.com/spreadsheets/d/1atc1XXbl-l-qE4rWO6fzxt_jElJNVcIOJzB79c416D4/edit#gid=0&vpid=A1
Akshay, could you add a row at the bottom of the spreadsheet that mentions the total venue related expenditure for each venue? (for easy readability and comparison) Thanks!
On Tue, Nov 24, 2015 at 5:41 PM, qua non <akshayaurora@gmail.com> wrote:
@amit the schedule outlined above is talks 20 minutes Plus 10 minutes of time between talks.
On Fri, Nov 20, 2015 at 1:51 PM, Amit Sethi <amit.pureenergy@gmail.com> wrote:
When we say shorter talks of 20 mins. Are we including the time for questions and setting up as well. I think 20 minutes of speaking time is fine but we should include some 10 minutes for questions, configuration etc ...
Thanks Amit
On Fri, Nov 20, 2015 at 8:21 AM, vijay kumar <vnbang2003@gmail.com> wrote:
+1 for Dehli. Thanks PyDehli team for well planned proposal so whole community can review. I think it too early to decide on schedule , we should let selection committee take those call as they are one who will work closely with each proposer/submitter. One more point: We tried to have 3 keynote speaker this year but due to budget constraint we were not able to take decision on time. I would request you guys to see if we can fit 3 keynote speaker for 2016.
On Fri, Nov 20, 2015 at 12:14 AM, qua non <akshayaurora@gmail.com> wrote:
Here is updated schedule based on 20 minute talks. Doc updated as well.
-
08:00AM Breakfast -
09:00AM - 9:15AM Introductions/Welcome -
09:20AM - 10:10AM Keynote -
10:10AM - 10:50AM Break (Expo Hall 210)
Hall 1
Hall 2
Hall 3
10:50AM - 11:10AM Talk
Ditto
Ditto
11:20AM - 11:40PM Talk
Ditto
Ditto
11:50PM - 12:10PM Talk
Ditto
Ditto
12:20PM - 012:50PM Talk
Ditto
Ditto
01:00PM - 02:00PM Lunch
Ditto
Ditto
02:00PM - 02:20PM Talk
Ditto
Ditto
02:30PM - 02:50PM Talk
Ditto
Ditto
03:00PM - 03:20PM Talk
Ditto
Ditto
03:20PM - 03:50PM High Tea break
03:50PM - 04:30PM Panel Discussion
04:30PM - 05:30PM Lightning talks
05:30PM Conclusion/break networking
On Thu, Nov 19, 2015 at 10:15 AM, PULKIT PAHWA < pulkitpahwa11@gmail.com> wrote:
+1 from me too to shorter talks.
Shorter talks means better talks, to the point material, better concentration of the listener.
*Best Regards* *Pulkit Pahwa* *8130425877*
On Thu, Nov 19, 2015 at 8:49 AM, mahanthesh hv <mantheshv@gmail.com> wrote:
> hi, > > 20 min talks is a good suggestion +1 from me > > regards > mahanthesh hv > On Nov 19, 2015 8:40 AM, "Noufal Ibrahim KV" <noufal@nibrahim.net.in> > wrote: > >> On Thu, Nov 19 2015, Harsh Gupta wrote: >> >> > I suggest reducing the duration of the talks. Most of the talks at >> > PyCon were there to introduces a new tool or technique and 40 >> minutes >> > is too long for that. More interested people can always look up >> > details on the internet or talk to the speaker personally. I was >> at >> > SciPy, Austin this summer. Except for the keynote speeches all the >> > talks at SciPy are of 20 minutes and it works pretty well for >> them. >> > Shorter talks will also allow more people to talk and I think this >> > will be good for everybody. >> >> [...] >> >> The suggestion is sensible. +1 from me. >> >> Also, in general, I'm in support of experimenting with things like >> schedules, talks, tracks etc. Things might go south but if we stick >> to >> "the way things always were", we'll never get better. >> >> >> -- >> Cordially, >> Noufal >> http://nibrahim.net.in >> _______________________________________________ >> Inpycon mailing list >> Inpycon@python.org >> https://mail.python.org/mailman/listinfo/inpycon >> > > _______________________________________________ > Inpycon mailing list > Inpycon@python.org > https://mail.python.org/mailman/listinfo/inpycon > >
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- Thanks, Vijay
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- A-M-I-T S|S
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
_______________________________________________ Inpycon mailing list Inpycon@python.org https://mail.python.org/mailman/listinfo/inpycon
-- JD
participants (10)
-
Amit Sethi -
Harsh Gupta -
Jaidev Deshpande -
Kracekumar Ramaraj -
mahanthesh hv -
Noufal Ibrahim KV -
PULKIT PAHWA -
qua non -
Shakthi Kannan -
vijay kumar