View source for 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 organisation==
details  Carousel , SWOT and three day process

=Sessions=

==Wednesday 11 December (Day 1)==

===SWOT session===
{{SWOT 
|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

|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

|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

|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===

<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
<h4>Diversity of people (strength)</h4> {{anchor|How to Get Started}}
<hr>
<div style="display:block;background-color:#d1dffa;-moz-column-gap:20px;padding:10px;margin-top:20px;-moz-border-radius:10px;">
<div style="width:100%;display:block;">
<div style="size:30px;color:red">'''What'''</div>
</div>
<div style="-moz-column-count:1;">
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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:10px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''How (assets)'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
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
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:10px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:10px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Revised actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:10px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Owners'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
Lukas (Dino co-lead/support)
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:10px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Resources needed'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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
</div>
</div>
</div>


<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
<h4>Teach openness (opportunity)</h4> {{anchor|How to Get Started}}
<hr>
<div style="display:block;background-color:#d1dffa;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="width:100%;display:block;">
<div style="size:30px;color:red">'''What'''</div>
</div>
<div style="-moz-column-count:1;">
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
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Why'''</div>
<div style="-moz-column-count:1;">
Part of our mission. And it makes the world better. Enables participation.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''How (assets)'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
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
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Revised actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Owners'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
Christie 
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Resources needed'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
</div>
</div>
</div>


<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
<h4>Mandate unity across the board (opp)</h4> {{anchor|How to Get Started}}
<hr>
<div style="display:block;background-color:#d1dffa;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="width:100%;display:block;">
<div style="size:30px;color:red">'''What'''</div>
</div>
<div style="-moz-column-count:1;">
unify, grow, and scale contributors in support of the 1MM goal. 
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''How (assets)'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Revised actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Owners'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
Dino 
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Resources needed'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">

</div>
</div>
</div>


<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
<h4>Mentoring + leveling up after on-board (Weaknesses)</h4> {{anchor|How to Get Started}}
<hr>
<div style="display:block;background-color:#d1dffa;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="width:100%;display:block;">
<div style="size:30px;color:red">'''What'''</div>
</div>
<div style="-moz-column-count:1;">
Supporting   individuals throughout the contributor lifecycle: introduction to   program, recruiting, on-boarding, escalation of responsibilities, skill   building, leadership, de-boarding, alumni network/support. 
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''How (assets)'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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]
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Revised actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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.
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Owners'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
Amie + Ally
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Resources needed'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
</div>
</div>
</div>


<div style="display:block;-moz-border-radius:10px;background-color:#A2BFF4;padding:20px;margin-top:20px;">
<h4>Distributed Leadership (opp)</h4> {{anchor|How to Get Started}}
<hr>
<div style="display:block;background-color:#d1dffa;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="width:100%;display:block;">
<div style="size:30px;color:red">'''What'''</div>
</div>
<div style="-moz-column-count:1;">
diversified   decision makers,  leadership in more geos, x-functional leadership so   that *efficient*  knowledge distribution happens, keeps the org  informed  and progress  moving forward . 
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''How (assets)'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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"?]
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Revised actions'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
*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)

</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Owners'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
Michelle (Ally would like to support this/co own)
</div>
</div>

<div style="display:block;background-color:#d1dffa;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="size:30px;color:red">'''Resources needed'''</div>
<div style="-moz-column-count:1;-moz-column-gap:20px;">
Amie
</div>
</div>
</div>

===other priorities ordored by number of votes===

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

==Second day==

Carousel notes about work of Day 1

* Priorities
  How do we scale our culture?
  1. Diversity
     + cultural, geographic (both what we have and what we don't have yet)
  2. Teaching Openness
     + domain experts
     + sharing with partners (FxOS)
     + how does this differ for different groups?
     + leading by example
  3. Mentoring and Onboarding
     + whole cycle
     + smooth pathways and transitions (always a Moillian?)
  4. Distributed Leadership
     + cultural customisations
  5. Unity and focus
     + intention to communicate
     + bottom-up mandate?

*Mitchell wants more leaders in the org.

*Working with Pathways on drop-off.

==Third day==

<div style="display:block;-moz-border-radius:10px;background-color:#9fd285;padding:20px;margin-top:20px;">
===Final Action Plan/Action List===
<div style="display:block;background-color:#c4e1b6;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="-moz-column-count:1;">

*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]
</div>
</div>


===Measuring Success===
<div style="display:block;background-color:#c4e1b6;-moz-column-gap:20px;padding:20px;margin-top:20px;-moz-border-radius:10px;">
<div style="-moz-column-count:1;">
*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
</div>
</div>
</div>