Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Quoting Bjorn Helgaas (2020-01-15 15:03:47)
> On Wed, Jan 15, 2020 at 4:07 PM Michael Turquette
> <mturquette@xxxxxxxxxxxx> wrote:
> > I added the first entry, "Bidirectionally sync Patchwork patch status
> > with Gmail labels". Stephen Boyd and I use a local solution to
> > coordinate patches in the Linux Clk tree. Our solution requires
> > Patchwork + the Notmuch mail indexer + Gmail/G Suite to work. My
> > proposal is to remove the Notmuch requirements and teach Patchwork to
> > talk directly to Gmail (and vice versa), perhaps via a solution in the
> > cloud, running on a server somewhere, and not dependent on the uptime
> > of my laptop.
> >
> > From my discussions with kernel devs, I believe there is a reasonably
> > sized Venn diagram of people that use both Patchwork for patch
> > tracking as well as Gmail/G Suite for email. Having those two talk
> > might mean that I never have to use the Patchwork web interface again,
> > a big win IMO, and I can just use email.
> That's a really cool idea.  What do you do about the Gmail/plain text
> problem?  I know Gmail *can* sent plain-text email, but you don't have
> much control over the formatting, and I really don't like reviewing
> code in a Gmail draft.  I hate to admit it, but I'm always bouncing
> back and forth between Gmail and mutt.

I don't use gmail at all for composing or sending emails. I basically
use it as a glorified label and email storage database. Downside is I
can't work on my phone, which is probably a good thing when I have to
write something long but a bad thing when I just want to apply the patch
and integrate it into my tree.

I've dreamed about moving away from gmail entirely and just syncing down
the mbox files from for linux-clk (or maybe that thing
that catches all the lists that have my address in the to or
cc) and then writing a UI around mbox files that I can use to reply and
tag/update patchwork state. Basically treat lore as my email storage
database. This fails when people want to email me privately, so maybe
I'll have to keep injecting the patchwork files into my notmuch database
for now.

[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux