MoFo Contributor Dashboard(s) – switching to Plan A

tl;dr: We’re wrapping up work on the MoFo Interim Dashboard The only other data source we’ll add is the badge counts for webmaker mentors & hive community members This is still our MoFo working document for the time being Then, we’ll switch our development efforts into integrating with Project Baloo Baloo is where we will de-dupe contributors across teams/tools etc. areweamillionyet.org will become our working document in time (‘time’ is TBC) Switching to Plan A The MoFo contributor dashboard we’ve been working with this year is our *interim* counting solution, and just as we’re “completing” it we’re now in a position to switch from an interim solution to a fully integrated system which is properly integrated with MoCo. This is pretty good timing, but it’s a change in scope for our immediate work so is worth a status update. Within … Continue reading »

When ‘less than the sum of our parts’ is a good thing

Here’s a happy update about our combined Mozilla Foundation (MoFo) and Mozilla Corporation (MoCo) contributor dashboards. TL;DR: There’s a demo All Mozilla Contributor Dashboard you can see at areweamillionyet.org It’s a demo, but it’s also real, and to explain why this is exciting might need a little context. Since January, I’ve been working on MoFo specific metrics. Mostly because that’s my job, but also because this/these organisations/projects/communities take a little while to understand, and getting to know MoFo was enough to keep me busy. We also wanted to ship something quickly so we know where we stand against our MoFo goals, even if the data isn’t perfect. That’s what we’ve built in our *interim* dashboard. It’s a non de-duped aggregation of the numbers we could get out of our current systems without building a full integration database. It gives us … Continue reading »

Contributor Dashboard Status Update (‘busy work’?)

While I’m always itching to get on with doing the work that needs doing, I’ve spent this morning writing about it instead. Part of me hates this, but another realizes this is valuable. Especially when you’re working remotely and the project status in your head is of no use to your colleagues scattered around the globe. So here’s the updated status page on our Mozilla Foundation Contributor Dashboard, and some progress on my ‘working open‘. Filing bugs, linking them to each other, and editing wiki pages can be tedious work (especially wiki tables that link to bugs!) but the end result is very helpful, for me as well as those following and contributing to the project. And a hat-tip to Pierros, whose hard-work on the project Baloo wiki page directly inspired the formatting here. Now, back to doing!

Progress on Contributor Dashboard(s)

We’re seeing real progress getting data into the MoFo Contributor Dashboard now, but we need to keep in mind that counting existing contributors and engaging new contributors are two separate tasks that will help us move this line upwards. The gains we are seeing right now are counting gains rather than contribution gains. Getting this dashboard fully populated with our existing contributor numbers will be an achievement, but growing our contributor numbers is the real end goal of this work. 40-50% done? Using our back-of-the-napkin numbers from 2013 as a guide the current data sources shown on the dashboard today capture about 40% of the numbers we’re expecting to see here. Depending on how good our estimates were, and how many new contributors have joined in Q1, we expect this will be near the 5k mark by the time it’s … Continue reading »

Who’s teaching this thing anyway?

This is an idea for Webmaker teacher dashboards, and some thoughts on metadata related to learning analytics This post stems from a few conversations around metrics for Webmaker and learning analytics and it proposes some potential product features which need to be challenged and considered. I’m sharing the idea here as it’s easy to pass this around, but this is very much just an idea right now. For context, I’m approaching this from a metrics perspective, but I’m trying to solve the data gathering challenge by adding value for our users rather than asking them to do any extra work. These are the kind of questions I want us to be able to answer and that can inform future decision making in a positive way… How many people using Webmaker tools are mentors, students, or others? Do mentors teach many … Continue reading »

What I see in these graphs of Github contribution

Context: Last week I shared a few graphs (1, 2, 3, 4) looking at data from our repositories on Github, extracted using this Gitribution app thing, as part of our work to dashboard contributor numbers for the Mozilla Foundation. I didn’t comment on the graphs at the time because I wanted time for others to look at them without my opinions skewing what they might see. This follow up post is a walk-through of some things I see in the graphs/data. The real value in looking at data is finding ways to make things better by challenging ourselves, and being honest about what the numbers show, so this will be as much about questions as answers… Also, publishing this last week flagged up some missing repositories and identified some other members of staff so these graphs are based on the … Continue reading »

Gitribution

Over the last week or so I’ve been building a thing: Gitribution. It’s an attempt to understand contributions to Mozilla Foundation work that happen on Github. It’s not perfect yet, but it’s in a state to get feedback on now. Why did I build this? For these reasons (in this order): Counting: To extract counts of contributor numbers from Github across Foundation projects on an automated ongoing basis Testing: To demo the API format we need for other sources of data to power our interim contributor dashboard Learning: To learn a bit about node.js so I can support metrics work on other projects more directly when it’s helpful to (i.e. submitting pull-requests rather than just opening bugs) 1. Counting The data in this tool is all public data from the Github API, but it’s been restructured so it can be … Continue reading »

The immediate value of working in the open

I’m both excited and a tiny bit nervous about how “open” Mozilla are about the way they work. As I’m getting to know the Foundation, and the projects and priorities, and to make sense of what exactly I’ll be doing here I’ve been reading lots of Etherpads. If you don’t know what an Etherpad is, it’s a bit like a Google Doc (the ‘word doc’ variety) but less slick and more open. If you give someone a link to an Etherpad, the barrier to them contributing to the document is almost non-existent. Anyway, the value of this open working process somewhat blew my mind today. While lots of these docs have been useful in a general sense, today I read the documents from the initial planning around MoFo metrics that led to recruiting for my role (so it was pretty … Continue reading »

As ready as I’m going to be

Tomorrow is the first day in my new role at the Mozilla Foundation, and I’m getting the new job nerves and excitement now. Between wrapping up at WWF, preparing for Christmas, house hunting, and finishing off my next study assignment (a screenplay involving time-travel and a bus), I’ve been squeezing in a little bit of prep for the new job too. This post is basically a note about some of the things I’ve been looking at in the last couple of weeks. I thought it would be useful to jump through various bits of tech used in a number of MoFo projects, some of which I’d been wanting to play with anyway. This is not deep learning by any means, but it’s enough hands-on experience to speed up some things in the future. I setup a little node.js app locally … Continue reading »

Evening coding

With lots of interesting client work on at the moment, I’ve decided to spend some evening time moving along the next version of Done by When. This is nothing too stressful, but the project is getting really interesting now. I think I’m over the initial conceptual learning curve and now I’m making proper progress. Where the launch version of Done by When was primarily a working proof of concept, this next version is about attention to detail and responsiveness (that’s the speed of interactions as opposed to the adaptive layout stuff that’s already in place). I feel like I’m properly upgrading something when I’m spending as much time removing code as I am writing it new. More updates soon.