From: Sasha Levin <sashal@kernel.org>
To: tech-board-discuss@lists.linuxfoundation.org,
ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] TAB Nomination - Sasha Levin
Date: Sun, 8 Sep 2019 08:57:48 -0400 [thread overview]
Message-ID: <20190908125748.GE2012@sasha-vm> (raw)
While it is true that many eyeballs make all bugs shallow, we are short
on eyeballs. Our current development methodology doesn't work well when
we don't have enough developers reviewing the code: it takes longer for
code to be reviewed and merged upstream, it allows more bugs to sneak
into the upstream kernel, and even more bugs into stable kernels - which
our users rely on. The kernel sees continued growth year after year, and
extensive efforts are made to introduce "new blood", but I believe it is
not enough: the way forward is not only to get more eyeballs in the
game, but also to enable our existing eyeballs to be even more effective
and to allow them to focus on what matters most - the code.
If elected, I would work to promote and encourage LF projects and
initiatives that make our existing developers more effective:
- Better kernel infrastructure, such as the work being done on
lore.kernel.org or pgpkeys.git.
- Better testing infrastructure, such as the recently founded kernelci
project.
- New initiatives to reduce developer overhead, such as AUTOSEL or the
pull-tracker bot.
- Great conferences: LPC Is a great tool to help developers, but right
now it's at capacity and we need to find ways to address that.
In short, as a TAB member I would like to focus more on the day to day
work we all do, and work with the the Linux Foundation to make it a more
hospitable home for us - Linux Kernel developers.
About me: I maintain the stable/LTS kernel trees and liblockdep. I'm
currently employed by Microsoft where I maintain the internal kernel
tree for our various products, maintain the upstream Hyper-V subsystem,
support developers making the switch from Windows to Linux, and advise
on various technical topics not directly related to the kernel.
--
Thanks,
Sasha
reply other threads:[~2019-09-08 12:57 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=20190908125748.GE2012@sasha-vm \
--to=sashal@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tech-board-discuss@lists.linuxfoundation.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).