Stewards/Coding/Group 01 30 13: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Meeting Details= * Meeting time: Wednesday, January 30 at 11 AM Pacific * Video: David's vidyo room ([https://v.mozilla.com/flex.html?roomdirect.html&key=LagZYeSPnhIA use this ...")
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 9: Line 9:


* [[Stewards/Coding/Group_01_23_13#Action_Items|Action items from last meeting]]
* [[Stewards/Coding/Group_01_23_13#Action_Items|Action items from last meeting]]
* Welcome to Mike Hoye
** For reference, some possible project ideas we have discussed previously: https://etherpad.mozilla.org/CommunityManagerProjects


* Community dashboards
* Community dashboards
Line 32: Line 35:
** Can we segment who we reach out to?  People who made one patch vs. more than one patch?
** Can we segment who we reach out to?  People who made one patch vs. more than one patch?
** What questions do we want to ask?
** What questions do we want to ask?
* Coordinating with other contribution funnels
** QA
** Support?  Others?
* Screencasts
** https://developer.mozilla.org/en-US/docs/User:teoli/TestPopcorn - Building Firefox from scratch on Ubuntu
* Coding community manager
** [http://careers.mozilla.org/en-US/position/oByUWfwJ Community Manager, Firefox Engineering] posted
** Setting community managers up for success
*** https://etherpad.mozilla.org/CommunityManagerProjects
*** [http://benjamin.smedbergs.us/triage-groups.fcgi/static/edit.html Mapping Bugzilla components to teams]


* Rewards process for contributors
* Rewards process for contributors
Line 58: Line 48:
** [https://bugzilla.mozilla.org/show_bug.cgi?id=751795 Mach]
** [https://bugzilla.mozilla.org/show_bug.cgi?id=751795 Mach]
*** Are we able to see how this has helped people in the conversion metrics we have?
*** Are we able to see how this has helped people in the conversion metrics we have?
* Coordinating with other contribution funnels
** QA
** Support?  Others?
Place holders
* Screencasts
** https://developer.mozilla.org/en-US/docs/User:teoli/TestPopcorn - Building Firefox from scratch on Ubuntu


* Experiments
* Experiments
** The mobile team is experimenting with posting a "featured bug" (http://lucasr.org/2012/12/07/featured-bug-1-in-firefox-for-android/)
** The mobile team is experimenting with posting a "featured bug" (http://lucasr.org/2012/12/07/featured-bug-1-in-firefox-for-android/)
Place holders


* Academic institutions
* Academic institutions
Line 70: Line 67:
** [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?


* Contributor survey
==Action Items==
 
* Mike to talk to Kyle, Seif and Josh about leveraging the community metrics work they've done


==Action Items==
* Mike to look into the narrative behind a set of people who have made one patch and then left to inform what information we want to find out from that set of contributors
 
* Mike and David to connect about recognition efforts and report back to group

Latest revision as of 19:31, 30 January 2013

Meeting Details

  • Meeting time: Wednesday, January 30 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

  • Contacting contributors who stop contributing
    • Can we segment who we reach out to? People who made one patch vs. more than one patch?
    • What questions do we want to ask?
  • 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?
  • Coordinating with other contribution funnels
    • QA
    • Support? Others?

Place holders

Action Items

  • Mike to talk to Kyle, Seif and Josh about leveraging the community metrics work they've done
  • Mike to look into the narrative behind a set of people who have made one patch and then left to inform what information we want to find out from that set of contributors
  • Mike and David to connect about recognition efforts and report back to group