From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: workflows@vger.kernel.org,
Till Kamppeter <till.kamppeter@gmail.com>,
Aveek Basu <basu.aveek@gmail.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?
Date: Fri, 17 Jan 2020 21:25:24 +0100 [thread overview]
Message-ID: <CAKXUXMwa-4mc4zNfO=mTHCyiwhNYzQFA=HocaTZF0jeCZrnZ3g@mail.gmail.com> (raw)
In-Reply-To: <CAEG3pNCgLTYrwoeA4_F9Ru-81O1dWWJ9SnnKKcWfr4nG=y2zRw@mail.gmail.com>
On Wed, Jan 15, 2020 at 11:07 PM Michael Turquette
<mturquette@baylibre.com> 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.
>
Michael, thanks for this first proposal. Would you also be interested
in mentoring this project idea or should we ask and look for potential
mentors for this project?
Of course, more proposals are welcome :)
Lukas
next prev parent reply other threads:[~2020-01-17 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 18:07 Explore ideas on workflows improvements with Google Summer of Code mentoring program? Lukas Bulwahn
2020-01-15 22:07 ` Michael Turquette
2020-01-15 23:03 ` Bjorn Helgaas
2020-01-16 19:39 ` Michael Turquette
2020-01-17 1:34 ` Stephen Boyd
2020-01-16 0:59 ` Daniel Axtens
2020-01-16 19:35 ` Michael Turquette
2020-01-17 2:19 ` Daniel Axtens
2020-01-17 20:25 ` Lukas Bulwahn [this message]
2020-01-17 20:38 ` Michael Turquette
2020-01-18 7:18 ` Lukas Bulwahn
2020-01-21 22:14 ` Michael Turquette
2020-01-22 6:18 ` Lukas Bulwahn
2020-01-22 22:22 ` Michael Turquette
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-all 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='CAKXUXMwa-4mc4zNfO=mTHCyiwhNYzQFA=HocaTZF0jeCZrnZ3g@mail.gmail.com' \
--to=lukas.bulwahn@gmail.com \
--cc=basu.aveek@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=till.kamppeter@gmail.com \
--cc=workflows@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).