From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from r-finger.com (r-finger.com [178.79.160.5]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 8989FE0070C for ; Tue, 26 Jun 2012 10:18:47 -0700 (PDT) Received: from [192.168.0.2] (host86-170-68-253.range86-170.btcentralplus.com [86.170.68.253]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by r-finger.com (Postfix) with ESMTPSA id D7A3A9C07 for ; Tue, 26 Jun 2012 18:18:46 +0100 (BST) Message-ID: <4FE9EEF6.7050001@r-finger.com> Date: Tue, 26 Jun 2012 18:18:46 +0100 From: Tomas Frydrych User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120329 Icedove/10.0.3 MIME-Version: 1.0 To: yocto@yoctoproject.org References: <10398861.esnekvBoZU@helios> <4FE9D965.4070906@linux.intel.com> <3153041.1FMPtSpq0x@helios> <4FE9E58C.9020408@r-finger.com> In-Reply-To: Subject: Re: the current yocto FAQ is pretty much valueless X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 17:18:47 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 26/06/12 17:53, Robert P. J. Day wrote: > and if you want major industry players to take yocto seriously, the > last thing you want to do is answer their heartfelt pleas for > assistance with, "i'm sorry, that's technically not a yocto question, > you should try another mailing list." That's never been case on this list as far as I recall, folk here are pretty responsive to questions being asked. At the same time, OE/Poky/Yocto is a fairly complex framework and nobody should expect that the necessary expertize to build a commercial grade products with it can be acquired by simply reading a FAQ, no matter how well written, or by just endlessly asking questions on a mailing list. As a commercial player you are either prepared to make the in house investment that is necessary to acquire that expertize (reading the documentation and studying the source code, etc.), or you you can buy the expertize on commercial basis from someone who has it. Tomas