Workflows Archive on
 help / color / Atom feed
From: Michael Turquette <>
To: Lukas Bulwahn <>
	Till Kamppeter <>,
	Aveek Basu <>,
	Stephen Boyd <>
Subject: Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?
Date: Wed, 15 Jan 2020 14:07:24 -0800
Message-ID: <> (raw)
In-Reply-To: <>

Hi Lukas,

On Tue, Jan 14, 2020 at 11:06 AM Lukas Bulwahn <> wrote:
> Dear all,
> Till Kamppeter and Aveek Basu organize the Google Summer of Code
> student mentoring program in the name of the Linux Foundation. They
> have set up a page for project ideas for the Linux Foundation's
> participation in the linuxfoundation wiki:
> I believe many ideas discussed here on this list, e.g., extensions to
> patchwork, public-inbox, further bots, scripts, etc., are well suited
> to be prototyped or implemented by students in the GSoC program.
> If you agree and have some good ideas, please add your ideas to this
> currently still empty draft page:

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.

Best regards,

> Ideas should be roughly described in five to six sentences, possibly
> with a list of expectations on required knowledge a student should
> show for its application. Within the application period later,
> interested students have to write a much more extensive project
> proposal as part of their application, by exchanging with the group to
> refine the rough idea to a proper task and student project.
> Please also take into account that the deadline for the application as
> mentoring organization is Feb 5 and after that Google will evaluate
> the applications. So have the ideas (at least most of them, ideas can
> be posted up to the student application deadline) in by then to raise
> chances to get accepted and get slots for students assigned.
> If you have any questions concerning GSoC organisation, you can reach
> out to Till, Aveek or me.
> Best regards,
> Lukas

Michael Turquette
CEO - Los Angeles, CA
BayLibre - At the Heart of Embedded Linux
Schedule a meeting:

  reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 18:07 Lukas Bulwahn
2020-01-15 22:07 ` Michael Turquette [this message]
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
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 publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Workflows Archive on

Archives are clonable:
	git clone --mirror workflows/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 workflows workflows/ \
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone