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>] [day] [month] [year] [list]
Message-ID: <ZV37QCEB9zEk368g@archie.me>
Date:   Wed, 22 Nov 2023 19:59:44 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Martyn Welch <martyn.welch@...labora.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Staging Drivers <linux-staging@...ts.linux.dev>,
        Linux Kernel Janitors <kernel-janitors@...r.kernel.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Dan Carpenter <error27@...il.com>,
        Alison Schofield <alison.schofield@...el.com>,
        Bruno Moreira-Guedes <codeagain@...eagain.dev>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Jakub Kicinski <kuba@...nel.org>
Subject: Re: [PATCH 1/2] MAINTAINERS: Update Martyn Welch's address

On Wed, Nov 22, 2023 at 11:15:19AM +0000, Martyn Welch wrote:
> 
> On 22/11/2023 09:41, Bagas Sanjaya wrote:
> > He is now active on the mailing lists using his Collabora  >
> > (@collabora.com) address. Reflect it in MAINTAINERS and also add >
> address mapping for him.
> Hmm, mapping yes, changing the email assigned to the VME stuff, no. This is
> not something that I consider related to my work at Collabora. Any time
> spent on it at this point will be personal time, hence the use of my
> non-work email address.
> 
> Realistically, I've lost access to hardware to test anything regarding VME
> and it's not something that's particularly easy to acquire. With the other
> patch in this series removing Manohar, removing me as a maintainer would
> leave Greg, who has been amazing covering my shoddy maintenance of this
> subsystem (what can I say, life has rather got in the way), but I feel it's
> unfair to leave him as the sole maintainer. I wonder whether I/we should
> admit this is basically orphaned at this point?

I also feel similar thing when basically the subsystem gets more care from
kernel janitors (including outreachy applicants and people specializing
in checkpatch fixes) than real users, like the case of DECNET [1]. So
I'm agree to orphan VME.

Thanks.

[1]: https://lore.kernel.org/lkml/20220818004357.375695-1-stephen@networkplumber.org/

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