X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs-
X-Authentication-Warning: basis.Desk.nl: listserv set sender to owner-beastium-list AT basis DOT desk DOT nl using -f
Message-ID: <19981208204824.C8178@cerebro.laendle>
Date: Tue, 8 Dec 1998 20:48:24 +0100
From: Marc Lehmann <pcg AT goof DOT com>
To: beastium <beastium-list AT desk DOT nl>
Subject: FAQ maintainer wanted
Mail-Followup-To: beastium <beastium-list AT desk DOT nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Operating-System: Linux version 2.1.131 (root AT cerebro) (gcc version egcs-2.92.25 19981130 (gcc2 ss-980609 experimental)) 
Sender: owner-beastium-list AT basis DOT Desk DOT nl
Status: RO
Content-Length: 1503
Lines: 39


As some of you might/might not know, the FAQ is basically orphaned. I keep
answering the same questions differently each time, but have no time to
update the faq accordingly.

Whats needed would be people that actively collect information on FAQ items
(like "mmx/3dnow support") from the replies other and I give on the list,
and prepare them in a form suitable for inclusion into the FAQ. Or, even
better, a FAQ maintainer devoting time into this.

The format the FAQ is prepared with basically looks like this:

Q: a question, possibly multi-line, is
put here?
A:and here is the naswer, again possible multi-line

i.e. a FAQ entry consists of "Q:" on a line with the question, and an "A:"
on a line with the answer, plus some additional details I don't want to
bother here. The current categories are:

faq	# the header
background
compatibility
installation
optimization
troubleshooting

Help would be _really_ appreciated. Not welcome are people that, as a first
measure, put their name into the FAQ as faq maintainer and then stop working
on it (yes, we had these).


      -----==-                                              |
      ----==-- _                                            |
      ---==---(_)__  __ ____  __       Marc Lehmann       +--
      --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com       |e|
      -=====/_/_//_/\_,_/ /_/\_\                          --+
    The choice of a GNU generation                        |
                                                          |