From: Kevin Conder <kwconder@yahoo.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Re: documentation or lack thereof
Date: Tue, 10 Dec 2002 21:37:15 -0800 (PST) [thread overview]
Message-ID: <20021211053715.41569.qmail@web21007.mail.yahoo.com> (raw)
In-Reply-To: <E18Lut8-0005PF-00@sc8-sf-list2.sourceforge.net>
> > on the other hand, having more documentation is almost always a
> > good thing. now, where are the volunteers?
>
> Lot's of possible flames here but the main thing is that the
> people who do understand the alsa-driver well enough are either
> too busy to find the time or have justifiable reservations
> about getting their prose online.
>
> Unfortunately the people like myself are not in a position to
> edit large amounts of code documentation which we scour from
> the lists. I can however do a reasonable attempt at formatting
> the stuff. However I don't have much time or inclination to
> learn docbook at the moment so it wouldn't be a standard format.
>
> AFAIK there is only one other person round here who has the
> motivation and skills to do the docbook work and he must be
> busy at the moment or found other things to do.
Perhaps you're referring to me... It's true that I am busy with the
Alternative Csound Reference Manual these days. But I will help convert
ALSA documentation to DocBook/SGML (or Docbook/XML), if asked. I'm
currently helping Takashi with his HOWTO.
=====
-- kwconder at yahoo dot com
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next parent reply other threads:[~2002-12-11 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18Lut8-0005PF-00@sc8-sf-list2.sourceforge.net>
2002-12-11 5:37 ` Kevin Conder [this message]
2002-12-09 16:23 documentation or lack thereof Paul Davis
2002-12-10 17:59 ` 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=20021211053715.41569.qmail@web21007.mail.yahoo.com \
--to=kwconder@yahoo.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