Contribute/Education/Notes/2013-12-13 Commmunity Builders Meetup: Difference between revisions

Contribute/Education/Notes/2013-12-13 Commmunity Builders Meetup (view source)

Revision as of 21:51, 30 January 2014

3,842 bytes added , 30 January 2014

no edit summary

Melek

Confirmed users

152

edits

@@ Line 1: / Line 1: @@
-Raw notes: [https://cbt.etherpad.mozilla.org/2013-meetup-track-education]
+=General=
-----
 == Statement ==
@@ Line 12: / Line 11: @@
 == Main Goals==
 ====Increase "default open" in the project====
 *To broaden: conduct a contributor census including attitudes towards openness and diversity
@@ Line 28: / Line 28: @@
 **Measured by: How many people completed the training
-==Sessions and workshops==
+==Sessions organisation==
-===Wednesday December 11th - SWOT + Priorities Setting [1 Hour]===
+details  Carousel , SWOT and three day process
-====Goal====
-TO SET
+=Sessions=
-====Assests identification and Mapping====
-**reps, student ambassadors, mentors, interns
+==Wednesday 11 December (Day 1)==
-**Mozilla lexicon
-**safari books, rosetta stone
+===SWOT session===
-**red carpet, mofo "new hire" wiki
-**tribe, lead training
+====Strengths====
-**global mobility
+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
-**web literacy standard, remixable teaching kits, teachtheweb mooc, webmaker, p2pu, appmaker, hive learning networks, popcorn
-**open badges
+====Weaknesses====
-**work.com, phonebook, intranet, mana, bugzilla, bug mentoring, mozillians.org
-**mdn, wikimo, mailinglists, irc
-**verbatim (l10n), github, sorce code repositories (svn, hg, bzr, mxr, etc.)
-**airmozila, capture mozillia, video archive, history of mozilla, onboarding video
-**mozilla.org
-**mozila summit, all hands, weekly project meeting, mozcamps
-**manifesto, code of conduct, cultural literacy, culture pulse, diversity council
-====SWOT Analysis====
-*'''''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
-====First five priorities====
-'''''1-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.
+====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
-''Why''
+====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
-For education: this is not just about teaching diversity, but raising awareness of our initatives/projects/resources through diversity to maintain innovation; and making sure the educational efforts of these initatives reaches all people.
+===Top 5 Priorities===
-''How (assets)''
+====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.
-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
+'''''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''
+'''''Actions'''''
 *Identify what various communities mean by diversity and how they want to diversify their communities.
-***Survey on diversity -
+**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''
+'''''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''
+'''''Resources needed'''''
-**Time and webdev assistance to help craft workshop tools
+*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
+*Proper survey consultation for creating pre & post workshop survey about diversity and visualize the data over time/cohort
-**localization of workshop materials
+*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'''''
+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
+'''''Action(s)'''''
+*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
+====Mandate unity across the board (opp)====
+'''''What'''''
+unify, grow, and scale contributors in support of the 1MM goal.
+'''''Action'''''
+*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
+====3 Mentoring + 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.
+'''''Action'''''
+*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
+====Distributed Leadership (opp)====
+'''''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 .
+'''''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
+==Second day==
+==Third day==