From: Donald Zickus <dzickus@redhat.com>
To: laura.nao@collabora.com, Nikolai Kondrashov <nkondras@redhat.com>
Cc: kernelci@lists.linux.dev,
Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: Test catalog
Date: Thu, 19 Sep 2024 02:41:50 -0400 [thread overview]
Message-ID: <CAK18DXZH4TQCfeBJap4jh9mC6CZF=4-60D0xdXQZ5fQ8fhhpqQ@mail.gmail.com> (raw)
In-Reply-To: <CAK18DXYVgOhjxQA5qTLOJwks0AFWCc2UCcCQjJurYyi08rOH2g@mail.gmail.com>
Hi,
Resending as last night mimecast rejected the email to the mailing list.
Cheers,
Don
On Wed, Sep 18, 2024 at 6:19 PM Donald Zickus <dzickus@redhat.com> wrote:
>
> Hi Folks,
>
>
>
> On Mon, Sep 16, 2024 at 11:47 AM Donald Zickus <dzickus@redhat.com> 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.
>
>
> Thanks for the replies and interest. Sorry for the late reply, I wasn't sure if I had to reserve something.
>
> Let's meet at 10am by the BoF rooms where they served lunch. Then we can walk over and grab an empty room. I think there were 4 available.
> I don't plan on more than an hour.
>
> Cheers,
> Don
>
>>
>> Cheers,
>> Don
prev parent reply other threads:[~2024-09-19 6:42 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
2024-09-18 13:20 ` Mark Brown
[not found] ` <CAK18DXYVgOhjxQA5qTLOJwks0AFWCc2UCcCQjJurYyi08rOH2g@mail.gmail.com>
2024-09-19 6:41 ` Donald Zickus [this message]
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='CAK18DXZH4TQCfeBJap4jh9mC6CZF=4-60D0xdXQZ5fQ8fhhpqQ@mail.gmail.com' \
--to=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).