From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: more improvement of alsa web pages
Date: Wed, 24 Apr 2002 15:13:33 +0200 [thread overview]
Message-ID: <s5hbsc9grya.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020424122621.A7A461E8A9@Cantor.suse.de>
At Wed, 24 Apr 2002 08:29:44 -0400,
Paul Davis wrote:
>
> >how about to add informational pages for each driver, and make links
> >from soundcard matrix? then a user can reach to the detailed info by
> >two clicks from the top page.
> >
> >a driver page will contain:
>
> [ ... ]
>
> >the pages should be controlled by cvs, so that both developers and web
> >admins can keep them up-to-date.
> >an advantage is that we can generated documents for
> >alsa-kernel/Documentation from these files.
> >
> >i'm not sure whether these docs to be auto-generated or should be
> >static files. also, we need to discuss which format is best - sgml,
> >docbook, html or else.
> >
> >we can start from converting existing docs (e.g. CMIPCI.txt) to
> >such pages.
> >
> >
> >any comments please?
>
> we had quite a bit of discussion about this a month or two back. some
> people were in favor of something like a wiki, where people could add
> information in a dynamic, immediate way, and thus increasing the
> likelihood that we'd accumulate a bunch of useful information. others
> wanted something more like you're suggesting.
ah, i remember the thread, too.
> i think that its important that there is a mechanism to make
> collecting information from users extremely easy, because otherwise
> there simply won't be very much in this pages. CVS doesn't meet this
> requirement since its intended to grant write access to a relatively
> small number of people (and certainly not just anybody who happens to
> have a useful piece of info about their audio interface).
yes, feedbacks from users are very important. however, i am
suspicious to give any possibility for arbitrary users to write /
update the contents. i prefer a non-interactive system with
moderators (or editors) to keep the quality and consistency of
contents (please remember that i think of documents to be put in the
kernel tree, too). moderators receive a page source (e.g. wiki) from
users and put it to the web.
for quick reaction to the new info, we can have an e-mail account
which notifies the mails to all moderators, so that it's updated asap
by one of them. in the above i suggested cvs only as a method to keep
the page sources and solve the confliction between moderators for
updates.
> patrick even mocked up a sample page which i critiqued in a number of
> ways.
>
> whatever we do, we should move forward with this fairly quickly,
> because its one of the biggest weaknesses (after the complete lack of
> user-usable documentation for ~/.asoundrc) of ALSA at this time.
yeah, exactly..
Takashi
next prev parent reply other threads:[~2002-04-24 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 9:31 more improvement of alsa web pages Takashi Iwai
2002-04-24 12:29 ` Paul Davis
[not found] ` <20020424122621.A7A461E8A9@Cantor.suse.de>
2002-04-24 13:13 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-24 12:46 Patrick Shirkey
2002-04-24 13:15 ` Takashi Iwai
2002-04-26 11:18 Patrick Shirkey
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=s5hbsc9grya.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=pbd@op.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.