Report our major upstream contributions in our quarterly updates

[choldgraf]

Context

I have been working on our quarterly team update using @damianavila's excellent "team changelog" list that he shared below:

• [blog] Quarter 2 update #452

However, that changelog tracks items that tend to be 2i2c-focused (around our hubs, communities, etc). Given that a large part of our mission entails providing upstream contributions and support, we should also communicate to our stakeholders what kind of upstream work we have done.

Proposal

We should define some way to track the upstream contributions that 2i2c team members have performed while "wearing their 2i2c hat". AKA, things that are in-scope for being on the clock (and not things that people feel they are doing in their off-work hours, 2i2c shouldn't get credit for that IMO).

It will be difficult to track this automatically and easily, but here are a few rubrics we might follow:

• Define a few key stakeholder projects (e.g., jupyter, jupyterlab, jupyterhub, pydata-sphinx-theme, executablebooks).
• For each project:
• Grab a list of any pull request that was merged with a window of time, that was authored by a 2i2c team member
• Calculate the number of comments we gave on issues and code reviews we performed
• Have a section for "upstream contributions" that includes any notable PRs we grabbed above, as well as some summary statistics for each like "participated in N conversations"

Updates and actions

No response