MozCamps 2014/Planning

From MozillaWiki
Jump to: navigation, search


April 2014 Design Session

  • Location: San Francisco, CA
  • Attendees:


Next Steps

Alpha Runs

Beta Run

  • Location: Bangalore/Mumbai, India
  • Date: June 21-22, 2014
  • Participants count: ~100

Potential structure

Potential structure for MozCamp India June 2014

Participation Criteria & Processes


These are the criteria for inviting a Mozillian to a MozCamp. A Mozillian may fulfill one or all of these criteria to be part of the MozCamps.


  • Commitment to promote the Mozilla mission and spread it among new people.
  • Participate in group initiatives to onboard new members.
  • Share knowledge through mentoring, blog posts, documentation, social media etc., so that other community members can learn from it.


  • Regional community leader: contributor who knows well the regional community and acts as leader communicating the organizational goals, getting the community active and excited and recruiting and mentoring new contributors
  • Mozillian with a good track record of organizing and leading events. However, a Rep might be good event organizer, but disconnected from the community. So, that needs to be factored in.
  • Mozillian with Community Building / Mentoring experience.


  • Pathways expert: expertise in specific pathway(s) with strong interest and experience onboarding new contributors
  • Active contributor focused on bringing in new active contributors, teaching or mentoring
  • Active contributor with a key role in a pathway who can benefit from learning how to mentor and bring in new contributors.


  • Over 18 years old at events that involves international travel, i.e., for following events in the countries we can have minors, but not in the beta MozCamp.
  • Proficient in their primary language.


There are two primary processes of inviting participants. One is a nomination-based proces and the other is an application-based process.


  • Key Reps community leaders nominate participants through range voting.
  • Make sure the pathway of the nominees is clear so that we can make sure there is a balance of participants.
  • Invitation Group with CBT, regional community manager from engagement and key local reps decide on final list.


  • Invite open applications based on the participation criteria.
  • Have key local reps and the functional area leads go through the list and do range voting.
  • Make sure the pathway of the nominees is clear so that we can make sure there is a balance of participants.
  • Invitation Group with CBT and regional community manager from engagement decide on final list.


(add notes for your group in the sections below)

Event Name and Branding

Structure & Agenda

The Event Funnel: Understand Mozilla and why you're here --> identify and build a community --> get the skills to teach that community --> develop a plan to implement in the near future


  • Weekend preferred for community, reps and volunteers
  • 2.5 days
  • Assign content wranglers for each track (Part 2+3) who manage people, time and funnel people through the learning experience

Day 1: Friday Afternoon (1-5pm)

  • Part 1
  • Welcome Reception (facilitate conversation for example: tell someone you don't know your Mozilla story, pick people from different countries)

Day 2: Saturday Full-Day (9-6pm)

  • Part 2 and 3
  • Team building (fun) activity at night

Day 3: Sunday Morning (9-3pm)

  • Part 4


Part 1: Telling the story

Goal: Teach how to share the Mozilla mission & story and how you fit into it (organizational and personal storytelling)

  • Whole team
  • Mozilla mission & story/how to tell it your way (include privacy in content, its embedded across many aspects)
  • Importance of community. Why we need contributors. Who are our current contributors and their stories
  • Company update on goals and roadmap
  • Relevant product updates
  • Who's here and what everyone's roles are. Attempt to level the playing field to show we are all here to learn together (mozfest style)
  • Set the tone of the event
    • Sprinting, collaborating and creating together (participatory). Show the Mozilla style of events and learning
  • Emotional appeal, we're family, you're here to help us grow our family..
  • Time for reflection & discussion at the end of the day.

Part 2: Community Building

Goal: Teach how to be a community builder

  • Guidelines and Resources
  • Management tips?
  • Contribution areas (include localization specific contribution), include privacy lens (toolkits for people really interested in privacy to take to next functional areas)
  • How do you grow a community, communicate and engage with them. RETENTION! how to communicate your actions back globally
  • Going beyond just sending emails and actually working with communities to be effective
  • How to motivate and avoid burnout
  • Teaching how to communicate Part 1 and how to spread that emotional appeal
  • Time for reflection & discussion at the end of the section.

Part 3: Training

Goal: Teach how to recruit, on-board and retain contributors (contribution pathway content)

  • events toolkit
  • tips on how to recruit & retain contributors - types of contributions
  • Additional time to create new sessions/ask attendees what they want to hear/work on and let attendees help create the agenda.
  • MDN
  • Coding
  • Webmaker
  • Engagement
  • Web compatibility
  • Privacy
  • QA
  • User Research
  • Time for reflection & discussion at the end of the section.

Part 4: Action Plan and Follow-up

Goal: Attendees leave with a plan on what to do next to implement a next Mozcamp

  • Action plan on how to run future Mozcamps in the area
  • Follow-up communications and pathways
  • Hack time to develop an action plan (template - 30/60/90 days)
    • playtesting of action plan
  • How to stablish a long term relationship
  • Gather the documentation
  • Do attendees have everything they need to run a similar event themselves?
  • Have learners playtest / teach each other in small groups
  • Time for reflection & discussion at the end of the section.
  • Ideas:
    • A pledge wall (then maybe everyone picks a pledge someone else put up and reads it out loud)
    • Turn to your neighbor say one thing you learned, swap partners a few times or do in a few big groups


Distributed Events Model


(put links to all relevant etherpads here)