Text of wiki.python.org › python › conferences › pycon › PyCon2007 › Feedback › Comments.html as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PyCon 2007 / Feedback / Comments - Python Wiki

Python Wiki Python Wiki / Python Wiki / Conferences / PyCon / PyCon 2007 / Feedback / PyCon 2007 / Feedback / Comments View as Markdown PyCon 2007 / Feedback / Comments ¶ Legacy Wiki Page This page was migrated from the old MoinMoin-based wiki. Information may be outdated or no longer applicable. For current documentation, see python.org . Other comments ¶ How can we improve PyCon next year? ¶ Have lightning talk speakers sign up for lightning talks in advance, and have people vote on the lightning talks on the first day or so, so it gets a little more condensed?

OTOH that kinda defeats the purpose of lightning talks. Just an idea. Having the Open Space schedule available online would have been very convenient. Although I realize that budget is a concern, if possible, it would be nice to have something quick and easy available at breakfast time both for convenience and to foster socializing in the mornings before the Keynotes. Serve breakfast. Meals in some sort of hall with better table arrangement for eating and socializing during meals.

More visible vendor tables. Coffee available 1st thing in the morning!!!! Have speakers show something other than slides. Far too many presentations consisted of nothing but slides. At the moment, I’m too ecstatic about this one to have any criticism in mind. I’ll get back on this one. more wireless bandwidth, more vendors, See if you can get Guido to dress up in the BDFL costume from Monty Python 😉 Make sure hotel guests are not relocated.

Better snacks. More tutorial days/options. Free WiFi in hotel room Perhaps better sound? Also, I got *VERY* annoyed at people constantly coming in late to every single talk. It really disrupted things. It was very aggravating and very rude. Wireless network – was very difficult on Friday, but got better on Saturday and Sunday (thankfully). I still think soup + 600 geeks with laptops is a bad idea. I don’t like having Guido’s keynote during lunch; this is really the one unmissable talk of the entire conference, and it simply takes too long to get people out of the rooms and into line, through the line, and back into the ballroom in time for his talk.

Further, his keynote usually expands to either fill or slightly surpass the time available, so starting a little late because of the lunch logistics means that the schedule of other presentations later in the day is impacted. (Although the session chairs did a VERY good job of getting everything back on track quickly, many kudos to them.) Make sure the hotel contract doesn’t allow the hotel to shuffle people to other hotels after they’ve already had reservations okayed by the main venue.

Were the chairs and tables designed to punish my back for sins of a past life? I developed terrible back pains very quickly. They don’t seem well- suited to laptop use. Cluster the jython presentations on one day, and similarly the IronPython ones. Need to get more AV staff - perhaps ask for volunteers early, like session chairs? Would be nice to have optional short bios of people on the PyCon site coming prior to coming, so that newbies (and others) can identify people that they’d perhaps like to meet with, rather than depend on hit-and-miss… clearly not an issue for old hands.

Not sure. You are already doing a great job. Increase available bandwidth. Better network access (more bandwidth, access points, etc). Knowing that the B/G radios were going to be cranked down so low would have been nice to know ahead of time (to get an A card). Maybe that was an on the spot decision though. A single pre-convention email with various tips about what to bring/be prepared for/other last minute announcements would be nice.

Maybe the week before the convention. The pycon website could be better. Some of the talks seemed to be too basic, it would be nice to have some more advanced talks (I know it’s hard to please everyone). This also may be due to how much time they have to spend on their talk, and it is difficult to hit much during that time. I found the food at the hotel to be less than satisfying, and the talks this year were generally less useful to me than last year, because I felt that they were mostly too shallow in what they covered.

I also missed several talks that conflicted with other talks I would like to attend. I would prefer only 2 tracks, rather than three, and I would like there to be fewer keynotes and more long/advanced talks that can go into increased depth. Select the accepted talks earlier. Add speaker name in schedule. Survey attendees about talk interest before fixing the original schedule. Consider a variable number of parallel tracks (i.e. not always 3).

Group the talks a bit better around themes. For example, there could have been 4 talks in a row about Python in Education running in parallel with talks about Python web frameworks - as these two topics likely have little overlap in terms of attendees interest. Make it possible for attendees to give feedback anonymously by email to speakers about their talk. More lightning talks. Group topics to dig deeper; more BOFs (Best practices - For example, a linked series of testing talks - Unit testing, nose for running a series of unit tests, load testing, etc.

Multiplatform programming - Apple, windows, palm, nokia. Use the same program and get it to run on as many systems as possible.) Schedule more time for lightning talks. They were very entertaining and informative! I also think a continental breakfast would be nice. It is difficult to be gone over the weekend. The tutorials were terrific. If I were to attend next year I would probably attend two days of tutorials (given the right topics were offered).

The talks were not long enough. It seemed that the talks were long enough for the inexperienced speaker to get themselves into trouble but too short for any real depth. Lightning talks serve the purpose of brief overviews and status reports. The talks should go deeper. 1) more lightning talks 2) keep the web schedule updated with the write-in Bof/open space sessions 3) can you require presentation materials before the talk (or at least some early version of them) to help decide which ones to attend?

4) Name badges should have indicated what location and/or company people are coming from 5) Maybe before keynotes, during lunches or any other periods of inactivity, you can run a slideshow loop. use previous pycon photos and allow people to submit photos before hand (example, screenshots of people’s projects, allow anything python related). allows people to be creative and not necessarily have to give a lightning talk to get their word out.

More breaks with fruit or vegetable trays for snacks. Nuts are good, too. Not so much the fruit bars. Ned Batchelder’s suggestion: Allow people to list URLs, projects, talks, or companies that they are associated with. Annotate name tags with that info. Similarly, maybe a who’s who book with that info. *WARMER* rooms… PyCon should not be a huge fridge Bigger event rooms. More information on the given talks. Hard to note what you want to see with 5-10 lines.

Enforce people to post their slides beforehand. Better evening event organisation, was a shambles trying to find out what was happening and when. 9AM without coffee & muffins was rough. 5 minutes between talks was good; back to back is tough. Longer supper break? No supper break? Provide some dinner? Two lightning talk tracks, separated by subject? I was happy with PyCon coverage. However I ran into several other system admins who use Python.

They may be a fairly small group though. Consider organizing the talks into categories (or maybe even tracks in the schedule) such as: 1. Case studies of Python use (e.g. education) 2. Intros to Python applications (e.g. Trac, Django) 3. The Python language and dev/dist tools 4. Fringe/new ideas, projects in their infancy Begin call for papers much sooner, specifically targeting more technical papers, in-depth talks that give code

The rest of this page is on the live site.