Revision as of 19:41, 1 August 2012

Meeting Details

MozCamp proposal: https://wiki.mozilla.org/MozCampEU2012/resources-for-helping-potential-code-contributors
- Let's find out if this will be recorded
- We can also look at using this as a template for future events

Swag for people completing mentored bugs
- https://etherpad.mozilla.org/coding-rewards
  - Flesh out proposal, get details about Store changes, get feedback on our proposal, set this as a requirement
  - Invite William Q to talk through how ReMo swag process works when he's back after Aug 17

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?

Tools
- How to make use of http://whatcanidoformozilla.org/
  - Creating a promo and finding places to promote it on Mozilla sites like MDN and other sites like Stackoverflow (bug 775771)
  - Business cards, possibly add to ReMo toolkit

Using community dashboards
- Measure effectiveness of first patch approved email when conversion tracking in place
- Contributor survey once we have information about conversion path

Expanding representation at this meeting
- B2G: Anyone else?
- Fennec: Lucas and anyone else?
- Devtools, webapps, others?
- Creating a cross-product coding contribution opportunity entry page? Similar to Webdev Get Involved page

@@ Line 11: / Line 11: @@
 *** Next steps: push the review process and changes to dashboards
 ** Exploring uses for Metrics API ([https://bugzilla.mozilla.org/show_bug.cgi?id=729703 bug 729703])
+** Is Ohloh data useful to include in our plans as well as our own dashboards?
+*** http://www.ohloh.net/p/firefox/
 ** Conversion funnel
 *** Next phases: adding Bugzilla data in Q3 and then adding more data sources and branches to funnel