OP mentions this has been an issue for a long time. Is there a way to diagnose it ?
I don’t want to hose down your enthusiasm, I really love the energy you’re pouring into looking at all of these issues …
But please don’t just mark them all NEEDSINFO/MOREINFO, ask the OP (who in this case is a long term contributor and who provided ample information to reproduce it) if it’s still present, and repost it here for someone else to act on.
It would be much more helpful if you spent some of that energy on trying to answer some of those things yourself. Getting the OP to take time out of their day to repeat themselves isn’t a good use of their time or a good way to encourage them to donate more of it to report more of the issues they notice in the future. And if I have to drop what I was otherwise doing to reopen/reconfirm a bug that should never have been reverted to NEEDSINFO in the first place, that just means it’s going to take longer for me to finish the things I need to do before I have time to work on more of these things.
So maybe start with the ones that you can test or investigate more yourself, and then only if you actually have something new to add to the report, seek confirmation and/or a sanity check from the OP and other people if you aren’t absolutely sure about what your new information really means.
It’s ok for bugs to be open and for people to be too busy to fix them all today. That’s why we have a tracker. Work on triaging them is very welcome, but to be properly helpful that needs to be more than just waving them at other already busy people in a different forum.
It’s ok if you have to pass some of them over because you don’t know what to do with them either too. But if they just end up closed simply because nobody had time to respond to you marking them NEEDSINFO, that doesn’t really help anyone.
We’re a very limited team, we have to work smart if we want to make the most of our limited time.
1 Like