Love the scientific focus. We need to be better at tracking stuff like this because not all code has the same level of risk.
The "scientific focus" is what I was going for. This article will be one I update as I gather more information on various projects (may even include data passed on to me via reliable sources).
If we could get tooling to indicate what line or method an error occurred, maybe something to look at FIX commits, it might be possible to automate some of this, but it requires process changes and discipline. It's an interesting idea.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.