Thursday, February 28, 2008
Wednesday, February 20, 2008
We are experiencing persistent problems with our credit card payment processor, a third-party.
If you encounter a problem with credit card payment, don't panic. Please submit a change request and we'll respond as soon as possible. You will still be asked to pay the rate in effect at the time of your registration, not the time of your payment.
The change request form is available via the My Registration page: click the link for your invoice, and you'll see links near the bottom of the page.
Remember, we're volunteers, so PyCon problems usually aren't handled during our day jobs. Please be patient.
Tuesday, February 19, 2008
The problem with credit card processing has been resolved. If you were affected, we'll send you email letting you know how to proceed with payment. Apologies for the inconvenience.
Registrations and invoices that are submitted will be saved, and the early-bird price will be honored even if you end up completing the payment after the deadline.
A PyCon representative will e-mail you as soon as the problem is resolved with instructions on completing the checkout process.
We apologize for the inconvenience.
UPDATE: The problem has been resolved. Register away!
Saturday, February 16, 2008
The tutorials for PyCon 2008 are filling up quickly. We have ten rooms set aside for tutorials: five quite large (capacity 50), one medium-plus (capacity 24), two medium (capacity 20), and two small (capacity 14). We had no idea which tutorials would be the most popular, so we're using attendance numbers to assign the rooms. Greg Lindstrom (the tutorial coordinator) and I are watching the attendance numbers carefully.
Yesterday we had to close the first tutorial as full: PM6, Faster Python Programs through Optimization and Extensions I, to be presented by Mike Müller. It's not the tutorial with the highest attendance, but we have no choice now but to put it in one of the medium-sized rooms, with a practical limit of about 20 people. There are six afternoon tutorials with larger attendance, which get the five large rooms and the one medium-plus room (and there's a battle going on there). These aren't full yet, but full enough to dictate the room assignment for PM6.
With a large number of tutorial proposals and a huge demand for more tutorials in past years, we tried something new this year: three sessions on Tutorial Day (Thursday March 13) -- morning, afternoon, and evening. We had no idea if people would go for three sessions, or whether people would get tired and one session would suffer. I'm happy to say that all three sessions are about equally attended, and about two thirds of attendees are signing up for three tutorials. That's a lot of learning packed into one day!
We'll probably have to close more tutorials as they fill up over the next few days.
Tutorials are first come, first served. So if you're interested in taking tutorials, don't delay, register today! And don't forget, early-bird registration ends on Wednesday.
Tuesday, February 12, 2008
If you haven't registered for PyCon yet, now is the time! The early-bird registration deadline is February 20, one week away. After that, the price for registration will be going up.
The deadline for hotel reservations at the conference rate is also February 20. Act now, because the regular rate is considerably higher!
A reminder to tutorial and talk speakers: you are responsible for your own registration and hotel reservations. So don't delay!
Friday, February 08, 2008
Wednesday, February 06, 2008
Intro to Sprinting (60 minutes, at 3:20 pm)
This will be a plenary session, and will begin with a talk explaining what sprints are and how we do them at PyCon, followed by a panel discussion where the sprint leaders will answer questions.
Sprint Tutorials (90 minutes to 3 hours, at 4:40 pm)
After a break, participating sprint leaders will gather the sprinters of their projects, go to different rooms, and the project will be explained. Everything from code walkthroughs to granting repository access can be presented here. This way, you'll be able to start working on the sprints effectively on Monday morning, without a long setup delay.