Confirmed users
152
edits
Contribute/Education/Notes/2013-12-13 Commmunity Builders Meetup: Difference between revisions
Jump to navigation
Jump to search
Contribute/Education/Notes/2013-12-13 Commmunity Builders Meetup (view source)
Revision as of 22:04, 30 January 2014
, 30 January 2014no edit summary
No edit summary |
No edit summary |
||
| Line 164: | Line 164: | ||
'''''Resources needed''''' | '''''Resources needed''''' | ||
Amie | Amie | ||
===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== | ==Second day== | ||
==Third day== | ==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 | |||