All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Constable <markc@renta.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Status of ALSA documentation?
Date: Fri, 15 Feb 2002 14:56:11 +1000	[thread overview]
Message-ID: <E16baPy-0005d8-00@usw-sf-list1.sourceforge.net> (raw)
In-Reply-To: <20020214100252.3E1D0274E@sitemail.everyone.net>

On Thu, 14 Feb 2002 20:02, Patrick Shirkey wrote:

> 1: Less developer news
> 2: A mission statement
> 3: More emphasis on information related to vendors
>
> What else do people want to see changed?

Developers are usually familiar with ALSA and know where
to look for further information. To me, the main strength
of the website should be for end-user information like
how to set up and configure ALSA drivers and modules so
clear links to HOWTOS and anything that eases the pain
for new ALSA users to get the most out of their audio
systems would be great.

I recently showed a Mac user interested in using Linux
for live stage work (no gui needed) the ALSA site so they
could get some idea of progress... they just laughed and
said there was _nothing_ there to help them evaluate whether
ALSA (therefor Linux) was going to be useful to them... well,
not within a 5 minute perusal anyway.

No doubt a slash/nuke-like portal would be asking too much ?

--markc

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  parent reply	other threads:[~2002-02-15  4:56 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 10:02 Status of ALSA documentation? Patrick Shirkey
2002-02-14 13:57 ` Jaroslav Kysela
2002-02-15  4:56 ` Mark Constable [this message]
2002-02-15  5:03   ` Paul Davis
2002-02-15  7:45     ` Mark Constable
  -- strict thread matches above, loose matches on Subject: below --
2002-03-04  8:25 Patrick Shirkey
2002-03-02 23:58 Samuel S Chessman
2002-03-02 19:28 ` Paul Davis
2002-03-02 15:33 Patrick Shirkey
2002-03-02 13:08 Patrick Shirkey
2002-03-02 17:27 ` Paul Davis
2002-03-05 14:56 ` Juhana Sadeharju
2002-03-05 10:18   ` Paul Davis
     [not found] <E16g5Uz-0001y7-00@usw-sf-list1.sourceforge.net>
2002-02-28 20:05 ` Juhana Sadeharju
     [not found] <E16foSl-0000MV-00@usw-sf-list1.sourceforge.net>
2002-02-28 19:57 ` Juhana Sadeharju
2002-02-27  8:46 Patrick Shirkey
2002-02-27  8:19 Patrick Shirkey
2002-02-27 14:51 ` Paul Davis
2002-02-26  7:20 Patrick Shirkey
2002-02-26 15:10 ` Paul Davis
2002-02-26  7:02 Patrick Shirkey
2002-02-26 15:07 ` Paul Davis
2002-02-26  4:53 Patrick Shirkey
2002-02-26  5:17 ` Paul Davis
2002-02-19 15:01 Patrick Shirkey
2002-02-19 15:42 ` Mark Constable
2002-02-21  6:31 ` Kai Vehmanen
2002-02-25 17:43   ` Paul Davis
2002-02-26 14:49     ` Jaroslav Kysela
2002-02-15 12:12 Patrick Shirkey
2002-02-21 11:31 ` James Tappin
2002-02-15  7:39 Patrick Shirkey
2002-02-15  7:36 Patrick Shirkey
2002-02-15  7:34 Patrick Shirkey
2002-02-15 15:45 ` James Courtier-Dutton
2002-02-15 18:18   ` Kevin Conder
2002-02-15 18:22     ` Paul Davis
2002-02-15 20:23     ` Andy Wingo
2002-02-15 22:05       ` Kevin Conder
2002-02-13  9:32 Patrick Shirkey
2002-02-13 10:05 ` Kai Vehmanen
2002-02-14  9:15 ` Jaroslav Kysela
2002-02-12 16:17 Kevin Conder
2002-02-12 17:17 ` Kai Vehmanen
2002-02-12 18:43   ` Kevin Conder
2002-02-12 19:33     ` Kai Vehmanen
2002-02-12 19:57     ` Jaroslav Kysela
2002-02-13  8:39   ` Guenther Sohler
2002-02-13  9:12     ` Jaroslav Kysela

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=E16baPy-0005d8-00@usw-sf-list1.sourceforge.net \
    --to=markc@renta.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.