Comment 500 for bug 371897

I know I'm just a user and I probably don't understand much of wine's developement, but Maarten put a lot of effort into a patch that fixes an issue ( or a serious lacking, up to you ) that wine'd had for 5 years now, shouldn't that be enough to prove himself to the devs' team? At least take a look at his work, everybody who tested it can say how well it works, and it's surely better than the other pulse patch around. Heck, it even makes games run smoother now that alsa/pa don't hog the cpus anymore.
Even if you still don't trust him, or if he committed some errors in the past, you have to face the actual situation: years ago pulseaudio was considered ( by some ) to be the future of sound management for linux, writing a driver for it was pretty much a gamble, especially since wine already had a ton of other drivers that could work with pa. Right now though, pa is the default on many distros, including the most popular ones, and it's actually been like that for a couple of years. How much longer will this have to carry on? Wine's support for pa should be a must right now, sticking with alsa is just not viable anymore ( you don't believe me? Check how many distros ship a patched wine with pa support ), and waiting for Maarten to "prove himself worthy" by doing unrelated work will just push back this necessary feature for how much? Months? Years? Even worse, the other pa patch could be included in wine before that, the one with many sound issues and that still causes cpu spikes, and that'd just make harder ( if not impossible, or "not worth it" ) to include the only working pa support we have right now.
Seriously, at least take a look at his work and give some technical reasons why you don't want to include it in upstream wine, else it'll keep looking like you just don't care about pa for personal reasons, as I ( and probably other people ) think. It's really time to catch up with the present.