Stewards/Coding/Group 09 26 12

Meeting Details

• Meeting time: Wednesday, September 26 at 11 AM Pacific
• Video: David's vidyo room (use this link for guest access)
• Audio: If video doesn't work, call +1 800 707 2533, pin 369, conf 9634#
• Back channel: #mozillians

Agenda

• Community dashboards
  • Dashboard of dashboards
    • Making Josh's mentored bugs graphs public
    • Making coding dashboards public (bug 771581)
  • Conversion funnel
    • Next phases: adding Bugzilla data in Q3 and then adding more data sources and branches to funnel
    • Josh's conversion tracking
  • Leverage ratio
    • Adding leverage ratio to coding dashboards (bug 783038)
  • Exploring uses for Metrics API (bug 729703)

• Job descriptions
  • Coding Community Manager
  • Education Community Manager
  • B2G Community Manager (need to write a job description?)

• Rewards process for contributors
  • Mentored bug for creating gear nominations to use at gear.mozilla.org
  • https://wiki.mozilla.org/Stewards/Coding/Rewards

• Coding Community Tools
  • What Can I Do For Mozilla?
    • Creating a promo and finding places to promote it on Mozilla sites like MDN and other sites like Stackoverflow (bug 775771)
  • Bugs Ahoy
  • Mach

• Expanding representation at this meeting
  • Fennec: Inviting Margaret -- may not be able to make 10 pacific. Change meeting times?
  • B2G: Anyone else?
  • Devtools, webapps, others?
  • Creating a cross-product coding contribution opportunity entry page? Similar to Webdev Get Involved page

Place holders

• Goal setting
  • Should we use leverage ratio as goal for our efforts? If so, what's the target leverage? Currently at 1:1.6 (although this may be high since some people are labelled volunteers in dashboard who are employees)

• Academic institutions
  • Move forward with just mailing list: https://lists.mozilla.org/listinfo/education
  • Clean up references to Google Groups and newsgroup versions of forum that aren't linked anymore
  • Any next steps with student-project keyword?
  • Creating a case study that would promote this work and make it easier to duplicate?

• Using community dashboards
  • Measure effectiveness of first patch approved email when conversion tracking in place
  • Contributor survey once we have information about conversion path