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.

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

• 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.

• 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.

Lukas (Dino co-lead/support)

• 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

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

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

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

• 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.

• 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.

Christie

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

• 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

• 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.

Dino

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

• 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]

• 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.

Amie + Ally

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

• 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"?]

• 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)

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

Amie

• 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]

• 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