|
|
Re: since MAMETesters simply close issues which appear in current git builds....
09/16/15 03:59 AM
|
|
|
> I'll make no excuses for supporting what I perceive could be a beneficial and
> valuable method of communication with this project's Developers and the userbase. All
> end users, developers and contributors should at least attempt to work together for
> the betterment of this massive project. In fact, I've started up the GIT Issue
> Tracker today to see how that functions to allow active users to report confirmed
> pre-release regressions. So far, so good.
No it isn't good so far. It's a whole lot more e-mail noise for nothing. MAME is not a day job: we are not paid, we are not on call, we have other responsibilities. We don't have to answer to users in this way. Even if these were paying customers, accepting bug reports that are not from a baseline release would be stupid, as it just generates far too much noise.
I can see a few outcomes to this, and none of them are positive: the majority of these reports are ignored as they're known or expected issues and MAMEdevs don't have time or inclination to respond, so users decide MAMEdev is unresponsive and reputation is harmed; some MAMEdevs try to respond to all reports, get burned out, and leave the project; MAMEdevs steer well clear and it becomes an echo chamber of people with no clue talking crap, but it still appears to be officially endorsed and thereby harms MAMEdev's reputation.
This is seriously misguided, and I'm not the only MAMEdev expressing displeasure about it. You really need to consider what the people who actually do the tough development think before pushing forward with these things.
|
|
Index 
Flat 
Re: since MAMETesters simply close issues which appear in current git builds....
Reply
