From: Matthew Wilcox <willy@infradead.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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: Fri, 23 Jun 2023 03:32:28 +0100 [thread overview]
Message-ID: <ZJUEPPSIRsOFNoWP@casper.infradead.org> (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:
> - The roles of maintainer and reviewer should be taught in universities at
> a post-graduate level to increase the talent pool.
Umm. I can't say that I know anyone who studied computer science at a
post-graduate level and then became a Linux maintainer. They probably
exist, but I'm not aware of them. In contrast, I can name two people
who started a PhD in another subject and then got lured into Linux
development, abandoning their PhD. I suspect most have a bachelors.
Some do not have a degree.
I don't think it's the role of a computer science department to do
this kind of teaching. It feels more practical. Now maybe it's part
of a software engineering curriculum, but then I don't think it's a
post-graduate topic.
It could also be something a professional society pushes. The British
Computer Society were really into that kind of thing twenty-five years
ago when they were trying to persuade me to join.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@infradead.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: tech-board-discuss@lists.linux-foundation.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Tech-board-discuss] [PATCH] Documentation: Linux Contribution Maturity Model and the wider community
Date: Fri, 23 Jun 2023 03:32:28 +0100 [thread overview]
Message-ID: <ZJUEPPSIRsOFNoWP@casper.infradead.org> (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:
> - The roles of maintainer and reviewer should be taught in universities at
> a post-graduate level to increase the talent pool.
Umm. I can't say that I know anyone who studied computer science at a
post-graduate level and then became a Linux maintainer. They probably
exist, but I'm not aware of them. In contrast, I can name two people
who started a PhD in another subject and then got lured into Linux
development, abandoning their PhD. I suspect most have a bachelors.
Some do not have a degree.
I don't think it's the role of a computer science department to do
this kind of teaching. It feels more practical. Now maybe it's part
of a software engineering curriculum, but then I don't think it's a
post-graduate topic.
It could also be something a professional society pushes. The British
Computer Society were really into that kind of thing twenty-five years
ago when they were trying to persuade me to join.
next prev parent reply other threads:[~2023-06-23 2:32 UTC|newest]
Thread overview: 54+ 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:41 ` [Tech-board-discuss] " Finn Thain
2023-06-19 9:55 ` Greg Kroah-Hartman
2023-06-19 9:55 ` [Tech-board-discuss] " Greg Kroah-Hartman
2023-06-20 3:48 ` Finn Thain
2023-06-20 3:48 ` [Tech-board-discuss] " Finn Thain
2023-06-20 13:00 ` James Bottomley
2023-06-20 13:00 ` [Tech-board-discuss] " James Bottomley
2023-06-19 11:32 ` James Bottomley
2023-06-19 11:32 ` [Tech-board-discuss] " James Bottomley
2023-06-20 3:50 ` Finn Thain
2023-06-20 3:50 ` [Tech-board-discuss] " Finn Thain
2023-06-20 22:52 ` James Bottomley
2023-06-20 22:52 ` James Bottomley
2023-06-19 19:42 ` Theodore Ts'o
2023-06-19 19:42 ` [Tech-board-discuss] " Theodore Ts'o
2023-06-20 3:54 ` Finn Thain
2023-06-20 3:54 ` [Tech-board-discuss] " Finn Thain
2023-06-20 21:25 ` Theodore Ts'o
2023-06-20 21:25 ` [Tech-board-discuss] " Theodore Ts'o
2023-06-21 1:51 ` Finn Thain
2023-06-21 1:51 ` [Tech-board-discuss] " Finn Thain
2023-06-21 12:41 ` Greg Kroah-Hartman
2023-06-21 12:41 ` [Tech-board-discuss] " Greg Kroah-Hartman
2023-06-22 7:02 ` Finn Thain
2023-06-22 7:02 ` [Tech-board-discuss] " Finn Thain
2023-06-22 7:10 ` Greg Kroah-Hartman
2023-06-22 7:10 ` [Tech-board-discuss] " Greg Kroah-Hartman
2023-06-22 7:24 ` Finn Thain
2023-06-22 7:24 ` [Tech-board-discuss] " Finn Thain
2023-06-22 17:39 ` Theodore Ts'o
2023-06-22 17:39 ` [Tech-board-discuss] " Theodore Ts'o
2023-06-23 0:52 ` Finn Thain
2023-06-23 0:52 ` [Tech-board-discuss] " Finn Thain
2023-06-23 1:45 ` Mark Brown
2023-06-23 1:45 ` Mark Brown
2023-06-21 14:08 ` Steven Rostedt
2023-06-21 14:08 ` Steven Rostedt
2023-06-21 22:48 ` Finn Thain
2023-06-21 22:48 ` Finn Thain
2023-07-01 1:46 ` Measurement, was " Finn Thain
2023-07-01 1:46 ` [Tech-board-discuss] Measurement, was " Finn Thain
2023-07-01 7:04 ` Greg Kroah-Hartman
2023-07-01 7:04 ` Greg Kroah-Hartman
2023-07-01 22:54 ` Finn Thain
2023-07-01 22:54 ` Finn Thain
2023-06-21 22:44 ` Finn Thain
2023-06-21 22:44 ` [Tech-board-discuss] " Finn Thain
2023-06-23 2:32 ` Matthew Wilcox [this message]
2023-06-23 2:32 ` Matthew Wilcox
2023-06-19 19:49 ` Kees Cook
2023-06-19 19:49 ` [Tech-board-discuss] " Kees Cook
2023-06-20 3:54 ` Finn Thain
2023-06-20 3:54 ` [Tech-board-discuss] " 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=ZJUEPPSIRsOFNoWP@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=fthain@linux-m68k.org \
--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 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.