How to make your own mini-MozFest

This new debrief and documentation from the 2012 Mozilla Festival lays out the key ingredients, reviews and recommendations.

Mozilla Festival

How do you turn dull conferences into festival-style jams packed with more hack / less yak? Michelle Thorne’s full “Aftermath Report” from the 2012 Mozilla Festival is so thorough and open, it basically provides an introductory blueprint for others thinking about hosting their own #MozFest-style event. Recommended reading for anyone interested in creative community-powered event design.
Mozfest_11Nov_050

A MozFest Manifesto?

Excerpting from Michelle’s post:

  1. Make everything hands-on, hackable, and collaborative. Participants hack and learn in small, decentralized groups. Sessions focus on solving real problems and teaching applicable skills. The schedule is always evolving in response to participants’ interests.
  2. Learn who is building what, and how they can share and help each other. The opening Science Fair and closing demo party help with this.
  3. Fuel leaders who want to invent, teach and organize. For us, that meant planning sessions with community members to design next year’s Summer Code Party and the growth of the global Hive network.
  4. Design the things you want to build next. For us this year it was two important new verticals: mobile and games.
  5. Use an open submission process. Hold a facilitator “boot camp” before the event. Designate community “space wranglers.” (Lots more detail on all the nuts and bolts in Michelle’s post.)

Mozilla Festival

Reviews from participants

Mozilla Festival
Get involved

  • Host your own Webmaker event. Our handy event kits make it pretty easy.
  • Help turn this into HOW TO documentation. Get in touch with Michelle if you’re interested in helping to turn her post into a more robust HOW TO.
  • Check out the feedback on recommendations for next year’s MozFest. Rough etherpad notes from our last Webmaker community call.

Submit a comment

Your email address will not be published. Required fields are marked *