skip to navigation
skip to content

PyCon2005/Feedback

This page summarizes the feedback from the user-response forms from PyCon 2005.

Overall ratings

Please rate your overall ...

Very low

Low

High

Very high

... satisfaction with PyCon

2

50

57

... satisfaction with the keynotes

6

55

56

... satisfaction with the talks

10

79

21

... satisfaction with the topics

13

77

26

... satisfaction with the sprints

2

3

20

19

... satisfaction with the network

3

24

46

24

... satisfaction with the food

1

15

62

32

... likelihood of attending next year

1

4

48

63

Talks

3 Favorite Talks

Please list your 3 favorite talks.

Disclaimer: these are not scientific counts.

  • People are often vague (does "OO talk" mean Alex Martelli or Bruce Eckel?)

  • Some people wrote down more than three talks (e.g. "Roundup and Traits", "Alex's talks" -- both votes were counted in this case).

  • Some votes were ignored because I couldn't figure out what talk they referred to.

  • All votes for a lightning talk were counted as a vote for 'Lightning talks'.

  • All votes for something in open space were counted as votes for 'open space'.

  • Keynotes have an unfair advantage because so many people see them.

Vote count:

  • PyWebOff (28 votes)

  • Keynote: GvR (17)

  • Keynote: Jim Hugunin (16)

  • Lightning talks (16)

  • Iterators/generators -- Martelli (16)

  • OOP -- Martelli (15)

  • PythonCard (15)

  • Bruce Eckel (15)

  • matplotlib (15 votes)

  • Keynote: Greg Stein (12)

  • Dabo (12)

  • Durus (8)

  • Yarn (7)

  • Improving memory allocation -- Jones (6)

  • Descriptors -- Mike Fletcher (5)

  • py.test (5)

  • Air Traffic Control (4)

  • State of Zope (4)

  • Python on Series 60 (4)

  • Responsive HTML/HTTP (4)

  • Profiling/Visualizing (3)

  • US PTO with Xapian (3)

  • Chandler parcels (3)

  • Envisage (3)

  • PyPy Type Inference (3)

  • Traits (3)

  • Roundup (3)

  • Open space (3)

  • Decimal module (3)

  • Sequential code/event-driven world (3)

  • Schevo (2)

  • PyChinko (2)

  • Layered Event System (2)

  • Scripting the Mac (2)

  • Breaking the Rules (2)

  • Cross-Platform Apps (2)

  • WSGIKit (2)

  • XML Acceptance (2)

  • Fast Networking (2)

  • Serengeti Lions (2)

  • Personal Internet Endpoint (2)

Single votes: Learning Arabic, Happy Hooking, SchoolBell, Localized Type Inference, Time of Day, Documentation Costs Avoided, Streaming Python, PyBlosxom, PyLucene.

Accommodations

"Where did you stay?"

  • Hotel (62/53%)

  • Local (33/28%)

  • With friends/family (11/9%)

  • Hostel (11/9%)

  • Other: Room in a house; rented mini-apartment.

"If you attend PyCon next year, would you stay at a conference hotel?"

  • Yes (72/72%)

  • No (27/27%)

If yes, what is your maximum per-person nightly hotel room budget?

  • <$75 (12/15%) (100% of respondents can afford this)

  • 100 (19/23%) (85% of respondents can afford this)

  • 125 (20/25%) (62% of respondents can afford this)

  • 150 (17/21%) (37% of respondents can afford this)

  • 200 (12/15%) (16% of respondents can afford this)

  • >200 (1/1%) (1% of respondents can afford this)

Which location would you prefer for PyCon 2006?

  • Downtown hotel (28/25%)

  • Suburban hotel (8/7%)

  • Airport hotel (2/2%)

  • Conference center (27/24%)

  • Don't care (46/41%)

  • Other: Anywhere on Metro.

Is the Washington DC metropolitan area convenient for you?

  • Yes (96/83%)

  • No (20/17%)

If PyCon were not to be in Washington DC, what 3 cities/regions would you prefer?

Boston (20 votes)

Chicago (20)

NYC (20)

San Francisco (18)

Philadelphia (14)

Seattle (12)

East Coast (9)

Atlanta GA (9)

Baltimore (9)

Orlando FL (7)

Texas (5)

Las Vegas NV (5)

