From: "Michael S. Tsirkin" <mst@redhat.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-doc@vger.kernel.org, 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: Thu, 15 Dec 2022 04:53:29 -0500 [thread overview]
Message-ID: <20221215044126-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221214185714.868374-1-tytso@mit.edu>
On Wed, Dec 14, 2022 at 01:57:14PM -0500, Theodore Ts'o wrote:
> + * The number of upstream kernel contributions by engineer, team, and
> + organization (e.g., all people reporting up to a manager, director,
> + or VP).
This is the only one that gave me pause. Seems eminently gameable by
trash variable-name-tweaking patches, unnecessary commit splitting etc.
I'm not going to name names but I'm seeing some of this as it is.
And if people decide to count patches posted as opposed to commits, oh
my ... I don't think we should make people focus on the number of
contributions as opposed to their quality, and incorrect incentives tend
to promote incorrect behaviour.
Fundamentally I presume companies will evaluate contributions based on
how important the given functionality is for the company, so
I'm not sure we need to get involved here. Maybe just add this at the
end:
+ The metrics can be measured by team or
+ organization (e.g., all people reporting up to a manager, director,
+ or VP).
Or simply drop this part.
Besides this:
Acked-by: Michael S. Tsirkin <mst@redhat.com>
--
MST
next prev parent reply other threads:[~2022-12-15 9:55 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 [this message]
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
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=20221215044126-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--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).