From: Sasha Levin <sashal@kernel.org>
To: tech-board-discuss@lists.linux-foundation.org
Subject: [Tech-board-discuss] Nomination: Sasha Levin on the TAB
Date: Sun, 12 Nov 2023 22:26:03 -0500 [thread overview]
Message-ID: <ZVGXJOc4RldU6W7Q@sashalap> (raw)
Hi folks,
I'd like to nominate myself for another term serving on the Linux
Foundation Technical Advisory Board.
I try to focus on the area that is between the kernel community and end
users, whether it's individuals or companies. While helping out with
the -stable trees gives me visibility into more technical issues, being
able to serve on the tab allows me to help with broader issues related
to community and process.
Some of my current focus is on:
- How can we help our users use an up-to-date kernel: doing so has the
potential to both reduce maintainer toil by having less kernels to
maintain, as well as help our users take advantage of the Cambridge
Promise: we'll never break them on purpose. How do we successfully
turn the current too-long-term-supported kernel model into something
that is a win-win for our community and users?
- Hardware vulnerabilities are here to stay, how do we help our
community set a higher bar for fixes coming out of embargo?
- How can we play better with academic researchers? Some of the most
exciting developments in the kernel world are a result of academic
research (AUTOSEL for example), how do we play better with
researchers in a way that doesn't cause additional strain on
maintainers?
I would love to keep serving the kernel community on the TAB.
--
Thanks,
Sasha
reply other threads:[~2023-11-13 3:26 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=ZVGXJOc4RldU6W7Q@sashalap \
--to=sashal@kernel.org \
--cc=tech-board-discuss@lists.linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).