From owner-freebsd-questions@FreeBSD.ORG Sat Feb 12 04:16:59 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07D9C16A4CE for ; Sat, 12 Feb 2005 04:16:59 +0000 (GMT) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 927E643D41 for ; Sat, 12 Feb 2005 04:16:58 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1CzoiG-000Glc-0p for freebsd-questions@freebsd.org; Fri, 11 Feb 2005 21:16:56 -0700 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <583702950.20050212044425@wanadoo.fr> References: <200502112325.j1BNPw201164@clunix.cl.msu.edu> <1108168477.45718.19.camel@p4><1108178253.46376.11.camel@p4> <583702950.20050212044425@wanadoo.fr> Message-Id: From: Chad Leigh -- Shire.Net LLC Date: Fri, 11 Feb 2005 21:16:55 -0700 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.619) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on hobbiton.shire.net X-Spam-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50 autolearn=disabled version=3.0.0 X-Spam-Level: X-SA-Exim-Version: 4.1+cvs (built Mon, 23 Aug 2004 08:44:05 -0700) X-SA-Exim-Scanned: Yes (on hobbiton.shire.net) Subject: Re: Please don't change Beastie to another crap logo such as X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Feb 2005 04:16:59 -0000 On Feb 11, 2005, at 8:44 PM, Anthony Atkielski wrote: > Robert Marella writes: > >> As far as the codebase question, he was not the one to bring it up. If >> I can read between his lines, I understand that when you go in front >> of the suits you can't tell them RTFM. You have to explain why FreeBSD >> is head and shoulders above the leader of the pack. > > Yes. Things to remember if you must present FreeBSD to "suits" (not an > exhaustive list): > > - You must provide sound arguments and/or hard data to support your > suggestions. "FreeBSD is just great!" will not do. > > - You must provide costs. "It's free" won't do. Nothing is ever free. > If you don't have costs, either you aren't being serious, or you > haven't done your homework. > > - You cannot killfile anyone who asks questions that you don't like. > > - Calling the suits stupid because they refuse to unconditionally agree > with you guarantees failure. Do not throw tantrums. > > - You must be confident, but not arrogant. Stick to your guns when you > are discussing something that you know to be objectively true, but do > not argue about opinions. > > - You must know exactly what point you wish to make to the suits, and > you must stick to it. A long discussion of how much you love Beastie > will not impress. > > - You need to leave documentation with them, including a copy of your > presentation. > > - You need to explain how they will obtain support when something goes > wrong. "Nothing ever goes wrong!" will not work. > > - You need to explain how FreeBSD will fit in with their IT strategy. > It's up to you to research this; it is not up to them to figure it out. > > - Don't knock the competition unless you can objectively back up what > you say (even then, be judicious). > > - Be prepared to address legal issues, such as licensing, patents, and > copyrights. > > - If you say "If you don't like it this way, go somewhere else," they > will. > This is all very well and good, but is irrelevant to the earlier discussion. You are not a Suit we are trying to impress or get to use FreeBSD. You are on a general technical support mailing list and "behavior" here is different than would be in a formal presentation or even official support mechanism. Chad