Toronto (5)

California (5)

Hawaii (4)

Los Angeles CA (4)

Washington DC (4)

Northern VA (4)

Portland OR (4)

Midwest (4)

Miami FL (4)

San Diego (4)

North Carolina RTP (4)

West Coast (3)

Pittsburgh (3)

Colorado (3)

Montreal (2)

Vancouver BC (2)

San Jose CA (2)

Annapolis MD (2)

Richmond VA (2)

Other suggestions: New Orleans, Santa Fe NM, Providence RI, Minneapolis MN, NY State, South Carolina, and other places.

Tutorials

Would you be interested in attending half-hour or hour-long tutorials next year?

  • Yes (87/70%)

  • No (27/22%)

  • No response (10/8%)

Would you be interested in half-day (3-hour) tutorials?

  • Yes (67/%)

  • No (13/%)

How much would you be willing to pay for a half-day tutorial?

  • $0 (3/5%)

  • $25 (10/15%)

  • $50 (32/48%)

  • 100 (21/32%)

Please list tutorial subjects you would like to attend.

  • GUI toolkits (20 votes)

  • OOP/patterns/metaclasses (18 votes)

  • Twisted (17 votes)

  • Web (15)

  • Databases (10)

  • Zope (9)

  • Beginning Python (7 votes)

  • New features in Python 2.x (7)

  • Writing C extensions (6)

  • Itertools/generators/listcomps (6)

  • Programming techniques (agile, XP, debugging) (5)

  • Plone (4)

  • Decorators (4)

  • Packaging (distutils, standalone apps) (4)

  • PyGame (4)

  • Intermediate-level Python (4)

  • Data structures (3)

  • Serial port/networking (3)

  • Python internals (3)

  • XML (3)

  • Numeric/science (3)

  • IronPython (3)

  • Jython (2)

  • Testing (2)

  • Profiling (2)

  • PyObjC (2 votes)

Single-vote topics: Win32, pcap files (?), how to do sprints, Unicode, cellphone programming, Chandler, frameworks, IT use of Python, migration from other languages, introspection, regexes, functional programming.

Comments

Multiple-vote items

  • (25) Longer sessions (mostly 45 minutes; a few people suggested 60)

  • (12) Better wireless (no timeout; in all rooms; supporting SMTP)

  • (11) More tutorials

  • (9) Temperature too warm in lecture rooms

  • (2) More sessions

  • (7) More power strips in lecture rooms

  • (4) Have sprints after conference

  • (4) More social events (evening parties, book signings)

  • (4) Better speaker quality

  • (4) Rate talks by level/audience

  • (4) Ensure presentations available ahead of time; include them on a CD?

  • (3) Make lightning talks a plenary session

  • (3) Provide more info on schedule handout (speaker bio, abstracts)

  • (2) Job board

  • (2) Separate talks into subject groups (math/science, applications, etc.)

  • (2) Keep conference on one floor

  • (2) Fewer concurrent tracks

  • (2) End talks on time

  • (2) Have more water; veggie, non-dairy options

  • (2) Have presenters use a standard slide template

One-vote items

  • Provide lunches/snacks at sprints

  • Organize sprints better

  • More publicity for sprints

  • Better open space signup procedures and signage

  • Use whiteboards for open space schedule

  • Method to organize dinner/pub meetings (like how open space is done)

  • Have a large, solidly anchored bulletin board

  • More application talks

  • More how-to talks, fewer 'this is what I did' talks

  • Invite developers from other communities to give presentations

  • Recording agreements should specify a license

  • Hold a programming contest?

  • Shorter daily schedule

  • Keep 1/2 hour length of talks

  • Order talks suitably in the schedule, having basic ones before advanced ones

  • Have closing keynotes/plenaries each day

  • Ensure speakers don't have microscopic demos or slide text

  • Provide water for speakers

  • Keep providing lunch and snacks

  • Dinner reservation reminders at lunch (???)

  • Include info on restaurants (w/ price) in wiki

  • Add city+state+country, affiliation to badges

  • Use larger font for printed schedule

  • Online feedback, & return immediate feedback to attendees during con


CategoryPyCon2005

EditText (last edited 2005-07-28 08:59:06 by denali)

DeleteCache (cached 2007-02-06 17:23:45)