Here is a very early CFP draft proposal. http://wiki.python.org/moin/PyConIndia2011/CFP This is much the same as last year. I would like feedback on, 1. Dates 2. Format 3. Topics - Should we highlight some topics or add more topics (remove some also ?) Please send this to me by end of the week (Friday) or discuss in the list. Plan to work on the CFP on the website during the week-end. I have given Mar 7 as a tentative date. However I would like the CFP to go live no later than March 10. -- --Anand
Some more questions related to the CFP.... 1. Should the CFP should also make a call for tutorial tracks or we handle them separately ? 2. Do we want to highlight certain themes for this year's conference - while not "tracks" per se, these could be some themes we highlight in the topics. Examples could be NoSQL with Python or Cloud computing using Python, the rather "hot" topics of late. 3. Talk lengths - Do we keep 30 min slots or have 45 min and 1 hour talks ? Suggestions ? --Anand On Wed, Mar 2, 2011 at 11:55 AM, Anand Balachandran Pillai < abpillai@gmail.com> wrote:
Here is a very early CFP draft proposal.
http://wiki.python.org/moin/PyConIndia2011/CFP
This is much the same as last year. I would like feedback on,
1. Dates 2. Format 3. Topics - Should we highlight some topics or add more topics (remove some also ?)
Please send this to me by end of the week (Friday) or discuss in the list. Plan to work on the CFP on the website during the week-end.
I have given Mar 7 as a tentative date. However I would like the CFP to go live no later than March 10.
-- --Anand
-- --Anand
Hello,
Some more questions related to the CFP....
1. Should the CFP should also make a call for tutorial tracks or we handle them separately ?
Let's keep them together, but state the requirements clearly for each of them. We can have two different types of talks - "talk" & "workshop". Both have different duration & material related differences.
2. Do we want to highlight certain themes for this year's conference - while not "tracks" per se, these could be some themes we highlight in the topics. Examples could be NoSQL with Python or Cloud computing using Python, the rather "hot" topics of late.
We could. As a matter of fact, we were thinking about having three tracks, "newbie", "advanced" & "theme". IMHO it's a good idea to have a general theme. As far as themes like "NoSQL with Python", don't you think that those talks will turn out to be general evangelism about the NoSQL DB and some tips about using the related client library? It's not bad per se, but can turn out to be monotonous if we have many talks along the same lines.
3. Talk lengths - Do we keep 30 min slots or have 45 min and 1 hour talks ?
I would recommend 45 mins (+/- 5 mins) with a solid 10 minutes for Q&A and a break of 5 mins between every talk. Regards, BG -- Baishampayan Ghose b.ghose at gmail.com
On Wed, Mar 02 2011, Baishampayan Ghose wrote: [...]
We could. As a matter of fact, we were thinking about having three tracks, "newbie", "advanced" & "theme". IMHO it's a good idea to have a general theme. As far as themes like "NoSQL with Python", don't you think that those talks will turn out to be general evangelism about the NoSQL DB and some tips about using the related client library? It's not bad per se, but can turn out to be monotonous if we have many talks along the same lines.
I don't think this is a good idea. Tracks should be made using a single criterion if they're to be sensible. Either we choose 'theme' as the criterion in which case, the tracks would be like "testing", "web", "core python" etc. The "level" of the talk (novice, intermediate etc.) would be something extra. Or We choose 'level' as the criterion and let the tracks become 'novice', 'intermediate', 'advanced' but with a mix of subjects. Also, I agree about staying away from tracks like "cloud" and "noSQL". Like you said, we'll get a lot of talks from n00bs who've read the man pages and it'll get boring. I heard a lot of negative feedback about the mongodb talk last year. [...] -- ~noufal http://nibrahim.net.in
All right, I will put up a revised draft with some of these ideas by Friday. Please take a look at it, if it is fine, I will work with Anand C to create the CFP on the site and get it live by March 10. Meanwhile, can someone take a look at the topic list and suggest anything to be removed or added specifically or a change in order ? --Anand On Wed, Mar 2, 2011 at 2:07 PM, Noufal Ibrahim <noufal@gmail.com> wrote:
On Wed, Mar 02 2011, Baishampayan Ghose wrote:
[...]
We could. As a matter of fact, we were thinking about having three tracks, "newbie", "advanced" & "theme". IMHO it's a good idea to have a general theme. As far as themes like "NoSQL with Python", don't you think that those talks will turn out to be general evangelism about the NoSQL DB and some tips about using the related client library? It's not bad per se, but can turn out to be monotonous if we have many talks along the same lines.
I don't think this is a good idea. Tracks should be made using a single criterion if they're to be sensible.
Either we choose 'theme' as the criterion in which case, the tracks would be like "testing", "web", "core python" etc. The "level" of the talk (novice, intermediate etc.) would be something extra.
Or
We choose 'level' as the criterion and let the tracks become 'novice', 'intermediate', 'advanced' but with a mix of subjects.
Also, I agree about staying away from tracks like "cloud" and "noSQL". Like you said, we'll get a lot of talks from n00bs who've read the man pages and it'll get boring. I heard a lot of negative feedback about the mongodb talk last year.
[...]
-- ~noufal http://nibrahim.net.in _______________________________________________ Inpycon mailing list Inpycon@python.org http://mail.python.org/mailman/listinfo/inpycon
-- --Anand
On Wed, Mar 02 2011, Anand Balachandran Pillai wrote:
Some more questions related to the CFP....
1. Should the CFP should also make a call for tutorial tracks or we handle them separately ?
I think it'd be simpler if the tutorial was a kind of talk but of a longer duration and only on a specific day. At the very least, the UI would be simpler.
2. Do we want to highlight certain themes for this year's conference - while not "tracks" per se, these could be some themes we highlight in the topics. Examples could be NoSQL with Python or Cloud computing using Python, the rather "hot" topics of late.
I don't think so. I'm sure things trends will emerge automatically.
3. Talk lengths - Do we keep 30 min slots or have 45 min and 1 hour talks ?
I think we should a single length for talks. Say 40 minutes. IT's annoying when people request a 45 minute slot to be "safe" and then have just 30 minutes of content to deliver. Pack it in that much time. Keep it short and to the point. Tutorial are different. I'm not sure if it's been discussed here but usually, they're 3 hour things with a day devoted to them. Students pay for them separately and receive printed notes etc. Is that the way we're planning to go? [...] -- ~noufal http://nibrahim.net.in
participants (3)
-
Anand Balachandran Pillai -
Baishampayan Ghose -
Noufal Ibrahim