Stewards/Coding/Group 12 05 12: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Meeting Details=
=Meeting Details=


* Meeting time: Wednesday, December 6 at 11 AM Pacific
* Meeting time: Wednesday, December 5 at 11 AM Pacific
* Video: David's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use this link for guest access])
* Video: David's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use this link for guest access])
* Audio: If video doesn't work, call +1 800 707 2533, pin 369, conf 9634#
* Audio: If video doesn't work, call +1 800 707 2533, pin 369, conf 9634#
Line 11: Line 11:


* Community building workshops
* Community building workshops
** Past workshops: [[Contribute/Workshops/Designing_for_participation|Designing your project for participation]] and [[Contribute/Workshops/Identifying_contributors|Identifying Contributors]] and Measuring and evaluating contributions
** [[Contribute/Workshops/Designing_for_participation|Designing your project for participation]]  
** [[Contribute/Workshops/Identifying_contributors|Identifying contributors]]
** [[Contribute/Workshops/Metrics_for_growth|Metrics for growth]]
** Is there any value in running these workshops at Engineering work weeks?  Would be around 3-4 hours for all 3.
** Is there any value in running these workshops at Engineering work weeks?  Would be around 3-4 hours for all 3.
* Screencasts
** https://developer.mozilla.org/en-US/docs/User:teoli/TestPopcorn - Building Firefox from scratch on Ubuntu


* Community dashboards
* Community dashboards
*** Enhancements for patch dashboards:
** Enhancements for patch dashboards
**** Better organize the components -- at least the mobile patches, which just show up as part of "Other"
** Measure effectiveness of [https://bugzilla.mozilla.org/show_bug.cgi?id=721206 first patch approved email]
**** The default filter shouldn't be "Firefox". That only corresponds to the front-end work, which is a small part of the total work.
*** Kyle looking into this as part of Bugzilla Anthropology: https://projects.mozilla.org/browse/BA-90
** Other dashboards in the works
** Other dashboards in the works
*** http://www.joshmatthews.net/swagger/health.html
*** http://www.joshmatthews.net/swagger/index.cgi
*** Patch size vs. review time -- [https://projects.mozilla.org/browse/METRICS-1290 patch data to be added to Bugzilla Anthropology]
*** Mentored bugs graphs
*** Mentored bugs graphs
*** [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0ApOXjgdvXthCdG9UY09MejgzSHNzN3dCQ0t2U01RRnc&invite=CKfXqpEO Conversion tracking]
*** [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0ApOXjgdvXthCdG9UY09MejgzSHNzN3dCQ0t2U01RRnc&invite=CKfXqpEO Conversion tracking]
*** Leverage ratio
*** Leverage ratio
*** Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 bug 729703])
*** Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 bug 729703])
** New ideas to discuss
*** 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.


* Coding community manager
* Coding community manager
Line 53: Line 64:
** [https://etherpad.mozilla.org/working-with-academic-institutions-case-study Creating a case study] that would promote this work and make it easier to duplicate?
** [https://etherpad.mozilla.org/working-with-academic-institutions-case-study Creating a case study] that would promote this work and make it easier to duplicate?


* Using community dashboards
* Contributor survey
** Measure effectiveness of [https://bugzilla.mozilla.org/show_bug.cgi?id=721206 first patch approved email] when conversion tracking in place
** Contributor survey once we have information about conversion path


==Action Items==
==Action Items==
* David to follow up with Dietrich and Ben about possibly running community building workshops at a B2G work week
* Josh to think about where to promote the Building Firefox screencast
* Kyle to report when he can measure effectiveness of first patch approved emails in Bugzilla
* Seif to investigate how to update the Firefox release notes to include people who have submitted their first patch for that release

Latest revision as of 22:02, 5 December 2012

Meeting Details

  • Meeting time: Wednesday, December 5 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

  • Rewards process for contributors
  • 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

  • Contributor survey

Action Items

  • David to follow up with Dietrich and Ben about possibly running community building workshops at a B2G work week
  • Josh to think about where to promote the Building Firefox screencast
  • Kyle to report when he can measure effectiveness of first patch approved emails in Bugzilla
  • Seif to investigate how to update the Firefox release notes to include people who have submitted their first patch for that release
Retrieved from "https://wiki.allizom.org/index.php?title=Stewards/Coding/Group_12_05_12&oldid=492282"