Contribute/Workshops/Planning: Difference between revisions

Mozilla is small compared to companies creating other browsers and mobile operating systems (we're even small compared to other global non-profits).  Because [http://www.mozilla.org/mission/ our mission] resonates with people around the world who want to help, we have an enormous opportunity.  A thoughtful approach to identifying where we need to build community and supporting teams so they are successful at community building will bring in the people that Mozilla needs to achieve our goals.

 

We could connect volunteers to our strategic goals by being explicit about where we need help and what the tasks are.  This requires more than simply being open and letting people [http://www.catb.org/esr/writings/homesteading/cathedral-bazaar/ar01s02.html scratch their personal itch] though.

 

What would a system look like that could identify where we need to build community and what contributors could do to help teams achieve their goals? This workshop is intended to help figure that out by having discussions with teams about their needs and what would help them.

 

One thought that came out of the recent [http://vreplay.mozilla.com/replay/showRecordingExternal.html?key=o3Z5FlBjoJnUmcQ Design Projects for Participation] workshop was to provide some structure to thinking about this with a [https://docs.google.com/document/d/1v4zkMYObGt6RE2l5ch2i3xKz0Tnh-V61OTLdH3pY9r8/edit worksheet template] that teams could use to identify tasks and to structure those into discrete opportunities that volunteers can help with.

 

 

To fully leverage the huge opportunity we have with volunteers around the world, Mozilla needs to evolve our informal, organic and ad hoc community building efforts into a thoughtful, intentional and scalable approach. That approach would include the following: