Differences between revisions 39 and 41 (spanning 2 versions)
Revision 39 as of 2005-05-11 13:02:13
Size: 3085
Comment: Remove venues
Revision 41 as of 2005-05-11 19:34:07
Size: 2954
Editor: ORR6227
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Barring a surprising change in Python's growth, PyCon 2006 will be too large
for GWU's facilities. The 2005 conference will therefore be the last one at GWU.

The larger the venue, the further in advance we need to book it, so we should regard 2006 venue choice as an immediate problem, rather than waiting until it's too late.

Since venues typically book up to 18 months in advance, you might argue we are already too late, and I wouldn't disagree. Typically we should expect to be doing long-range planning 18-24 months in advance.

First let's try to establish some ground rules. Before we start to advocate particular venues, let's all try to agree on what we'd like from an ideal venue. The hope is that this can be incorporated into some kind of "scoresheet" that those who visit potential venues can use to report back - preferably to the pycon-organizers list, with a summary here.
We need to find a venue for PyCon 2006.
Line 12: Line 5:
 * Must allow maintaining PyCon as a low-cost conference (early bird registration around $175-200).
Line 14: Line 9:
 * Convenient for low-cost accommodation. Not necessarily in the immediate vicinity, but if not then we'd need to establish such accommodation and the route(s) to it. Low-cost can be defined as under $60 per night (although I'll accept arguments on this).  * Convenient for low-cost accommodation. Not necessarily in the immediate vicinity, but if not then we'd need to establish such accommodation and the route(s) to it.
Line 20: Line 15:
 * Venue must support sprints before or after the conference or we need another venue to hold the sprints.  * Venue must support sprints before or after the conference.
Line 30: Line 25:
 * nearby open area where people can sit and have spur-of-the-moment meetings and collaborations. This can be a plaza, terrace, indoor court, etc. If outdoor, we'll need provisions for inclement weather. - MO
Line 31: Line 28:

 * University of Delaware, Newark, DE http://www.udel.edu/conf/clayton_rm.htm

 * Trenton Marriott at Lafayette Yard http://marriott.com/property/propertypage.mi?marshaCode=TTNMC
   Commercial location, but the room rates are listed at $79. Trenton is
   not an exciting place so far as I can tell, but it is easily
   accessible from NY and Philadelphia.

 * San Diego State University conference center http://www.sa.sdsu.edu/hrlo/conference/

 * Emory University conference center http://www.emoryconferencecenter.com/Emory.html

We need to find a venue for PyCon 2006.

Desirable Venue Characteristics

  • Must allow maintaining PyCon as a low-cost conference (early bird registration around $175-200).

  • Close to public transport. We are interpreting this to mean within a five-minute walk of a Metro station, with no obstacles to wheelchair-bound or otherwise disabled delegates.
  • Convenient for low-cost accommodation. Not necessarily in the immediate vicinity, but if not then we'd need to establish such accommodation and the route(s) to it.
  • Able to handle at least 750-800 delegates (estimated figure for PyCon 2007). Given that consensus was to begin moving PyCon around, PyCon 2008 will presumably be in a different city.

  • Facilities support must be comparable or better than what you have at GWU. Plus be aware that the cost of catering, networking, equipment, etc. could be significant additional costs beyond the base venue. as they were for the first two events, but yes, they clearly have to be budgeted -- sh

  • Venue must support sprints before or after the conference.
  • Venue must allow for sessions in the evening for the annual PSF meeting, BOFs, etc.
  • I want a demo-room, for people who want to give demos. I'd like a little more formal structure backing this -- certainly one can use Open Space for demos, and we did, but I think there would be more demos if it had its own independent and formal structure. --lac

  • room for tutorial sessions. aside from this, no 'ballroom' like rooms for sessions [Note: this might mean reserving additional space just for delegates to eat -- SH].

  • nearby open area where people can sit and have spur-of-the-moment meetings and collaborations. This can be a plaza, terrace, indoor court, etc. If outdoor, we'll need provisions for inclement weather. - MO

Ideas

Questions for site visit

  • Get detailed food costs: costs for breakfast, lunch, breaks. Are tips/tax included? Do we have a choice of caterers? --CatherineDevlin

  • How much will wireless support cost? Can it be open to everyone or are access controls required?
  • Function space: Any auditorium-style space?
  • Function space: get capacities and style information.
  • A/V equipment: projectors. Cost?
  • Is function space available in the evening?
  • Parking cost for attendees?


CategoryPyCon2006

PyCon2006/Venue (last edited 2008-11-15 14:00:11 by localhost)

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