Skip to main content

Rearranging the rooms

(Reviewing of proposals is still going on; nothing to report at the moment.)

PyCon 2007 is in the same hotel as the 2006 conference, and we have the same set of rooms available to us.

At a chat session of PyCon organizers on October 30th, we decided to make some radical changes in how we'll be using the rooms. Credit should be given to Doug Napoleone for suggesting this rearrangement. Here's the plan:

  • Ballroom A-E, Ballroom F-J: refereed talks (just like last year).
  • Mesquite (last year's quiet room): 3rd track of refereed talks.
  • Preston Trail and Bent Tree: will both be divided into 3 rooms each = 6 small rooms total. 5 of these rooms will be available for open-space discussions; the 6th will be the conference logistics and storage area.
  • Addison (last year's conference storage room): will be the quiet room.

This rearrangement has a bunch of potential advantages:

  • People complained that Preston Trail was too long and skinny for talks; if you were in the back, the screen is very far away. Mesquite is more rectangular, but only seats 15 fewer people (210 to Preston Trail's 225) in theatre style, not much of a loss in seating.
  • 2006's conference had too little open space: available slots were snapped up very quickly. Having 5 smaller rooms that seat about 50-60 people each will make more slots available; I expect the attendees will still manage to fill all the slots.
  • Staff won't need to run all the way to Addison to get supplies; instead we'll use the Bent Tree room closest to the registration desk for storage.
  • Because of its remote location, Addison should have fewer people talking outside it and be quieter than Mesquite.

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
Who should write a proposal? Everyone! If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…