Advocacy Writing Tasks / Running a Conference - Python Wiki
Python Wiki Python Wiki / Python Wiki / Community & User Groups / Advocacywritingtasks / Advocacy Writing Tasks / Running a Conference View as Markdown Advocacy Writing Tasks / Running a Conference ¶ Legacy Wiki Page This page was migrated from the old MoinMoin-based wiki. Information may be outdated or no longer applicable. For current documentation, see python.org . Planning a Python Conference ¶ Author: Andrew M.
Kuchling Date: 2008-07-29 Contents Introduction Types of conferences Planned conferences Sprints Unconferences Combinations Volunteers Finding a location Scheduling the conference Drawing up the program Networking Food and Catering Publicizing your conference Running your conference Finances References Legal Introduction A great way to energize the Python® community in your area is to hold a Python conference. Conferences are an excellent way for people to meet old friends and make new friends, to exchange ideas and knowledge, and to work together on projects using fast face-to-face discussions instead of slower e-mail and chat sessions.
After a successful conference, people come away excited and energized. In this white paper, I will be discussing how to organize and run a small conference, one that runs for one or two days and will have 50-100 attendees. If you want to run a smaller conference for only 20-50 attendees, the advice here will still be useful to you because the problems are much the same. Larger conferences such as PyCon or EuroPython are more complicated to plan for many reasons.
They run for three to five days, so you need to fill more program space. They’ll usually attract a few hundred attendees, so your choice of locations is reduced and the likelihood of getting the location for free is small (schools are probably the only chance). Some of the information below will still be helpful, but if you’re interested in planning such a conference, I suggest joining the conferences mailing list and asking for advice.
I’d also strongly suggest getting your feet wet by running a smaller conference first. Types of conferences Small conferences can be structured in a number of ways. Planned conferences A planned conference is the most traditional kind, with a fixed timetable and pre-selected schedule of speakers. Attendees will spend most of the conference time listening to speakers and occasionally making a comment or asking a question.
Pre-conference planning: Speakers need to be chosen. The conference organizers might issue a call for speakers and then have a program committee select from the responses, or might invite specific people to give a talk. The selected speakers then need to be arranged into a schedule for each day of the event. Sprints Sprints (also called hackathons) feature small groups of 3-10 people, who gather around a table and work on various projects.
Sprints are very decentralized because there are no speakers who stand up and talk while the rest of the room listens; instead the activity is in the conversations within each small group. Requirements: Networking of some sort is an absolute necessity for sprints. People will be writing code, and today writing code requires access to code repositories, bug trackers, and online reference materials. Pre-conference planning: Find out which projects will be present.
A project needs a certain number of people in order to sustain a sprint. It may be critical to have a skilled developer from the project who can actually answer questions from new developers and commit changes to the master repository. Unconferences An unconference is a conference where the content of the sessions is invented day-by-day by the participants. Often the program for each day is planned at the first session every morning.
Participants introduce themselves, describe session topics they’re interested in, and assemble into groups. This may seem like a risky way to run a conference: what if no one suggests anything and you end up with a room full of people staring at each other in silence? This is unlikely to happen in practice. In a sizable group, there will be some people who want to learn about something and other people who can talk about it.
Unconferences often feature lightning talk sessions containing a series of brief 5 to 10-minute talks, with a minute or two for questions between each talk. Many people can give such a short talk about a personal project or a library they’ve used, and writing three or four slides doesn’t take much effort. Attendees enjoy lightning talks, too, because a single hour-long session will introduce them to ten or twelve different projects.
Alternate terms for unconferences are “open space conference” or “barcamp”. Combinations You can combine more than one of these styles. For example, a two-day conference might feature one day of planned talks and one day for a more loosely-structured unconference or for sprints. From my experience with PyCon, sprints are more efficiently held at the tail-end of a conference. Holding sprints after the conference talks means that sprints won’t collide with any necessary set-up work, and lets speakers advertise their sprint and attract more participants.
Another benefit of putting sprints after the conference is making the sprint more efficient if you’re having several days of sprints. The opening hours of a sprint are usually spent getting all the participants ready to work; they need to download software, check out a source tree, and figure out how to compile it. When sprints are before the conference, a new bunch of people arrive every day and need to perform the initial setup.
A post-conference sprint starts out with the maximum number of attendees and people drop out as the days pass, so you can get this initial configuration completed for everyone. Volunteers It would be difficult (though not impossible) for a single person to organize and run a conference, but the job is much easier for a group of organizers. Volunteers can: Explore locations before the conference. Run the registration desk.
Help advertise the conference locally at schools, user groups. Help prepare the conference rooms, wireless networking, badges, etc. Your very first step should be to look for a pool of volunteers. Many conferences are organized by members of the local Python user group. If the conference location will be a school, there might be a computer club or ACM student chapter. During the months before the conference, schedule a regular volunteer meeting to discuss recent progress and what tasks need to be done next.
Following a definite schedule pushes people to complete tasks in time for the next meeting. Meetings can be held in-person or over instant messaging or IRC. For PyCon, we met every two weeks for an hour, and two months before the conference the frequency increased to weekly meetings. Finding a location The most important things about the location are: One or more places to talk such as an auditorium or conference room.
Equipment to talk with (a projector and screen, microphones). Schools, libraries, hotels, and conference centers are all possible locations that might have rooms of the right size. As the number of attendees increases, locations get harder to find. In the US, most high schools, universities, or libraries will have an auditorium that can seat at least 100 people, and they’ll also have classrooms that can hold 20-30 people.
Schools, libraries, or a Python-friendly company are your best bets for a relatively small conference because they may let you use the meeting space for free. Your local Parks and Recreation Department may have art centers or community facilities that can be rented for a few hundred or thousand dollars. Hotels are less practical for small conferences because they’ll either charge you for using their meeting space or expect you to attract enough guests to fill a block of rooms.
In either case, you’re making more of a financial commitment and may end up losing money.
The rest of this page is on the live site.