Events/Hack Jam/Popcorn - Revision history

Mdthorne: /* What */

2012-01-24T14:08:53Z

What

← Older revision		Revision as of 14:08, 24 January 2012
Line 19:		Line 19:
	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.'''		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!		Hack jams can also be self-organized following this handy guide! '''Download the [[Media:Popcorn_hackjam.pdf\|PDF]].'''

	== Who ==		== Who ==

Mdthorne at 14:06, 24 January 2012

2012-01-24T14:06:18Z

← Older revision		Revision as of 14:06, 24 January 2012
Line 10:		Line 10:

	The motto: '''Less yak, more hack!'''		The motto: '''Less yak, more hack!'''

			[[File:Popcorn_hackjam2.png\|right]]

	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.		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.
Line 20:		Line 22:

	== Who ==		== Who ==
	~~[[File:Popcorn_hackjam2.png\|right]]~~

	Teams consist of:		Teams consist of:
	* Video-makers with an existing project		* Video-makers with an existing project
Line 31:		Line 31:

	=== Pre-Hack Jam Engagement ===		=== Pre-Hack Jam Engagement ===
	[[File:Popcorn_hackjam3.png\|~~left~~]]		[[File:Popcorn_hackjam3.png\|right]]
	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.'''		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.'''

Line 41:		Line 41:
	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.		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.

	[[File:Popcorn_hackjam4.png\|~~right~~]]		[[File:Popcorn_hackjam4.png\|left]]

	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.		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.
Line 47:		Line 47:
	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.		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.

	[[File:Popcorn_hackjam5.png\|~~left~~]]		[[File:Popcorn_hackjam5.png\|right]]

	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.		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.

Mdthorne: /* Case Studies */

2012-01-24T14:04:04Z

Case Studies

← Older revision		Revision as of 14:04, 24 January 2012
Line 69:		Line 69:

	== Case Studies ==		== Case Studies ==
			'''Independent Television Service (ITVS) + Mozilla, San Franciso.'''
			http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1
			Video: http://mozillapopcorn.org/the-living-docs-hack-day/

	~~Independent Television Service (ITVS) + Mozilla~~, ~~San Franciso. October~~ 2011.		'''“ButterCamp”, NYC, March 2011.'''
	~~http://www.wired.com/underwire/2011/10/coders-filmmakers-popcorn/all/1~~		http://mozillapopcorn.org/videoblog-buttercamp/
	~~Video:~~ http://mozillapopcorn.org/~~the-living-docs-hack~~-~~day~~/

	Mozilla Festival, London. November 2011.		'''Mozilla Festival, London. November 2011.'''
	http://mozillapopcorn.org/what-we-made-at-mozfest/		http://mozillapopcorn.org/what-we-made-at-mozfest/
	~~Video: https://www.youtube.com/watch?v=zeiO9dS29Bo~~

	~~(For youth)~~ Bay Area Video Coalition + Mozilla, San Francisco. ~~August, 2011.~~		'''Bay Area Video Coalition + Mozilla (For youth), San Francisco.'''
	http://mozillapopcorn.org/bavc/		http://mozillapopcorn.org/bavc/

			''Photos: CC BY-NC-SA by Jonathan Mcintosh''

Mdthorne: /* How */

2012-01-24T14:02:28Z

How

← Older revision		Revision as of 14:02, 24 January 2012
Line 31:		Line 31:

	=== Pre-Hack Jam Engagement ===		=== Pre-Hack Jam Engagement ===
			[[File:Popcorn_hackjam3.png\|left]]
	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.'''		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.'''

Line 38:		Line 39:

	=== Agenda ===		=== 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.

	[[File:~~Popcorn_hackjam3~~.png\|~~left~~]]		[[File:Popcorn_hackjam4.png\|right]]

	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.		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.

	~~[[File:Popcorn_hackjam4.png\|right]]~~

	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.		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. [[File:Popcorn_hackjam5.png\|left]]		[[File:Popcorn_hackjam5.png\|left]]

			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.		'''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.

