Harvard Science Center, Cambridge, MA, USA - Saturday, March 21st and Sunday, March 22nd, 2009
Audio and slides are now available, and we invite your feedback.
Home | Report | Attendees | Speakers | Main Schedule | Getting There | Staying There | Social events
OpenCoference Guide / Schedule | Track 1: HPP | Track 2: FNS | Track 3: Activism
Your guide to proposing and running sessions.
High Priority Projects
Free Network Services
Free Software Activism
Rules for Session Leaders
- Your session is not guaranteed, so make your proposal punchy and fun!
- Remember, we're here to talk about Free Software -- there are a million conferences about Open Source, so let's frame this in the best possible terms.
- There are no projectors, so giving slides will probably be hard. You could probably deliver something on your laptop
- But let's have the laptops running a free software OS only please. No Mac OS X, No Windows XP, No Windows Vista...
- Sessions should be proposed by writing the subject, the structure of the session and the organizer (probably you) on a sticky note and placing it on one of the boards by the food area.
- Sessions can be structured as lectures, group discussions or hacking sprints. Please make clear which you are proposing. Hack sprints may take up two consecutive slots if needed.
- There are five minute slots at the end of the day for quick announcements or questions. These are a great opportunity to get the word out about your new project or to find people to discuss issues with.
- Sessions can also be proposed on this wiki up until 10am Sunday. Please create the page in the appropriate namespace for the track it would belong to, and add the category OpenConferenceSession.
- When running a session please use this wiki to keep notes, or to link to notes kept on a project site, and link to resources such as slides or the pre-prepared text of a talk if it exists. If you need help with the wiki ask FSF staff, who will be able to help you.
- At the end of the day you will have an opportunity to tell the conference about your session, so bear this in mind when running the session. This can be as simple as stating what you talked about, which features were worked on or what decisions were reached.