Hey all, sorry I took a bit of a break from testing as I got rather busy with work, I didn’t just disappear.
I’ll look into the buddy system that @ankursinha mentioned!
It’s okay, it was just a bit confrontational, but I don’t think it broke the code really. It’s just I think someone who was really busy, I was trying to file bug for the upcoming Fedora 44 at the time while in beta. They probably were dealing with a lot of work due to the upcoming release themselves. And they weren’t wrong, they weren’t the ones who should have fixed it, I was told they were, but in hindsight it was the wrong instruction. And things like that happen.
I find in almost every open source project, devs seem to have their set of conventions or expectations, some of them clearer than others. And perhaps they think they deal with people who always know what they are doing, but some of us are a bit newer and would still like to learn. And a lot of the “read the manual” crowd might forget that instructions have to be understood by someone who doesn’t have the same context as the people who wrote those instructions.
I have had people in another distribution criticize me because I had posted a bug where wher code didn't look like this. I had actually lost the formatting between me drafting the post in a text file and copying it into the bug post.
And they ignored the bug itself, which frustrated me to no end because it prevented some PCs from booting with that kernel, and that was more important than how code looked.
When I posted this same bug in Bugzilla for Fedora, it got patched, so Fedora never shipped the kernel with the regression. So I already feel you guys do try to focus on what matters compared to some other places 
(although the formatting was fine that time.)
I think it’s a bit of a general “cultural” divide between new people and veterans, rather than a breach of code 
Given that a buddy system exists, the solution I mentioned is already in place. I will look into it.