Received-SPF: softfail
 receiver=logan.com; client-ip=64.102.122.148; envelope-from=echristley@nc.rr.com
Message-ID: <47CEA1C6.6000801@nc.rr.com>
Date: Wed, 05 Mar 2008 08:36:06 -0500
From: Ernest Christley <echristley@nc.rr.com>
Reply-To: echristley@nc.rr.com
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: Rotary motors in aircraft <flyrotary@lancaironline.net>
Subject: Re: [FlyRotary] Re: Rotary Best Practices Web Site
References: <list-2777080@logan.com>
In-Reply-To: <list-2777080@logan.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

bmears9413@aol.com wrote:
> I saw new infor on that Wiki thing that I've never seen before. Maybe we could pool some info on the Lancair site and do the same thing there. There's a lot of good info to be used. I scoured the Internet looking for this information as I was doing my engine setup. Including the best practices and was disappointed about the pages not there. Maybe its not necessary....the info is on the Lan site....you just have to search around for it
>   
The greatest aspect of the Internet is that it is decentralized and 
anyone can publish anything.  The worst thing about the internet is that 
it is decentralized and anyone can publish anything.

Everyone has the greatest of intentions when going through the process 
of building their own engine.  For instance, I have every intention of 
improving the engine rebuild checklist that is on rotarywiki.org.  Make 
it a document with instruction followed by blanks to fill in measured 
values.  Unfortunately, we get so caught up in actually getting the work 
done and wanting to fly the thing some day, that we let the good 
intentions fall by the wayside.  My own website has gone from detailed 
accounts of what I've done and what I'm going to do, to a few new 
pictures occasionally.   But I promise I'll get all my documentation 
pulled together and organized 'Real Soon Now'.

Until that time, I think the rotarywiki.org is the best place to publish 
info that needs to be archived.  Anyone can easily contribute a small 
piece of the puzzle instead of having to collect and organize everything.