Memoirs of a PyCon Australia organiser: Part 1 (of no idea how many)
This past weekend saw the staging of the third PyCon Australia conference. It’s been a very long time coming, and the subject of countless hours of hard work by myself (chasing sponsors, arranging to fill a programme, and ensuring delegates attended the conference), not to mention my amazing co-organisers, Joshua Hesketh, Matthew D’Orazio, and Josh Deprez.
We held the conference in Hobart, my home city, and the capital city of Tasmania – this follows two successful conferences in Sydney. Despite a lot of scepticism about Hobart as a venue for a conference, we managed to attract 240 signups (placing us somewhere in the middle of the first two Sydney conferences in terms of attendance (woo!)).
The first conference activity, the CodeWars programming tournament, started on Friday evening, with teams of up to 4 competing to solve programming problems against each other on projectors. This was a great event, which let delegates meet and greet each other before the conference started, and we’re very thankful to our event sponsor, Kogan, for helping us to make it happen.
This year, we were graced by the presence of two overseas keynote speakers –– Mark Ramm, the current engineering manager on Canonical’s Juju project, and Kenneth Reitz, the chief Python guy at Heroku.
Mark’s passionate and entertaining keynote delved into the murky waters of product management, and showed that applying the tools of testing and scientific process to product development and evaluation was something well in the reach of everyday engineers, even those with small projects. A smattering of war stories from his days leading product management at SourceForge rounded the talk off. It was a great way to start the conference, and it really helped set the informal, enthusiastic tone of the event.
Kenneth’s talk dwelled on his philosophies of designing libraries in Python. He’s the developer of the python-requests HTTP library –– a library that has taken its rightful place as the obvious way to do HTTP in Python. His keynote gave us some strong insights into places where Python can make itself more accessible to newcomers, as well as being easier to remain involved for developers who use Python in their day-to-day lives. Kenneth’s presence was a great asset to the conference –– through his keynote, and also by making himself readily available to chat with delegates in the hallway track. Hopefully we’ll be seeing him back at PyCon Australia in future years, with more of his Heroku colleagues.
Our conference dinner was held at the beautiful Peppermint Bay restaurant near Woodbridge (some 30km South of Hobart); delegates were delivered there by the fast catamaran, the MV Marana. We saw some excellent views of Hobart at twilight – the silhouettes of Mt Wellington and the Hobart Hills were quite spectacular. Unfortunately, the river got a bit choppy near the entrance to the D’Entrecasteaux channel, which left a few of our delegates feeling a bit worse for wear. Luckily for us, the dinner itself was a fantastic evening of socialising, and finding out about other delegates’ interest in Python. It was a great event, with great food, and we’re going to have a lot of difficulty topping it.
There are countless people who made an amazing effort to help improve our conference, including our volunteers, our speakers (some of whom stepped in at the very last minute to help improve our conference), Ritual Coffee (who produced their own custom blend for the conference, named “African Swallow“, no less!), the venue staff at Wrest Point (especially Kelly Glass, who’s put up with my worrying about conference rooms for several months now), our sponsors (who helped to keep the conference itself affordable), and many many more. It’s helped make my life as an organiser so much more tolerable.
Anyway, that’s it for now. I expect that I’ll have a follow-up to this post, dwelling on what we did right as an organising team, and how we can improve for next year. Incidentally, the conference will be run in Hobart again next year – if you’re in a position to help out with sponsorship, shoot me an e-mail at firstname.lastname@example.org, and I’ll get a prospectus to you as soon as possible!