Meeting Details

• Meeting time: Wednesday, December 12 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: #planning

Agenda

• Action items from last meeting

• Screencasts
  • https://developer.mozilla.org/en-US/docs/User:teoli/TestPopcorn - Building Firefox from scratch on Ubuntu

• Community dashboards
  • Enhancements for patch dashboards in Metrics' goals for Q1
    • Change default filter -- to what?
    • Better organize patches using BZ components -- note that this won't cover anything not in BZ such as Github issues
    • More accurately identify volunteers and staff
  • Measure effectiveness of first patch approved email
    • Kyle looking into this as part of Bugzilla Anthropology: https://projects.mozilla.org/browse/BA-90
  • Other dashboards in the works
    • From a Statistics PhD student who just contacted us about getting involved: https://scss.tcd.ie/~seoriord/mozilla-firefox.html
    • http://www.joshmatthews.net/swagger/health.html
    • http://www.joshmatthews.net/swagger/index.cgi
    • Patch size vs. review time -- patch data to be added to Bugzilla Anthropology
    • Mentored bugs graphs
    • Conversion tracking
    • Leverage ratio
    • Metrics API (bug 729703)
  • New ideas to discuss
    • New contributor dashboards/metrics for portions of the tree (eg. gfx/, dom/, whatever)
    • Get engineers to tag nontrivial bugs with common annotation (eg. [complex]). Write a tool that watches for successful resolution of these bugs and adds assignee to list of promising contributors.

• Coding community manager
  • Community Manager, Firefox Engineering posted
  • Setting community managers up for success
    • https://etherpad.mozilla.org/CommunityManagerProjects
    • Mapping Bugzilla components to teams
  • Identifying coding areas with needs for community management -- Firefox OS, webdev, education liaison, ???

• Rewards process for contributors
  • jdm's prototype for contributor first patch notifier to feed into Gear Store for sending shirts
  • graememcc's prototype for tool to issue badges to people contributing to a specific Firefox release
    • Could also use for adding info about new contributors for that release to release notes, automating credits additions, content for Spotlights, Friend of Tree?
  • Defining other recognition points on coding path
  • 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
    • Are we able to see how this has helped people in the conversion metrics we have?

• Community building workshops
  • Next steps: David to talk to Dietrich and Ben about upcoming B2G work weeks

• Experiments
  • The mobile team is experimenting with posting a "featured bug" (http://lucasr.org/2012/12/07/featured-bug-1-in-firefox-for-android/)

Place holders

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

• Contributor survey

Action Items

• David to follow up with Metrics about making patch dashboards unfiltered by default

• Seif to follow up with group in early January to prepare for promoting contributors in release notes

• Seif to follow up with the Statistics PhD student who sent dashboards recently

• Benjamin to discuss coordination with new Bugmaster role in upcoming meeting