Because they give kids (kids have no experiences & are immature) the right to decide if your bug is good or not.
i don't like the bug/translator system. Badly organised..
I understand it may appear irresponsible of me to grant someone who isn't employed at Multiverse, the power to essentially decide which bugs are legit and which are not. I want to make two things very clear, though.
Moderating them is very, very easy. Not only can I see everything they do, what they report to me and what they do not - you can do this as well. The reason why we have labels isn't to make our job easier, it's to add transparency so everyone can see what decisions we're making. This isn't only to moderate Jens and Dogeritos, you can see what I choose to accept as well. If we were to ever incorrectly give someone a reward, or incorrectly neglect someone who shouldn't be, you have the power to call us out on that, and make sure we do our jobs properly. So far I haven't received a single complaint, so I think everything is working as intended.
Second of all, the only problem people seem to have with this, is that I don't always have time to reply to bug reports on mondays. I don't work full time, and when I'm at the office, I have a million things to do. This means I sometimes have to prioritise doing something else instead of reading bug reports. This does
not mean a bug report will go unnoticed, I will eventually see everything. If I ever miss something, you'll be able to see that I did since we're using public labels. I'll give you an example
This week I've been at the office for a total of 6 hours, in which I've only managed to verify 2 bug reports. Why is this?
On monday we had a bit of an emergency, where Christian suspected he might've released a very severe bug to BR, which could potentially ruin projects permanently. Mads, Phillip and I spent all of our time entirely dedicated to reproducing this issue, so I ended up leaving without having read a single report.
I can't disclose in detail what I spent most of my day doing today, but it's some boring stuff that has to do with how we report stuff internally. I spent a lot of time talking to programmers about these changes, writing emails to other people within the company, and implementing the changes. Thankfully it didn't take all of my time, and as such I managed to verify those two issues.
Keep in mind even after I've spent that much time doing something else than verifying bugs, I still have a ton of other tasks to do. Thankfully they are lower priority tasks, so hopefully I'll be able to verify the remaining reports tomorrow.
Hopefully this gives you some insight into how all of this works, I hope I've changed your mind regarding me being poorly organised.
