Contribute/Archive/Community Building Team/Meetings/2014-08-04

From MozillaWiki
Jump to: navigation, search

Core team weekly meeting
Date & Time: Monday 4 August 2014 @ 5pm UTC
Location: CBT vidyo room (
Moderator: David
Last agenda + notes:
Parking lot:

  • Q&A with Mary Ellen

  • FYI about monthly Engagement meeting this Wednesday at 8:30 pacific.  Details below:

A few minutes before 8:30am Pacific / 16:30 UTC, go to Air Mozilla  and click the Sign In button on the right to sign in using the email  address you use for . 
This will allow you to view the stream as a vouched Mozillian. 

We have booked the SFO Yoshi space, MV Zombocom and TOR 5O High Park as well.

Vidyo Room: Engagement (8420)
Vidyo Room PIN: 2891

Dial In Information(**to be used by presenters and audio only participants**)
US: 1(650) 903-0800 then 92 ext 98420*2891#
Toll Free: +1 (800) 707-2533, pin 369 - then 98420*2891#

Air Mozilla Information
Accessibility: Mozilla Employees and Contributors Only
Note: To access link above you need to click the orange Persona "Sign In" button.

You can also follow along in our IRC channel and help take notes on etherpad: 

  • #engagement on IRC 

  • Breaking down real or perceived obstacles between community building and community engagement team
  • Opportunities to leveraging and synergizing the teams
  • It's a place for us to come together
  • Contributor engagement = Brian's team
    User engagement: Social media, email marketing, etc (Winston. Replacing that role now)
    Supporter engagement: Mobilizer, student ambassador, (Jessica)

Contributor engagement: Brian, reps program
Guillermo and Gen, Rosana (reps manager), William Reynolds, (someone whose name I did not hear)

  • Making connections between all the teams

The goal of Enabling Communities with Impact is something that we're focusing on still. Community is not only an important and evergreen part of our organization, but it's still a top-line goal.
Is there an opportunity to start being more systemic about our growth? It's not just quantity, but also quality.
Need appropriate tools and systems to support and measure both quantity and quality

We've been maybe a bit lost in the goal of enabling communities of impact? What are the highest points of leverage?

  • Organizing internal conversation to see how each of these contribution areas have been in support of this goal
  • Showing how community has both benefiting from and we've also been benefiting from communities

Sean take note, this student story from Dietrich is a story of community innovation

  • Getting someone in on the ground floor is the best way to get people involved
  • "How do we prove?" there are positive developments
  • "Are the seeds of intentionality there?"

Less about proving it and more about showing it

  • The first approach of going department by department was the best way to start, but probably not the best way to end
  • Now that we've gotten this, how do we continue
  • How does partnership and pathway working need to develop in ways other than just the functional area pathways we have been working on
  • how do we handle contributor dropoff and burnout

some things might be "one and done"
    other dropoff may show a problematic issue
    how do we avoid burning out core contributors and how do we build depth in so that when core people leave <- Community Commitment Curve helps us design this (

  • We have a level of organization that we've brought to the functional areas, but not a lot that we've brought to the regional areas. We could bring these to the regional areas as well

IE Grow

  • Helping projects grow in ways that we can support in terms of changing focus and matrices

If we're in a partnership and we're struggling to find ways of participating, functionally, regionally, geographically, and using a diagnostic tool to figure out where participation can be most useful
    User journey as a concept
    People are getting certain needs met through contribution
    Sometimes a functional area like QA may be a way to gain skills and mastery

  • Badges, for example is a way to discover complementary skills through skill attainment
  • The user journey and the Mozilla journey
  • That may be one of the skills needed to keep people around
  • We don't actually know if people are leaving, or if they're jumping around
  • There's a huge layer of people we need to be recognizing
  • Help people see where they can move and scale
  • Should our contribution pathways be visible?
  • Third dimension beyond product... Have we looked beyond product?
  • There's a tool that explains how we work with people in a way that's repeatable
  • We are currently very handson, but how do we replicate that on a larger scale?
  • The work we are going to do in the second half of the year is different from the first half
  • How do we productize these stories?
  • We need to have a philosophy around community building
  • "The Power Law" [by Jade..] focusing on power, how we can enable contributors and provide them with skills (Jennie)
  • There's a community building thing the week after MozFest
  • We can look beyond Open Source
  • How do we broaden our lens?

Douglas Atkin's book "The Culting of Brands" on brands (like cult brands)

  • What are the next steps with Mark?

Mark, Michelle T, Brian K, MaryEllen to touch base.
    Convene in person in mid-September
    First week of December to think about 2015

  • Can we bundle this internal communication theme to other things like get Involved?
  • how can we help with making connections
  •     show our work and tell our story
  • We're great!
  • Mary Ellen wants people to know the Mozilla philosophy on Community Building

Community Building needs a 'brand' so we can tell our story

  • Some things that we're doing is standard best practices, but the scale at which we're doing it is very open ended and people are excited by this
    David: "our culture is one of participation even if we are not on the community building team" so it's important to included and showcase others doing this, not just us

Community Building Superstars:
Keith Severson

implicit to explicit -> productizing community building -> making this all feel more tangible -> not just making tangible but showing how it is actually applied

Video of call is at: