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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 23 Nov 2020 08:32:41 -0800
From:   Joe Perches <>
To:     James Bottomley <>,
        Miguel Ojeda <>
Cc:     Kees Cook <>,
        Jakub Kicinski <>,
        "Gustavo A. R. Silva" <>,
        linux-kernel <>,,,,,,,,,,,,,,,,,,,
        Linux ARM <>,,,,,,
        Linux Crypto Mailing List <>,,
        Ext4 Developers List <>,,,,,,,,,
        linux-input <>,,,
        Linux Media Mailing List <>,, Linux-MM <>,,,,,,,,,,,
        linux-wireless <>,
        Network Development <>,,,,,,,,,,,,,,,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <>,,,
        Nick Desaulniers <>,
        Nathan Chancellor <>,
        Miguel Ojeda <>
Subject: Re: [PATCH 000/141] Fix fall-through warnings for Clang

On Mon, 2020-11-23 at 07:58 -0800, James Bottomley wrote:
> We're also complaining about the inability to recruit maintainers:
> And burn out:

> What I'm actually trying to articulate is a way of measuring value of
> the patch vs cost ... it has nothing really to do with who foots the
> actual bill.

It's unclear how to measure value in consistency.

But one way that costs can be reduced is by automation and _not_
involving maintainers when the patch itself is provably correct.

> One thesis I'm actually starting to formulate is that this continual
> devaluing of maintainers is why we have so much difficulty keeping and
> recruiting them.

The linux kernel has something like 1500 different maintainers listed
in the MAINTAINERS file.  That's not a trivial number.

$ git grep '^M:' MAINTAINERS | sort | uniq -c | wc -l
$ git grep '^M:' MAINTAINERS| cut -f1 -d'<' | sort | uniq -c | wc -l

I think the question you are asking is about trust and how it
effects development.

And back to that wired story, the actual number of what you might
be considering to be maintainers is likely less than 10% of the
listed numbers above.

Powered by blists - more mailing lists