workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: "kernelci@groups.io" <kernelci@groups.io>
Cc: kernelci-members <kernelci-members@groups.io>,
	automated-testing@lists.yoctoproject.org,
	Collabora Kernel ML <kernel@collabora.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jsbarnes@google.com>,
	Summer Wang <wangsummer@google.com>,
	linux-kselftest@vger.kernel.org, workflows@vger.kernel.org,
	kunit-dev@googlegroups.com,
	clang-built-linux <clang-built-linux@googlegroups.com>
Subject: KernelCI Hackfest #2 - Sept 6-10 2021
Date: Mon, 2 Aug 2021 10:00:15 +0100	[thread overview]
Message-ID: <74f7b4cf-926f-d8bd-19c2-375cfe7a12b2@collabora.com> (raw)

The first KernelCI hackfest[1] early June was successful in getting
a number of kernel developers to work alongside the core KernelCI
team.  Test coverage was increased in particular with kselftest,
LTP, KUnit and a new test suite for libcamera.  We're now improving
documentation and tooling to make it easier for anyone to get
started.  Find out more about KernelCI on https://kernelci.org.

The second hackfest is scheduled for the 6th-10th September.  It
should be a good opportunity to start discussing and working on
upstream kernel testing topics ahead of the Linux Plumbers
Conference[2].

Here's the project board where anyone can already add some ideas:

  https://github.com/orgs/kernelci/projects/5

There is no registration system, but please reply to this email or
send a message on IRC (#kernelci libera.chat) or kernelci.slack.com
if you would like to take part so you'll get email updates and
invitations to the meetings and open hours sessions online.  You
may just drop in and out at any point during the hackfest as you
see fit.

The hackfest features:

* Daily open hours online using Big Blue Button to discuss things
  and get support from the KernelCI team

* KernelCI team members available across most time zones to provide
  quick feedback

* A curated list of topics and a project board to help set
  objectives and coordinate efforts between all contributors


As always, KernelCI is at the service of the kernel community so
please share any feedback you may have to help shape this upcoming
hackfest in the best possible way.

Thanks,
Guillaume


[1] https://foundation.kernelci.org/blog/2021/06/24/the-first-ever-kernelci-hackfest/
[2] https://www.linuxplumbersconf.org/event/11/page/104-accepted-microconferences#cont-test

             reply	other threads:[~2021-08-02  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  9:00 Guillaume Tucker [this message]
2021-08-03 16:46 ` KernelCI Hackfest #2 - Sept 6-10 2021 Alice Ferrazzi
2021-09-02 20:24   ` Guillaume Tucker
     [not found] <169771B791E5E075.25031@groups.io>
2021-09-02 20:22 ` Guillaume Tucker

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=74f7b4cf-926f-d8bd-19c2-375cfe7a12b2@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jsbarnes@google.com \
    --cc=kernel@collabora.com \
    --cc=kernelci-members@groups.io \
    --cc=kernelci@groups.io \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=wangsummer@google.com \
    --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 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 NNTP newsgroup(s).