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
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.
LOC communication
fortnightly web meetings
Face 2 Face meetings
what worked
what would we have done differently
Venue
General comments
what worked
what didn't work
what would we do differently
WiFi
Gets its own topic? or could be a sub-heading in venues
what worked
what didn't work
what would we do differently
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
selecting papers
keynotes
streams
what worked
what didn't work
what would we do differently
Merchandise
General comments on the FOSS4G branded kit (banners, t-shirts, and the stuff in the delegate packs)
what worked
what didn't work
what would we do differently
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
what didn't work
what would we do differently
Academic track
Everything relating to the academic track, papers, journals, mixing the presenter in and around the main prog and academic bursaries
what worked
what didn't work
what would we do differently
Website
FOSS4G web presence - did it work, what tools did we use and why
what worked
what didn't work
what would we do differently
Entertainment
After-skool fun.
what worked
what didn't work
what would we do differently
Timeline
The timeline from winning the bid to the event starting
August 2012
Sept 2012
During the event
Stuff that went down at the event and how we reacted to things to keep everything on track