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

General

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 breakout format

Complet break out

Sessions

Wednesday 11 December (Day 1)

SWOT session

S Strengh Number of resources Diversity of projects Open & editable resources Evolution and iterative Care Teaching and learning Accessible for almost all Each project has a leader (point person) Priority Diversity of people Long history Localizing resources

W Weakness Lack of focus Conflicting or out of date information Sprawling resources Redundancies Hard to identify leader Resisteance to retire things Lack of shared vision Hesitation to share (sometimes) Hard to sustain intiatives

O Opportunity 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 organisation Reps and FSA Working with external partners Clear invitation to participate and contribute Default open Clear indication when something should *not* be shared

T Threat 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

Top 5 Priorities

Diversity of people (Strength)

---

What

What do we mean by "diversity": diversity is a practice not a thing, skills, interests, hobbies, economic status, learning styles, country of orgin, language, etc. anything and everything that makes you you.

How (assets)

Making our sources of knowledge accessible to everyone: localization, accesibility, time/place, etc. Support a mindset where every mozillian thinks about approach solutions in the most inclusive way. Add human part/full potential/not seeking permission/how you show up

Actions

• Identify what various communities mean by diversity and how they want to diversify their communities.
  • Survey on diversity -
  • Using the Diversity Working Group and the DICE workshop
  • Note: Survey development/completion should not block smaller efforts to increase diversity.

Revised actions

• Create a survey to identify: what diversity means across the org, asses current demographics, what areas of diversity needs improvement, identify barries to local leadership and community building
• Using the Diversity Working Group and the DICE workshop
• Note: Survey development/completion should not block smaller efforts to increase diversity.

Owners

Lukas (Dino co-lead/support)

Resources needed

• Time and webdev assistance to help craft workshop tools
• Proper survey consultation for creating pre & post workshop survey about diversity and visualize the data over time/cohort
• localization of workshop materials

Teach openness (opportunity)

---

What

Sharing and collaborating whenever possible; presuppose all can be open and that which cannot be is called consciously closed; also learn about the tools that help you contribute openly

Why

Part of our mission. And it makes the world better. Enables participation.

How (assets)

Test and help build the teaching resources and trainings in Webmaker and create more resources aligned with the Web Literacy Framework. https://webmaker.org/standard

Actions

• Identify what various communities mean by diversity and how they want to diversify their communities.
• Index resources. Identify if they are open, consciously closed. A way to visualize.
  • name of resource
  • how to access
  • who can access (public, privledged)
  • who is lead contact person
  • how to contribute (user-editable vs siloed)
• URLs can be collected, searched and tagged using webmaker.org. Mozillians and the broader world can use these resources to learn about openness.

Revised actions

• Plan new TRIBE module around teaching "openness"; use this model as a template for creating additional modules. Explore module creation processes using by testing a module around 'openness' as a model.
• Index resources. Identify if they are open, consciously closed. A way to visualize (flags to indicate: open/not(yet), a11y, localized, read-only vs. accepting contributions, production-level supported service, has owner(s)?) . Resouces should be user-editable by default.

Owners

Christie

Resources needed

Mandate unity across the board (opportunity)

---

What

unify, grow, and scale contributors in support of the 1MM goal.

How (assets)

Actions

• Broadcast resource index initiative. Demonstrate we're working together and that people can join.
• Work with other teams to create a grass roots campaign to support this goal.
• Can use the #millionmozillians template for people to say how they will help reach the goal. See example: https://fuzzyfox.makes.org/thimble/a-million-mozillians and more https://webmaker.org/en-US/search?type=tags&q=millionmozillians

Revised actions

• Communicate efforts of the education team and show how anyone can get involved.
• Campaign to show efforts to the index resource
• Repurpose the #millionmozillians template in a campaign for people to say how they will help the goal.

Owners

Dino

Resources needed

Mentoring and leveling up after on-board (Weaknesses)

---

What

Supporting individuals throughout the contributor lifecycle: introduction to program, recruiting, on-boarding, escalation of responsibilities, skill building, leadership, de-boarding, alumni network/support.

How (assets)

Actions

• Bring new voices into the discusion to vet/refreash existing content.
• Rethink how the 90 day on-boarding tool can be available to help with the life-cycle of a contributor (from on-boarding to off-boarding).
• Leverage the TRIBE mentorship program to extend mentoring in the org and also certify skill levels.
• Get on-boarding materials into a place on the web that you can i) find later and ii) add to.
• Design and implement badges: mentor levels, learning levels [work w/Recognition]

Revised actions

• Expand access to the on-boarding portal and create an index of the content on wiki.mozilla.org. Incorporate existing community-based on-boarding material.
• Explore expanding/scaling/copying existing mentoring programs (Reps, local communities) for scalability across Mozilla.

