From: Jonathan Corbet <corbet@lwn.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pia Eichinger <pia.eichinger@st.oth-regensburg.de>,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
Wolfgang Mauerer <wolfgang.mauerer@oth-regensburg.de>
Subject: Re: Related work to MAINTAINERS truth and fiction
Date: Fri, 15 Jan 2021 09:52:46 -0700 [thread overview]
Message-ID: <20210115095246.653748af@lwn.net> (raw)
In-Reply-To: <CAKXUXMzj=LYJK74Le+rYnAaY3ji6AxugppwHwneAEL_xTTAyGw@mail.gmail.com>
On Fri, 15 Jan 2021 07:57:51 +0100
Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> Pia Eichinger has done some related analysis and work in this area as
> part of her bachelor's thesis on Maintainers Expectations vs.
> Maintainers Reality: An Analysis of Organisational and Maintenance
> Structure of the Linux Kernel. Simply quoting her conclusion:
>
> "We showed that around 20% of all patches were theoretically wrongly
> integrated when strictly analysing MAINTAINERS. The reality of
> integration and maintenance structure is more complicated than that,
> which we also explored. Furthermore, we identified 12 major subsystems
> of the Linux kernel. This is very helpful for an overview of the
> organisational structure, realistic grouping of subsystems and further
> Linux kernel topology discussions."
>
> Announcement and thesis here:
> https://lists.elisa.tech/g/devel/message/1269
> https://drive.google.com/file/d/12ta2YxgEzEfrIcmWid8kwIyVEywbUjbA/view?usp=sharing
Interesting, I was completely unaware of this work. I blame Wolfgang, who
should have pointed it out to me :)
Thanks,
jon
next prev parent reply other threads:[~2021-01-15 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 6:57 Related work to MAINTAINERS truth and fiction Lukas Bulwahn
2021-01-15 16:52 ` Jonathan Corbet [this message]
2021-01-15 17:35 ` [EXT] " Wolfgang Mauerer
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=20210115095246.653748af@lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pia.eichinger@st.oth-regensburg.de \
--cc=ralf.ramsauer@oth-regensburg.de \
--cc=wolfgang.mauerer@oth-regensburg.de \
/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