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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c3b8e4f-ac8f-1c79-387d-7b68b64ca645@linux-m68k.org>
Date:   Thu, 22 Jun 2023 08:48:12 +1000 (AEST)
From:   Finn Thain <fthain@...ux-m68k.org>
To:     Steven Rostedt <rostedt@...dmis.org>
cc:     Theodore Ts'o <tytso@....edu>, linux-doc@...r.kernel.org,
        tech-board-discuss@...ts.linux-foundation.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [Tech-board-discuss] [PATCH] Documentation: Linux Contribution
 Maturity Model and the wider community

On Wed, 21 Jun 2023, Steven Rostedt wrote:

> 
> > 
> >   Making the maintainer role more lucrative will provide a 
> >   disincentive for more automation (with or without level 5 
> >   performance reviews) unless remuneration is tied to metrics that 
> >   reflect maintainer effectiveness.
> 
> I'm not sure I totally understand your point above. I do not think that 
> making the maintainer role more lucrative provides a disincentive for 
> more automation. 

You're right -- it's a moot point (whether paying people more will reward 
underperformers) since it all depends on the performance metric. I was 
assuming a metric that reflects my own bias.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