Comment 526 for bug 371897
Revision history for this message
|
|
#526 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to Austin English from comment #406)
> Bugzilla is not for discussion, as has been pointed out, e.g.,
> http://
>
> Please take the discussion somewhere else.
To avoid further discussion in this bug report, which seems to come back to life every so often, could you (Wine's staff) set up a place where it can be held, and where devs would actually give us (wine users) some kind of information about this issue? Mailing lists aren't so easy to follow when one doesn't have the time to dig through it all (I may be wrong, but the newest information regarding winepulse on wine-devel is months old), and having someone rationally explaining why winepulse is being kept away from upstream (in a non-wiki form, where users could actually ask questions and explain their perplexities and needs, and where they'd be able to hear actual devs explaining the technical difficulties, with a real interaction between the two) would prevent this bug report being flooded, AND it could also help to improve the general opinion of Wine devs (which some claimed to be narrow minded and refusing winepulse by personal believes/grudges rather than technical reasons).
Simple answers (eg. "we're working on it", "talk about it somewhere else", "read wine-devel") won't really prevent this discussion to spawn again in the future, isn't it better to face this problem now, after 8 years? I know users don't really have the right to make any demand to developers, but so far we've been ignored, threatened to being suspended from being able to post bug reports, and mocked (as it has been said in the forums sometimes, "install alsa or disable sounds" and such, which is plain mockery as some people actually need pulse for a reason or another), I believe we deserve some clear answers after all that.
So please, I beg you, set up a place where devs and users can, even for limited time, have a constructive chat about this issue, so that everyone can have an idea of what is actually gonna happen in the future regarding an upstream pulse driver.