From: "Sean" <sean.brogan@microsoft.com>
To: Laszlo Ersek <lersek@redhat.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] TianoCore Community Meeting Minutes - Feb 6
Date: Fri, 14 Feb 2020 15:24:10 -0800 [thread overview]
Message-ID: <28117.1581722650484878720@groups.io> (raw)
In-Reply-To: <96a33178-ed1b-426f-b3e4-635647121ea4@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 784 bytes --]
next prev parent reply other threads:[~2020-02-14 23:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 3:47 TianoCore Community Meeting Minutes - Feb 6 Soumya Guptha
2020-02-14 18:25 ` [edk2-devel] " Sean
2020-02-14 18:50 ` Rebecca Cran
2020-02-14 22:14 ` Laszlo Ersek
2020-02-14 22:14 ` Laszlo Ersek
2020-02-14 23:24 ` Sean [this message]
2020-02-17 8:12 ` Laszlo Ersek
2020-02-18 17:47 ` Soumya Guptha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28117.1581722650484878720@groups.io \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox