public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Leif Lindholm <leif.lindholm@linaro.org>, Eric Jin <eric.jin@intel.com>
Cc: edk2-devel@lists.01.org, Jiaxin Wu <jiaxin.wu@intel.com>
Subject: Re: [PATCH] uefi-sct/SctPkg:Add conformance test cases for deprecated EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS attribute.
Date: Wed, 17 Oct 2018 14:04:01 +0200	[thread overview]
Message-ID: <41ea021e-c68b-a875-9c70-670699c98d28@redhat.com> (raw)
In-Reply-To: <20181016022826.kj63jctabgoxcf2h@bivouac.eciton.net>

Hi Leif,

On 10/16/18 04:28, Leif Lindholm wrote:

> Laszlo: a few years ago, you also posted a _really_ useful email about
> the process of being a maintainer, and helpful workflows (like "sort
> emails to review immediately on reception, even if you don't have time
> to review now"). I have since failed to find it in my history (or via
> google). Since you're very organised - do you have it lying around,
> and if so would you be able to re-post it?

I'm sure I still have the email, if I sent it; however, I can't find it
now, because I don't personally remember the *specific* email you refer
to, and so I can't come up with good search terms, for the program that
indexes my mailbox ("recoll").

Anyway, what I generally do is:

- I maintain a set of tagged emails that present work items. This set
(of emails) exists in addition to bugzillas that are assigned to me.

- I process emails in batches. I sync my mailbox, and then turn off
synching, until I have covered everything possible, at that point, that
relate to my mailbox.

- In every new batch in my INBOX, I go over the emails as quickly as
possible, trying to triage emails as I go. If I can take care of an
email immediately, I do. If it needs more work (especially focused
work), then I tag the email, and archive it at once. If the tagged email
is private (not on any list), then I'll let it sit tagged in my personal
archive folder. If the email is also on some list, then I might choose
to tag the email in that folder instead, and archive the personal copy
without tagging it.

- I go over all the new emails in my list folders as well (i.e. emails
that I'm not personally CC'd on). Dependent on list, I dedicate
different amounts of attention.

- Once I'm done triaging / tagging the new batch (and therefore I have
no unread messages in my entire mailbox), I search my mailbox for all
tagged messages. I usually list those hits in chronological order, but
not always (e.g., sometimes I group them by containing folder). I work
my way through these items slowly. Importantly, I shut out interruptions
while I do this -- no more email synching, no phone, no IRC. And the
FIFO processing order of the tagged messages mostly ensures good
responsiveness from my side, despite this process being quite OK at
throughput as well.

(Your present email fell in the "take care of it at once" category :) )

Thanks,
Laszlo


  reply	other threads:[~2018-10-17 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13 15:19 [PATCH] uefi-sct/SctPkg:Add conformance test cases for deprecated EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS attribute Eric Jin
2018-10-15  2:46 ` Supreeth Venkatesh
2018-10-15 13:09   ` Supreeth Venkatesh
2018-10-16  2:28 ` Leif Lindholm
2018-10-17 12:04   ` Laszlo Ersek [this message]
2018-10-26 11:50     ` Leif Lindholm

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=41ea021e-c68b-a875-9c70-670699c98d28@redhat.com \
    --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