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: <CAG72VMfSwMitWSyBYHF7a3DCJtc_awO4fw=rJkuvcxh-qeqqNQ@mail.gmail.com>
Date: Wed, 23 Oct 2024 12:50:16 +0300
From: Anna Antonenko <portasynthinca3@...il.com>
To: jeffbai@...c.io
Cc: aospan@...up.ru, conor.dooley@...rochip.com, ddrokosov@...rdevices.ru, 
	dmaengine@...r.kernel.org, dushistov@...l.ru, fancer.lancer@...il.com, 
	geert@...ux-m68k.org, gregkh@...uxfoundation.org, hoan@...amperecomputing.com, 
	ink@...assic.park.msu.ru, linux-alpha@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-fpga@...r.kernel.org, 
	linux-gpio@...r.kernel.org, linux-hwmon@...r.kernel.org, 
	linux-ide@...r.kernel.org, linux-iio@...r.kernel.org, 
	linux-media@...r.kernel.org, linux-mips@...r.kernel.org, 
	linux-renesas-soc@...r.kernel.org, linux-spi@...r.kernel.org, 
	manivannan.sadhasivam@...aro.org, Matt Turner <mattst88@...il.com>, 
	netdev@...r.kernel.org, nikita@...n.ru, ntb@...ts.linux.dev, 
	patches@...ts.linux.dev, richard.henderson@...aro.org, s.shtylyov@....ru, 
	serjk@...up.ru, shc_work@...l.ru, tsbogend@...ha.franken.de, 
	v.georgiev@...rotek.ru, wangyuli@...ontech.com, 
	wsa+renesas@...g-engineering.com, xeb@...l.ru
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various
 compliance requirements.

> > Although this commit has been merged, it's still important to know the
> > specific reason (or even an example) that triggered this change for
> > everyone here, right?
> >
> > And those maintainers who have been removed should be notified.
>
> Seconded
>
> <...omitted...>
>
> So I repeat - call the decision-makers out and ask for their
> explanation.

Seconded. I'm no Linux kernel developer, but as a user, I would still like
to know the reason behind a bunch of maintainers getting erased. I wouldn't
go as far as to claim that I sense malice, but there's definitely something
fishy. I would like a proper, public statement about what happened and why.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