Meeting Details

• Meeting time: Wednesday, March 20 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

• Note that we won't be meeting next Wednesday

• Discussion with rep from Safari Books at noon pacific today for anyone interested

• Community dashboards
  • Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs:
    • Data about number of mentored bugs resolved fixed sorted by mentor (as proxy to learn who outstanding mentors are to then capture learnings to share with other mentors)
    • Coding activity dashboards based on query to search for work done by non MoCo email addresses in certain time period
    • Mentored bugs to return to pool of available contributors based on query for mentored bugs with an assignee who has not touched it in >2 weeks
    • Splitting out R- and R+ from review and retention dashboards and comparing time from R+ to closing bug fixed
    • Measure effectiveness of patch approved email and other changes like releasing Mach
    • Patch size vs. review time -- patch data to be added to Bugzilla Anthropology
    • Mentored bugs graphs
    • Conversion tracking
    • Leverage ratio of coding employees and volunteers
    • Investigating the use of the Metrics API (bug 729703)
    • 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.
  • Other topics
    • Working with Bitergia on analysis project?
    • Enhancements for patch dashboards in Metrics' goals for Q1

• Clarifying types of starter bugs
  • Thread on dev.planning

• Surveying contributors who stop contributing
  • Can we segment who we reach out to? People who made one patch vs. more than one patch?
  • What information do we want to find out? Can we work with User Research to craft the right questions?

• Recognition plans for contributors
  • Webdev badges live on badges.mozilla.org
  • Report back on usefulness of Award API for badge automation and Gear store form
  • Mapping recognition items to conversion points
  • This may need some updating? https://wiki.mozilla.org/Stewards/Coding/Rewards

• Coding Community Tools
  • What Can I Do For Mozilla?
  • Bugs Ahoy
  • Mach

• Infrastructure
  • Is it possible to host the tools we're building on Mozilla servers?
    • Is mozillalabs.com still an option?
  • How do we garden all this stuff -- thoughts on a coding community building portal?

• Academic institutions
  • Creating a toolkit and coordinating with groups with similar interests: Hive, Student Reps, Intern program

Place holders

• Coordinating with other contribution funnels
  • QA, Metrics, Support? Others?

• Discussion other project ideas we have considered previously: https://etherpad.mozilla.org/CommunityManagerProjects

• Videos
  • Reprise of Josh's FOSDEM presentation
  • https://developer.mozilla.org/en-US/docs/User:teoli/TestPopcorn - Building Firefox from scratch on Ubuntu

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

Action Items

• Mike and Liz to discuss how to include flagging starter bugs in bug days

• Josh working on a demo for a timeline of contributor's history

• Josh working on training missions for new coding contributors

• Mike moving forward with coding badges and will present more details to group

• David to move infrastructure topic to Placeholder section for now to revisit another time