Differences between revisions 5 and 6
Revision 5 as of 2004-03-30 01:06:36
Size: 1863
Editor: panix2
Comment:
Revision 6 as of 2004-03-31 15:39:31
Size: 2428
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:

A postmortem IRC session is scheduled for 1PM EST, Friday April 2nd.

= Statistics =

43 badges were never picked up.

18 paid registrations on-site.
Line 13: Line 21:
 * Put Lightning Talk sessions (one or two of them) in the program.
 * Possibly hold the sprints after the conference (or both before and after?)
 * Need more time between sessions
Line 14: Line 25:
 * Need more time between sessions  * Do feedback forms on the web (e.g. Shane McChesney's offer)
Line 36: Line 47:
 * Steve will chair one more conference; we need to arrange the succession for
 PyCon 2006. Perhaps having a vice-chair closely involved in next year's planning process would be optimal.

This page is for use by PyCon organizers to to record learning experiences from this year's conference, and to remember things that we could do better next time.

A postmortem IRC session is scheduled for 1PM EST, Friday April 2nd.

Statistics

43 badges were never picked up.

18 paid registrations on-site.

Ideas for next time

  • When registering users, get permission to send them status e-mail (or to put them on a mailing list).
  • When accepting proposals, request that users put their

    presentations under one of the [http://creativecommons.org Creative Commons] licenses, as [http://zak.greant.com/archives/000622.html the MySQL conference has done.]

  • Put Lightning Talk sessions (one or two of them) in the program.
  • Possibly hold the sprints after the conference (or both before and after?)
  • Need more time between sessions
  • Do feedback forms on the web (e.g. Shane McChesney's offer)

  • Schedule first day of Open Space before conference -- first day had hardly any Open Space going
  • Put conference before sprint
  • Make conference four days and sprint three days; last day of conference gears up for sprint
  • Do we need to use pycon.org?

I found having two copies of information irritating, and the limited number of people who could update the pages was a bottleneck at times. Could we use the existing pydotorg CVS instead? --amk

  • Make sure that early bird registration deadline ends *after* all the papers have been accepted and the schedule has been created and posted for people to see.
  • Having the catering table in the back of the keynote room may not be a good idea; it's noisy when the staff refreshes the table in the middle of a talk.

Tasks for next time

  • Steve will chair one more conference; we need to arrange the succession for

    PyCon 2006. Perhaps having a vice-chair closely involved in next year's planning process would be optimal.

  • Finish off and polish the conference software so that next year it doesn't have to be developed as capabilities are needed; having to do this resulting in our missing several promised deadlines and pushing things too close to the conference date.

    (AMK will do this. Please record ideas on [http://www.amk.ca/ng-arch/ConferenceSWIdeas this Wiki page], and join [http://www.amk.ca/mailman/listinfo/conf the conf mailing list] for discussion.)

PyConPostMortem (last edited 2008-11-15 14:00:43 by localhost)

Unable to edit the page? See the FrontPage for instructions.