FOSS4G2013 Reflections by the LOC

This FOSS4G Cookbook documents the process, tips, hint and lessons learned by the FOSS4G 2013 local organising committee. It does not attempt to recreate the FOSS4G_Cookbook but should provide some useful pointers for future LOC's

Introduction

Information about the LOC and UK chapter

LOC Members

The list of responsibilities against each team member gives an indication of the main lines of responsibility only, almost everyone pitched in on much more than their allocated tasks

Steven Feldman, Chair - sponsors, finance, keynoters, program Jo Cook, Deputy Chair - web, liaison with OSGeo community, giveaways, ice-breaker Jeremy Morley, Deputy Chair - liaison with university, technical stuff for workshops, program, gala night

Abi Page - program book, volunteer organiser

Addy Pope - educational bursaries, ice breaker

Antony Scott - communications, web site, signage, program book, gala night

Barend Kobben - academic program, cartography, program

Barry Rowlingson - web design and development, online program, workshop registration system, map gallery, gala night

Claire Gilmour - organisation, organisation and organisation, registrations

Franz-Josef Behr - academic program

Ian Edwards - hackathon, OSGeo Live DVD's, liaison with UK Chapter

Ian Holt - workshops

Kenneth Field - Opening up the Map competition

Mark Iliffe - workshops, closing party

Matt Walker - workshops

Peter Batty - OSGeo Board representative and dispenser of calm wisdom

Rollo Home - program coordinator, communications

Suchith Anand - academic program and educational content

UK Chapter

IE and SA are both active within the UK Chapter. Several other participants in the UK chapter were volunteers at the event.

Lessons learnt (chairman's perspective)

1. you need more people for more time than you can possibly imagine before you start so try to get extra people involved

2. people volunteer with the best of intentions but then life/the day job intervenes so try to get double cover for every role

3. everyone will surprise you

Concept

What was the aim of the LOC for FOSS4G2013? We were trying to engage with communities that traditionally saw enterprise solutions being the preserve of proprietary software and big contracts. This includes the tie in with AGI.

Venue

General comments

WiFi

Gets its own topic because it is so so important. This was a tech event with over 800 delegates per day (most sucking up 2 connections for phone and laptop or tablet) where the wifi stood up throughout. We even managed to cope with the launches of iOS 7 and QGIS 2.0 during the conference which must have boosted the download rate.

We paid a contribution of £5,000 specifically to get the internet pipe and router infrastructure upgraded. That works out at approx £6.50 per delegate.

what worked

Just about everything except for 1 router on day 1 which gave some users a problem. Having a dedicated technician on site for the first day helped to solve the problem and gave us a lot of reassurance.

what didn't work

Nothing that I can think of

what would we do differently

Nothing that I can think of

Advice to future FOSS4G organisers

Most venues do not have enough bandwidth or access points, consider paying for extra if you can

Programme

== General == This covers the call for papers, selecting papers, organising the schedule, dealing with presenters that drop out and how the prog went at the event

Merchandise

General comments on the FOSS4G branded kit (banners, t-shirts, and the stuff in the delegate packs)

Workshops

Everything relating to the workshops,from the call, to sorting out rooms to timetables and ensuring that hardware/software needs were fulfilled

what worked

• Presenters that took advantage of the testing sessions prior to their workshop had a much easier time, those that did not received harsh feedback
• Workshops that used writable LiveUSB went down well with the delegates
• A number of delegates took advantage of being able to change their workshop booking prior to the event via the booking system
• We had positive feedback regarding running workshops during the main conference
• Providing lunch bag which delegates could help themselves to
• Tea and coffee in the morning was appreciated

what didn't work

• Some delegates complained that the schedule did not provide a progression from intro to advanced
• Using heavily locked down university hardware made life a lot harder for organisers and presenters
• The university proxy was a challenge for some
• We where a few lunch bags short should of ordered another 10%

what would we do differently

• Publish the schedule of workshops earlier
• Allow delegates to book individual workshops when they register
• Look to schedule intro workshops before advanced if possible
• Rent good spec laptops for workshops with VirtualBox installed
• Encourage all presenters to submit either a VM or USB/DVD prior to the event with instructions for testing

Academic track

Everything relating to the academic track, papers, journals, mixing the presenter in and around the main prog and academic bursaries

Website

The public web site was originally a WordPress (WP) site running on an Amazon server paid for by one of the LOC, WP was chosen because of some experience using it within the team. A search for conference functionality turned up a plugin that had some of the required functionality and was used to display sponsors on the site.

However the advanced functionality of scheduling talks, workshops, presentations etc didn't seem to be available from any (free) WP plugin - and we eschewed commercial solutions.

After investigating python/Django solutions, the same server was configured to run Django alongside WP, and a large amount of conference-handling code developed for PyConDE was used to manage the Workshop schedule.

A separate custom Django system was developed to handle Workshop bookings. Registered workshop users could log in and book workshop sessions - either one or two day's worth depending on what they had paid for. The system prevented users from booking overlapping workshops (and due to the different workshop lengths, this was not as trivial as preventing two bookings at the same start time). Integration with the payment system was via emailed excel spreadsheets, read in via a python script that updated the Django database.

More custom Django code was written to handle the overall timetable, integrating presentations, plenaries, breaks, and events.

Integration with an Android conference scheduling app (Giggity) was achieved - no such luck with iOS though.

Further Django apps were developed for the 'Pledge' pages and the Map Gallery.

Code for the Django apps and the WP skin were pushed to a public github site.

Post-conference, the whole site (WP, Django, etc) will be statically mirrored so it can be served from a plain HTTP server, with reduced functionality (no searching, voting, etc),

what worked

WP worked okay as a content management system for pages. Enough of us had the ability to edit and create new pages.

The daily interactive timetable seemed popular - having hyperlinks between presenters, sessions, rooms etc. Icons for various highlighted talks, bookmarks etc.

what didn't work

In the early days the site would crash under moderate load, due to MySQL dying. A watchdog script was written to restart MySQL on its demise. For the time nearer the conference the Amazon instance was upgraded.

what would we do differently

• Make the conference management system design a priority from day one.

• Use a single integrated conference management solution - payment, registration, submission, timetabling.

• Possibly get that solution from an external provider, the most obvious being Eldarion who develop python conference solutions based on Symposion, an open-source conference system.

Entertainment

After-skool fun.

Timeline

The timeline from winning the bid to the event starting

During the event

Stuff that went down at the event and how we reacted to things to keep everything on track