Community Workshops: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
* Overview & Goal: Give the community access to parts of the projects other than l10n, through a series of workshops that will give the appropriate training and tools for community members to get involved with SUMO, QA, Web Security. Jetpack & add-on development, and potentially engineering.  
* <b>Overview & Goal</b>:  
* Audience: We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities
Give the community access to parts of the projects other than l10n, through a series of workshops that will give the appropriate training and tools for community members to get involved with SUMO, QA, Web Security. Jetpack & add-on development, and potentially engineering.  
* <b>Audience</b>:
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities
* Tools and Training
* Tools and Training
**
   
   



Revision as of 20:59, 29 November 2011

  • Overview & Goal:

Give the community access to parts of the projects other than l10n, through a series of workshops that will give the appropriate training and tools for community members to get involved with SUMO, QA, Web Security. Jetpack & add-on development, and potentially engineering.

  • Audience:
We will develop this initial pilot program with Mozilla Tunisia and hopefully roll it out to other interested communities
  • Tools and Training


  • Potential teams that would be a good fit to launch this program:
    • 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 • choffman, mary, Guillermo,…

  • Distribution channels and support
    • Tutorials videos
  • Thoughts....
    • Identify leaders from the community for each workshop and embrace them to become technical leaders afterward
    • Establish clear milestones after each workshop
    • Keeping track of bugs available and bugs filed (how do we monitor progress for each)
  • Composition of the team

- one Mozilla point of contact for each workshop to walk the community through the initial training and provide them with the right tools

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