Mdthorne: /* Agenda */

2012-01-24T13:47:50Z

Agenda

← Older revision		Revision as of 13:47, 24 January 2012
Line 49:		Line 49:
	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.		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.		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. [[File:Popcorn_hackjam5.png\|left]]

	~~[[File:Popcorn_hackjam5.png\|left]]~~

	'''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.		'''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.

Mdthorne: /* Resources */

2012-01-24T13:46:53Z

Resources

← Older revision		Revision as of 13:46, 24 January 2012
Line 59:		Line 59:
	=== Resources ===		=== Resources ===

	* At least one computer per team.		* At least one computer per team.
	* Video-editing software as well as a fast browser.		* Video-editing software as well as a fast, modern browser.
	* Popcorn.js installed.		* Popcorn.js installed.
	* Video files for each project.		* Video files for each project.
	* Reliable wifi.		* Reliable wifi.
	* Power outlets.		* Power outlets.
	* Projector with suitable adapters		* Projector with suitable adapters
	* Amenities such as coffee, water, and snacks.		* Meals – events must be catered
			* Amenities such as coffee, water, and snacks.
	* Travel support to the hack jam, where needed.		* Travel support to the hack jam, where needed.

Mdthorne: /* Agenda */

2012-01-24T13:46:10Z

Agenda

← Older revision		Revision as of 13:46, 24 January 2012
Line 39:		Line 39:
	=== Agenda ===		=== 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.		[[File:Popcorn_hackjam3.png\|left]]

	~~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~~.		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.

	~~Two-thirds through Day 1,~~ teams ~~circle back~~ and ~~share what they~~'~~ve done so far~~. ~~The group provides feedback~~. ~~The teams return to their project~~. ~~Day 1 ends with a recap of~~ where each ~~project stands and would like to achieve~~ the ~~next day~~.		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.

	~~Day 2 opens with a quick welcome, and teams go to work on their project~~.		[[File:Popcorn_hackjam4.png\|right]]

	~~By the afternoon of~~ Day 2, ~~teams wrap up their work~~ and ~~outline next steps. Some might decide to meet later and continue hacking. Others might have upcoming events or ongoing projects where they can continue to improve~~ the ~~video~~. ~~Others will be finished~~ with ~~what they set out~~ to achieve.		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 ~~closes~~ with a screening of the projects ~~with feedback followed by a group discussion about what they learned~~, ~~how they would improve~~ the hack jam~~, and their~~ next steps.		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.

			[[File:Popcorn_hackjam5.png\|left]]

			'''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 ===		=== Resources ===

Mdthorne: /* Pre-Hack Jam Engagement */

2012-01-24T13:36:29Z

Pre-Hack Jam Engagement

← Older revision		Revision as of 13:36, 24 January 2012
Line 31:		Line 31:

	=== Pre-Hack Jam Engagement ===		=== 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 ~~skillset~~ 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.		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 ===		=== Agenda ===

Mdthorne: /* Who */

2012-01-24T13:36:02Z

Who

← Older revision		Revision as of 13:36, 24 January 2012
Line 20:		Line 20:

	== Who ==		== Who ==
			[[File:Popcorn_hackjam2.png\|right]]

	Teams consist of:		Teams consist of:
	* Video-makers with an existing project		* Video-makers with an existing project
	* Web developers skilled in Javascript		* Web developers skilled in Javascript

	Each video project is paired with at least one developer.		Each video project is paired with at least one developer. Facilitators and web designers are also key roles at the hack jam.

	Facilitators and web designers are also key roles at the hack jam.

	== How ==		== How ==

Mdthorne: /* What */

2012-01-24T13:15:47Z

What

← Older revision		Revision as of 13:15, 24 January 2012
Line 2:		Line 2:

	== What ==		== What ==

			[[File:Popcorn_hackjam1.png\|left]]

	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.		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.