From: Tales da Aparecida <tales.aparecida@gmail.com>
To: kernelci@lists.linux.dev
Subject: Invitation: KernelCI Dashboard WG - Bi-weekly meeting
Date: Tue, 16 Sep 2025 20:21:13 -0300 [thread overview]
Message-ID: <CAPo4OxSPZXF+6syLrTQydnpTY-26sEHK03D7Tz=TH88F61+VHw@mail.gmail.com> (raw)
Hello kernelci lists.linux.dev,
TL;DR: You have been invited to a recurring meeting for KernelCI
Dashboard Working Group
Next Meeting: Monday, September 22nd, 14 UTC
Repeats: Every 2 weeks on Mondays at 14 UTC
I’d like to invite anyone interested in discussing the future of the
[KernelCI Dashboard], in regard to new functionality, bug fixes and
overall enhancement of usability, following the success we had in the
first meeting of the [KernelCI Labs Working Group], about how KernelCI
integrates with and manages hardware testing laboratories.
The KernelCI Dashboard is a web platform (Django + React) which aims
at providing an easy way for the community to look at the test
results. Its API also powers [kci-dev] - our cmdline tooling - for
results visualization in the terminal. It is still under active
development and we are open to your feedback and feature requests!
We have some promising ideas in our roadmap, like
- kernel test coverage
- hardware information of the test host
- test/build aggregation (Define common fields to compare historical data)
- personalized notifications
- improved regression reporting
If you’re interested in contributing ideas or simply learning more,
please feel free to join the discussions live every 2 weeks on Monday
at 14:00 UTC, starting 2025-09-22
Meeting notes will be available at:
https://docs.google.com/document/d/1aoNpi69WRhn1nENbdAY1CPXYVkufbVnG_lFoGfA0aM4
[KernelCI Labs Working Group]:
https://lore.kernel.org/kernelci/010101992a9a3b51-fdf26386-9ac2-4716-9e5c-12cf21bd1800-000000@us-west-2.amazonses.com/T/#u
[KernelCI Dashboard]: https://dashboard.kernelci.org/
[kci-dev]: https://github.com/kernelci/kci-dev/
Ways to join meeting:
1. Join from PC, Mac, iPad, or Android
https://zoom-lfx.platform.linuxfoundation.org/meeting/97717382678?password=4cdaf4f9-f132-4d79-94a6-56f8f03d22fb
2. Join via audio
One tap mobile:
US (iOS): +12532158782,,97717382678#,,,,*911276# or
+13462487799,,97717382678#,,,,*911276#
US (Android): +12532158782;97717382678#;911276# or
+13462487799;97717382678#;911276#
Or dial:
US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301
715 8592 or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll
Free) or 855 880 1246 (Toll Free)
Canada: +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 or +1
204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or 855 703 8985
(Toll Free)
Meeting ID: 97717382678
Meeting Passcode: 911276
International numbers: https://zoom.us/u/alwnPIaVT
--
Kind regards,
Tales da Aparecida (He, Him)
Software Engineer @ cki-project.org
next reply other threads:[~2025-09-16 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 23:21 Tales da Aparecida [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-26 18:27 Invitation: KernelCI Dashboard WG - Bi-weekly meeting Tales da Aparecida
2025-11-17 12:43 Tales da Aparecida
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='CAPo4OxSPZXF+6syLrTQydnpTY-26sEHK03D7Tz=TH88F61+VHw@mail.gmail.com' \
--to=tales.aparecida@gmail.com \
--cc=kernelci@lists.linux.dev \
/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).