Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA docs
Date: Sun, 21 Jul 2002 15:40:52 +0900	[thread overview]
Message-ID: <3D3A5774.9030107@boosthardware.com> (raw)
In-Reply-To: s5heldzr516.wl@alsa2.suse.de

Takashi Iwai wrote:
> At Sat, 20 Jul 2002 01:17:46 +0900,
> Patrick Shirkey wrote:
> 
>>I'm in the process of reading up about different ways of setting up the 
>>new alsa docs so that they are in the style of the new website design 
>>and have the look and feel of current documentation on other websites.
>>
>>I'm using the online manual for http://www.php.net as the design basis.
>>
>>Before I spend any more time on coding up a dynamic user 
>>maintained/contributed site what is the general consensus on allowing 
>>contribution to the documentation from anybody?
>>
>>I have an almost fully working setup now which will allow users to 
>>contribute ideas and helpful hints. The problem I now face is whether or 
>>not to automate the input or filter it by having it sent to me (or other 
>>people) so I/we can post it at our discretion.
>>
>>I note that a lot of sites that seemed to originally have allowed input 
>>from users to be automatically added to their webpages have decided to 
>>change their policy to filtering due to spam or misleading information 
>>being posted.
> 
> 
> imo, the documents on the "official" web site should be reviewed and
> moderated.  one reason is to keep the contents technically correct,
> and another is to keep the consistency of the page design (and
> to avoid possible spam problems as you mentioned above, of course).
> 
> for auto-generated documents, we already have wiki.
> isn't it enough?
> i've been very impressed by the convenience of wiki.
> 

Yes me too.

> 
> well, if you think it's too much for you to moderate the input from
> users, then i don't mind to change this policy.

I don't mind being a moderator if people trust my judgement enough. If 
it becomes a too much work then we can change how it's done. Keep things 
fluid.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-07-21  6:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19 16:17 ALSA docs Patrick Shirkey
2002-07-19 17:39 ` Takashi Iwai
2002-07-21  6:40   ` Patrick Shirkey [this message]
2002-07-25 16:20     ` Patrick Shirkey
2002-07-25 16:32       ` Paul Davis
2002-07-25 17:03         ` Patrick Shirkey
2002-07-25 17:51           ` Patrick Shirkey
2002-07-27  0:15             ` Paul Davis
2002-07-29  4:38               ` Patrick Shirkey
2002-07-29 12:08                 ` Paul Davis
2002-07-29 17:55                   ` Patrick Shirkey
2002-07-29 18:12                     ` Paul Davis
2002-07-29 19:12                       ` Patrick Shirkey
2002-07-29 20:25                         ` Patrick Shirkey
2002-07-27  0:20           ` Paul Davis

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=3D3A5774.9030107@boosthardware.com \
    --to=pshirkey@boosthardware.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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