All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Florian Schmidt <mista.tapas@gmx.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: doc-page
Date: Fri, 05 Dec 2003 04:15:39 +0900	[thread overview]
Message-ID: <3FCF87DB.10106@boosthardware.com> (raw)
In-Reply-To: 20031204194243.4841b5a7.mista.tapas@gmx.net

Florian Schmidt wrote:
> Hi Patrick. I saw your changes to the doc page and have one or two
> remarks:
> 
> 1.] The layout is a litle bit messed up here. The black line goes
> through "Supported Soundcards" and "Userspace Tools". If i use a smaller
> font, it's ok. so i don't know, if it's a mozilla thing [Mozilla Debian
> Package 1.5-3]..
> 

Yeah I removed it (was just playing around with layout).

> 2.] There's quite a lot of info in the wiki allready and i wonder if we
> could just create [initially empty] entries in the wiki for the missing
> links [like dmix/dsnoop, 5.1 sound...]. There's already a dmix page in
> the wiki which we could link to. As it grows more mature it can  someday
> maybe be integrated into the "normal" documentation..
> 
> Using the wiki for drafts for these pages also has the advantage of that
> it is very easy to set up initial pages which then can be improved.
> Let's say: it becomes much easier for the user to contribute
> documentation this way.. Also users who don't know what a wiki is will
> soon learn if links from the doc pages go to it :)
> 

I would prefer to have actual data before we make a link. It drives me 
nuts when I go to find info on the official site for a project and the 
links just lead to dead ends. The extra clicks for nothing make me feel 
annoyed.

> 3.] Contrary to my first draft of the TOC i would suggest moving the
> soundcard matrix to the system maintainers section. Also the name "Sound
> Card Matrix & User documentation" is misleading. I suppose this means
> the user supplied info regarding each driver. I would rather have "User
> documentation" as a single Topic for documentation that is really aimed
> at the end user [This contains the userspace tools and the .asoundrc,
> though this also overlaps with system maintainers stuff]
> 

People have given a lot of suggestions for the matrix which I'm working 
on adding. I'm trying to find a way to combine all these things into a 
neat little package. Until then we will just have to make do with links 
to all the various sources as our main stay.

> 
> P.S.: If you want help with it, i could just do the changes to a local
> copy and then send you a diff.
> 

Sure. Any contributions are welcome.


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================


  Apparently upon the beginning of the barrage, the donkey broke 
discipline and panicked, toppling the cart. At that point, the rockets 
disconnected from the timer, leaving them strewn around the street. 
Tethered to the now toppled cart, the donkey was unable to escape before 
the arrival of U.S. troops.

United Press International
Rockets on donkeys hit major Baghdad sites

By P. MITCHELL PROTHERO
Published 11/21/2003 11:13 AM



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  reply	other threads:[~2003-12-04 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 18:42 doc-page Florian Schmidt
2003-12-04 19:15 ` Patrick Shirkey [this message]
2003-12-05 17:16   ` doc-page Martin Langer
2003-12-07 15:43     ` 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=3FCF87DB.10106@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mista.tapas@gmx.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.