Contribute/analysis

Mozilla Contributor / Contribution Analysis Project (Joint MoCo & MoFo)

This page is a home for a short piece of work happening in Oct/Nov 2014 to explore some of our existing contribution data.

The goal and scope of the work:

• Explore existing contribution datasets to look for possible insights and metrics that would be useful to monitor on an ongoing basis, before the co-incident workweek in Portland at the beginning of December.

• We will:
  • Stress-test our current capacity to use existing contribution data
  • Look for actionable insights to support Mozilla-wide community building efforts
  • Run ad-hoc analysis before building any 'tools'
  • If useful, prototype tools that can be re-used for ongoing insights into community health
  • Build processes so that contributors can get involved in this metrics work
  • Document gaps in our existing data / knowledge
  • Document ideas for future analysis and exploration

See also: Original Proposal Document (See Part 2 - Cohort Analysis)

Who is working on this?

• Adam Lofting (Mozilla Foundation)
• Dave Eaves (Consultant)
• Pierros Papadeas (Mozilla Corporation)

• Contributors who have offered support:
  • Sujith Reddy
  • Harish Ramesh
  • Rami Khader

How can I get involved?

If you would like to contribute, we would love your support. Please join the mofo-metrics mailing list here.

The 3 questions we plan to answer

1. Cohort analysis
   • Can we look at data from 3 weeks of over the past 1.5 years, grab all the people who came to the volunteer page and see how far down various engagement funnels different contributors have gone from each cohort.
2. Impact of response times
   • Can we grab data from Bugzilla (and other sources) to assess if “response times” (e.g. the time it takes to get a contribution reviewed or a request signed off on) have an impact on the likelihood to contribute again in the future.
3. TBC: Impact of *asking* for contributions
   • Search for data when we email (or do some form of outreach) towards contributors asking them to take action or do something. Does such outreach cause regular contributors to contribute? Does it activate non-participating contributors? Does it create new contributors?
4. TBC: Multiple contributions over time
   • AKA 'Members Returning for Action' (KPI title used by SumOfUs)

Other questions you would like to explore

link to bug / etherpad?

Bugzilla tickets for this work

File a new ticket here

Full Query

ID	Summary	Priority	Status
1081111	Question 6: Contributor retention rate statistics	--	ASSIGNED
1082631	Export contribute mailing list emails for April 2013	--	RESOLVED
1082651	Question 5: Can we create a geographical overview of our contributors. i.e. by country.	--	NEW
1086200	Question 1: Contributor Cohort Analysis	--	ASSIGNED
1086201	Question 2: Impact of response times on future contributions	--	NEW
1086203	Question 3: Impact of *asking* for contributions	--	NEW
1086204	Question 4: "Members Returning for Action"	--	ASSIGNED
1086210	Question 7: What is the impact on localization community of leaning on them to push the launch of FirefoxOS in a new market?	--	RESOLVED
1086213	Document a process for Metrics contributors to sign an NDA	--	NEW
1097606	Question 8: Can we measure a return on investment of dedicating resources to community building?	--	NEW
1101047	Export mailing lists for May 2014 to-date	--	ASSIGNED

11 Total; 9 Open (81.82%); 2 Resolved (18.18%); 0 Verified (0%);