Stewards/Coding/Group 08 08 12

From MozillaWiki
Jump to: navigation, search

Meeting Details

  • Meeting time: Wednesday, August 8 at 10 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


  • Community dashboards
    • Making coding dashboards public (bug 771581)
      • Next steps for review: get public comment and get feedback on other potential changes to dashboards
      • Friendlier URLs: and ?
    • Exploring uses for Metrics API (bug 729703)
    • Is Ohloh data useful to include in our plans as well as our own dashboards?
    • Conversion funnel
      • Next phases: adding Bugzilla data in Q3 and then adding more data sources and branches to funnel
  • Swag for people completing mentored bugs
      • Flesh out proposal, get details about Store changes, get feedback on our proposal, set this as a requirement
      • Invite William Q to talk through how ReMo swag process works when he's back after Aug 17
  • Tools
    • How to make use of
      • Creating a promo and finding places to promote it on Mozilla sites like MDN and other sites like Stackoverflow (bug 775771)
      • Business cards, possibly add to ReMo toolkit
  • Using community dashboards
    • Measure effectiveness of first patch approved email when conversion tracking in place
    • Contributor survey once we have information about conversion path
  • Expanding representation at this meeting
    • B2G: Anyone else?
    • Fennec: Lucas and anyone else?
    • Devtools, webapps, others?
    • Creating a cross-product coding contribution opportunity entry page? Similar to Webdev Get Involved page

Action Items

  • David to follow up with legal about comments made on dashboards in public review process
  • David to file bugs to get friendlier URLs for those dashboards
  • Josh and Brian to audit Ohloh dashboards and see what interesting data they are tracking
  • David and Josh to work on MozCamp session
  • David to follow up with Kate on how to move forward with Rewards process
  • Brian to update Coding Community Manager job description to include rewards process tasks
  • Gregory to come back when Mach is stable and take about implementing it and building a community around it