workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: workflows@vger.kernel.org
Subject: Re: Tooling and workflows meeting at OSS EU Lyon
Date: Mon, 28 Oct 2019 06:03:01 -0400	[thread overview]
Message-ID: <CAMwyc-SJ2BmgWiicGNcCiL7Gq7VPB-+VjUF_KSSHA-jD8KMnZA@mail.gmail.com> (raw)
In-Reply-To: <CAMwyc-TRnJdiNcKiwK1cAUysGqQQLucPDHb_xRWf+-iCm2medw@mail.gmail.com>

On Mon, 28 Oct 2019 at 05:25, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> OK, slight complication. It's a lot more people than expected:
>
> > - Steven Rostedt
> > - Greg Kroah-Hartman
> > - Dmitry Vyukov
> > - Konstantin Ryabitsev
> > - Christian Brauner
> > - Laurent Pinchart
> > - Jon Corbet
> > - Daniel Vetter
> > - Nicolas Belouin
> > - Shuah Khan
>
> - Nicolas Belouin
> + Daniel Díaz
> + Rafael Wysocki
> + Han-Wen Nienhuys
> + Kevin Hilman

Okay we can make this work -- there are 3 round tables at the right
forward corner of the sponsor showcase room (to the very right of the
entrance doorways). It's quiet and next to the noise-cancelling walls,
so we should be able to meet and discuss there.

So:

Tooling and Workflows meeting, 14:00-15:00 in the Sponsor Showcase room.
Rough agenda:

14:00: introductions
14:05: Enhancing the email workflow:
    - cryptographic attestation of patches
    - adding (and requiring) base tree information in submitted patches
    - git-to-ML bridging
    - attestable bot, forge and developer activity feeds
14:30 Maintainer and developer tooling
    - can forges integrate with email workflows?
    - defining a minimal set of features useful for the maintainer
tool (kit/kthul)

The meeting will be unconference-style, so time overruns and agenda
usurpation is 100% expected.

I would love to brainstorm more about CI/bot integration, but I think
it makes sense to make it a separate discussion, perhaps with a
smaller subset of people. I believe if we manage to establish a
workflow around attestable public-inbox feeds, that will pave a
possible way for bot cross-integration.

I will be semi-permanently in the developer lounge area, so please
feel free to come and chat about any of these or other topics.

-K

  reply	other threads:[~2019-10-28 10:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 20:58 Konstantin Ryabitsev
     [not found] ` <<20191024205803.qdn6p32iyj5rqvc6@chatter.i7.local>
2019-10-25  6:58   ` Nicolas Belouin
2019-10-25 11:16 ` Laurent Pinchart
2019-10-25 11:20   ` Dmitry Vyukov
2019-10-25 12:24     ` Veronika Kabatova
2019-10-25 13:36       ` Konstantin Ryabitsev
2019-10-25 14:15         ` Veronika Kabatova
2019-10-26 12:00 ` Kevin Hilman
2019-10-28  9:25 ` Konstantin Ryabitsev
2019-10-28 10:03   ` Konstantin Ryabitsev [this message]
2019-10-28 11:42 ` Frank Rowand

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=CAMwyc-SJ2BmgWiicGNcCiL7Gq7VPB-+VjUF_KSSHA-jD8KMnZA@mail.gmail.com \
    --to=konstantin@linuxfoundation.org \
    --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