Contribute/Education/Notes/2013-12-13 Commmunity Builders Meetup

Raw notes: [1]

---

Statement

The education/culture track will build an action plan around curricula, tools and programs both (1) to support staff in learning to work in the open and support volunteer contributors, and also what curriculum, tools and programs are needed (2) to support volunteers in becoming active/core contributors.

How to

Three axes were identified:

• Broaden: Assess and inform the status of Mozilla's diversity and levels of openness. Advise on actions to broaden participation in the project.
• Share: Promote "default open" by indexing and unifying resources with an emphasis on improving wiki.mozilla.org.
• Teach: Develop and incorporate existing curricula to on-board and mentor Mozillians through their contribution lifecycle.

Main Goals

Increase "default open" in the project

• To broaden: conduct a contributor census including attitudes towards openness and diversity
  • Measured by: sentiment towards openness and inclusion
• To share: index wiki.mozilla.org
  • Measured by: number of edits on the wiki
• To teach: publish and expand the on-boarding content.
  • Measured by: number of Mozillians who complete the on-boarding

Increase community building capacity in the project

• To broaden: repurpose the #millionmozillians and and community quilt projects to learn about the health of communities and commitments to the Million Mozillians goal.
  • Measured by: Quilt participation (number of tiles made).
• To share: Consistent comms and cadence on past accomplishments, biggest challenges (pain points), upcoming goals
  • Measured by: Establish communication cadence [X communications per quarter for the year]
• To teach: to develop and run a CB curriculum
  • Measured by: How many people completed the training

Sessions and workshops

Wednesday December 11th - SWOT + Priorities Setting [1 Hour]

Goal

Participants are asked to identify the strengths, weaknesses, opportunities and threats related to their specific community building pillar. This will help serve as the contextual backdrop for the rest of the session.

Assets mapping

• Strengths

number of resources, diversity of projects, open & editable resources, evolution + iterative, care, teaching + learning, accessible for allmost all, each project has a leader/point person, priority, diversity of people, long history, localizing resources.

• Weaknesses

lack of focus, conflicting or out of date info, sprawling resources, redundancies, hard to identify leader, resisteance to retire things, lack of shared vision, hesitation to share (sometimes), hard to sustain intiatives

• Opportunities

distributed leadership, millian mozillians goal, desire to do more & better, to teach openess, platform ("mozillia") that many pay attention to, to tell mozillia's story, alumni network (de-boarding), mandate unifying across the org, reps + fsa, working with external partners, clear invitation to participate and contribute, default open, clear indication when something should *not* be shared

• Threats

privacy, trying to do too much, too many people coming on board, loss of Mozilla's culture, tunnel vision if too exclusive of org's goals, lack of metrics + clear definition, anti-open source attitudes, we have to rely on partners that are not open, hubris, missing people who aren't in spaces we're active in, credibility ep of mozilla as an educator, possibly seen as self-serving