External impact

One of our (ambitious?) goals for this project is to get a sense of the impact of members of the UCL community on external open source projects.

We learned from the Turing folks that community health dashboards tend to be inward-facing. That is: for a GitHub organisation potentially plus several repos, but still "organisation first" rather than "contributor first". We will therefore probably have to spend some effort in creating a bespoke tool to help us answer this.

Definition of done

• Have defined a minimum viable (first pass) criteria to select "members of the UCL community"
• Have identified some GitHub API queries to obtain some exploratory data
• Have documented the criteria
• Have sanity-checked our criteria with some obvious known contributors (David in matplotlib, Mose in Julia).

Possible ideas

(and shortcomings)

• Usage of a @ucl.ac.uk email address to sign any commits (but we don't require that people use their UCL email).
• Members of the @UCL organisation (but we don't require staff and students to be members, and we don't necessarily remove leavers from the org).

Ultimately, we'll have to compromise.

Start by reviewing the issue's definition of done and the possible ways to identify UCL community members. Investigate GitHub API queries for exploratory data, document the selected criteria, and sanity-check them against the named contributors in matplotlib and Julia.