On 18/05/16 09:38, Steven Sykes wrote:
Then I'll be seeing about finding a venue. UC seems a natural choice as it's close to public transport, various accommodation and other facilities - its downside is somewhere to put about 650 people in a single room for key note speakers etc (although there is streaming). I'll also be looking at the possibility of the Convention Centre. In either case I'm looking into meeting with people to see about using either facility.

Steven,

As an aside, where and how can you tell what seating size any of the lecture theatres are at UoC?

"The first thing to think about is your team. At the BoF, it was strongly suggested that you need around five to six people for a good bid. I've seen conferences run with fewer people than that, but it is risky. LCA is a large and complicated event these days, and with a planning horizon of around two years, you need to be prepared for there to be a fair bit of churn in your core organizing team. Some people will move away, or change jobs. Others might have a new child and discover they're much too busy for a conference as well. So, remember when you're putting that initial team together to pack in some extra folks in order to handle the churn. Most Australian capital cities have former LCA organizers in them these days as well (we call them ghosts in the Linux Australia community). You should try to find one or two of these people to be involved as well. For example, the Canberra bid committee currently stands at 14 people, seven or whom have been on a LCA core team before, 3 of whom have served on Linux Australia's national committee, and at least two of whom have run their local Linux User's Group at some point in the past. " - Michael Still (http://www.stillhq.com/conference/lca2013/bid/000003.html)

And very much looking forward to linux.conf.au 2017 in Hobart. https://hobart.lca2017.org

Andrew

_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users

Reply via email to