In article <[EMAIL PROTECTED]>, Paul Rubin <http://[EMAIL PROTECTED]> wrote: >Stephan Deibel <[EMAIL PROTECTED]> writes: >> >> I have to admit, I'll keep coming to PyCon even if all the talks suck >> abysmally as long as there's good hallway time, open space, BoFs, and >> sprints. ;-) > >OK, so why not get rid of all the talks and other stuff, and just have >a basically structureless conference, beyond scheduling some open >meetings on various topics? That would be a lot less expensive and a >lot more interesting.
Don't think we haven't discussed this. The problem is that some kinds of talks demand a lot of preparation (and therefore need to be scheduled in advance), plus plenty of people like some structure. PyCon -- like most organized human endeavors -- is in many ways about the art of compromise, trying to figure out how to satisfy as many people as possible and disappointing as few as possible, keeping in mind that it is almost impossible to completely satisfy anyone and most people will have some disappointment (if only because two talks that are ABSOLUTELY CRITICAL to them are cross-scheduled). -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "It is easier to optimize correct code than to correct optimized code." --Bill Harlan -- http://mail.python.org/mailman/listinfo/python-list
