Page MenuHomePhabricator

Consolidating time ranges across tech community metrics
Closed, ResolvedPublic

Description

Our tech community metrics would benefit from a consolidation of time ranges. A proposal:

  • Updated on a monthly basis.
  • Recent activity normalized to the past three months
    • Currently we have many metrics counting the last month only. While this might capture well the professional developers, it might affect the scenario of active volunteer contributors, which might accumulate significant contributions in a quarter, but not always month after month.
  • Active community normalized to the past twelve months
    • In our context, it is fair to define active contributors those that have registered activity in the past 12 months.
  • Offer all-time stats where it makes sense
    • We are doing this in most cases, but it is good to include it in the checklist.

Event Timeline

Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)
Qgil added a project: wikimedia.biterg.io.
Qgil added subscribers: Qgil, Acs.

For a ten year old project, it makes sense to have curves more normalized (and each data point not being entirely disjunct). The only small downside would be that we cannot quickly realize a trend that has only happened in the last month.

Generally agreeing on having less data points and clearer data. Now to identify which data sources we have, keep, and should update to the proposal above.

Qgil added a project: ECT-February-2015.
Qgil set Security to None.
Qgil added a subscriber: Dicortazar.

@Dicortazar, what do you think about the proposal to normalize graphs? Maybe we can offer tables with the exact numbers for every month, but then normalize graphs to see the actual trends with more consolidated data.

Qgil lowered the priority of this task from Medium to Low.Feb 3 2015, 1:23 PM
Qgil removed a project: ECT-February-2015.

Meh, the more I think about this, the more I believe that it is better to focus on publishing the metrics we need, keeping these ideas as a reference but without having to agree on them beforehand. Lowering priority for now.

After a chat today with @Dicortazar, and after he showed the reports they are preparing for OpenStack (example), I'm actually leaning toward quarterly samples for metrics counting people, i.e.

  • Number of active users in Gerrit
  • Number of users exercising +2/-2 in Gerrit
  • Active users in Phabricator

Taking quarterly samples is probably better to count the "long tail" of volunteer contributors. We can assume that almost all professional developers are active every month, but that is not necessarily true for volunteers.

On the other hand, graphs with quarterly metrics also provide less volume of information, less noise. Anyway, something like the population of contributor doesn't change radically from a month to another (there might be exceptions, yes).

Qgil removed Qgil as the assignee of this task.Mar 3 2015, 1:19 PM
Qgil claimed this task.

I don't know whether this is resolved or declined or both, :) but the fact is that we don't have a problem "Consolidating time ranges across tech community metrics" today.