View source for Contribute/Meetup/MountainView Aug 2014

{{contribute_nav_bar}}

=Purpose=

[[Image:Cb mid year meetup 2014 small.jpg|400px|right]]

This meetup is designed to bring together 3 of our community building working groups with internal Subject Matter Experts (community managers, Reps leadership) and internal client partners (functional area representatives). 

*During these three days we will work to identify support that the Community Building working groups can offer to our internal partners, as well as create an action plan that will help us get there.  
*We will also be focused on integrating solutions that our SME's have already implemented, and creating ways for those to be systematized across the organization.

=Attendees=
==Logistics==
We are in Mountain View in The Atom. 

Breakfast and lunch will be provided each day. Please come early if you want to take part in breakfast. 
Each breakfast and lunch will have gluten free and vegan options.  

Sessions run each day from  9-5pm Pacific time.  There will be a group dinner on Tuesday August 19th at 6pm at Amarin Thai.  Please attend that if you can. 
==Onsite==
*Larissa Shapiro (CBT)
*Michelle Marovich (CBT)
*Christie Koehler (CBT)
*Madalina Ana ( SUMO remote Day 1) 
*Brian King ( Reps/ Community Engagement)
*Jennie Halperin (CBT)
*Abulkadir Topal (SUMO)
*William Reynolds (Community Engagement)
*Elizabeth Noonan ( Brand/Engagement)
*Lyre Calliope (Pathways Working Group Core member)
*Emily Gologoski ( MoFo Badge Amazingness)
*Amy Tsay (AMO/Marketplace Community Manager )
*Rebecca Billings (QA Community Champion)
*Stacy Martin ( Privacy Maven)
*Janet Swisher ( Developer Relations Community Manager) 
*Mike Hoye ( Coding Community Manager) 
*Dietrich Ayala ( FxOS Community Ambassador and all around stellar human) 
*Amie Tyrrel ( People Team-- Core Contributor Recognition)
*Srikar Ananthula (Pathways Working Group Core member)
*Sean Bolton (CBT, Day 1)

==Remote==
===Remote Participation Info===
* Day 1 we will facilitate remote participation via Vidyo for the 3 Working Group Sessions.  The Introduction portion will be participatory and parts of it will not be geared to remoties.

*Day 2 we are staying flexible with the structure of the work, and will solve for remote participation for the people who appear on vidyo during the first part of the day.  ( 9-10am Pacific) 

*Day 3 This day is very remote friendly, we can collaborate on planning and documenting via IRC and over Vidyo.

=Agenda=
<b>Day 1:</b> This day is dedicated to working group updates as well as learning from our community building partners.  We will learn what they need from each working group in the coming months.   There will also be discussion of what is working well within the org, and where resources or changes are needed around Recognition/Pathways/Education

*9:00-10:00 Introduction
*10:00-10:15 Break
*10:15-11:30  Recognition Conceptualize/Share/Create ( Michelle)
*11:45-1:00  Lunch
*1:00-2:30  Pathways Conceptualize/Share/Create (Larissa) 
*2:30-2:45 Break
*2:45 - 4:15  Education Brainstorm (Christie) 

*6:30 Dinner at Amarin Thai for the whole group. 

<b>Day 2:</b> This day is about creating solutions to the high priority work we surfaced on Day 1. 
*9:00-9:45 Goal statement creation-- by end of 2015 "What are our end points?"
*9:45-10:00 Break
*10:00-10:45 Tools we need/have, Resources we need/have, Buy In we need/have
*11:00-12:00  New Badges System Overview-- provide a number of tools and resources for the above  
*12:00-1:00 Lunch
*1:00-2:45   Working Session 1
*2:45-3:00 Break
*3:00 - 4:45  Working Session 2

<b>Day 3:</b> This day is about documenting the solutions, and then clearing all the easy work immediately.   
 
*9:00-10:00 GROUP PHOTO 9:15am. Then regroup from yesterday.  Pick a project. Figure out how to attack it. Do that. 
*10:00-11:00 GROW call
*11:00-12:00 Documentation-- create clarity from our notes and discussions, capture it all on the wiki for next steps. 
*12:00- 1:00 Lunch
*1:00-1:30 Parking Lot 
*1:30-4:00 Clear the easy wins from our priority list together
*4:00-4:30 Plan for momentum-- what needs to happen next?  How will we communicate that?
*4:30-5:00 Celebrate/Closing  It's important that we are explicit about what we've achieved in these three days, and how we expect that to make a difference.  We should celebrate as well. 
==Pathways==
===Key Learnings and Discussions===
What are the key things we discussed, agreed upon, and want to share with the project?
* The working group discussed the needs of community builders and managers around the project and agreed that:
** the pathways working group has made progress this year in clarifying the role and scope of pathways but more work is needed
** there is not a project-wide agreement or alignment on the definitions of user/supporter/casual contributor/active contributor/core contributor and that lack is hurting forward progress.
** there is a substantive need for better support of brand new contributors in getting involved in Mozilla, finding the right pathway for them, and taking their first steps on it.
** the project continues to struggle in building pathways that bring people into important Mozilla initiatives and successfully connect them to the right work, especially at scale.

===Roadmap===
Insert links to updated roadmaps here
===Info for next steps===
Capture next steps, and how to engage here

==Education==
===Key Learnings and Discussions===
What are the key things we discussed, agreed upon, and want to share with the project?
===Roadmap===
Insert links to updated roadmaps here
===Info for next steps===
Capture next steps, and how to engage here
==Recognition==
===Key Learnings and Discussions===
These are the major themes that emerged in the recognition discussions:
* There is no system that tracks contribution activity and notifies community managers/ community leaders when people are doing good work that needs to be recognized. 
* We do not have a way to keep track of how specific contributors have been recognized across the project, which would help us have an understanding of where people are making an impact. 
* Recognition needs to be for quality, not for quantity of contribution efforts. 
* Recognition efforts for our active and core contributors needs to have a component of personal development to them. 
* We need to allow people to specify what types of contribution are meaningful to them and work toward a culture that makes recognizing a priority. 

None of this is surprising, it mirrors what we've been hearing from contributors for the last year and highlights the ways that the lack of a consistent system of recognition is hurting retention and satisfaction in the organization.  
We decided to stay focused on the wins we could make in 2014, that will have a high impact for the project.  For 2015, we need to have a long term planning discussion on how to address some systemic issues. 
===Road-map===
[[https://wiki.mozilla.org/Contribute/Recognition/Roadmap_v2|The road-map for Recognition can be found here]].

===Info for next steps===
Capture next steps, and how to engage here

==Organizational Support==

If there are resource requests that come out of this meetup, this is where we will capture them, along with the methods of asking for those resources. 

If we need executive or leadership support, this is where we will document it, and share plan for requesting specific support from appropriate people.

=Etherpad=

Find out more notes, links and other information on the etherpad for the meetup:
*Tuesday:  https://cbt.etherpad.mozilla.org/august-wg-agenda-Aug19
*Wednesday: https://cbt.etherpad.mozilla.org/august-wg-agenda-Aug20
*Thursday: https://cbt.etherpad.mozilla.org/august-wg-agenda-Aug21

=Photo Streams=

* Flickr : https://www.flickr.com/photos/ananthulasrikar/sets/72157646804826512/