Received-SPF: pass
 receiver=logan.com; client-ip=64.102.122.148; envelope-from=echristl@cisco.com
Message-ID: <42023582.3060808@cisco.com>
Date: Thu, 03 Feb 2005 09:30:26 -0500
From: Ernest Christley <echristl@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040929
MIME-Version: 1.0
To: Rotary motors in aircraft <flyrotary@lancaironline.net>
Subject: Re: [FlyRotary] Re: FAQ
References: <list-656521@logan.com>
In-Reply-To: <list-656521@logan.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

jbker@juno.com wrote:

>Hi Ernest,
>
>Great idea to have a separate FAQ. It is certainly going to take some work to pull it together, but would save folks down the road a lot of grief. In particular is source of parts with part numbers etc.
>
>I could not reach you site at:  http://ernest.isa-geek.org/FlyRotary
>
>Bernie
>  
>

Bernie, I already pulled the small amount of information that I had out 
of my nascent FAQ and dumped it into Bob's WIKI.

If you've never used a WIKI before, you'll be pleasantly suprised after 
a very short learning curve.  Ever read a FAQ that was about 3yrs to 
old, so that about half the information was either irrelevant or just 
plain wrong?  Or  maybe the maintainer just lost interest halfway 
through and it is incomplete? The organic nature of a WIKI avoids that 
problem.  Since anyone can contribute, errors can be corrected quickly 
and easily, new information can be added without losing the old, and 
(most important) one person doesn't have to toil through the work of 
pulling it all together.

The only real work the maintainer has to do is make timely backups.  And 
backups are important.  Even if you're running a RAID system, you'll 
want to make backups.  So, it was an easy decision to dump my FAQ.   
Let's just hope that Bob makes backups.

Bob, did I mention that an ocassional backup would be a good idea?
8*)