Stewards/Coding/Group 04 10 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Meeting Details= * Meeting time: Wednesday, April 10 at 11 AM Pacific * Video: David's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use this...")
 
Line 9: Line 9:


* [[Stewards/Coding/Group_04_03_13#Action_Items|Action items from last meeting]]
* [[Stewards/Coding/Group_04_03_13#Action_Items|Action items from last meeting]]
* 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 [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 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 [https://bugzilla.mozilla.org/buglist.cgi?emailtype2=notequals;list_id=5842047;field0-0-0=owner_idle_time;resolution=---;emailtype1=notequals;status_whiteboard_type=allwordssubstr;emailassigned_to1=1;query_format=advanced;status_whiteboard=mentor%3D;email2=general%40js.bugs%20;emailassigned_to2=1;email1=nobody%40mozilla.org;type0-0-0=greaterthan;value0-0-0=2w query for mentored bugs with an assignee who has not touched it in >2 weeks]
*** Splitting out R- and R+ from [https://metrics.mozilla.com/bugzilla-analysis/Community_NextReviews.html review] and [https://metrics.mozilla.com/bugzilla-analysis/Community_Retention.html retention] dashboards and comparing time from R+ to closing bug fixed
*** Measure effectiveness of [https://projects.mozilla.org/browse/BA-90 patch approved email] and other changes like releasing Mach
*** Patch size vs. review time -- [https://projects.mozilla.org/browse/METRICS-1290 patch data to be added to Bugzilla Anthropology]
*** Mentored bugs graphs
*** [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0ApOXjgdvXthCdG9UY09MejgzSHNzN3dCQ0t2U01RRnc&invite=CKfXqpEO Conversion tracking]
*** Leverage ratio of coding employees and volunteers
*** Investigating the use of the Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 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 [http://blog.bitergia.com/2012/07/19/the-project-metrics-grimoire-started/ Bitergia] on analysis project?
*** Enhancements for patch dashboards in Metrics' goals for Q1
* Recognition plans for contributors
** [https://badges.mozilla.org/en-US/profiles/profile/webdev Webdev badges live on badges.mozilla.org]
** Report back on usefulness of [https://github.com/mozilla/badges.mozilla.org/wiki/Award-API Award API] for badge automation and Gear store form
** [[Contribute/Conversion_points#Coding|Mapping recognition items to conversion points]]
** This may need some updating? https://wiki.mozilla.org/Stewards/Coding/Rewards
* Coding Community Tools
** Training missions
** [http://whatcanidoformozilla.org/ What Can I Do For Mozilla?]
** [http://www.joshmatthews.net/bugsahoy/ Bugs Ahoy]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=751795 Mach]
* Academic institutions
** Creating a toolkit and coordinating with groups with similar interests: Hive, Student Reps, Intern program
* 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?
Place holders
* Coordinating with other contribution funnels
** QA, Metrics,  Support?  Others?
* 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?
* Discussion other project ideas we have considered previously: https://etherpad.mozilla.org/CommunityManagerProjects
* Videos
** Reprise of [http://www.joshmatthews.net/fosdem/ 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==
==Action Items==
* Margaret to create mailing list for Coding Stewards

Revision as of 16:34, 8 April 2013

Meeting Details

  • Meeting time: Wednesday, April 10 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: #mozillians

Agenda

Action Items

Retrieved from "https://wiki.allizom.org/index.php?title=Stewards/Coding/Group_04_10_13&oldid=644681"