As described in the last post, we’re working on general event types that can plug in Mozilla’s programmatic content. See the [Mozilla Event Menu Lite](http://michellethorne.cc/2012/01/mozilla-event-menu-lite/) for more background.
[Brett Gaylor](http://etherworks.ca/) and I took a first stab at a **[hack jam kit for video-makers](https://wiki.mozilla.org/Events/Hack_Jam/Popcorn).** This kit builds on previous workshops run by Brett & the Popcorn team together with partners like Independent Television Service (ITVS) and Bay Area Video Coalition (BAVC). [This piece in WIRED](http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1) summarized the recent ITVS jam quite well.
This is the draft we sent to a few film festivals and other video-related programs looking to host hack jams for Popcorn. You can also grab the [PDF](https://wiki.mozilla.org/images/0/01/Popcorn_hackjam.pdf) or [check out the wiki page](https://wiki.mozilla.org/Events/Hack_Jam/Popcorn). Let us know what you think — and if you’re interested in getting involved!
# Mozilla Hack Jam for Video-Makers #
## What ##
A **Mozilla Hack Jam for Video Makers** is a two-day event that teams up video makers with web developers. Interactive video projects are built from concept to running code over the course of the event, using open tools and collaborative design.
Every team is expected to make a **“minimum viable product”** that works, albeit roughly, by the end of the hack jam.
The motto: **Less yak, more hack!**
Participants will learn about the power of web cinema, how to develop projects based on their interests, and about the benefits of collaboration and working in the open.
Hack jams can be hosted in partnership with Mozilla, who provides facilitation experience and extensive knowledge of key software, in particular Popcorn.js, a Javascript library for HTML5 video.
Mozilla will work with partners to ensure participants leave with both a **deeper understanding of the web as a storytelling medium and improved video projects.**
Hack jams can also be self-organized following this handy guide! [PDF](https://wiki.mozilla.org/images/0/01/Popcorn_hackjam.pdf)
## Who ##
Teams consist of:
* Video-makers with an existing project
* Web developers skilled in Javascript
Each video project is paired with at least one developer. Facilitators and web designers are also key roles at the hack jam.
## How ##
### Pre-Hack Jam Engagement ###
Mozilla and partners identify the participating video projects. **Ideal candidates are video-makers with existing video and a vision for improving it with interaction on the web.**
Through lightweight interviews, each video-maker is paired with a web developer whose interests and skill-set meets the video-maker’s vision.
The newly-formed team discusses the vision determine if any further preparation should be done in advance of the hack jam.
### Agenda ###
All the participants and facilitators meet on Day 1 for a **group briefing.** Demos of web cinema, including common templates and plugins, are shown and discussed. If needed, a quick crash-course on Popcorn will be provided. Each project presents it’s vision for the hack jam.
The group breaks into the small teams and **determine how they’ll work together.** Some might use napkin-sketches to quickly test ideas and interfaces. Some might already have code prepared. Some might address shared problems and team up. This is where facilitators can be especially helpful ensuring each team makes the most out of the time together.
Two-thirds through Day 1, **projects should be writing code** and creating the broad strokes of their experience. Day 1 ends with a group recap of where each project stands and would like to achieve the next day.
Day 2 opens with a quick welcome, and teams go to work on their project. The remainder of the day is a **“sprint to the finish”,** always with the expectation that teams will “ship” a final project at a screening and party.
**A screening and party** is held in the evening of Day 2 to demo final projects, collect feedback, and to celebrate all the hard work.
Before leaving, participants should **decide on next steps** for their projects. Examples include: continue hacking at an upcoming event, fold outcomes into an existing project, or publish results from the hack jam. Decisions on next steps are shared with the group and key stakeholders.
### Resources ###
* At least one computer per team.
* Video-editing software as well as a fast, modern browser.
* Popcorn.js installed.
* Video files for each project.
* Reliable wifi.
* Power outlets.
* Projector with suitable adapters
* Meals – events must be catered
* Amenities such as coffee, water, and snacks.
* Travel support to the hack jam, where needed.
## Case Studies ##
**Independent Television Service (ITVS) + Mozilla, San Francisco.**
[http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1](http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1 )
Video: [http://mozillapopcorn.org/the-living-docs-hack-day/](http://mozillapopcorn.org/the-living-docs-hack-day/)
**“ButterCamp”, NYC, March 2011.**
[http://mozillapopcorn.org/videoblog-buttercamp/](http://mozillapopcorn.org/videoblog-buttercamp/)
**Mozilla Festival, London. November 2011.**
[http://mozillapopcorn.org/what-we-made-at-mozfest/](http://mozillapopcorn.org/what-we-made-at-mozfest/)
**Bay Area Video Coalition + Mozilla (For youth), San Francisco.**
[http://mozillapopcorn.org/bavc/](http://mozillapopcorn.org/bavc/)
*Photos: [CC BY-NC-SA](https://creativecommons.org/licenses/by-nc-sa/3.0/) by [Jonathan Mcintosh](www.flickr.com/photos/jonathanmcintosh/sets/72157628099406338/with/6332190107/)*
As described in the last post, we’re working on general event types that can plug in Mozilla’s programmatic content. See the [Mozilla Event Menu Lite](http://michellethorne.cc/2012/01/mozilla-event-menu-lite/) for more background.
[Brett Gaylor](http://etherworks.ca/) and I took a first stab at a **[hack jam kit for video-makers](https://wiki.mozilla.org/Events/Hack_Jam/Popcorn).** This kit builds on previous workshops run by Brett & the Popcorn team together with partners like Independent Television Service (ITVS) and Bay Area Video Coalition (BAVC). [This piece in WIRED](http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1) summarized the recent ITVS jam quite well.
This is the draft we sent to a few film festivals and other video-related programs looking to host hack jams for Popcorn. You can also grab the [PDF](https://wiki.mozilla.org/images/0/01/Popcorn_hackjam.pdf) or [check out the wiki page](https://wiki.mozilla.org/Events/Hack_Jam/Popcorn). Let us know what you think — and if you’re interested in getting involved!
# Mozilla Hack Jam for Video-Makers #
## What ##
A **Mozilla Hack Jam for Video Makers** is a two-day event that teams up video makers with web developers. Interactive video projects are built from concept to running code over the course of the event, using open tools and collaborative design.
Every team is expected to make a **“minimum viable product”** that works, albeit roughly, by the end of the hack jam.
The motto: **Less yak, more hack!**
Participants will learn about the power of web cinema, how to develop projects based on their interests, and about the benefits of collaboration and working in the open.
Hack jams can be hosted in partnership with Mozilla, who provides facilitation experience and extensive knowledge of key software, in particular Popcorn.js, a Javascript library for HTML5 video.
Mozilla will work with partners to ensure participants leave with both a **deeper understanding of the web as a storytelling medium and improved video projects.**
Hack jams can also be self-organized following this handy guide! [PDF](https://wiki.mozilla.org/images/0/01/Popcorn_hackjam.pdf)
## Who ##
Teams consist of:
* Video-makers with an existing project
* Web developers skilled in Javascript
Each video project is paired with at least one developer. Facilitators and web designers are also key roles at the hack jam.
## How ##
### Pre-Hack Jam Engagement ###
Mozilla and partners identify the participating video projects. **Ideal candidates are video-makers with existing video and a vision for improving it with interaction on the web.**
Through lightweight interviews, each video-maker is paired with a web developer whose interests and skill-set meets the video-maker’s vision.
The newly-formed team discusses the vision determine if any further preparation should be done in advance of the hack jam.
### Agenda ###
All the participants and facilitators meet on Day 1 for a **group briefing.** Demos of web cinema, including common templates and plugins, are shown and discussed. If needed, a quick crash-course on Popcorn will be provided. Each project presents it’s vision for the hack jam.
The group breaks into the small teams and **determine how they’ll work together.** Some might use napkin-sketches to quickly test ideas and interfaces. Some might already have code prepared. Some might address shared problems and team up. This is where facilitators can be especially helpful ensuring each team makes the most out of the time together.
Two-thirds through Day 1, **projects should be writing code** and creating the broad strokes of their experience. Day 1 ends with a group recap of where each project stands and would like to achieve the next day.
Day 2 opens with a quick welcome, and teams go to work on their project. The remainder of the day is a **“sprint to the finish”,** always with the expectation that teams will “ship” a final project at a screening and party.
**A screening and party** is held in the evening of Day 2 to demo final projects, collect feedback, and to celebrate all the hard work.
Before leaving, participants should **decide on next steps** for their projects. Examples include: continue hacking at an upcoming event, fold outcomes into an existing project, or publish results from the hack jam. Decisions on next steps are shared with the group and key stakeholders.
### Resources ###
* At least one computer per team.
* Video-editing software as well as a fast, modern browser.
* Popcorn.js installed.
* Video files for each project.
* Reliable wifi.
* Power outlets.
* Projector with suitable adapters
* Meals – events must be catered
* Amenities such as coffee, water, and snacks.
* Travel support to the hack jam, where needed.
## Case Studies ##
**Independent Television Service (ITVS) + Mozilla, San Francisco.**
[http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1](http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1 )
Video: [http://mozillapopcorn.org/the-living-docs-hack-day/](http://mozillapopcorn.org/the-living-docs-hack-day/)
**“ButterCamp”, NYC, March 2011.**
[http://mozillapopcorn.org/videoblog-buttercamp/](http://mozillapopcorn.org/videoblog-buttercamp/)
**Mozilla Festival, London. November 2011.**
[http://mozillapopcorn.org/what-we-made-at-mozfest/](http://mozillapopcorn.org/what-we-made-at-mozfest/)
**Bay Area Video Coalition + Mozilla (For youth), San Francisco.**
[http://mozillapopcorn.org/bavc/](http://mozillapopcorn.org/bavc/)
*Photos: [CC BY-NC-SA](https://creativecommons.org/licenses/by-nc-sa/3.0/) by [Jonathan Mcintosh](www.flickr.com/photos/jonathanmcintosh/sets/72157628099406338/with/6332190107/)*
Comment (1)