From: Benjamin Copeland <benjamin.copeland@linaro.org>
To: Laura Nao <laura.nao@collabora.com>
Cc: Donald Zickus <dzickus@redhat.com>,
Nikolai Kondrashov <nkondras@redhat.com>,
kernelci@lists.linux.dev,
Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: Test catalog
Date: Tue, 17 Sep 2024 12:18:22 +0100 [thread overview]
Message-ID: <CAL0q8a4cm-W9TFdmnxPd6exXeb-x71vPdKYSQJDM2LsiAp69Xg@mail.gmail.com> (raw)
In-Reply-To: <6edcd2a2-4e09-4f41-a4f5-5595fefecf75@collabora.com>
HI all,
This sounds like a great subject area that I know some folks including
me from Linaro would like to be in.
There are a few of us folks here this week, so we'd be interested to
sit in this chat and talk about some of the challenges and areas of
engagement from our side.
Regards
Ben
On Tue, 17 Sept 2024 at 11:14, Laura Nao <laura.nao@collabora.com> wrote:
>
> Hi Don,
>
> Sure, count me in! Thursday morning works for me. Looking forward to the
> discussion. I agree it's important to centralize info on available test
> suites and how to pick the right subset for each platform, focusing on
> maintainers' needs.
>
> Best,
>
> Laura
>
> On 9/16/24 17:47, Donald Zickus wrote:
> > Hi Laura,
> >
> > I was talking with Gustavo and Nikolai about the test catalog idea that
> > has been floating around. I think having a way for maintainers to
> > accurately describe their test and hardware needs to define what does
> > 'testing done' look like from a maintainers perspective, allows the
> > community to come together and work on filling the gaps. I don't
> > believe a single CI system nor lab has enough resources to provide
> > everything a maintainer wants. But as a community we can.
> >
> > I would like to sit down with folks from Collabora, Red Hat and others
> > at LPC to discuss this more. I see this as a 2025 roadmap. Gustavo
> > thinks that Thursday morning somewhere might be an open time where folks
> > don't have talks. I was hoping to chat for an hour. This could help us
> > drive conversations with community members on how they could contribute
> > (mostly focused on hardware vendors).
> >
> > All are welcome to chat. Let me know if there is interest and I can
> > find a room and timeslot.
> >
> > Cheers,
> > Don
>
>
next prev parent reply other threads:[~2024-09-17 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK18DXZ9610pCm42m-D-gAKTrGQuh5TmEwaPyA6QHiB_80pK4Q@mail.gmail.com>
2024-09-17 10:15 ` Test catalog Laura Nao
2024-09-17 11:18 ` Benjamin Copeland [this message]
2024-09-18 13:20 ` Mark Brown
[not found] ` <CAK18DXYVgOhjxQA5qTLOJwks0AFWCc2UCcCQjJurYyi08rOH2g@mail.gmail.com>
2024-09-19 6:41 ` Donald Zickus
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=CAL0q8a4cm-W9TFdmnxPd6exXeb-x71vPdKYSQJDM2LsiAp69Xg@mail.gmail.com \
--to=benjamin.copeland@linaro.org \
--cc=dzickus@redhat.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=laura.nao@collabora.com \
--cc=nkondras@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).