Upstream activity#

This page summarizes where 2i2c spends its time in the Jupyter ecosystem and in our own technical repositories. It’s goal is to give us an idea for where we’re shouldering maintenance and development burden and having impact.

Last updated: Nov 16, 2026

Data sources

These plots use SQLite releases from jupyter/github-data and 2i2c-org/github-data.

TODO: This needs another few QA passes, but it’s useful-enough that we are posting it as-is. See this issue to track QA checks we should implement: 2i2c-org/kpis#81

Merged PRs authored by a team member#

Reflects where we are making technical and community contributions.

Table of issues and PRs that match the plot above:

Issues opened by a team member#

Reflects where we are opening suggestions and design proposals for improvements or bugs.

Table of issues and PRs that match the plot above:

Comments on PRs by non-team authors#

Reflects where we are spending time reviewing and giving feedback for other contributors.

Table of issues and PRs that match the plot above:

Comments on issues by non-team authors#

Reflects where we are providing support and discussion for users and other contributors.

Table of issues and PRs that match the plot above:

Upstream leaderboards#

LFX Insights is a service from the Linux Foundation to track community health and contributions. We keep an eye on the contribution leaderboards to see where we, and the collaborators we work with, stand in relation to others.

JupyterHub
Jupyter Book
Jupyter Organization

Activity in 2i2c repositories#

Reflects where we’re spending our time in 2i2c infrastructure repositories (these are all open source, but currently controlled by 2i2c).

Table of issues and PRs that match the plot above: