From: Finn Thain <fthain@linux-m68k.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>, Jonathan Corbet <corbet@lwn.net>,
tech-board-discuss@lists.linux-foundation.org,
Kees Cook <keescook@chromium.org>,
Dan Williams <dan.j.williams@intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Linux Contribution Maturity Model and the wider community
Date: Thu, 22 Jun 2023 17:24:03 +1000 (AEST) [thread overview]
Message-ID: <5243a27c-afcc-3b67-7481-5e4fb5620f67@linux-m68k.org> (raw)
In-Reply-To: <2023062245-engraver-antsy-005c@gregkh>
On Thu, 22 Jun 2023, Greg Kroah-Hartman wrote:
>
> > If there was consensus, it might be feasible to give a formula for
> > "recognized usage" which could be quantified. From there we could
> > create a kind of heat map to show which commits, maintainers,
> > processes, models, modules etc. were the most "useful" within some
> > time interval.
>
> Determining code use is difficult given that we are not going to add
> tracking to the kernel source for obvious reasons, so this is a
> non-starter, as you know.
>
It never crossed my mind that the kernel might "phone home". Counting
execution events (privately) doesn't work either because it seems
hopelessly skewed towards fast processors, clusters and fast paths.
Or am I missing something?
next prev parent reply other threads:[~2023-06-22 7:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:41 [PATCH] Documentation: Linux Contribution Maturity Model and the wider community Finn Thain
2023-06-19 9:55 ` Greg Kroah-Hartman
2023-06-20 3:48 ` Finn Thain
2023-06-20 13:00 ` James Bottomley
2023-06-19 11:32 ` James Bottomley
2023-06-20 3:50 ` Finn Thain
2023-06-20 22:52 ` [Tech-board-discuss] " James Bottomley
2023-06-19 19:42 ` Theodore Ts'o
2023-06-20 3:54 ` Finn Thain
2023-06-20 21:25 ` Theodore Ts'o
2023-06-21 1:51 ` Finn Thain
2023-06-21 12:41 ` Greg Kroah-Hartman
2023-06-22 7:02 ` Finn Thain
2023-06-22 7:10 ` Greg Kroah-Hartman
2023-06-22 7:24 ` Finn Thain [this message]
2023-06-22 17:39 ` Theodore Ts'o
2023-06-23 0:52 ` Finn Thain
2023-06-23 1:45 ` [Tech-board-discuss] " Mark Brown
2023-06-21 14:08 ` Steven Rostedt
2023-06-21 22:48 ` Finn Thain
2023-07-01 1:46 ` Measurement, was " Finn Thain
2023-07-01 7:04 ` [Tech-board-discuss] Measurement, was " Greg Kroah-Hartman
2023-07-01 22:54 ` Finn Thain
2023-06-21 22:44 ` Finn Thain
2023-06-23 2:32 ` Matthew Wilcox
2023-06-19 19:49 ` Kees Cook
2023-06-20 3:54 ` Finn Thain
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=5243a27c-afcc-3b67-7481-5e4fb5620f67@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linux-foundation.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).