Raising the Bar - PA flames

Andrew Mason slackmase2 at gmail.com
Wed Jul 1 07:13:59 UTC 2009

Seeing where things break is often the motivation that is needed in
order to get things fixed. KDE and xorg is a good example. People in
xorg new that certain functions in the graphics drivers were not
working correctly but no one was using them so they don't become a
priority. Pushing the boundaries exposes those weaker areas and makes
the whole experience stronger for the whole community.

Also you mentioned wine is not compatible in this scenario but are
there any free as in libre applications that developers can test this
with? I personally don't have any proprietary applications that I
would be able to test wine with.


On Wed, Jul 1, 2009 at 2:35 PM, Eli Wapniarski<eli at orbsky.homelinux.org> wrote:
> On Tuesday 30 June 2009 23:25:44 Rex Dieter wrote:
>> FACT:  There are a small (gladly) subset of systems, drivers, apps that,
>> unfortunately, for one reason or another (I'm not assigning blame), that
>> do not interoperate well with pulseaudio.  Note, I am not assigning
>> blame, and neither should you.
> Actually... This is the core issue alot of the discussion that follows is indeed OT.
> If anyone wants to help to try to do more triage with the bug I reported it can be found at:
> https://bugzilla.redhat.com/show_bug.cgi?id=507589
> (Not a promo - By the way... the game I mention in the bug report is a lovely MMORPG with some of the nicest graphics I've seen anywhere).
> The key thought here is that are things like pulseaudio that mostly works but it does not work completely. My particular feeling is that in Fedora's enthusiasm (maybe over enthusiasm) to embrace the new stuff; and (indeed, that's why we're here at Fedora) we forget that it takes sometime for other projects to catch up and this in turn effects interoperablity which in turn has an impact on the user's experience. In the example being discussed wine and pulseaudio is one such example and with an impact on major subsystems such as wine.
> Now... it has been noted that the wine project is actively rewriting their sound subsystem which will also be embracing pulseaudio, probably for the better. But in the meantime I've got this funny networking problem with the game where if pulseaudio is running the game simply does not connect to the games servers. pasuspend does not work. Killing pulseaudio is the only way I was able to get the game to connect to its servers. But doing that breaks other things and this impacts once again negatively on the users experience.
> I guess what I'm trying to say is that one of the things that can be done to "raise the bar" is to try to be more certain that things work not just mostly works. If a project is alive and advancing then some accommodation should be made to ensure that it works; especially with major subsystems like wine. If the project seems to be dead, then well (maybe) it should be excluded.
> Any additional thoughts are surely welcome. I leave the floor open and will keep my keyboard to myself from this point forward regarding this topic.
> Eli
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> _______________________________________________
> fedora-kde mailing list
> fedora-kde at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/fedora-kde
> New to KDE4? - get help from http://userbase.kde.org

More information about the kde mailing list