MozillaWiki

Community Workshops: Difference between revisions

(Created page with "* Overview & Goal: Give the community access to parts of the projects other than a11y (Accessibility). *Potential teams that would be a good fit to launch this program: ** SUMO...")
 
No edit summary
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
* Overview & Goal: Give the community access to parts of the projects other than a11y (Accessibility).  
*<b>Overview & Goal</b>: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla.  


*Potential teams that would be a good fit to launch this program:
*<b>Audience</b>: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012.  
** SUMO (Michelle Luna)
** QA (Tony and Marcia)
** Web Security
** Jetpack and add-on development
** Engineering (FE vs. BE)
• hacking FE UI (Paul Rouget)
• backend ⇒ C++


MozCamp ⇒ sprio south America
*<b>Process</b>:
• choffman, mary, Guillermo,…
**Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop (Q4 2011)
**Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization (Q4 2011)
**Create an internal Engineering Committee to assist with the development of those workshops (Q4 2011)
**Start developing workshops (Q4 2011 / Q1 2012)
**Launch the first workshop in Q1 2012 ; followed by another 4-5 sessions
**Bring guidance to the community and clear milestones to keep the community engaged afterward (2012)
**Create clear processes on how to get involved and opportunities available for each team/workshop (2011-12)


*Distribution channels and support
*<b>Potential ideas for the workshops</b>:
**Tutorials videos
**SUMO (Michelle Luna)
**
**QA (Tony Chung, Marcia Knous, and Stephen Donner)
**IT (puppet automation) (mrz)
**Web Security (Michael Coates)
**Labs (BrowserID, Popcorn Maker)
**Jetpack & add-on development
**Engineering (FFx and Platform)


*Thoughts....
*<b>Tools and Support</b>:
**Identify leaders from the community for each workshop and embrace them to become technical leaders afterward
**Have a clear channel of distribution and one central location for community members to have easy access to resources
**Establish clear milestones after each workshop
**Build an Engineering Committee
**Keeping track of bugs available and bugs filed (how do we monitor progress for each)
**Series of Tutorial videos (Rainer)
 
**Provide clear documentation
* Composition of the team
**Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible.  
- one Mozilla point of contact for each workshop to walk the community through the initial training and provide them with the right tools
**Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)
 
- one technical leader from the community
- figure out how many new members can each team absorb at once (for example, mcoates mentioned 20-30 new contributors. What's a reasonable number?)
- how can we successfully advertise the different opportunities within Mozilla (mutual effort between Workshop Owner and Community Technical Lead)?
 
- Rewarding the community:
* Self valorization within the community and Mozilla (badges?)
*

Latest revision as of 00:49, 30 November 2011

  • Overview & Goal: Give the community access to parts of the Mozilla projects other than l10n, through a series of workshops that will give new volunteers the appropriate training and tools to contribute to Mozilla.
  • Audience: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities. Mozilla Tunisia will be launching a university starting in Dec. 2011 so hopefully we could target those workshops to students as early as Q1 2012.
  • Process:
    • Identify technical leads within Mozilla Tunisia that would be interested in owning a specific workshop (Q4 2011)
    • Assess overall technical knowledge for each workshop lead and offer appropriate training if needed. We need to give them the technical expertise to then run their own community, based on interest and fit within the organization (Q4 2011)
    • Create an internal Engineering Committee to assist with the development of those workshops (Q4 2011)
    • Start developing workshops (Q4 2011 / Q1 2012)
    • Launch the first workshop in Q1 2012 ; followed by another 4-5 sessions
    • Bring guidance to the community and clear milestones to keep the community engaged afterward (2012)
    • Create clear processes on how to get involved and opportunities available for each team/workshop (2011-12)
  • Potential ideas for the workshops:
    • SUMO (Michelle Luna)
    • QA (Tony Chung, Marcia Knous, and Stephen Donner)
    • IT (puppet automation) (mrz)
    • Web Security (Michael Coates)
    • Labs (BrowserID, Popcorn Maker)
    • Jetpack & add-on development
    • Engineering (FFx and Platform)
  • Tools and Support:
    • Have a clear channel of distribution and one central location for community members to have easy access to resources
    • Build an Engineering Committee
    • Series of Tutorial videos (Rainer)
    • Provide clear documentation
    • Have some sort of toolkit ready to be installed; one VM per workshop with all the right tools and environment, and make it easily accessible.
    • Come up with a set of expectations and projects available for the community each quarter, leveled by priorities (provide more structure overall)
Retrieved from "https://wiki.mozilla.org/index.php?title=Community_Workshops&oldid=374314"