Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Topic

Indicate which topic your proposal falls under:

  • Enhance Core Contributor Onboarding
  • Improve Collaboration, Communication & Reporting
  • Improve Fulfilling Commitments and Planning Processes
  • Improve Review Processes

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.

Solution

Reinstate Open edX's GrimoireLab instance (metrics-dashboard) previously deployed by Axim to report participation metrics across Open edX repositories, Discourse, and Slack.

Pick some salient, out-of-the-box metrics from the CHAOSS list to track in the Contributors Updates and CC program annual report, e.g

  • Newcomer Experience – How well does an open source community attend to welcoming newcomers? 

  • Conversion Rate – What are the rates at which new contributors become more sustained contributors? 

  • Change Request Closure Ratio – Is the project keeping up with change/pull requests?

  • Issue Response Time – How much time passes between the opening of an issue and a response in the issue thread from another contributor?

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 adding GrimoireLab to our toolset by counting the number of places where the CC program uses this data.

Timeline

In 2022, OpenCraft estimated the effort needed to reliably deploy GrimoireLab at 115 hours . This estimate includes:

  • Upgrade metrics-dashboard to the latest version

  • Improve deployment using helm charts and terraform (discovery only)

  • Pull data from github + Discourse + Slack

Additional concerns:

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

In addition to operational resources to set up and maintain the data, this proposal requires someone to pay for hosting the service and its databases.

Have asked Edward Zarecoron Slack for advice on both points.

  • No labels