Owners

Amie + Ally

Resources needed

Distributed Leadership (opportunity)

---

What

diversified decision makers, leadership in more geos, x-functional leadership so that *efficient* knowledge distribution happens, keeps the org informed and progress moving forward .

How (assets)

Actions

• those gaps become asks
• Advise the TRIBE program to incorporate "teach openness" resources and other topics. [help to design a modual structure]
• Learning to make resources available to all levels
• Support wiki.mozilla.org as a top-level product and teach people how to use it effectively.
• Incorporate questions in the diversity survey about barriers to local leadership and community building. [move up to "Diversity"?]

Revised actions

• Make TRIBE training acessible to more Mozillians (literally accessible, ReMo in 2014). [& Manager Hacking?]
• Plan a community building curriculum and test it by training some brave Mozillians. !!!!!!!!!
• Assign owner(s) who can prioritize turning wiki.mozilla.org into a top-level product, train the entire community on how to use it effectively so that its value increases to the project and facilitates p2p-exchange of knowledge. (localize it, organize it better, make things discoverable, let it be more customizable, bring in visual editing, make sure it's accessible to all)

Owners

Michelle (Ally would like to support this/co own)

Resources needed

Amie

Other priorities ordored by number of votes

1. Have to work with partners who are not open (threats) (Teaching openness?)
2. Loss of Mozilla's culture (threat)
3. Find the right resource for the right need (Weaknesses)
4. Deafult open (opp)
5. Hard to sustain initiatives (Weaknesses)
6. Teaching and Learning (part of NoM)(Strength)
7. Bad internet trends (Threats)
8. Lack of metrics and clear definitions (Threats)
9. Clear invitation to participate and teach
10. Localizing resources

Second day

Carousel notes about work Day 1

1. Working with Pathways on drop-off

2. Mitchell wants more leaders in the organisation

3. Priorities : How do we scale our culture?

• Diversity
  • Cultural
  • Geographic (both what we have and what we don't have yet)
• Teaching Openness
  • Domain experts
  • Sharing with partners (FxOS)
  • How does this differ for different groups?
  • Leading by example
• Mentoring and Onboarding
  • Whole cycle
  • Smooth pathways and transitions (always a Moillian?)
• Distributed Leadership
  • Cultural customisations
• Unity and focus
  • Intention to communicate
  • Bottom-up mandate?

Third day

Final Action Plan/Action List

• Create a survey to identify: what diversity means across the org, asses current demographics, what areas of diversity needs improvement, identify barries to local leadership and community building [#diversity][#leadership]

• Plan new TRIBE module around teaching "openness"; use this model as a template for creating additional modules. Explore module creation processes using by testing a module around 'openness' as a model. [#teach openness]

• Index resources. Identify if they are open, consciously closed. A way to visualize (flags to indicate: open/not(yet), a11y, localized, read-only vs. accepting contributions, production-level supported service, has owner(s)?) . Resouces

should be user-editable by default. [#teach openness][#unify]*Communicate efforts of the education team and show how anyone can get involved. [#Unity]

• Campaign to show efforts to the index resource [#Unity]

• Repurpose the #millionmozillians template in a campaign for people to say how they will help the goal. [#Unity]

• Expand access to the on-boarding portal and create an index of the content on wiki.mozilla.org. Incorporate existing community-based on-boarding material. [#mentoring/on-boarding]

• Explore expanding/scaling/copying existing mentoring programs (Reps, local communities) for scalability across Mozilla. [#mentoring/on-boarding]

• Make TRIBE training acessible to more Mozillians (literally accessible, ReMo in 2014). (& Manager Hacking?) [#distributed leadership]

• Plan a community building curriculum and test it by training some brave Mozillians. !!!!!!!!! [#leadership][#teach openness]

• Lead improvements to wiki.mozilla.orgt, train the entire community on how to use it effectively so that its value increases to the project and facilitates p2p-exchange of knowledge. (localize it, organize it better, make things discoverable, let it be more customizable, bring in visual editing, make sure it's accessible to all) [#leadership] [#mentoring/on-boarding] [#unity]

Measuring Success

• Events
  • Planning - events, budget, presentation

• Resource/content database - what kind of resources can we make available to help people; can have event consultant/buddy; local area database; one central repository to see

• Feedback Process + implementation - we are not always good at giving feedback or sourcing feed; we need to capture better info; how do we get feedback from our volunteers to; how do we use the feedback to improve the next event [implementation]

• Improving training opportunities - train the trainer, training opp in emerging communities

• Even Barriers - we put in place an event that people do not want to repeat; how do we lower the barriers; is it possible to make a leader or designate a person to manage the project