Meeting Details

• Meeting time: Wednesday, November 28 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

• Community building workshops
  • Measuring and evaluating workshop on November 29 at 10 pacific (meeting details)
  • Past workshops: Designing your project for participation and Identifying Contributors
  • Is there any value in running these workshops at Engineering work weeks? Would be around 3-4 hours for all 3.

• Community dashboards
  • Patch dashboards now public at arewegrowingyet.com/codingmap and arewegrowingyet.com/codingtrends
    • Ideas for enhancements:
      • Add patch size to get some information for comparison
      • Ratios of submitted vs approved vs commited patches
      • Better organize the components -- at least the mobile patches, which just show up as part of "Other"
      • The default filter shouldn't be "Firefox". That only corresponds to the front-end work, which is a small part of the total work.
      • Combine patches from contributors who have used multiple email addresses would be really nice.
  • Other dashboards in the works
    • Mentored bugs graphs
    • Conversion tracking
    • Leverage ratio
    • Metrics API (bug 729703)

• 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
  • Are we able to pull out information about people who have submitted patches to feed into Gear Store?
  • Defining other recognition points on coding path
  • 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
    • Are we able to see how this has helped people in the conversion metrics we have?

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?

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

Action Items

• David to talk to Metrics team about improving organization of components and changing default filter in patch dashboards

• David to talk to Kyle to see if patch size data is included in Bugzilla Anthropology data

• Josh to show prototype of script to get data for use in nominating people to receive shirts

• Graeme to work on prototype for creating badges for people contributing to specific releases

Notes

• David: last community building workshop tomorrow; we can evaluate next week whether the workshops could be repeated for other audiences (eg. work week)
• David: patch dashboards are now public: https://blog.mozilla.org/community/2012/11/26/coding-contribution-dashboards-now-available/
• David: collecting feedback; what should we prioritize when talking to Metrics?
• Josh & Benjamin: prioritize getting better module categorization (possibly bugzilla components instead) and better default filter
• Benjamin: community manager hiring process - phone screening in process, interesting conversations happening (contributing as gamification, for example)
• Josh: prototyping new contributor first patch notifier; read in data from git on a regular schedule, keep database of commits, find new contributors that appear - should have demo in one week
• Benjamin: prototyping holding entire bugzilla database (without actual patches) in memory, allowing near-instant queries; should be able to be pretty open about it eventually. Will allow for must easier exploration of bugzilla data than current Elastic Search-based Bugzilla Anthropology project
• Graeme: thinking about automated badges for "contributed to FF release N"; prototype at http://www.graememcc.co.uk/badger/ (Blog post)
• David: could we use this for automatic about:credits additions?
• Benjamin: from phone conversations with candidates: interest in tying contributions to rapid release; show that this person's first patch was in release X
• David: we could publicize this better (community blog, release notes, ...?) and celebrate it