Understanding the contributor metrics on the trends dashboard

A contributor is defined as anyone who has performed any code related activity across all monitored repositories for the project. A code activity can be anything from:

  • Commits pushed
  • Code Change Requests submitted
  • Code Change Requests reviewed (including comments/reactions/approvals)
  • Code Change Requests merged
  • Code Change Requests comments (outside of reviews)
  • Issues submitted
  • Comments added on issues
  • Reactions added on issues
  • Issues closed
    Any member of the community participating in any or all of the above activities are included in the computation of the contributor strength metrics on the trends dashboard which is therefore an aggregated value of the all the unique contributors for a project. The contributors from each sub-project are aggregated at the project group or the foundation level still maintaining the uniqueness across the entire foundation.

Thank you for the write-up @sgupta this is great to know, and welcome to the community :sunglasses:!

One question I have regarding this is, are there any plans to include confluence contributions to the aggregate contribution trend data in the main page of insights?

Hi @Henry_Quaye yes we will be adding more metrics on the trends dashboard encompassing other areas like documentation, mailing lists and social media.


A critical piece in the computation of Contributor Strength is understanding how contributor identities play a significant role in getting the most up-to-date count of unique contributors.

Let’s take a look at this commit snapshot

As seen, there are two different identities, one that of the committer and the other of the one creating the PR to get the commit merged.

This is a common practice and one of the perks of contributing to open source projects that a contributor can choose the identity from which they would want to contribute to a project. While the Github account can be the same, the underlying commit identity can be different. Hence it becomes imperative to associate different identities to the same user in order to uniquely identify the contributor.

In the above example, both the identities Github username ‘1010sachin’ and the commit identity ‘sgupta@linuxfoundation.org’ belong to that same person (that’s me) hence when computing the contributor strength these two identities will be counted as one belonging to the same contributor profile.

Many projects have implemented various ways to deal with this complexity of multiple identities by means of gitdm files, DCOs and CLAs but this is still a small chunk of the vast open source communities.

In Insights, our team constantly work on finding identities that belong to the same user and merge them in the background. Hence, as identities are merged, the count of the contributors vary on the dashboards. Once all the contributors are correctly identified all their future contributions coming from the same identities will automatically be synced and there no need to take any actions. However, this exercise needs to be performed regularly as new contributors join the project. Hence handling the identities manually is not a scalable solution.

With LFX, we are trying to solve this by introducing a self-serve portal called the ‘Individual Dashboard’ that allows the contributors of open source projects to not only claim their own identities but also get an aggregated view of their code contributions in addition to other key details like events attended, badges etc. You can view your own personalized Individual Dashboard by signing in at https://openprofile.dev and connecting your identities under the Identities section here Individual Dashboard | The Linux Foundation.