linux-kernel - [PATCH 0/2] get_maintainer: report subsystem status separately from maintainer role

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250114-b4-get_maintainer-v1-0-ecf40f0d032d@suse.cz>
Date: Tue, 14 Jan 2025 09:57:53 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Joe Perches <joe@...ches.com>
Cc: workflows@...r.kernel.org, Theodore Ts'o <tytso@....edu>, 
 Bryan O'Donoghue <bryan.odonoghue@...aro.org>, 
 Thorsten Leemhuis <linux@...mhuis.info>, Kees Cook <kees@...nel.org>, 
 linux-kernel@...r.kernel.org, Vlastimil Babka <vbabka@...e.cz>
Subject: [PATCH 0/2] get_maintainer: report subsystem status separately
 from maintainer role

The script currently uses the subystem's status (S: field) to change how
maintainers are reported. One prominent example is when the status is
Supported, the maintainers are reported as "(supporter:SUBSYSTEM)".

I have been confused myself in the past seeing "supporter" and have seen
somebody recently wondering what it means as well.

I have read the threads from 2022 that in the end resulted in adjusting
documentation only [1]. I very much agree with Ted's points about taking
the subsystem status and applying it to all maintainers being wrong [2].

The attempt to modify get_maintainer output was retracted after Joe
objected that the status becomes not reported at all [3]. This series
addresses that by reporting the status (unless it's the most common
Maintained one) as part of the subsystem name.

Given this new approach, the next logical step is to do the same also
for reporting reviewers and mailing lists. In fact, subsystems with an
Orphan status some catch-all mailing list and no maintainers, so the
"(orphan minder:SUBSYSTEM)" would never be currently reported by
get_maintainer.  The second patch thus adds reporting the subsystem
status in the same way for lists (and reviewers).

Changes since RFC [4]
- keep the special handling for THE REST section ("chief penguin")
- added patch 2 for reviewers and mailing lists
- R-b on patch 1 from Kees

[1] https://lore.kernel.org/all/20221006162413.858527-1-bryan.odonoghue@linaro.org/
[2] https://lore.kernel.org/all/Yzen4X1Na0MKXHs9@mit.edu/
[3] https://lore.kernel.org/all/30776fe75061951777da8fa6618ae89bea7a8ce4.camel@perches.com/
[4] https://lore.kernel.org/all/20241213112921.180978-2-vbabka@suse.cz/

Signed-off-by: Vlastimil Babka <vbabka@...e.cz>
---
Vlastimil Babka (2):
      get_maintainer: decouple subsystem status from maintainer role
      get_maintainer: print subsystem status also for reviewers and lists

 scripts/get_maintainer.pl | 68 ++++++++++++++++++++++++++---------------------
 1 file changed, 38 insertions(+), 30 deletions(-)
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250114-b4-get_maintainer-cc3358be81c0

Best regards,
-- 
Vlastimil Babka <vbabka@...e.cz>