From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Finn Thain <fthain@linux-m68k.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: Wed, 21 Jun 2023 14:41:03 +0200 [thread overview]
Message-ID: <2023062144-hefty-why-305d@gregkh> (raw)
In-Reply-To: <5490402b-8b9f-f52d-3896-41090e639e51@linux-m68k.org>
On Wed, Jun 21, 2023 at 11:51:19AM +1000, Finn Thain wrote:
> > You appear to have a very different model of how non-profits might
> > approach the Linux kernel --- could you go into more detail about why
> > they might want to contribute to the Linux kernel, and how we might
> > encourage them to contribute more engineering effort?
> >
>
> Sure. Here's a recent example, in which a not-for-profit volunteer might
> have been granted an opportunity to work upstream:
> https://lore.kernel.org/all/129c9d5e-213a-80c9-092e-dc1dcf38ae3e@linux-m68k.org/
>
> The driver in question may may not be commercially viable, but that
> doesn't matter, if the intention is to foster new maintainers and increase
> the talent pool. And the problem ostensibly being addressed in the Linux
> Contributor Maturity Model is a shortage of maintainers.
I would NEVER recommend ANYONE picking up obsolete hardware and trying
to get it to work to maintain the driver if NO ONE is actually using the
stuff. That should not be for a not-for-profit to maintain as
obviously, no one uses it.
It's up to those that need/use the code to help maintain it, don't ask
not-for-profit groups to maintain and support code that no one uses,
that's a sure way to waste resources all around.
So that's a good example of how our ecosystem works properly, if no one
needs the code, it gets dropped. Don't ask for it to come back without
real users who are invested in it please.
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-21 12:41 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 [this message]
2023-06-22 7:02 ` Finn Thain
2023-06-22 7:10 ` Greg Kroah-Hartman
2023-06-22 7:24 ` Finn Thain
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=2023062144-hefty-why-305d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=fthain@linux-m68k.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).