In a message of Thu, 21 May 2009 10:03:31 BST, Jonathan Hartley writes: >Hey Laura, > >Ohno! I hope you have some nice tea and feel better soon! > >I just put together a first pass at the schedule, photographed here: >http://tartley.com/files/EPSchedule/ > >I assumed that we might have to chat on the phone while looking at it >for anyone to make any sense of it, but John and Zeth appear to have >deciphered enough to already have offered some feedback. (thanks!) > >So. We can chat today and try swapping things around to fix the things >they mentioned, and whatever else we spot. Suggestions (or even just >observed shortcomings) very welcome. > > Jonathan
This looks very good. Some suggested changes. There should be no 'web frameworks' track, or rather The notion that 'web programming' is one track, and should not be scheduled against each other is faulty -- Django talks should not be scheduled against each other, but if you are interested in Django then you are most likely uninterested in other web frameworks- So the web framework track needs to be seriously grouped by what framework it is, sort of like mono-culture farming. Alas, the whole track needs to be reordered, sorted by frameworks. The idea is to never give people a session with a varied collection of different framework talks if you can help it. ie Problems Django cannot solve should be close to Failsome Django, and Simon Willison's talk, and any other Django related things. Otherwise it is too disruptive with people hopping up and down for the only one talk in the session that they are interested in. web frameworks and jython should not be scheduled against armin's pypy talk, because armin's pypy talk talks about how jython and pypy are sharing things. if you have to schedule franks talk vs an other python implementation talk, schedule against hotpy The hotpy talks should follow one after the other. They really are one long talk with a pause in the middle. Zen of Web should be scheduled early, in case there is somebody new to web programming who shoudl see this talk first. samuele pedroni's javascript talk should not be scheduled against armin's talk either, it is ok now, but a thing to remember when you are moving hotpy around. jumping worlds with python should not be scheduled against python .net and the weather. They should follow each other in one session. they are about the same thing, and indeed the authors of both need to meet each other. Ctypes should not be scheduled vs christian tismer's talk on psyco. but they should be scheduled with ironclad, in the same session, ideally ironclad followed by ctypes. They are aimed at exactly the same audience. maybe swap out the 'jumping worlds' from alternative implementations and keep it with python .net and the weather? Luke Leighton's stuff probably needs to go together, because if you want to hear it you probably want to hear both of them, and if you do not, you want to hear neither. It's more of the web frameworky thing. Can we make Stani Michael's talk plenary? I am not sure, but I think that Python and Nuke and the Visual studio plugin should not be scheduled against each other. The iron python talks are all spread out. is it possible to group them together? .... ok, I will go back to being sick. Let me know what you think. And, being sick I may have missed the mark in making these comments. If they sound harsh, it is me being sick and insensitive, and I apologise. I think that you have done a marvellous job. Laura _______________________________________________ Europython-improve mailing list [email protected] http://mail.python.org/mailman/listinfo/europython-improve
