From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tinyArch.localdomain (unknown [78.110.170.148]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 38D1AE0072B for ; Fri, 18 Nov 2011 08:56:58 -0800 (PST) Received: from [192.168.0.56] (unknown [195.171.99.130]) by tinyArch.localdomain (Postfix) with ESMTPSA id 1B1D124D01 for ; Fri, 18 Nov 2011 16:55:58 +0000 (GMT) Message-ID: <4EC68E4D.2030002@communistcode.co.uk> Date: Fri, 18 Nov 2011 16:56:45 +0000 From: Jack Mitchell User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: yocto@yoctoproject.org References: <94FEB92A-6B46-4F5E-A331-B558F109B796@keylevel.com> <4EC6280B.1010308@communistcode.co.uk> <4D9E0AFD9C2FCC428A8EAADA898F5B2D0E8A96@TAMANS-MB100V.thcg.net> <4EC68022.7040407@mlbassoc.com> <4EC68104.30305@balister.org> <4EC68212.2030702@mlbassoc.com> In-Reply-To: <4EC68212.2030702@mlbassoc.com> Subject: Re: Yocto usability questions 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: Fri, 18 Nov 2011 16:57:05 -0000 Content-Type: multipart/alternative; boundary="------------010206030802090803040604" --------------010206030802090803040604 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 18/11/2011 16:04, Gary Thomas wrote: > On 2011-11-18 09:00, Philip Balister wrote: >> On 11/18/2011 10:56 AM, Gary Thomas wrote: >>> On 2011-11-18 08:02, Ourada, Paul wrote: >>>> Jack said: >>>>> From: yocto-bounces@yoctoproject.org >>>>> [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Jack Mitchell >>>>> Sent: Friday, November 18, 2011 2:40 AM >>>>> To: yocto@yoctoproject.org >>>>> Subject: Re: [yocto] Yocto usability questions >>>>> >>>>> On 17/11/2011 21:38, Chris Tapp wrote: >>>>> On 16 Nov 2011, at 22:07, Jeff Osier-Mixon wrote: >>>>> >>>>> >>>>> Mark& everyone else listening: >>>>> >>>>> >>>>> It is very frustrating when you come to an issue that isn't >>>>> documented, however I have found the IRC an invaluable>resource as >>>>> well as this mailing list. If documentation was to become more >>>>> extensive I feel the categories should be>defined further and split >>>>> into more documents. >>>> >>>> I would just add that for some corporate/enterprise customers (such as >>>> myself), while IRC is great, it isn't as great an option because >>>> corporate IS locks down IRC protocols. To use IRC, I would have to do >>>> so from a non-work computer and likely outside of normal work hours, >>>> of which I already put in way more than my wife would prefer. >>> >>> IMO, IRC is like gossip - only those present learn anything I think >>> information >>> should be shared and archived and IRC doesn't really cover that. >>> That's >>> part of why >>> I pepper these lists with questions and problems and ... >>> >> >> Good irc channels are logged and the logs will be hit with google >> searches. > > But that's hardly the same as having the "conversation(s)" delivered > to my desk, > along with [normally] useful subject lines, that I can peruse at > will. It's > the difference between push [mailing lists] and pull [IRC logs]. > Quite often I will only use IRC if a problem is specific to something I am doing. If it is an actual issue then the problem should be relayed to the bug tracker and fixed. For example, nobody wants to know why my layer called xyz with package zyx won't compile because I used a wrong bitbake flag, however if it turns out to be a compilation bug or a flag that isn't documented then it will be pushed to the bug tracker and hopefully fixed. --------------010206030802090803040604 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 18/11/2011 16:04, Gary Thomas wrote:
On 2011-11-18 09:00, Philip Balister wrote:
On 11/18/2011 10:56 AM, Gary Thomas wrote:
On 2011-11-18 08:02, Ourada, Paul wrote:
Jack said:
From: yocto-bounces@yoctoproject.org
[mailto:yocto-bounces@yoctoproject.org] On Behalf Of Jack Mitchell
Sent: Friday, November 18, 2011 2:40 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto usability questions

On 17/11/2011 21:38, Chris Tapp wrote:
On 16 Nov 2011, at 22:07, Jeff Osier-Mixon wrote:


Mark&   everyone else listening:


It is very frustrating when you come to an issue that isn't
documented, however I have found the IRC an invaluable>resource as
well as this mailing list. If documentation was to become more
extensive I feel the categories should be>defined further and split
into more documents.

I would just add that for some corporate/enterprise customers (such as
myself), while IRC is great, it isn't as great an option because
corporate IS locks down IRC protocols. To use IRC, I would have to do
so from a non-work computer and likely outside of normal work hours,
of which I already put in way more than my wife would prefer.

IMO, IRC is like gossip - only those present learn anything   I think
information
should be shared and archived and IRC doesn't really cover that.  That's
part of why
I pepper these lists with questions and problems and ...


Good irc channels are logged and the logs will be hit with google searches.

But that's hardly the same as having the "conversation(s)" delivered to my desk,
along with [normally] useful subject lines, that I can peruse at will.  It's
the difference between push [mailing lists] and pull [IRC logs].


Quite often I will only use IRC if a problem is specific to something I am doing. If it is an actual issue then the problem should be relayed to the bug tracker and fixed. For example, nobody wants to know why my layer called xyz with package zyx won't compile because I used a wrong bitbake flag, however if it turns out to be a compilation bug or a flag that isn't documented then it will be pushed to the bug tracker and hopefully fixed.
--------------010206030802090803040604--