Topic

Indicate which topic your proposal falls under:

Overview

We have some specific pain points around newcomer onboarding and the pull request review process which we hope to address as part of this Summit. Establishing metrics for these issues is critical to understanding where we are, and whether we've improved.

Author Note: This proposal has been updated to reflect the data which currently exists on openedx.biterg.io

https://www.loom.com/share/90059496bee54a769d8f56157371194b?sid=c40194f1-cd5c-4a89-869f-a39e7d33adcb

Solution

The Open edX's Bitergia instance (openedx.biterg.io) has a number of useful metrics we can use to measure the effect of the changes implemented as part of this Summit.

Improve Review Processes

These existing metrics that can help us measure our progress on the review process.

Github > Pull Requests Efficiency

Enhance Core Contributor Onboarding

To report on improvements to the Newcomer experience we can use these existing metrics.
Community > Contributor Growth

To measure newcomer experience more directly, we would need to update openedx.biterg.io to report additional participation metrics across Open edX repositories, Discourse, and Slack.

Some salient metrics from the CHAOSS list are:

Wikimedia use a system called Gerrit for managing their change requests, and they have several newcomer-related dashboards we could borrow from, though we would still need to build our data sets and charts ourselves.

Impact

This proposal aims to measure the health of Open edX in general, and the effectiveness of improvements/changes made to the program. We can measure the effectiveness of using openedx.biterg.io metrics by counting the number of places where the CC program uses this data.

Timeline

The existing metrics can be used right away.

It’s difficult to estimate how much time it will take to build each metric, since I haven’t done this before. But once one is done, others will surely be quicker to add. And modeling our work on existing dashboards will also speed things up.

Additional concerns:

Deploying GrimoireLab was relatively straightforward, but the process for cleaning up the data was onerous.

Have asked Edward Zarecoron Slack for advice on this, as he did the initial cleanup.