[madez]

This reads as if the author were not suited for that kind of work. Yes, working through code and figuring out what it does, and why it does it that way, and whether it can be improved is work, maintainer's work, and if it's stressful, hard or not fun to you, than maybe you just shouldn't do it.

I have seen the other side in this situation. I've found it at times very hard to get reports about real bugs to developers. While some developers won't even listen to you if you tell them why their code is broken, others actually tell you what you need to do to give them what they need, and then they work on it. Shoutout to the xorg/mesa people; I've found them to be of the latter type.