Hi, I’m a decade-plus Haskell dabbler who’s now in a position to contribute to GHC, and I’ve been considering how I might do so most effectively. In reading the recent bug report about the contribution experience https://gitlab.haskell.org/ghc/ghc/-/issues/26728, one takeaway I had was that improving the testing story could make a big difference—making sure tests are reliable, trying to make the test suite fail as fast as possible, etc. Since most of my $JOB for the last dozen years was devoted to building bespoke testing infrastructure and working with engineers to come up with effective strategies for optimizing fail-fast—and working in a codebase that, itself, started with an unreliable test suite—this seems like an issue where I could help. Unfortunately, I couldn’t find any documentation on whether there is a person or a group that is primarily responsible for the testing infrastructure—no doubt the information is out there somewhere, and I just didn’t look in the right place—and I would appreciate any pointers as to who best to talk to in order to get involved. Thanks, Mike.