workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	workflows@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: Tooling and workflows meeting at OSS EU Lyon
Date: Fri, 25 Oct 2019 09:36:14 -0400	[thread overview]
Message-ID: <20191025133614.spkxym5k6fp4ofw5@chatter.i7.local> (raw)
In-Reply-To: <239435160.6625525.1572006247406.JavaMail.zimbra@redhat.com>

On Fri, Oct 25, 2019 at 08:24:07AM -0400, Veronika Kabatova wrote:
>> > > 3. CI and bot integration
>> > >     - identifying the data that maintainers/developers want to see
>> > >     - communicating structured data over email
>> > >     - providing consumable feeds of CI/bot jobs (as public-inbox
>> > >       repositories?)
>> > >     - avoiding bug duplication
>> > >     - recognizing when a bug is fixed and following up on issues that
>> > >       nobody has taken on
>> > >
>
>Hi,
>
>if in the end any CI discussion fits into the agenda (or there will be
>a separate discussion), please consider inviting CI people too. They can
>offer information about what's feasible to do from CI point, and note
>any feedback to know what we should adjust for CI to be more useful for
>developers/maintainers.
>
>I can attend for CKI side and there should be multiple people from
>Kernel CI and LKFT attending the conference too.

I'm leaning towards having CI folks organize a separate session to go 
over integration points. I will be happy to attend that one as well, but 
if we have too many topics and too many attendees during the meeting we 
are trying to organize, it is unlikely to be very productive.

-K

  reply	other threads:[~2019-10-25 13:36 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 [this message]
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
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=20191025133614.spkxym5k6fp4ofw5@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=dvyukov@google.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=vkabatov@redhat.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