Stewards/Coding/Group 03 06 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 11: Line 11:


* Community dashboards
* Community dashboards
** [https://bugzilla.mozilla.org/buglist.cgi?emailtype2=notregexp;field0-0-0=longdesc;emailtype1=notregexp;chfieldto=Now;query_format=advanced;emailassigned_to1=1;chfield=assigned_to;chfieldfrom=2w;bug_status=NEW;bug_status=READY;bug_status=ASSIGNED;email2=.%40mozilla\.org;email1=.%40mozilla\.com;emailassigned_to2=1;type0-0-0=changedbefore;value0-0-0=2w;product=Firefox;list_id=5801525 Search for work done by non MoCo email addresses in certain time period]
** Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs
** Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs
** Potential data analysis contribution opportunities
** Potential data analysis contribution opportunities

Revision as of 20:04, 28 February 2013

Meeting Details

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

  • Community dashboards
    • Search for work done by non MoCo email addresses in certain time period
    • Creating a data analysis contribution opportunity landing page and seeding it with coding analysis needs
    • Potential data analysis contribution opportunities
      • 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
  • 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?
  • 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?

Action Items

  • Mike to get public data ready for posting and we can look at then creating a data analysis contribution landing page
  • Mike to post thoughts on improving experience with different types of starter bugs
  • Mike to look into ability to host sites on mozillalabs.com domain
  • David to connect Mike with Katherine about the Student Reps' Classroom Toolkit idea
Retrieved from "https://wiki.allizom.org/index.php?title=Stewards/Coding/Group_03_06_13&oldid=532617"