workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Axtens <dja@axtens.net>
To: Michael Turquette <mturquette@baylibre.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	workflows@vger.kernel.org,
	Till Kamppeter <till.kamppeter@gmail.com>,
	Aveek Basu <basu.aveek@gmail.com>,
	Stephen Boyd <sboyd@kernel.org>,
	stewart@flamingspork.com
Subject: Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?
Date: Fri, 17 Jan 2020 13:19:03 +1100	[thread overview]
Message-ID: <87wo9qkep4.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <CAEG3pNAg2yBk5o3qUv6gsbB6hx=nJ4ygohNe4R0CjRvaAha04w@mail.gmail.com>

Michael Turquette <mturquette@baylibre.com> writes:

> On Wed, Jan 15, 2020 at 4:59 PM Daniel Axtens <dja@axtens.net> wrote:
>>
>> Michael Turquette <mturquette@baylibre.com> writes:
>>
>> > Hi Lukas,
>> >
>> > On Tue, Jan 14, 2020 at 11:06 AM Lukas Bulwahn <lukas.bulwahn@gmail.com> 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:
>> >>
>> >> https://wiki.linuxfoundation.org/gsoc/google-summer-code-2020
>> >>
>> >> 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:
>> >>
>> >> https://wiki.linuxfoundation.org/gsoc/2020-gsoc-kernel-workflows
>> >
>> > 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.
>>
>>
>> <pw maintainer hat>
>> Let me know if there's anything you need in the REST API for this. We're
>> going to cut 2.2 Real Soon Now, which will be your last chance until 3.0
>> which, given our general velocity, will not be out until late 2020.
>
> Thanks for the support Daniel. The current solution that I use is
> based on the pwclient tool, and I have no idea if that uses the REST
> api under the hood or not. If this project gets picked up by students
> in GSoC then hopefully they can provide feedback to you on any API
> enhancements.

Ironically the pwclient tool is one of the last users of the old XMLRPC
API, but we're hoping to convert it eventually.

>
> I do have a working setup on gitlab that I can share, but again this
> assumes Notmuch is part of the toolchain.
>

No stress at the moment, I'll get in touch if I need more info.

Stewart Smith also had a similar setup:
https://www.flamingspork.com/blog/2018/08/22/pwnm-sync-synchronizing-patchwork-and-notmuch/

Regards,
Daniel

> Best,
> Mike
>
>>
>> Regards,
>> Daniel
>>
>>
>> > 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,
>> > Mike
>> >
>> >>
>> >> 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
>> > http://baylibre.com/
>> > Schedule a meeting: https://calendly.com/mturquette
>
>
>
> -- 
> Michael Turquette
> CEO - Los Angeles, CA
> BayLibre - At the Heart of Embedded Linux
> http://baylibre.com/
> Schedule a meeting: https://calendly.com/mturquette

  reply	other threads:[~2020-01-17  2:19 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 [this message]
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 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=87wo9qkep4.fsf@dja-thinkpad.axtens.net \
    --to=dja@axtens.net \
    --cc=basu.aveek@gmail.com \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=stewart@flamingspork.com \
    --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).