Ctrl+K

Upstream community activity

Upstream community activity#

This is a short visualization of the 2i2c team’s activity in upstream repositories. Its goal is to give a high level indication of where we’re spending our time in key upstream communities.

Last updated: Apr 28, 2024

Work in progress!

This is a work in progress, so some of the GitHub search queries might be slightly off. Use this to get a high-level view, but don’t read too much into the details.

Showing data from 2023-10-29 to 2024-04-28

Key upstream communities#

Key upstream communities are communities that 2i2c utilizes, empowers, and supports. We try to use technology from these communities wherever possible, and put additional team resources towards making upstream contributions and providing general support. See the 2i2c team compass for more information about this.

Below are 2i2c’s key upstream communities:

Key upstream communities:

Merged PRs authored by team members#

Pull Requests that were authored by a 2i2c team member, and merged by anyone. This gives an idea of where we’re committing code, documentation, and team policy improvements.

The plots below show recent activity over a 2-quarter window, while the button below runs a GitHub search for all activity since 2i2c’s creation.

All Merged PRs authored by 2i2c team members in key upstream communities

Click to see GitHub search

Now we break it down by repository to visualize where this activity has been directed.

Tip

Click a bar to show a GitHub search that roughly corresponds to the underlying data.

PRs merged by team members#

This gives an idea of which Pull Requests were merged by a team member (not necessarily authored). Merging Pull Requests is a reflection of reviewing and incorporating the work of others as opposed to only our own work.

Now we break it down by repository to visualize where this activity has been directed.

Tip

Click a bar to show a GitHub search that roughly corresponds to the underlying data.

Issues opened by team members#

This shows issues that a 2i2c team member has opened over time. This gives an idea of where we are noticing issues and suggesting improvements in upstream repositories. The plots below show recent activity over a 2-quarter window, while the button below runs a GitHub search for all activity since 2i2c’s creation.

All Issues opened by 2i2c team members in key upstream communities.

Click to see GitHub search.

Now we break it down by repository to visualize where this activity has been directed.

Tip

Click a bar to show a GitHub search that roughly corresponds to the underlying data.

Comments by a 2i2c team member#

Comments are a reflection of where we’re participating in conversations, discussions, brainstorming, guiding others, etc. They are a reflection of “overall activity” because comments tend to happen everywhere, and may not be associated with a specific change to the code.

visualize_over_time(comments, title=”Comments made by a team member, over time”)

Now we break it down by repository to visualize where this activity has been directed.

Tip

Click a bar to show a GitHub search that roughly corresponds to the underlying data.

Contents