Community Workshops

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