From: Guillaume Tucker <gtucker@gtucker.io>
To: "kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Cc: "kernelci-tsc@groups.io" <kernelci-tsc@groups.io>,
kernelci-members <kernelci-members@groups.io>
Subject: TSC update - 2024-02-08
Date: Fri, 9 Feb 2024 17:02:20 +0100 [thread overview]
Message-ID: <7e83f05e-3d99-446e-8364-15273124c414@gtucker.io> (raw)
Please find below a summary of yesterday's TSC monthly meeting:
*Paweł Wieczorek is joining the TSC*
Following Denys' proposal, the TSC voted yesterday in favour of
Paweł Wieczorek getting onboard. In spite of his relatively
recent direct contributions to KernelCI, he has been following
the project for a longer period of time and his on-going work on
LAVA as well as his Kubernetes experience will be very valuable
to the team. Congratulations Paweł and best of luck!
Note: I'm in the process of making a PR to update the docs
etc. so all the formalities and admin should come into effect
early next week.
*Rotating TSC representatives*
As we're still looking for a new TSC chair, we've agreed to opt
for the alternative solution offered by the Linux Foundation
Technical Charter[1] and have a TSC representative to attend
Advisory Board meetings and take part in votes on behalf of the
TSC instead of an elected Chair person. However, as there also
isn't anyone really available to do this continuously, we've
agreed to have a pool of representatives and rotate between them.
Call it musical TSC chairs if you wish... So far we have Nikolai
and Denys in the pool, in fact this is a nice way of bringing the
Board and TSC closer together so I would encourage all TSC
members to take part within practical limits - the timezone for
the biweekly meetings[2] isn't very APAC-friendly unfortunately.
The original timeline for the TSC Chair handover process was
meant to complete on 19th Feb so I shall stick to the plan and
step down on that date.
*groups.io owners*
The TSC also voted in favour to give full ownership to the
designated groups.io maintainers[3], namely Kevin, Gustavo and
Mark. While we're now using this regular kernel mailing list as
the main public discussion forum, groups.io is still needed for
private KernelCI topics among the TSC, Board, and working groups
such as Sysadmin and Web Dashboard. The
kernelci-members@groups.io address is also the one for potential
new project members to get in touch as advertised on
https://kernelci.org so it's very important to make sure there's
always someone available to respond. We've had suboptimal
moderation mechanisms in place recently, hopefully this will
help.
Please feel free to reply and ask for any additional information,
as always.
Best wishes,
Guillaume
[1] https://kernelci.org/docs/org/#technical-charter
[2] https://kernelci.org/docs/org/#advisory-board
[3] https://kernelci.org/docs/org/maintainers/#groupsio
reply other threads:[~2024-02-09 16:02 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=7e83f05e-3d99-446e-8364-15273124c414@gtucker.io \
--to=gtucker@gtucker.io \
--cc=kernelci-members@groups.io \
--cc=kernelci-tsc@groups.io \
--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).