From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: "kernelci@groups.io" <kernelci@groups.io>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
automated-testing@lists.yoctoproject.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernelci-members@groups.io, Shuah Khan <shuahkh@osg.samsung.com>,
Jesse Barnes <jsbarnes@google.com>,
Gustavo Padovan <gustavo.padovan@collabora.com>,
Collabora Kernel ML <kernel@collabora.com>
Subject: First KernelCI sprint this week
Date: Mon, 31 May 2021 08:33:34 +0100 [thread overview]
Message-ID: <f94a4f66-d16a-95b4-95df-9e9cff65620d@collabora.com> (raw)
A KernelCI sprint or "hackfest" is taking place this week,
initiated as a joint effort by the Google Chrome OS team and
Collabora. It is a public event and anyone is encouraged to take
part. This is the first edition, we're hoping to repeat this
exercise in the future with a growing involvement from the kernel
community. The goal is to provide an opportunity for developers
to focus on improving kernel test coverage and automation.
To find out about KernelCI, please see https://kernelci.org.
There is a workboard on GitHub to track progress and see which
topics are being worked on:
https://github.com/orgs/kernelci/projects/3
We are hosting open hours this week on a Big Blue Button
instance (same as Linux Plumbers Conference 2020):
Monday 31st: May 13:00-15:00 UTC
Tuesday 1st - Friday 4th June: 08:00-10:00 UTC, 18:00-20:00 UTC
The actual meeting link is not shared publicly here to avoid
abuse but please reply to this email or ask padovan or gtucker on
IRC (Libera) and we'll send it to you privately unless we've
reached maximum capacity.
Of course, please feel free to use this email thread to share any
ideas or comments you may have as well as the #kernelci channel
on IRC (Libera, transitioning from Freenode). We're otherwise
expecting some kselftest improvements and kernel bug fixes to be
sent out this week and as follow-ups. Stay tuned!
Best wishes,
Guillaume
reply other threads:[~2021-05-31 7:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f94a4f66-d16a-95b4-95df-9e9cff65620d@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.padovan@collabora.com \
--cc=jsbarnes@google.com \
--cc=kernel@collabora.com \
--cc=kernelci-members@groups.io \
--cc=kernelci@groups.io \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.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
all inboxes | Powered by JetHome®