From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.120])
 by mx.groups.io with SMTP id smtpd.web11.5955.1581927130707927944
 for <devel@edk2.groups.io>;
 Mon, 17 Feb 2020 00:12:10 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=I0JPsFiI;
 spf=pass (domain: redhat.com, ip: 205.139.110.120, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1581927129;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=2Fqi9mVk4nnMRNRbcwHkUgQpsBT27PGkWFWEdoWg3Rk=;
	b=I0JPsFiIC7o7uNa5qUFEufJkChWlwrymUqC8svNlBnSWqQoX+AwY70sVggrG3JJzcXG6lo
	gQMspQr1n09Vs7N7aVUwFd+zCoV1WRa1DCfa1EDzP9KgE99PqIn1WAcsq1b7AlbPVRJADe
	fEcgEMF/gfJhaklUik23vSG/ZTfZigE=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-102-jsZ3UDStOHC7iwR4dSIxSQ-1; Mon, 17 Feb 2020 03:12:03 -0500
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8C22A800D5B;
	Mon, 17 Feb 2020 08:12:02 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-195.ams2.redhat.com [10.36.116.195])
	by smtp.corp.redhat.com (Postfix) with ESMTP id D71FB60BEC;
	Mon, 17 Feb 2020 08:12:01 +0000 (UTC)
Subject: Re: [edk2-devel] TianoCore Community Meeting Minutes - Feb 6
To: devel@edk2.groups.io, sean.brogan@microsoft.com
References: <96a33178-ed1b-426f-b3e4-635647121ea4@redhat.com>
 <28117.1581722650484878720@groups.io>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <5558ee47-d5df-0367-778e-cf55fad5b519@redhat.com>
Date: Mon, 17 Feb 2020 09:12:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <28117.1581722650484878720@groups.io>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
X-MC-Unique: jsZ3UDStOHC7iwR4dSIxSQ-1
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 02/15/20 00:24, Sean via Groups.Io wrote:
> On Fri, Feb 14, 2020 at 02:14 PM, Laszlo Ersek wrote:
> 
>> 
>> I think Bugzilla tickets are the best place to capture the focused 
>> analysis of a bug. I write a *lot* of text in Red Hat bugzillas
>> (most of them are public, luckily!) -- I want to document my own
>> "adventure" with the issue, even if most paths prove dead-ends in
>> the end. How does that conflict with "forward progress"?
> 
> By this i mean during the meetings it is impossible to capture the
> conversation, be involved in the conversation, update the bugzilla,
> and still move fast enough.  In general I do believe putting detailed
> information in the bugzilla is great and not in conflict with forward
> progress but in the context of the meeting it is not practical.

Ah, agreed.

Thanks
Laszlo