From: Veronika Kabatova <vkabatov@redhat.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: workflows@vger.kernel.org
Subject: Re: Tooling and workflows meeting at OSS EU Lyon
Date: Fri, 25 Oct 2019 10:15:07 -0400 (EDT) [thread overview]
Message-ID: <939398650.6672462.1572012907257.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191025133614.spkxym5k6fp4ofw5@chatter.i7.local>
----- Original Message -----
> 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>
> Sent: Friday, October 25, 2019 3:36:14 PM
> Subject: Re: Tooling and workflows meeting at OSS EU Lyon
>
> 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.
>
I'm not sure if there are any meetings of this nature planned but I'll
notify you if I learn anything new, thanks for the interest! There is also
ATS [0] on Thursday which will include presentations about CI systems and
how they are/plan to be integrated with upstream development, in case you
(or anyone else on this list) are attending that as well.
Please keep the list posted about the outcomes!
[0] https://events19.linuxfoundation.org/events/ats-2019/
Veronika
> -K
>
next prev parent reply other threads:[~2019-10-25 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 20:58 Tooling and workflows meeting at OSS EU Lyon 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 [this message]
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
2026-02-06 10:21 ` odd b4 "Mail:" trailer added for USB patch Greg KH
2026-02-06 14:32 ` Konstantin Ryabitsev
2026-03-06 0:23 ` Konstantin Ryabitsev
2026-03-06 0:25 ` B4 Bugbot
2026-03-06 19:34 ` B4 Bugbot
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=939398650.6672462.1572012907257.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.