Stewards/Coding/Group 11 28 12

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
  • Designing your project for participation
  • Identifying Contributors
  • Measuring and evaluating workshop on November 29 at 10 pacific (meeting details)
  • 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