From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Web forums...
Date: Sat, 04 Feb 2006 13:59:05 -0500 [thread overview]
Message-ID: <1139079546.2791.42.camel@mindpipe> (raw)
It was recently brought to my attention that users are finding and
fixing (or at least working around) ALSA bugs in various web forums and
completely leaving the ALSA developers out of the loop. One user
basically implied that it was common knowledge that if you have $FOO
mainboard, then $BAR patch from som random Nvidia forum is needed to get
sound working. All news to me. I guess they assume we follow every web
forum in existence and know about every ALSA bug ever posted anywhere on
the Internet.
It seems like a valuable resource (users willing to test this stuff on
bleeding edge hardware) is going to waste because they don't even bother
to give feedback to the developers.
Of course ALSA development isn't moving to some lame web forum, and we
obviously don't have the bandwidth to follow 1000 hardware-specific
Linux user forums - can anything be done about this problem, other than
educating users that web forums are lame?
Lee
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-02-04 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 18:59 Lee Revell [this message]
2006-02-06 12:13 ` Web forums Tilman Kranz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1139079546.2791.42.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox