Thanks, David.
The scope for the module still sounds right. I'd love to see another
thread on near term goals and work -- or maybe a blog post from you if
governance is not the right place for that.
Also, I'd like to propose Michelle Thorne and Ryan Merkley as peers on
this module.
Michelle led our Summer Code Party, an effort to get people learning and
making on the web that got picked up in 650 cities this past summer. She
did informal metrics last summer, is working on a systematic approach
for next year as we grow our ongoing Webmaker instructor community.
Ryan lead our first attempt at Webmaker contributor metrics this year.
We focused on coders, content developers and teachers. I think he's
going to blog on that soon. Now, he is developing a more robust set of
participation and contributor metrics for Webmaker 2013, with a focus on
makers, badges and mentors.
Both Michelle and Ryan have alot to offer here, and also alot to learn.
ms
On 12-12-03 2:38 PM, [email protected] wrote:
Asa, thank you for the nomination.
Mark, those are good questions. Some thoughts below.
* What are the scope and goals of the participation metrics module?
I think the original scope of the module still feels right to me. The
description being used in the module list is:
"Develop, monitor and analyze metrics relating to participation in the Mozilla
project"
* Who are the peers? Do you and David think we need new / more peers?
In addition to having Asa, Daniel and Ken's continued guidance, I suggest
adding Dave Eaves, Annie Elliott and Pierros Papadeas as new peers.
Dave has been advocating for the use of metrics to improve our ability to do
community building for a long time now -- most recently with last week's
'Metrics for growth' community building workshop.
Annie has been a huge help taking the needs a team has and translating those
into clear deliverables for the Metrics team to make sure what gets created
will give us answers to the questions we're asking.
Pierros has been doing a lot of great work with creating ways to get visibility
into offline activities with the ReMo program that I think is relevant to the
whole project.
* David, do you have short term priorities / ideas on what needs to
happen within the scope of this module?
The way I want to move forward is to identify the relevant contribution
opportunities that exist for the different functional and regional parts of the
project.
You can see the initial efforts around that at the following wiki page where
we've started with mapping out the paths for Coding, Support and Webdev
contributions.
https://wiki.mozilla.org/Contribute/Conversion_points
Once the paths for the functional and regional areas have been identified,
we'll have the information we need to get visibility into the health and growth
of those areas.
To get a sense of what this would look like, we recently announced two coding
dashboards that give an idea of the type of data we think is relevant for
community building.
I think the people involved in the participation metrics module have a key role
to play in helping teams create these paths and then working with the Metrics
team and other people interested in analyzing data to figure out how to roll
out new efforts to get data across the whole project.
Thanks,
David
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
