Go to http://us.pycon.org/Addison/Hotels for hotel information and a registration link.
Update: the hotel has sold out of sleeping rooms on Thursday February 22, Friday February 23, Saturday February 24, Tuesday January 27, and Wednesday January 28.
Thanks to all the sponsors, and to Steve Holden, the sponsorship coordinator.
This year the Python Software Foundation is helping 18 people to come to PyCon, spending slightly less than US$9000. We look forward to seeing them all at PyCon!
The special PyCon room rates at the Dallas/Addison Marriott Quorum are US$79/night for 1-2 people, and US$89/night for 3-4 people; there's an additional hotel tax of 13% on top of this rate. This rate is only available until February 1st.
To register online, use the hotel's special event page for PyCon.
If you're looking for a roommate to reduce your costs, see the Room Splitting wiki page.
The number of available tutorials continues to shrink. "Code Like a Pythonista" is full, and we regret to announce that "Internet Programming With Python" has been cancelled. The remaining tutorials are:
- Morning session: Using the DB API, Python 101, How to Document a Python Open Source Project, Zope Component Architecture and zc.buildout.
- Afternoon session: Advanced Web Application Development with TurboGears, Faster Python Programs through Optimization and Extensions II, Testing Tools in Python.
Remember to book your hotel rooms before February 1st to obtain the lower conference rate.
Someone asked about ground transport from the airport to the hotel, and sharing rides. A taxi will cost about $40 one-way. There's also the Super Shuttle airport limo (minibus) service, which is cheaper than taking a taxi but reservations may be needed. Public transport is also available, but according to reports it isn't quick. See http://us.pycon.org/Addison/GroundTransit for details on all options.
I started a wiki page for people to arrange taxi splitting: http://us.pycon.org/Addison/TaxiSplitting. Sharing taxi rides may be difficult though, because arrival times are staggered and flights get delayed.
I recommend that anyone interested in sharing a taxis should wear a Python or PyCon T-shirt or sweatshirt when travelling so people can recognize each other. Here's a source of official Python garb: http://www.cafepress.com/pydotorg.
If anyone has other/better ideas, please add a comment.
Total early-bird registration was 363 people.
To compare with last year: at PyCon 2006, early-bird got 273 registrations. This year's figure is therefore a 32% increase.
Maybe we're just getting better at reminding people to register early and the final attendance figure will be about the same. On the other hand, Doug Napoleone notes that the number of proposals received was also up by 30% (see the discussion of proposal selection for the numbers). A 32% increase in '06's total attendance of 410 would mean 541 attendees.
My intuition is that both factors -- better early-bird advertising, and more total attendees -- are at work. My psychic prediction: final attendance for 2007 will be increased over 2006 to between 450-500 attendees: a significant increase, but not a 30% increase. (Please, no wagering...)
(I'm deliberately not mentioning which tutorials are at risk, because if a tutorial is on the edge, people may decide to sign up for some other tutorial. This post is intended to encourage everyone to hurry up and register.)
Don't forget to reserve your hotel room, too; to obtain the conference rate, you must register by February 1st.
The introductory Django tutorial, to be held in the morning, is now full.
Due to the level of interest in the Django tutorials, they've been given more space. I still expect the Django tutorials will fill up today; we don't have that much additional space...
Update: the afternoon "Advanced Django" tutorial, taught by Jacob Kaplan-Moss, is also full.
- displays a color-coded, up-to-date schedule
- displays pop-ups with descriptive information about each event
- allows selecting events to create your own personal schedule
- supports iCalendar output of both conference and personal schedules
If you have a PyCon login account, the application also:
- stores your schedule on the server instead of in a cookie.
- highlights talks that you're presenting or sessions you're chairing.
To create your own PyCon login account, visit the Site Signup Form, which is independent of your conference registration.
If you store your schedule on the server, your selections are included and summarized in a report for the PyCon organizers. We can therefore see which talks are the most popular, and this will help us schedule them in rooms with enough capacity.
A print-specific stylesheet is in development.
We think the schedule application is very neat, and hope it's useful in planning your PyCon attendance.
If you've registered for a different afternoon tutorial (or for no afternoon tutorial at all) and want to switch to the new Internet Programming tutorial, write to the conference address (pycon at python.org).
We apologize for the inconvenience.
Register for PyCon.
If you're interested in the tutorials you should register as soon as possible. One tutorial is nearing its maximum size; when that limit is reached, registration for that tutorial will be closed.
I will be presenting a talk at PyCon, "The Absolute Minimum an Open Source Developer Needs to Know About Intellectual Property." I want to tailor this talk so that it is interesting to as many attendees as possible.
I am familiar with a lot of the internal divisions in the Free Software/Open Source community. My intent is not to advocate for or against any specific position, but rather to promote a common understanding and address specific situations that developers may
encounter. In other words, a problem/solution approach, instead of an argumentative approach.
With that in mind, I had in mind the following subjects:
- A brief primer on intellectual property (what are patents, trademarks, copyrights, and trade secrets?)
- What to do when you have an idea you want to develop, but you are working for somebody else
- What it means to incorporate GPL'd modules into your own code
- Ways to protect ideas that you have put into a proprietary software product
- Ways to avoid, work around, or mitigate the effect of software patents
- Licensing, using, and distributing software (comparing and contrasting the GPL, BSD, and Python licenses)
I am interested in hearing about 1) other topics of interest, and 2) the relative level of interest in each topic. To keep within the time limits for my talk, I intend to address the most popular topics in roughly the order of their popularity.
Update: (January 15th) attendee #300 registered this morning.
(The problem described in this post has now been resolved.)
Several attendees have reported a problem when booking their hotel rooms; they've been told that the conference rate is no longer available and offered a much higher rate. We're talking to the hotel to resolve the problem; if you're given a too-high rate, don't book your room yet and wait until we announce the problem is resolved. (That announcement will be posted here.)
If you've already booked, please wait for the announcement and then call Marriott to fix the problem; if that doesn't work, send an email to (pycon at python.org) and we'll use our hotel contact to change your reservation.
Here's what's probably going on. PyCon has reserved X rooms per night at the conference rate. For most such reservations, the conference rate is no longer available once X rooms have booked. PyCon's contract is different, though: we get the conference rate until the hotel is full. The reservation staff was confused about this last year and they've probably gotten confused again this year.
The proposal being suggested: vendors would pay a vendor sponsorship fee of a few hundred dollars and would then get a table (probably a 6-foot size one) in a vendor area. Vendors could be open from after the first plenary session to before the last plenary session; that would be from 10:30AM to 5-something PM. You could store merchandise in a locked but unguarded room, but you'd probably still have to sign a liability waiver so that PyCon isn't responsible if your merchandise is stolen or damaged.
If you'd be interested, please add your name, product/company info and a contact e-mail to us.pycon.org/TX2007/Vendors.
This is a straw poll to gauge if there's interest, not a contract. Adding your name does not oblige you to sign up as a vendor, if/when we decide to have a vendor area and specify the costs and terms.