Tag Archives: hack-day

How should a hackday be run?

I’m working with a large public-sector organisation who have a considerable — and potentially very useful — body of data. They’re keen to open it up, and would like to encourage people to use it by having a hack event of some kind. At the same time, it’s gratifying that they’re clear that they don’t wish to unfairly exploit anyone.

We’re considering a number of options, and would welcome comments and additional suggestions.

The event could be held in the Midlands; over one day or two, on weekdays, weekend, or Friday-Saturday. Or a competition could be announced online, with a virtual or real-life “dragons den” type event, for people to present things they’ve worked on at home.

Cray-2 super computer

You won’t need one of these to take part…
Computer Museum: Cray-2 by cmnit, on Flickr, CC-BY

Should we set a specific challenge, or just ask people to do something interesting with the data?

I’ve suggested prizes might be offered for both the most compete solution, and the best idea, whether compete or not. There might be prizes in other categories, such as the best idea by a young person or the most accessible product, or different categories for commercial and hobbyist entrants.

The data holders might also like to consider developing business relationships to the developers of one or more of the products, separate to any prize giving; rights in all the entries would of course remain with their developers, otherwise.

How would you like such an event to happen? We’re aware of the Hackday Manifesto, but what else is best practice, and what other pitfalls should be avoided?

Over to you…

Wi-Fi checklist for unconference or hack-day organisers

Do you want to see your event branded a #WiFi #FAIL on Twitter?

In the last couple of years, I’ve been to or worked at a lot of unconferences, hack-days, social media cafes, social media surgeries, “tweet-ups” and similar events. I’ve had great fun, speaking at several, organising HyperWM & BrewCamp and facilitating ShropCamp. Unfortunately, at some of the events I’ve attended, the provision of Wi-Fi has been, shall we say, problematic. By which I mean awful. That’s frustrating for attendees and a right pain in the proverbial for those seen as responsible.

Frustration (was: threesixtyfive | day 244)

For some reason, the public sector (with honourable exceptions) don’t seem as capable of providing usable Wi-Fi as the private sector. If small independent coffee shops can get this right, then councils and colleges should be able to.

So here, for people organising hack-days, unconferences, and similar happenings, is a Wi-Fi checklist, based on the problems I’ve encountered as an event organiser and as a participant:

wifi

  • Make sure the staff at the venue know in advance that you will be needing Wi-Fi, and that your event depends on it working properly. If you’re paying for the venue, make it part of the deal, and have your requirements, in writing, signed off.
  • Check that the Wi-Fi is secure. If it isn’t, will your audience be prepared to use it? Will you?
  • Make sure your contact at the venue knows how the Wi-Fi works, what passwords are required and whether guest accounts need to be set up, and what the passwords and account IDs are.
  • Explain that your audience will need access to sites the venue may have blocked, such as Twitter, You Tube, WordPress.com, Google Docs and so on. And yes, I’ve known public sector organisations where all of those were blocked.
  • Before the event, test the Wi-Fi yourself, making sure you visit such sites.
  • Test the Wi-Fi on multiple devices, including non-Windows laptops and smart phones — one venue I visited had Wi-Fi that would only work on Windows devices.
  • If you’re providing each participant with a guest account, make sure it will work on multiple devices simultaneously; or provide spare accounts. I went to one event where I needed to use two devices, but my guest account would only support a single log-in.
  • Check that the Wi-Fi works where you will be meeting, including any breakout rooms — I’ve been to one event where people wanting to use Wi-Fi had to leave the meeting room and work in a stairwell.
  • Check the bandwidth. 4Mbps download and 500 Kbps upload may be adequate at home, but with dozens of people downloading — and hopefully uploading media —  at once, it will soon start to feel like a dial-up connection.
  • Know who to contact, and where to get hold of them, if the Wi-Fi goes down during the event. Make sure they don’t plan to be away for part of the day, and get a second contact if you can.
  • Have a 3G dongle on hand, equally tested (can you get a signal in your rural basement meeting room?), for any live presentations.
  • Plan how you will run things if the Wi-Fi (or the dongle) does die. Have archived copies of any websites you want to demonstrate, or video of live interactions, on a local hard drive. Have a spare speaker in the room, or a later speaker prepared to move up the running order at short notice (or at least learn some good jokes), in case a planned video-conference speaker disappears into the ether.
  • Provide ample power sockets and extension leads. It’s no use having Wi-Fi if people’s devices are dead by mid-afternoon.
  • On the day of the event, arrive in ample time and check that the Wi-Fi is on and working properly.
  • Relax and enjoy your event!

What other Wi-Fi related tips do you suggest?

One of the things I’ll be doing as part of my new freelance career is helping organisations to plan and run events; and live-blogging them. How can I help with yours?