> First, thanks to all of the MAME devs for their work over the years on an application > that continues to get better and better. There are plenty of us in the loft that do > appreciate you even if we don't always voice it. The application has literally > changed my life. > > That said, one reason many people go into the developer field (and I.T. and > accounting, for others) are because they are not people persons and deal best with > machines. I know I'm not alone when I say I stopped participating in MAME Testers > some time ago as well as most of the forums on MAMEWorld is because of getting > consistently pissed on for questions or reporting bugs. Not all of us are > programmers, and staying abreast of every change made to the application could be a > full-time job assuming you even understand them. More pats on the back might be > facilitated by fewer kicks in the nuts to the little people. When met with consistent > negativity and rancor, it does not motivate a lot of people to participate, let alone > donate. I'm sure I'll get flame replies for this, but it is what it is. Appreciation > works both ways.
I know that in some cases with bug reporting, dealing with reports and communication after determining validity those can seem harsh to those reporting. In your case I just now looked at each bug you've reported (showing you as the original poster) and you've had many resolved issues, a couple which are still confirmed and yet to be fixed, but many were closed. I didn't see any overt examples of people getting "pissed" over your bug reports (at least on MAME Testers). Perhaps you have an example?
Some of those closed were related to external artwork packages or cheat file issues which fall outside of the scope of MAME Testers. Some other were presumptions and observations of change but determined (after some research and convincing Developer input) not to be valid emulation issues. Some were local configuration problems which cleared up after deleting a machine's .cfg, .ini or nvram. There were even a few duplicate (already reported) closures which happened.
If you have suggestions how I could (or others could) handle bug reported better, of course I wouldn't mind some feedback. For myself, I apologize for your feelings of being disenfranchised with the bug reporting process.
|