linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Theodore Ts'o <tytso@mit.edu>, linux-doc@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, Kees Cook <keescook@chromium.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] Documentation/process: Add Linux Kernel Contribution Maturity Model
Date: Wed, 08 Feb 2023 13:31:36 -0700	[thread overview]
Message-ID: <87sfffucev.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221214185714.868374-1-tytso@mit.edu>

"Theodore Ts'o" <tytso@mit.edu> writes:

> As a follow-up to a discussion at the 2021 Maintainer's Summit on the
> topic of maintainer recruitment and retention, the TAB took on the
> task of creating a document which to help companies and other
> organizations to grow in their ability to engage with the Linux Kernel
> development community, using the Maturity Model[2] framework.
>
> The goal is to encourage, in a management-friendly way, companies to
> allow their engineers to contribute with the upstream Linux Kernel
> development community, so we can grow the "talent pipeline" for
> contributors to become respected leaders, and eventually kernel
> maintainers.
>
> [1] https://lwn.net/Articles/870581/
> [2] https://en.wikipedia.org/wiki/Maturity_model

So there were a few review comments on this document...  Ted, were you
planning a new revision or is it your feeling that it's ready to be
merged in this form?

Thanks,

jon

      parent reply	other threads:[~2023-02-08 20:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 18:57 [PATCH] Documentation/process: Add Linux Kernel Contribution Maturity Model Theodore Ts'o
2022-12-15  9:53 ` Michael S. Tsirkin
2022-12-15 15:14 ` Linus Walleij
2022-12-16  8:23   ` Bagas Sanjaya
2022-12-16  8:14 ` [PATCH] " Bagas Sanjaya
2022-12-16 14:34   ` Theodore Ts'o
2022-12-27 19:12 ` Florian Fainelli
2023-02-08 20:31 ` Jonathan Corbet [this message]

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=87sfffucev.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=brauner@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 NNTP newsgroup(s).