Ksummit-Discuss Archive on lore.kernel.org
 help / color / Atom feed
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
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 index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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

Ksummit-Discuss Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/ksummit-discuss/0 ksummit-discuss/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ksummit-discuss ksummit-discuss/ https://lore.kernel.org/ksummit-discuss \
		ksummit-discuss@lists.linuxfoundation.org
	public-inbox-index ksummit-discuss

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.linuxfoundation.lists.ksummit-discuss


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git