All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: tech-board-discuss@lists.linux-foundation.org
Subject: [Tech-board-discuss] Nomination: Ted Ts'o on TAB
Date: Tue, 14 Nov 2023 01:11:13 -0500	[thread overview]
Message-ID: <ZVMPgRAyGwQjgpvx@mit.edu> (raw)

Hi all,

[ Note: I know this is late; sorry, I thought until we had until 9am
  on the 14th.  My only excuse is that things have just been super
  busy, and I was doing last minute Maintainers Summit organization
  today.  :-( ]

My two year term on the TAB ends this year, and I'd like to put myself
forward for another two years.  In the past year, I was the primary
author of the Contribution Maturity Model[1].  The CMM was intended to
be a way to encourage companies to measure how much their support and
encouragement they are giving to their employees to conribute to the
upstream, on the theory that "you get what you measure".

[1] tech-board-discuss@lists.linux-foundation.org

The CMM also gradually encouraged companies to reward their employees
who took on community leadership roles, so we could ensure the
continued supply of people who could serve as kernel maintainers.
Given the fairly long thread on the ksummit discussion list about
maintainer burnout, it's become clear to me that in addition to
working with companies to try to address the supply of upstream
contributors who could become maintainers, that we also need to work
on the demand side of the equation.  We are asking individual
maintainers to do too much; and so we need to encourage a model where
more work can be sharded out and distributed to a wider base of
contributors.

I am interested in working on addressing these and other issues which
are critical to our long-term's community success, and I hope I can
return to the TAB to work on these goals.

                 reply	other threads:[~2023-11-14  6:11 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=ZVMPgRAyGwQjgpvx@mit.edu \
    --to=tytso@mit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.