From: "Ingo Müller" <alsa@ingomueller.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: The per-soundcard Documentation is ABSURDLY out of date
Date: Wed, 07 Feb 2007 18:37:39 +0100 [thread overview]
Message-ID: <45CA0E63.6030003@ingomueller.net> (raw)
In-Reply-To: <s5h7iuuudtq.wl%tiwai@suse.de>
Takashi Iwai schrieb:
> At Wed, 07 Feb 2007 09:58:42 -0500,
> Paul Davis wrote:
>> Someone on ardour-users just asked a question based on docs for the RME
>> HDSP 9632 @ alsa-project.org. I took a look.
>>
>> The docs there are written as if no linux distro has ALSA builtin. The
>> same appears to be true for every other card I looked at. It tells
>> people how to (re)build and (re)install ALSA.
>>
>> This is deeply confusing and wrong. I wish I had time to correct it
>> myself.
>
> I come to believe that it makes little sense to keep this style of
> project page, at least, as it is. We have too little horses while the
> load gets bigger and bigger. As I've suggested many times, we should
> change to more open style like Wiki to avoid rotten information.
> (Yeah once ago I was against Wiki, but the time changed...)
>
Hi!
I agree totally with you, Takashi. As you sure know, there is already a
wiki on http://alsa.opensrc.org/. I'd suggest to merge these two major
sources of information: the mentioned wiki and the official page. On
that mailinglist two months ago when I was not that deep into the
subject, I wrote (title "PLEASE improve the ALSA documentation!") that
one of the biggest problems was, that the documentation was "splattered
all over the internet". The merging of those two sites would therefor
not only be more easily to maintain, but it would be a lot better for
the user!
There's something else I already wrote back then: I said that I was
willing to help and I'm repeating it here! Since then, I made over 1500
contributions to the wiki, most of them simple transfering to a new
wikisoftware, but also restructuring and some new articles. I also said,
that I didn't want to be alone, but hey, nobody can conjure up
volounteers and as you said, Takashi, few horses and big loads... Maybe
this can be an occasion that more people join the forces and that the
documentation is finally rebuilt!!
Thanks to anyone sharing his ideas about that topic!
Regards, Ingo
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2007-02-07 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 14:58 The per-soundcard Documentation is ABSURDLY out of date Paul Davis
2007-02-07 16:34 ` Takashi Iwai
2007-02-07 17:37 ` Ingo Müller [this message]
2007-02-08 14:53 ` Takashi Iwai
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=45CA0E63.6030003@ingomueller.net \
--to=alsa@ingomueller.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.