Yes, I can add some more info here
Bitergia are great. They are an extremely helpful and intelligent team who even volunteered on our pre-Portland-All-hands contribution analysis project here: https://wiki.mozilla.org/Contribute/analysis
The tools they built are great if you’re looking at participation in open source software from a development point of view (Code / Bugs / IRC / mailing lists) but this was only part of what we were looking at last year. For context, the Foundation data I was looking at included a couple of hundred people who contributed this way, out of the ten thousand or so total contributors. So we needed many systems.
I did use one of their tools (Bicho) in the infrastrucuture that I pieced together to help get data out of Bugzilla for Webmaker.
If I was tasked with building a dashboard for a specific engineering project today, I’d definitely start with their tools.
The Webmaker dashboard Bitergia built for us (very kindly) was a proof of concept we hoped would have wider adoption, but it wasn’t an org priority so it hasn’t moved any further since then. We were missing some data, like mailing list archive files and IRC logs, but these could be solved if needed. One other challenge we hit was that our Bugzilla history is so large it was going to take a very long time to get the data into Bitergia. That’s why the demo just looked at Webmaker.
This was part of the reason why the data we cared about was being joined up in our internal project Baloo, because our data team could copy / transform / manipulate the data directly rather than rely on ‘scraping’ processes. I should note that no one is actively working on Baloo right now.
–
While that’s some extra background on our work, that doesn’t really answer the question of visualization.
The general challenge you’ll face is joining up data from many different types of interactions in a single format (this is the data warehousing excercise that Baloo was focussed on) and then using that central data to build visualizations.