X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from sj-iport-4.cisco.com ([171.68.10.86] verified) by logan.com (CommuniGate Pro SMTP 4.3.4) with ESMTP id 1002818 for flyrotary@lancaironline.net; Wed, 15 Jun 2005 10:22:31 -0400 Received-SPF: softfail receiver=logan.com; client-ip=171.68.10.86; envelope-from=echristley@nc.rr.com Received: from rtp-core-2.cisco.com (64.102.124.13) by sj-iport-4.cisco.com with ESMTP; 15 Jun 2005 07:21:46 -0700 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j5FELb52012601 for ; Wed, 15 Jun 2005 10:21:43 -0400 (EDT) Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 15 Jun 2005 10:20:57 -0400 Received: from [64.102.45.251] ([64.102.45.251]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 15 Jun 2005 10:20:57 -0400 Message-ID: <42B03949.5070708@nc.rr.com> Date: Wed, 15 Jun 2005 10:20:57 -0400 From: Ernest Christley User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rotary motors in aircraft Subject: Re: [FlyRotary] Re: fuel pump mounting References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Jun 2005 14:20:57.0460 (UTC) FILETIME=[728A1B40:01C571B5] jesse farr wrote: > I thought that was sort of what this list is. Just sort of, of course. > jofarr, soddy tn > >> It's a collaborative knowledge storage mechanism. Let's get away >> from a 'best practice' list and call it what it is. A 'known >> solutions' list. > > Your thinking is quite correct, Jesse. In fact, most of the current data that is in our wiki comes from postings made here. The only problem with this list is with off topic discussions, protracted discussions before reaching a consensus, searching and indexing, ie. all the 'volume'. The list archives are a step in the right direction, but an archive search for 'fuel system design' will leave you with many a nights worth of bedtime reading. On the other hand, the wiki is a "Just the facts, ma'am" medium where we cut the fluff, friendly banter, and general discussion, and then INDEX it so that it is easy to find. This could be done with a FAQ or someone's 'Best Practices' website. The two problems with that solution both lie with the single maintainer nature. First, what happens when the maintainer gets tired of maintaining? This is a job that will span years if not decades, after all. And second, what happens when the maintainer doesn't agree with a piece of information? Will it get included in the FAQ/website, or will the maintainer find a way to push it away? The Wiki maintainance is very low as the maintainer isn't required to be an editor, and the second problem is wiped away by the wiki's decentralized nature. But we still have all the information we find valuable condensed into one place and instead of RTF (read the faq), we'll tell newbies to RTW (read the wiki). There will be disagreements to approach and solutions. No problem. Proponents of both sides simply post their views. Done. No fuss. No muss. The neophyte is left to make his own decision from the discussion, or, even better, we've given them a place to start their investigations from so they can understand the give and takes of the issues involved. -- ,|"|"|, | ----===<{{(oQo)}}>===---- Dyke Delta | o| d |o www.ernest.isa-geek.org |